Chapter 21. Configuring Direct Deploy

When provisioning nodes, the director mounts the overcloud base operating system image on an iSCSI mount and then copies the image to disk on each node. Direct deploy is an alternative method that writes disk images from a HTTP location directly to disk on bare metal nodes.

21.1. Configuring the direct deploy interface on the undercloud

The iSCSI deploy interface is the default deploy interface. However, you can enable the direct deploy interface to download an image from a HTTP location to the target disk.

Note

Your overcloud node memory tmpfs must have at least 6GB of RAM.

Procedure

  1. Create or modify a custom environment file /home/stack/undercloud_custom_env.yaml and specify the IronicDefaultDeployInterface.

    parameter_defaults:
      IronicDefaultDeployInterface: direct
  2. By default, the Bare Metal Service (ironic) agent on each node obtains the image stored in the Object Storage Service (swift) through a HTTP link. Alternatively, Ironic can stream this image directly to the node through the ironic-conductor HTTP server. To change the service providing the image, set the IronicImageDownloadSource to http in the /home/stack/undercloud_custom_env.yaml file:

    parameter_defaults:
      IronicDefaultDeployInterface: direct
      IronicImageDownloadSource: http
  3. Include the custom environment file in DEFAULT section of the undercloud.conf file.

    custom_env_files = /home/stack/undercloud_custom_env.yaml
  4. Perform the undercloud installation:

    $ openstack undercloud install