 Home |
Products |
Support |
Community |
News |
xen-api
[Xen-API] XCP 1.0rc2 - coexistence with XCP 0.5
| To: | xen-api@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-API] XCP 1.0rc2 - coexistence with XCP 0.5 |
| From: | George Shuklin <george.shuklin@xxxxxxxxx> |
| Date: | Mon, 14 Feb 2011 21:56:30 +0300 |
| Delivery-date: | Mon, 14 Feb 2011 10:56:52 -0800 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; bh=soNt7fTtqRJacQJiHQxpw6dTbmBFkcsWPUuhjHLWFCE=; b=aqUvh0S7LOlHRfjoINXydotax+h+RahFbG741ZDyVw3Wv/hEb0ZzgiVSF2wATTGPi7 c/QH9d0OxqFl15bQt/ucueJyW9f5z6wi4a761G7go76gAhfxLdH0TlMIuGSy0GkwRgQf J+FB/E6XU8qDnjNh7rSf56iSXBom2eA/Ep+Mk= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=QJC4gb5L94MIPnVgpsPI2VL3W2MQccUBHx8/t3iiPtgR9tXruJJgWELvgIRjwPpRY1 gTYDdoxSYGO6M1F6I47GZVl3nYKw9sObHunuuszWt9ikg9UeX3kJ0FH5sxU1y+a8WuEL XHqGlJsAp4348zUA5oUX7T36Ga9c4JJRs6Uc0= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-api-request@lists.xensource.com?subject=help> |
| List-id: | Discussion of API issues surrounding Xen <xen-api.lists.xensource.com> |
| List-post: | <mailto:xen-api@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-api-bounces@xxxxxxxxxxxxxxxxxxx |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [Xen-API] Release date for XCP 1.0 stable, Jonathan Ludlam |
|---|---|
| Next by Date: | Re: [Xen-API] Release date for XCP 1.0 stable, Chris Percol |
| Previous by Thread: | [Xen-API] Re: [Xen-devel] About OpenNebula and XCP integration Pt2, Tim Deegan |
| Next by Thread: | Re: [Xen-API] XCP 1.0rc2 - coexistence with XCP 0.5, Jonathan Ludlam |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
