Re: [Xen-API] XCP 1.0rc2 - coexistence with XCP 0.5

[Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>]

You definitely can't have a pool of XCP 1.0 and XCP 0.5 hosts - all sorts of 
things will break. You've just got a bizarre error message as a result of the 
configuration not being supported.

You should definitely be able to upgrade a pool to 1.0 without VM downtime 
though - check out the docs for XenServer upgrade and follow the process 
described there. Essentially, you upgrade the master first, followed by each 
slave, migrating VMs between them. 

Jon

On 14 Feb 2011, at 18:56, George Shuklin wrote:

> Good day.
> 
> I'm starts testing and found first strange behavior: when I had tried to
> join xcp 1.0 host to xcp 0.5 pool I got:
> 
> 
> xe pool-join master-address=192.168.0.1 master-username=root
> master-password=guess --force
> You attempted an operation that was not allowed.
> reason: Network backends differ
> 
> I have scripts preparing networks on host before joining pool, they must
> be identical. I check manually - network list, name and their
> description match exactly.
> 
> /etc/xensource/network.conf on 0.5 and 1.0 is the same: openvswitch.
> 
> This means XCP 1.0 and 0.5 will not able to coexists? Or this is a bug?
> 
> Next question is possibility to migrate pool from 0.5 to 1.0 without VM
> shutdown...
> 
> 
> _______________________________________________
> 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