diff options
author | Devananda van der Veen <devananda.vdv@gmail.com> | 2013-02-19 12:39:55 -0800 |
---|---|---|
committer | Devananda van der Veen <devananda.vdv@gmail.com> | 2013-02-20 09:55:02 -0800 |
commit | c20110d15be37948ddd9ef5f38001328aabf5b1d (patch) | |
tree | 23f6b175cd96d4e2f89aa844010f119859491ecd /nova/context.py | |
parent | 666cb4eaf70c9f2f8dd05ba0df91f0e7dd6810cb (diff) | |
download | nova-c20110d15be37948ddd9ef5f38001328aabf5b1d.tar.gz nova-c20110d15be37948ddd9ef5f38001328aabf5b1d.tar.xz nova-c20110d15be37948ddd9ef5f38001328aabf5b1d.zip |
Add better status to baremetal deployments.
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
Diffstat (limited to 'nova/context.py')
0 files changed, 0 insertions, 0 deletions