Modify an Openstack environment using CLI

Modify an Openstack environment using CLIΒΆ


The Fuel command-line interface has been updated. Although old fuel commands are still available, we recommend that you use the new fuel2 commands instead. See the Fuel CLI commands comparison matrix.

You can modify your OpenStack environment after deployment by downloading the .yaml configuration files, editing settings, and then uploading the configuration files back to the Nailgun server. After uploading the files, you must redeploy your OpenStack environment.

Before modifying any settings, back up your OpenStack environment configuration.

If you upload any changes for provisioning or deployment operations, you freeze the configuration for the entire environment; any changes you later make to the networks, cluster, or disk configurations using the Fuel web UI will not be implemented. To modify these parameters, you must edit the appropriate section of each node’s configuration file and then apply the changes using Fuel CLI.

You can download the following configurations:

  • network
  • settings
  • node --disk
  • node --network
  • provisioning
  • deployment

When performing operations with nodes using fuel deployment and fuel provisioning commands, you can indicate specific nodes. For example:

fuel --env 1 deployment --node 1,2,3

When downloading configurations using fuel deployment and fuel provisioning commands, Fuel automatically generates the following files:

  • For deployment:


    Includes details about the Fuel Master node configuration for a specified OpenStack environment.


    Includes details about the node deployment. The <NODE_ID>.yaml file contains deployment details and is identical to the astute.yaml file stored on a specific node. The deployment tasks consume parameters included in <NODE_ID>.yaml through hiera.

  • For provisioning:


    Includes credentials for the provisioning service (Cobbler) engine.


    Includes details about provisioning for each node.

To modify an OpenStack environment using CLI:

  1. Back up your configuration.

  2. Download the .yaml configuration file(s).


    fuel --env 1 network download
    fuel --env 1 settings download
    fuel --env 1 deployment default
    fuel --env 1 provisioning download
    fuel node --node-id 2 --disk --download
  3. Modify the downloaded file(s).

  4. Save the changes.

  5. Upload the files to the Nailgun server:


    fuel --env 1 provisioning upload
    fuel node --node-id 2 --disk --upload
  6. Redeploy your OpenStack environment

  7. Create a backup of the updated OpenStack environment.


    You may want to delete the downloaded .yaml files, as they may contain unencrypted passwords. This may pose a security threat.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.