From 671ed19c3fbea3f62fca542377d06f076d91521a Mon Sep 17 00:00:00 2001 From: Jimmy McCrory Date: Mon, 11 Mar 2024 11:16:03 -0700 Subject: [PATCH] Remove obsolete nova_force_config_drive variable from docs The nova_force_config_drive variable was removed several releases ago. Update the docs to only mention using nova_nova_conf_overrides to disable the config drive. Change-Id: I1565e1e6e7b8fe12a6b70f09947c48cc893d3ef5 --- .../openstack-operations/managing-instances.rst | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/doc/source/admin/openstack-operations/managing-instances.rst b/doc/source/admin/openstack-operations/managing-instances.rst index 2b9ac73bcb..6b45df2220 100644 --- a/doc/source/admin/openstack-operations/managing-instances.rst +++ b/doc/source/admin/openstack-operations/managing-instances.rst @@ -237,23 +237,16 @@ such as cloud-init, to gain access to instance metadata. This is an alternative way of accessing the Nova EC2-style Metadata. To allow live migration of Nova instances, this forced provisioning -of the config (CD-ROM) drive needs either be turned off, or the format of +of the config (CD-ROM) drive needs to either be turned off, or the format of the configuration drive needs to be changed to a disk format like vfat, a format which both Linux and Windows instances can access. This work around is required for all Libvirt versions prior 1.2.17. -To turn off the forced provisioning of the config drive, add the following +To turn off the forced provisioning of and change the format of the +configuration drive to a hard disk style format, add the following override to the ``/etc/openstack_deploy/user_variables.yml`` file: -.. code-block:: yaml - - nova_force_config_drive: False - -To change the format of the configuration drive, to a hard disk style format, -use the following configuration inside the same -``/etc/openstack_deploy/user_variables.yml`` file: - .. code-block:: yaml nova_nova_conf_overrides: