> On 14 May 2016, at 5:36 AM, Flavio Percoco <fla...@redhat.com> wrote: > >> On 5/12/16 9:20 PM, Sam Morrison wrote: >> >> We find glance registry quite useful. Have a central glance-registry api >> is useful when you have multiple datacenters all with glance-apis and >> talking back to a central registry service. I guess they could all talk back >> to the central DB server but currently that would be over the public >> Internet for us. Not really an issue, we can work around it. >> >> The major thing that the registry has given us has been rolling upgrades. >> We have been able to upgrade our registry first then one by one upgrade our >> API servers (we have about 15 glance-apis) > > I'm curious to know how you did this upgrade, though. Did you shutdown your > registry nodes, upgraded the database and then re-started them? Did you > upgraded > one registry node at a time? > > I'm asking because, as far as I can tell, the strategy you used for upgrading > the registry nodes is the one you would use to upgrade the glance-api nodes > today. Shutting down all registry nodes would live you with unusable > glance-api > nodes anyway so I'd assume you did a partial upgrade or something similar to > that.
Yeah, if glance supported versioned objects then yes this would be great. We only have 3 glance-registries and so upgrading these first is a lot easier than upgrading all ~15 of our glance-apis at once. Sam __________________________________________________________________________ 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
