Open Stack

Yes, you need create new migration script. Btw, we already have started doing this.
The first example was when Jon added ‘neutron’ param to the ‘job_execution’ object:
https://review.openstack.org/#/c/63517/17/savanna/db/migration/alembic_migrations/versions/002_add_job_exec_extra.py

Regards,
Alexander Ignatov



On 30 Jan 2014, at 02:25, Andrew Lazarev <alazarev at mirantis.com> wrote:

> +1 on new migration script. Just to be consecutive.
> 
> Andrew.
> 
> 
> On Wed, Jan 29, 2014 at 2:17 PM, Trevor McKay <tmckay at redhat.com> wrote:
> Hi Sergey,
> 
>   In https://review.openstack.org/#/c/69982/1 we are moving the
> 'main_class' and 'java_opts' fields for a job execution into the
> job_configs['configs'] dictionary.  This means that 'main_class' and
> 'java_opts' don't need to be in the database anymore.
> 
>   These fields were just added in the initial version of the migration
> scripts.  The README says that migrations work "from icehouse". Since
> this is the initial script, does that mean we can just remove references
> to those fields from the db models and the script, or do we need a new
> migration script (002) to erase them?
> 
> Thanks,
> 
> Trevor
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140130/48ba183f/attachment.html>