On Tue, May 26, 2015 at 10:31:57AM -0400, Russell Bryant wrote: > On 05/21/2015 10:23 PM, Andy Hill wrote: > >> As a consequence, this requires dropping support for old versions of > >> XenServer. I don't expect that to be much of a problem. > > > > Unfortunately, the most recent release of XenServer (6.5) still ships > > with Python 2.4. > > > >> +Open vSwitch requires a version of XenServer (XCP) that includes a > >> +modern version of Python (2.7 or later). This excludes older releases > >> +based on Centos, which have Python 2.4. > > > > XCP seems looks EOL on after XenServer was open sourced.[1] > > > > Can we defer this until a later Open vSwitch release? Maybe the next LTS? > > > > [1] > > http://www.xenproject.org/component/content/article/100-misc/148-xcp-and-xenserver-faq.html > > - See "I am a user of XCP: how am I impacted?" > > This is going to get more and more painful. We may just have to fork > this library for OpenStack for now so we can carry a patch set to > support Python 3. It's a last resort, but we can't really wait if we > want to use this in OpenStack.
What if we apply these to the ovn branch, and then plan to merge ovn into master only after OVS 2.4 is released? I'm not sure whether OVS 2.4 will be LTS; we haven't discussed it. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
