On 14 December 2017 at 17:36, Clint Byrum <cl...@fewbar.com> wrote: > The batch size for "upgrade the whole cloud" is too big. Let's help our > users advance components one at a time, and then we won't have to worry > so much about doing the whole integrated release dance so often.
Is there any data about how operators approach this currently? Nectar (and I presume other large and/or loosely coordinated OpenStack clouds) has been running different projects across multiple versions for quite a while, sometimes 3 or 4 different versions. Coordinating upgrades in a federated cloud with distributed operations requires that we do this, e.g., our current Nova Newton upgrade has probably been in-train for a couple of months now. -- Cheers, ~Blairo __________________________________________________________________________ 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
