By default, Ironic deploys images to iSCSI shares exposed by IPA. We also support a different deploy method, when IPA fetches an image from a Swift temporary URL. Such approach should allow us scale better, especially in the undercloud, where 1. we have only one conductor, 2. we have Swift already, 3. we already use temporary URLs. This may need configuring Swift temporary URLs and configuring Ironic to use them. Then we need to document both supported deploy method. Finally, we should consider switching to deploy_interface=direct by default, leaving "iscsi" as an option.
This work was mostly done as part of the ansible deploy work. Needs support for containerized undercloud still.
The attached patch implements the direct deploy for both containerized under- and overcloud.
All patches merged. Changing to THT, since this work only concerns containerized undercloud and overcloud. The direct deploy is now the default for the undercloud.
Note: we may have to revert the default, since people are complaining that they can no longer deploy on their testing installations with reduced RAM. The feature itself will still be available in this case, just become opt-in. Bug 1607779 may improve the situation for Stein.
*** Bug 1610115 has been marked as a duplicate of this bug. ***
To clarify: the specific change in undercloud.yaml https://review.openstack.org/#/c/564457/3/environments/undercloud.yaml was reverted. Everything is still in place, particularly https://review.openstack.org/#/c/529342/, and can be tested. The defaults can be changed by setting IronicDefaultDeployInterface to 'direct' during deployment or setting a node's deploy_interface to 'direct'.
This is my understanding on how to enable this by using a customized file. We will have to update our test plan accordingly. Please simply confirm so we have this documented in this RFE 1) Have a customized file like: /home/stack/undercloud_custom_env.yaml parameter_defaults: IronicDefaultDeployInterface: direct 2) Then do your undercloud install openstack undercloud install
Yeah, but there is also a step to link to this new file in undercloud.conf.
Yes, I forgot to add and thanks for officially confirming. 1) Have a customized file like: /home/stack/undercloud_custom_env.yaml parameter_defaults: IronicDefaultDeployInterface: direct 2) Link this customized file into your undercloud.conf DEFAULT section custom_env_files = /home/stack/undercloud_custom_env.yaml 3) Then do your undercloud install openstack undercloud install
This has now been verified both using default config and manual Env: openstack-tripleo-heat-templates-9.0.1-0.20181013060859.ffbe879.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045