Open Stack

> On Mar 3, 2015, at 1:44 PM, Bob Ball <bob.ball at citrix.com> wrote:
> 
> We certainly care about this but converting the XenServer CI to Neutron+OVS has been hitting a number of issues (notably a few concurrency ones – although there are a few missing features) that we’ve been trying to sort through.
>  
> I am certainly hoping that we’ll have everything stable enough to set up a CI specifically for this combination before the Kilo release and would be very keen not to deprecate XenAPI support in Kilo.
> Certainly even if we don’t make the Kilo release for the CI we will still be pushing for it in L.
>  
> Bob

I guess that answers the question of whether anyone cares enough to work on enabling 3rd party CI, and that it may be premature to consider deprecation.  

Until CI is live, though, and in the absence of resources committed to fixing breakage when it is detected, I’m not sure it’s reasonable that core reviewers have to consider Xen support in determining whether a patch is ready to merge.  Given that, it’s entirely possible that we’ll end up shipping broken Xen support for kilo, especially given the changes coming to rootwrap and ovs interaction.  Should we as a community consider that acceptable with the hope that fixes will be proposed and backported in a timely-enough fashion?  Or maybe we should consider moving Xen support (which is centered on the ovs agent) out of the tree so that it can be maintained independent of the OpenStack release cycle? 


Maru

> From: Kevin Benton [mailto:blak111 at gmail.com] 
> Sent: 03 March 2015 21:06
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [neutron] The future of Xen + OVS support
>  
> It might make sense to send this to the users list as well. There may be a large deployment out there with resources willing to at least test changes even if they don't have any upstream development resources.
>  
> On Tue, Mar 3, 2015 at 12:50 PM, Maru Newby <marun at redhat.com> wrote:
> There have been a couple of patches [1] [2] proposed to neutron recently that could impact our support for Xen+OVS, but I don’t see an easy way for us to validate such changes.  I’m not aware of a 3rd party CI job that runs against Xen, and I don’t know of any active contributors able to manually validate changes.  Unless this changes, I think we should consider deprecating support for Xen in kilo.  We can’t afford to block changes for fear of breaking something that nobody seems to care about.
> 
> I’m hoping this post serves as a wake-up call to anyone that wants to see neutron maintain its support for Xen, and that they will be willing to devote resources to ensure that support for it continues.  I’ve also added this issue to next week’s irc meeting [3].
> 
> 
> Maru
> 
> 1: https://review.openstack.org/#/c/148969/
> 2: https://review.openstack.org/#/c/158805
> 3: https://wiki.openstack.org/wiki/Network/Meetings#On_Demand_Agenda
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
>  
> -- 
> Kevin Benton
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev