Follow-up to the configdrive change

This is a follow-up to commit 595db83ddc.

Change-Id: Ie3d177f77289a25077592a6a0c76d65fa4ce591b
Story: #2005083
This commit is contained in:
Dmitry Tantsur 2019-03-07 10:28:56 +01:00
parent 595db83ddc
commit 5d8231fa14
2 changed files with 9 additions and 3 deletions

View File

@ -33,8 +33,10 @@ CONFIG_DRIVE_ARG_HELP = _(
"the path to the configuration drive file OR the path to a "
"directory containing the config drive files OR a JSON object to build "
"config drive from. In case it's a directory, a config drive will be "
"generated from it. In case it's a JSON object, a config drive will "
"be generated on the server side.")
"generated from it. In case it's a JSON object with optional keys "
"`meta_data`, `user_data` and `network_data`, a config drive will "
"be generated on the server side (see the bare metal API reference for "
"more details).")
SUPPORTED_INTERFACES = ['bios', 'boot', 'console', 'deploy', 'inspect',

View File

@ -2,4 +2,8 @@
features:
- |
Supports passing a JSON object to ``--config-drive`` to build the config
drive on the server side (requires API version 1.56).
drive on the server side (requires API version 1.56) to the following
commands:
openstack baremetal node deploy <node> --config-drive '{...}'
openstack baremetal node rebuild <node> --config-drive '{...}'