Re: [openstack-dev] [tripleo] Rocky Ceph update/upgrade regression risk (semi-FFE)
On Fri, Jul 27, 2018 at 5:48 AM, Emilien Macchi wrote: > > > On Fri, Jul 27, 2018 at 3:58 AM Jiří Stránský wrote: >> >> I'd call this a semi-FFE, as a few of the patches have characteristics of >> feature work, >> but at the same time i don't believe we can afford having Ceph >> unupgradable in Rocky, so it has characteristics of a regression bug >> too. I reported a bug [2] and tagged the patches in case we end up >> having to do backports. > > > Right, let's consider it as a bug and not a feature. Also, it's upgrade > related so it's top-priority as we did in prior cycles. Therefore I think > it's fine. I second this. We must be able to upgrade so this needs to be addressed. > -- > Emilien Macchi > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] Rocky Ceph update/upgrade regression risk (semi-FFE)
On Fri, Jul 27, 2018 at 3:58 AM Jiří Stránský wrote: > I'd call this a semi-FFE, as a few of the patches have characteristics of > feature work, > but at the same time i don't believe we can afford having Ceph > unupgradable in Rocky, so it has characteristics of a regression bug > too. I reported a bug [2] and tagged the patches in case we end up > having to do backports. > Right, let's consider it as a bug and not a feature. Also, it's upgrade related so it's top-priority as we did in prior cycles. Therefore I think it's fine. -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tripleo] Rocky Ceph update/upgrade regression risk (semi-FFE)
Hi folks, i want to raise attention on remaining patches that are needed to prevent losing Ceph updates/upgrades in Rocky [1], basically making the Ceph upgrade mechanism compatible with config-download. I'd call this a semi-FFE, as a few of the patches have characteristics of feature work, but at the same time i don't believe we can afford having Ceph unupgradable in Rocky, so it has characteristics of a regression bug too. I reported a bug [2] and tagged the patches in case we end up having to do backports. Please help with reviews and landing the patches if possible. It would have been better to focus on this earlier in the cycle, but majority of Upgrades squad work is exactly this kind of semi-FFE -- nontrivial in terms of effort required, but at the same time it's not something we can realistically slip into the next release, because it would be a regression. This sort of work tends to steal some of our focus in N cycle and direct it towards N-1 release (or even older). However, i think we've been gradually catching up with the release cycle lately, and increased focus on keeping update/upgrade CI green helps us catch breakages before they land and saves some person-hours, so i'm hoping the future is bright(er) on this. Thanks and have a good day, Jirka [1] https://review.openstack.org/#/q/topic:external-update-upgrade [2] https://bugs.launchpad.net/tripleo/+bug/1783949 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
