Difference between revisions of "Neutron/DatabaseMigration"
< Neutron
| Line 15: | Line 15: | ||
# Stop quantum services | # Stop quantum services | ||
# Quantum repo $git checkout <your feature branch> | # Quantum repo $git checkout <your feature branch> | ||
| − | # quantum-db-manage --config-file /etc/quantum/quantum.conf --config-file <plugin.ini> -m "Description" --autogenerate | + | # quantum-db-manage --config-file /etc/quantum/quantum.conf --config-file <plugin.ini> revision -m "Description" --autogenerate |
# Restart Quantum services (if needed) | # Restart Quantum services (if needed) | ||
[note] First 20 chars of "Description" is used as a part of a filename of a migration script. | [note] First 20 chars of "Description" is used as a part of a filename of a migration script. | ||
Revision as of 17:39, 22 January 2013
Quantum Database Migration
Now Quantum supports database migration from Quantum Folsom to Quantum Grizzly+. When a developer submits a patch to Quantum that changes the database model, a database migration script is required.
- Detail description : https://github.com/openstack/quantum/blob/master/quantum/db/migration/README
Howto
- Quantum repo $git checkout master
- Run devstack (with your plugin)
- quantum-db-manage --config-file /etc/quantum/quantum.conf --config-file <plugin.ini> stamp head
- Stop quantum services
- Quantum repo $git checkout <your feature branch>
- quantum-db-manage --config-file /etc/quantum/quantum.conf --config-file <plugin.ini> revision -m "Description" --autogenerate
- Restart Quantum services (if needed)
[note] First 20 chars of "Description" is used as a part of a filename of a migration script.
