This patch introduces a few new baremetal states, which are used to track the deploy process. Now, nova-baremetal-deploy-helper updates the bm_nodes record directly when it begins and finishes deploying an image to that node. The next patch will add a LoopingCall inside driver.spawn() to wait for the deploy to complete. Also, since there can not be >1 active deployment per node, there is no need to have a separate table for storing them. This patch drops the table bm_deployments and adds the important information it contained to bm_nodes. Since the previous behavior was to mark a deployment as deleted once it completed, there is no need to copy any data from bm_deployments prior to dropping the table -- assuming that no active deployments are in process when the migration is run. Since this is the first migration for the baremetal database, it also adds a new test class, TestBaremetalMigrations, and refactors the test_migrations.py file to allow for multiple test classes. partially implements fix for bug 1096723 Change-Id: Iad30b462d49c88fc19babed43a2fb8540b1fad30
10 lines
317 B
Plaintext
10 lines
317 B
Plaintext
[DEFAULT]
|
|
# Set up any number of migration data stores you want, one
|
|
# The "name" used in the test is the config variable key.
|
|
#sqlite=sqlite:///test_migrations.db
|
|
sqlite=sqlite://
|
|
#mysql=mysql://root:@localhost/test_migrations
|
|
#postgresql=postgresql://user:pass@localhost/test_migrations
|
|
[walk_style]
|
|
snake_walk=yes
|