Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

ck-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable Hi folks, It was never really discussed if we would back-port upgrades to liberty. This came up during an irc conversation Friday [1],

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

stack-dev@lists.openstack.org> Sent: Tuesday, March 8, 2016 1:15:10 PM Subject: Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable Exceptions can always be rationalized which is one reason exceptions are evil among many. The facts however speak for th

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

8:03 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable Hi folks, It was never re

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On Mon, Mar 7, 2016 at 11:00 AM, Sam Yaple wrote: > > Obviously I am +1 on committing to a stable _stable_ branch. And that has > always required Z upgrades. Luckily the work we did in master is also usable > for z upgrades. Without the ability to perform an update after a >

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On 03/07/2016 05:22 PM, Michał Jastrzębski wrote: Upgrades are required, true, but not necessarily automatic ones. People still can rebuild and redeploy containers using normal deploy. It will be downtime causing and less optimal, but possible. Also with backport of named volumes it won't be

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On Tue, Mar 8, 2016 at 2:41 AM, Steven Dake (stdake) wrote: > > > On 3/7/16, 10:16 AM, "Paul Bourke" wrote: > > >This is a messy topic. I feel there's been some miscommunication and > >confusion on the issue which hopefully I can sum up. > > > >As far

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On 3/7/16, 10:16 AM, "Paul Bourke" wrote: >This is a messy topic. I feel there's been some miscommunication and >confusion on the issue which hopefully I can sum up. > >As far as I remember it, Sam is correct, we did always plan to do >Liberty upgrades. However, over

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

This is a messy topic. I feel there's been some miscommunication and confusion on the issue which hopefully I can sum up. As far as I remember it, Sam is correct, we did always plan to do Liberty upgrades. However, over the course of time post Tokyo these plans didn't really materialise, at

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Upgrades are required, true, but not necessarily automatic ones. People still can rebuild and redeploy containers using normal deploy. It will be downtime causing and less optimal, but possible. Also with backport of named volumes it won't be data-destroying. It will cause total downtime of APIs,

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On Mon, Mar 7, 2016 at 3:03 PM, Steven Dake (stdake) wrote: > Hi folks, > > It was never really discussed if we would back-port upgrades to liberty. > This came up during an irc conversation Friday [1], and a vote was > requested. Tthe facts of the discussion distilled are: >

[openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Hi folks, It was never really discussed if we would back-port upgrades to liberty. This came up during an irc conversation Friday [1], and a vote was requested. Tthe facts of the discussion distilled are: * We never agreed as a group to do back-port of upgrade during our back-port