undercloud: revert to using the iscsi deploy interface by default

The direct deploy interface looks promising in the scale tests so far,
but it prevent local testing and PoC with nodes with less than 8 GiB
RAM because it has to convert the overcloud-full image in memory.

This change changes back to the iscsi deploy interface, leaving
the direct deploy interface fully configured and opt-in.

This patch will likely be reverted in Stein.

Change-Id: I5f8126474ab15a310b4ba305c4d537b93e9f0399
Related-Blueprint: ironic-direct-deploy
This commit is contained in:
Dmitry Tantsur 2018-07-24 15:54:03 +02:00
parent d75fca71ed
commit 42c118244a
2 changed files with 5 additions and 6 deletions

View File

@ -68,7 +68,6 @@ parameter_defaults:
HeatReauthenticationAuthMethod: 'trusts'
IronicCleaningDiskErase: 'metadata'
IronicCorsAllowedOrigin: '*'
IronicDefaultDeployInterface: 'direct'
IronicDefaultInspectInterface: 'inspector'
IronicDefaultResourceClass: 'baremetal'
IronicEnabledHardwareTypes: ['ipmi', 'redfish', 'idrac', 'ilo']

View File

@ -1,12 +1,12 @@
---
upgrade:
- |
Ironic in the containerized undercloud now uses the ``direct`` deploy
interface by default for better performance and scalability. See
Ironic in the containerized undercloud now supports the ``direct`` deploy
interface for better performance and scalability. See
`the direct deploy documentation
<https://docs.openstack.org/ironic/latest/admin/interfaces/deploy.html#direct-deploy>`_
for details.
If undesired, this change can be reverted per node by setting the node's
``deploy_interface`` field to ``iscsi`` or globally by changing the new
``IronicDefaultDeployInterface`` to empty string.
This deploy interface can be enabled per node by setting the node's
``deploy_interface`` field to ``direct`` or globally by changing the new
``IronicDefaultDeployInterface`` parameter to ``direct``.