Chapter 25. Configuring Direct Deploy
When provisioning nodes, 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.
Support for the iSCSI deploy interface,
iscsi, will be deprecated in Red Hat OpenStack Platform (RHOSP) version 17.0, and will be removed in RHOSP 18.0. Direct deploy,
direct, will be the default deploy interface from RHOSP 17.0.
25.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.
Support for the iSCSI deploy interface will be deprecated in Red Hat OpenStack Platform (RHOSP) version 17.0, and will be removed in RHOSP 18.0. Direct deploy will be the default deploy interface from RHOSP 17.0.
Your overcloud node memory
tmpfsmust have at least 8GB of RAM.
Create or modify a custom environment file
/home/stack/undercloud_custom_env.yamland specify the
parameter_defaults: IronicDefaultDeployInterface: direct
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-conductorHTTP server. To change the service that provides the image, set the
parameter_defaults: IronicDefaultDeployInterface: direct IronicImageDownloadSource: http
Include the custom environment file in the
DEFAULTsection of the
custom_env_files = /home/stack/undercloud_custom_env.yaml
Perform the undercloud installation:
$ openstack undercloud install