openstack
/
fuel-docs
Code Issues Proposed changes

[UG] Change configuration drive format 

This patch adds steps how to change the
configuration drive format through Fuel CLI.

backport: mitaka

Change-Id: I3722ef4ca9965ac7e69e818d021bc06feb05530f
Closes-Bug: #1563722
This commit is contained in:
Olena Logvinova 2016-05-18 18:09:07 +03:00
parent 3541751c30
commit 2fe82ce022
2 changed files with 41 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
userdocs/fuel-user-guide/configure-environment.rst
View File

@ -33,6 +33,7 @@ This section includes the following topics:
configure-environment/map-logical-to-physical-nic.rst
configure-environment/verify-networks.rst
configure-environment/customize-partitions.rst
configure-environment/config-drive-format.rst
configure-environment/settings.rst
configure-environment/dns-ntp-support.rst

40
userdocs/fuel-user-guide/configure-environment/config-drive-format.rst Normal file
View File

@ -0,0 +1,40 @@
.. _config-drive-format:
Change the configuration drive format
-------------------------------------
For legacy reasons, Fuel uses the VFAT configuration drive format which is the
default option for live migration. But as the default format of the
configuration drive for OpenStack environments is ISO 9660, you can change the
VFAT to the ISO 9660 format using the ``config_drive_format`` option.
**To change the configuration drive format using Fuel CLI:**
#. Log in to the Fuel Master node CLI.
#. Download the configuration files:
.. code-block:: console
fuel --env=<env_ID> deployment --default
The default deployment information is downloaded to
``/<cwd>/deployment_<env_ID>``.
#. Edit *every* ``<node-id>.yaml`` file:
#. Find or add the ``compute`` section to the ``<node-id>.yaml`` file.
#. In this section, add the following parameter:
.. code-block:: console
compute:
config_drive_format option: iso9660
#. Upload the updated configuration files to the ``/<cwd>/deployment_<env_ID>``
directory:
.. code-block:: console
fuel --env=<env_ID> deployment --upload
Now, you can proceed with the environment deployment.