| |
|
 |
|
 |
|
|
|
| |
|
|
xen-api
RE: [Xen-API] Compatibility Xen-API XenServer and XCP
Hi,
The only plans we have atm are to minimize (over time) divergence between the
two trees by slowly reducing the size of our XCP-specific patchqueues.
In the future it may be possible to share more of the low-level code through
libxenlight or similar.
As a general principle I think people should be able to 'plumb through' new
low-level experimental features by only touching the low-level bits of the
code. Once experimental features have been experimented with enough and have
become understood, we would then be better able to figure out how best to
expose them at the Pool-level.
For example, in the xapi world we've put some effort into pushing more of the
domain-configuration steps into the C code which calls the domain builder. You
can do stuff like:
# xe vm-param-set uuid=<uuid> platform:myflag=true
And then modify:
http://xenbits.xen.org/xapi/xen-api.hg?file/3e8c0167940d/ocaml/xenguest/xenguest_stubs.c
(look for 'xenstore_get') to read 'myflag' and act upon it. No ocaml (or
python) code needs to be modified for these simple cases. We're keen to further
isolate our low-level domain management stuff with a view to splitting it off
and making the interface explicit. The domain management piece could then even
be replaced (if that was desirable)
I think the future of xend is really up to the people who maintain it. I can
only speak for the xapi people :)
Cheers,
Dave
-----Original Message-----
From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Joshua West
Sent: 12 November 2009 20:05
To: Dave Scott
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] Compatibility Xen-API XenServer and XCP
Hi Dave,
Question for you regarding xend vs XCP... Will we see XCP's equivalent
of xend merged into the main xen tree? Thus fully replacing xend and
its Xen API ... adios Python, hello OCAML?
Thanks.
Dave Scott wrote:
> Hi,
>
> The xapi toolstack (ie the part which exposes the xenapi) in the current XCP
> is the basically the same as in XenServer. The only differences are:
> 1. the code in XCP is the live, development version (not a final polished
> release)
> 2. the version numbers are different (XCP 0.1 vs XenServer ...)
> 3. in XCP all features are enabled by default (in XenServer some are disabled
> by default)
>
> Future XenServer releases will be based on top of the open-source XCP stuff.
>
> Hopefully your client will continue to work on the XCP xapi. If you encounter
> any problems, please report them and we'll take a look.
>
> Cheers,
> Dave
>
> -----Original Message-----
> From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Marco Sinhoreli
> Sent: 12 November 2009 17:06
> To: xen-api@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-API] Compatibility Xen-API XenServer and XCP
>
> Hi folks,
>
> I have an application write using the xenapi for Citrix XenServer (all
> hosts are too Citrix XenServer) and I'm thinking in migrate the hosts
> to use XCP. This application is integrated with others internals API
> like switches/balancers, monitoring API (nagios), deployment API, etc.
> I will need to change something in code soruce of my application to
> this migration?
>
> Regards,
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api
>
--
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
|
|
|
| |
|
Home