From: Mike McClurg <mike.mcclurg-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
To: "Sébastien Riccio" <sr-dWg6jWm8wxMIjDr1QQGPvw@public.gmane.org>
Cc: "xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
Jonathan Ludlam
<Jonathan.Ludlam-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org>,
"xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>
Subject: Re: [Xen-devel] XAPI on debian and openxenmanager
Date: Mon, 22 Aug 2011 19:31:26 +0100 [thread overview]
Message-ID: <4E52A07E.7090904@citrix.com> (raw)
In-Reply-To: <4E529D2B.4010805-dWg6jWm8wxMIjDr1QQGPvw@public.gmane.org>
(Moving this discussion to the xen-api list...)
On 22/08/11 19:17, Sébastien Riccio wrote:
> Hi again,
>
> actually I might have answered the question myself as it seems my
> openxenmanager do the same on
> some others xenserver 5.6 hosts. That brings me another question, should
> Citrix XenCenter works
> with xapi on debian ? :)
>
Now that's a totally different question ;) I think that the same issues
that impact XenCenter working with XCP will impact xapi on Debian as
well. I haven't even tried to get XenCenter working with my test box.
Having said that, I have gotten OpenXenManager to connect to my xapi on
Debian box. I had to patch OXM a bit to keep it from throwing an
exception (see here:
http://sourceforge.net/tracker/?func=detail&aid=3393870&group_id=327385&atid=1374139),
but it got through the synchronization phase just fine.
We definitely plan to have xapi on Debian work well with OXM, and I'll
be working with the OXM maintainer to be sure it works well with xapi on
Debian.
Mike
prev parent reply other threads:[~2011-08-22 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 18:11 XAPI on debian and openxenmanager Sébastien Riccio
2011-08-22 18:17 ` Sébastien Riccio
[not found] ` <4E529D2B.4010805-dWg6jWm8wxMIjDr1QQGPvw@public.gmane.org>
2011-08-22 18:31 ` Mike McClurg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E52A07E.7090904@citrix.com \
--to=mike.mcclurg-sxgqhf6nn4dqt0dzr+alfa@public.gmane.org \
--cc=Jonathan.Ludlam-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org \
--cc=sr-dWg6jWm8wxMIjDr1QQGPvw@public.gmane.org \
--cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).