Re: [Xen-API] [XCP 1.6 BETA] Joining a XCP 1.1 pool with a XCP 1.6 host

[John Else <john.else@xxxxxxxxxx>]

> -----Original Message-----
> From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx] On 
> Behalf Of Sébastien RICCIO
> Sent: 26 October 2012 13:17
> To: xen-api@xxxxxxxxxxxxx
> Subject: [Xen-API] [XCP 1.6 BETA] Joining a XCP 1.1 pool with a XCP 1.6 host
>
> Hi,
>
> Just would like to know if it would be theoritically possible to join a XCP 
> 1.1 pool with a XCP 1.6 freshly installed host. Are they compatible ?
>
> I tried to join it but the debug returns this:
>
>   [debug|xen-blade07|66 UNIX /var/xapi/xapi|pool.join_force 
> R:acadaaa60e2d|xapi] master PLATFORM_VERSION = Unknown, master compatibility 
> name = XCP; my PLATFORM_VERSION = 1.6.06, my compatibility name = XCP;
>
>
> this seems to match
>
> master compatibility name = XCP
> my compatibility name = XCP
>
> master PLATFORM_VERSION = Unknown <-- seems it can't get the version from the 
> 1.1 pool my PLATFORM_VERSION = 1.6.06
>
> If it was able to get the platform version, should it work ?
>
> Cheers,
> Sébastien

Hi Sébastien,

It's not possible to join XCP hosts of different versions into a pool - the 
only time XCP hosts of different versions should be in a pool together is 
during a rolling pool upgrade.

As for the reason you're seeing PLATFORM_VERSION = Unknown ...

PLATFORM_VERSION isn't actually defined in XCP 1.1 - it's a new field, added in 
XCP 1.5 I believe. The intention is that PLATFORM_VERSION is shared between the 
equivalent versions of XCP and XenServer (and is used for checks during pool 
join, rolling pool upgrade etc.). Older versions of XCP will have 
PRODUCT_VERSION defined (e.g XCP 1.1 has PRODUCT_VERSION = 1.1) but from XCP 
1.6 onwards PRODUCT_VERSION is not defined - it's now treated as a "cosmetic" 
field which is only defined in commercial XenServer.

This is all part of Project Swizzle which has been mentioned on this list now 
and then - the intention being that our build system will produce XCP and 
XenServer ISOs simultaneously, rather than the current situation where 
XenServer needs quite a bit of hacking before it can be turned into XCP.

John

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api