[openstack-dev] [keystone]Liberty->Mitaka upgrade: is it possible without downtime?
gyorgy.szombathelyi at doclerholding.com
Thu Apr 14 14:09:11 UTC 2016
> > Unknown column 'user.name' in 'field list'
> > in some operation when the DB is already upgraded to Mitaka, but some
> > keystone instances in a HA setup are still Liberty.
> Currently we don't support rolling upgrades in keystone. To do an upgrade,
> you need to upgrade all keystone service instances at once, instead of going
> one-by-one, which means you have to plan for downtime of the keystone
Thanks, then I'll try to minimize the upgrade window as small as possible for keystone.
> > Is this change is intentional? Should I ignore the problem and just
> > upgrade all instances as fast as possible? Or I just overlooked something?
> You are right that there will be an error if you try running Liberty+Mitaka,
> since the database schema is not compatible. We have an ongoing effort to
> support online schema migrations, but it didn't make into Mitaka.  
> We will have a presentation about Online DB Migrations at the summit (in the
> upstream development track), so if you are interested, you can attend or
> watch the recorded session afterwards . There will also be a discussion
> about this in keystone meetings at the design summit. 
Great, hope the next version(s) will handle rolling upgrades.
>  https://specs.openstack.org/openstack/keystone-
>  https://review.openstack.org/#/c/274079/
>  https://www.openstack.org/summit/austin-2016/summit-
>  https://etherpad.openstack.org/p/keystone-newton-summit-brainstorm
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev