Re: [Xen-API] [XCP 1.6 BETA] Upgrade to 1.6 switches network backend to Open vSwitch

[Brian Menges <bmenges@xxxxxxxxxx>]

I wouldn't say a bug either, but support of LACP should be included and 
accounted for. This will hurt my plans.

~Brian Menges
Sent from my Samsung Galaxy Nexus

Markus Schuster <ml@xxxxxxxxxxxxxxxxxxxx> wrote:


Hi,

one thing I discovered: When upgrading from XCP 1.5 (1.4.90) to 1.6 (61002c)
the network backend is automatically switched from bridge to Open vSwitch.
This is no bad idea in general, as Open vSwitch seems to work very well in
1.6, but if you configured an (unsupported) LACP bonding interface by
specifying some other-config settings for your storage bonding pif, you end
up with a storage bond that does not come up after the upgrade because Open
vSwitch doesn't like the options it gets passed in from the pifs other-
config settings.

I wouldn't rate this as bug (maybe the forced switch of the network backend
is?), as LACP was never supported in versions prior to 1.6, but a note in
the release notes would be good.

Regards,
Markus


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

The information contained in this message, and any attachments, may contain 
confidential and legally privileged material. It is solely for the use of the 
person or entity to which it is addressed.  Any review, retransmission, 
dissemination, or action taken in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you receive this 
in error, please contact the sender and delete the material from any computer.

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