[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: xen-api@xxxxxxxxxxxxx
  • From: Lars Kurth <lars.kurth@xxxxxxx>
  • Date: Thu, 25 Oct 2012 11:01:07 +0100
  • Delivery-date: Thu, 25 Oct 2012 10:01:28 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

I added it to the "Installation and Upgrade" section of the release notes at http://xen.org/download/xcp/releasenotes_1.6.0.html
Thank you

On 24/10/2012 13:00, Markus Schuster wrote:
Hi Lars!

  > but a note in  the release notes would be good.
If somebody can help me put together a short description of what should
be in the release notes, what the work-around is, etc. and I will add it
to the release notes
Well, I don't have a real work-around as I only used some test environment,
but maybe something like:

--- cut ---
Linux bridging users please note: During the upgrade to XCP 1.6 the network
backend will be switched to Open vSwitch. Please revert any custom settings
to your network interfaces (eg. other-config settings for pifs) or ensure
(before the upgrade) your settings will work with Open vSwitch.
Should you use an unsupported bondig mode (like LACP), it might be an option
to delete that bond before the upgrade and recreate it afterwards.
--- cut ---

Probably not perfect, but should describe the pitfal.


Xen-api mailing list

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.