Re: [Openstack] Handling Schema Changes in Keystone

2011-11-04 Thread Dolph Mathews
Sawalha ziad.sawa...@rackspace.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Handling Schema Changes in Keystone There is a BP out for how to handle continuious delivery and db upgrades within Nova. It does address some of the issues that keystone

Re: [Openstack] Handling Schema Changes in Keystone

2011-11-04 Thread Dolph Mathews
brian.sch...@nimbisservices.com, Ziad Sawalha ziad.sawa...@rackspace.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Handling Schema Changes in Keystone There is a BP out for how to handle continuious delivery and db upgrades within Nova. It does

Re: [Openstack] Handling Schema Changes in Keystone

2011-10-28 Thread Ziad Sawalha
@lists.launchpad.net Subject: Re: [Openstack] Handling Schema Changes in Keystone It's probably the best approach that doesn't depend on the Django ORM (like South). Does anyone use the experimental command line migrate to generate the migrate script? I always did it by hand. http

Re: [Openstack] Handling Schema Changes in Keystone

2011-10-25 Thread Jesse Andrews
I don't think the debate is whether to do migrations or not. I think the debate should be: Is there more value in not doing it the same way another openstack project does it? If you can use nova's method, then we get closer to having standard operating procedures for openstack projects... On