Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-07 Thread Kevin Benton
Oh, I suppose it depends on what you mean by "ovs" in this context. The Neutron OVS agent shouldn't trigger any flow losses, but restarted the OVS vswitchd process may do that. On Sat, Oct 7, 2017 at 2:31 AM, Sean Dague wrote: > On 10/06/2017 07:23 PM, Kevin Benton wrote: > >>

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-07 Thread Sean Dague
On 10/06/2017 07:23 PM, Kevin Benton wrote: >The neutron story is mixed on accessable upgrade, because at least in some cases, like ovs, upgrade might trigger a network tear down / rebuild that generates an outage (though typically a pretty small one). This shouldn't happen. If it does it

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-06 Thread Kevin Benton
>The neutron story is mixed on accessable upgrade, because at least in some cases, like ovs, upgrade might trigger a network tear down / rebuild that generates an outage (though typically a pretty small one). This shouldn't happen. If it does it should be reported as a bug. All existing OVS flows

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-05 Thread Thierry Carrez
Sean Dague wrote: > [...] > I still think it's hard to describe to folks what is going on without > pictures. And the tag structure might just be the wrong way to describe > the world, because they are a set of positive assertions, and upgrade > expectations are really about: "how terrible will

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-05 Thread Thierry Carrez
Graham Hayes wrote: > On Thu, 5 Oct 2017, at 09:50, Thierry Carrez wrote: >> [...] >> In particular, we created two paths in the graph: >> * upgrade < accessible-upgrade >> * upgrade < rolling-upgrade < zero-downtime < zero-impact >> >> I personally would get rid of zero-impact (not sure there is

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-05 Thread Sean Dague
On 10/05/2017 07:08 AM, Graham Hayes wrote: > > > On Thu, 5 Oct 2017, at 09:50, Thierry Carrez wrote: >> Matt Riedemann wrote: >>> What's the difference between this tag and the zero-impact-upgrades tag? >>> I guess the accessible one is, can a user still ssh into their VM while >>> the nova

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-05 Thread Graham Hayes
On Thu, 5 Oct 2017, at 09:50, Thierry Carrez wrote: > Matt Riedemann wrote: > > What's the difference between this tag and the zero-impact-upgrades tag? > > I guess the accessible one is, can a user still ssh into their VM while > > the nova compute service is being upgraded. The

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-05 Thread Thierry Carrez
Matt Riedemann wrote: > What's the difference between this tag and the zero-impact-upgrades tag? > I guess the accessible one is, can a user still ssh into their VM while > the nova compute service is being upgraded. The zero-impact-upgrade one > is more to do with performance degradation during

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-04 Thread Jimmy McArthur
Matt Riedemann October 4, 2017 at 10:51 AM What's the difference between this tag and the zero-impact-upgrades tag? I guess the accessible one is, can a user still ssh into their VM while the nova compute service is being upgraded. The zero-impact-upgrade one

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-04 Thread Matt Riedemann
On 10/3/2017 1:52 PM, Sean McGinnis wrote: I'm hoping this will get a little more attention. We recently started discussing removing governance tags that did not have any projects asserting them. I think this makes a lot of sense. Some tags were defined apparently in the hope that it would get

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-04 Thread Sean McGinnis
On Wed, Oct 04, 2017 at 02:07:53PM +0100, Jean-Philippe Evrard wrote: > > - I don't see any mention of documentation in the required steps to > get this governance tag. > I think it can serve the community better if we enforce the > inclusion of the documentation on > 'HOW to trigger this

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-04 Thread Jean-Philippe Evrard
On Tue, Oct 3, 2017 at 7:52 PM, Sean McGinnis wrote: > I'm hoping this will get a little more attention. > > We recently started discussing removing governance tags that did not have any > projects asserting them. I think this makes a lot of sense. Some tags were > defined

[openstack-dev] [ptl][tc] Accessible upgrade support

2017-10-03 Thread Sean McGinnis
I'm hoping this will get a little more attention. We recently started discussing removing governance tags that did not have any projects asserting them. I think this makes a lot of sense. Some tags were defined apparently in the hope that it would get projects thinking about them and wanting to