Open Stack

On 9/5/2018 8:39 AM, Dan Smith wrote:
> Why not?

Because of the versions table as noted earlier. Up until this point no 
one had mentioned that but it would be an issue.

> 
> I think the safest/cleanest thing to do here is renumber placement-related
> migrations from 1, and provide a script or procedure to dump just the
> placement-related tables from the nova_api database to the new one (not
> including the sqlalchemy-migrate versions table).

I'm OK with squashing/trimming/resetting the version to 1. What was not 
mentioned earlier in this thread was (1) an acknowledgement that we'd 
need to drop the versions table to reset the version in the new database 
and (2) any ideas about providing scripts to help with the DB migration.

-- 

Thanks,

Matt