Open Stack

These steps seem reasonable, and will help Operators. Thanks for going
through this!


- jlk

On Wed, Dec 2, 2015 at 12:06 PM, Lance Bragstad <lbragstad at gmail.com> wrote:

> Hey all,
>
> I wanted to send out a follow up on this. Yesterday in the keystone
> meeting we voted on Mitaka specs that we would like to commit to. The
> online-migration spec was accepted as something we would definitely like to
> see [0]. On the other hand, the development team doesn't really have enough
> insight into the online-migration process to effectively move forward. We
> want to shy away from over-architecting a migration solution that will
> inevitably cause issues and confusion. The conversation started as we
> compared using the expand/contract model versus stretching migrations over
> several releases, all of which was had in IRC [1].
>
> As a baby step, we came up with the following plan.
>
> Merge a unit test into keystone that detects certain offline migration
> operations. In order to pass the test, an exception has to be added to the
> test case and formal release notes must be proposed with the schema change.
> The release notes must explicitly detail the schema change, why it is
> changing, how to migrate data if any, what variables downtime would depend
> on, and any other useful bits an operator should know.
>
> We're hoping that this type of process change makes it easier for
> operators to plan migration changes, and schedule downtime if necessary.
> This wouldn't guarantee online-migrations for keystone, but it's a step
> forward as we gather more feedback from operators.
>
> Thoughts?
>
> [0]
> http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2015-12-01.log.html#t2015-12-01T18:41:52
> [1]
> http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2015-12-02.log.html#t2015-12-02T15:00:43
>
> On Fri, Nov 27, 2015 at 3:52 AM, Jesse Pretorius <
> jesse.pretorius at gmail.com> wrote:
>
>> Hi everyone,
>>
>> As we all know, upgrades are hard. Part of the problem relates to down
>> time due to offline database migrations.
>>
>> The Keystone team has put together a spec [1] and is seeking feedback for
>> implementing online schema migrations.
>>
>> Please weigh in, as operators, on the spec presented.
>>
>> [1] https://review.openstack.org/245186
>>
>> --
>> Jesse Pretorius
>> IRC: odyssey4me
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151203/05cdd01c/attachment.html>