deploy — Deploy Image to OpenStack Cloud
Synopsis
machinery deploy NAME -c CONFIG_FILE | --cloud-config=CONFIG_FILE
   [-i IMAGE_DIR | --image-dir=IMAGE_DIR]
   [-n CLOUD_IMAGE_NAME | --cloud-image-name=CLOUD_IMAGE_NAME]
   [-s | --insecure ]
machinery help [deploy]
Description
The deploy command builds and deploys an image to an OpenStack cloud.
This command is particularly useful for testing, debugging, or validation.
NOTE: Set Password for Unattended Work
Machinery asks for a password when sourcing the configuration file. This interrupts the work flow and the user has to enter this password. If you prefer to leave it uninterrupted and unattented, remove the following line in your cloud configuration file (see the
-coption):read -s OS_PASSWORD_INPUT
and set the password in the
OS_PASSWORDvariable:export OS_PASSWORD=YOUR_PASSWORD
Arguments
NAME(required): Name of the system description.
Options
- 
-c CONFIG_FILE,--cloud-config=CONFIG_FILE(required): Path to file where the cloud config (openrc.sh) is located. The configuration file is sourced by Machinery. - 
-i IMAGE_DIR,--image-dir=IMAGE_DIR(optional): Image file under specific path. - 
-n CLOUD_IMAGE_NAME,--cloud-image-name=CLOUD_IMAGE_NAME(required): Name of the image in the cloud. - 
-s,--insecure(optional): Allow to make "insecure" HTTPS requests, without checking the SSL certificate when uploading to the cloud. 
Prerequisites
- The 
deploycommand requires the packageskiwifor building the image andpython-glanceclientfor uploading the image to the cloud. 
Supported Architectures
Machinery only supports deploying x86_64 images on x86_64 systems.
Examples
- 
Build an image under the system description named
jeos. Deploy it to the OpenStack cloud nametux-cloudby using the configuration fileopenrc.shin directorytux:$
machinerydeploy jeos -n tux-cloud -c tux/openrc.sh