A recent patch moved the flavor management out of nova-manage
and into python-novaclient. This corrects the behaviour of lib/baremetal
so that it calls "nova flavor-key" instead of "nova-manage". This also
fixes a logical error in testing whether dnsmasq is installed.
Change-Id: I3fa821c22ae45a49e283d091b6e5ed51c9757e88
| ... | ... |
@@ -211,9 +211,7 @@ function configure_baremetal_nova_dirs() {
|
| 211 | 211 |
|
| 212 | 212 |
# ensure dnsmasq is installed but not running |
| 213 | 213 |
# because baremetal driver will reconfigure and restart this as needed |
| 214 |
- if [ ! is_package_installed dnsmasq ]; then |
|
| 215 |
- install_package dnsmasq |
|
| 216 |
- fi |
|
| 214 |
+ is_package_installed dnsmasq || install_package dnsmasq |
|
| 217 | 215 |
stop_service dnsmasq |
| 218 | 216 |
} |
| 219 | 217 |
|
| ... | ... |
@@ -256,12 +254,10 @@ function create_baremetal_flavor() {
|
| 256 | 256 |
ari=$2 |
| 257 | 257 |
nova flavor-create $BM_FLAVOR_NAME $BM_FLAVOR_ID \ |
| 258 | 258 |
$BM_FLAVOR_RAM $BM_FLAVOR_ROOT_DISK $BM_FLAVOR_CPU |
| 259 |
- nova-manage instance_type set_key \ |
|
| 260 |
- --name=$BM_FLAVOR_NAME --key cpu_arch --value $BM_FLAVOR_ARCH |
|
| 261 |
- nova-manage instance_type set_key \ |
|
| 262 |
- --name=$BM_FLAVOR_NAME --key deploy_kernel_id --value $aki |
|
| 263 |
- nova-manage instance_type set_key \ |
|
| 264 |
- --name=$BM_FLAVOR_NAME --key deploy_ramdisk_id --value $ari |
|
| 259 |
+ nova flavor-key $BM_FLAVOR_NAME set \ |
|
| 260 |
+ cpu_arch=$BM_FLAVOR_ARCH \ |
|
| 261 |
+ deploy_kernel_id=$aki \ |
|
| 262 |
+ deploy_ramdisk_id=$ari |
|
| 265 | 263 |
} |
| 266 | 264 |
|
| 267 | 265 |
# pull run-time kernel/ramdisk out of disk image and load into glance |