此内容没有您所选择的语言版本。
10.11. heat deployment-create
usage: heat deployment-create [-i <KEY=VALUE>] [-a <ACTION>] [-c <CONFIG>] -s <SERVER> [-t <TRANSPORT>] [--container <CONTAINER_NAME>] [--timeout <TIMEOUT>] <DEPLOY_NAME>
Positional arguments
- <DEPLOY_NAME>
Name of the derived config associated with this
deployment. This is used to apply a sort order to the
list of configurations currently deployed to the
server.
Optional arguments
- -i <KEY=VALUE>, --input-value <KEY=VALUE>
Input value to set on the deployment. This can be
specified multiple times.
- -a <ACTION>, --action <ACTION>
Name of action for this deployment. Can be a custom
action, or one of: CREATE, UPDATE, DELETE, SUSPEND,
RESUME
- -c <CONFIG>, --config <CONFIG>
ID of the configuration to deploy.
- -s <SERVER>, --server <SERVER>
ID of the server being deployed to.
- -t <TRANSPORT>, --signal-transport <TRANSPORT>
How the server should signal to heat with the
deployment output values. TEMP_URL_SIGNAL will create
a Swift TempURL to be signaled via HTTP PUT. NO_SIGNAL
will result in the resource going to the COMPLETE
state without waiting for any signal.
- --container <CONTAINER_NAME>
Optional name of container to store TEMP_URL_SIGNAL
objects in. If not specified a container will be
created with a name derived from the DEPLOY_NAME
- --timeout <TIMEOUT>
Deployment timeout in minutes.