Chapter 2. Top New Features

Sourcing a settings file on the undercloud, such as stackrc or overcloudrc, changes Prompt String 1 (PS1) to include the cloud name. This helps identify the cloud currently being accessed. For example, if you source the stackrc file, the prompt appears with an (undercloud) prefix:

source ~/stackrc
(undercloud) [stack@director-12 ~]$

[stack@director-12 ~]$ source ~/stackrc
(undercloud) [stack@director-12 ~]$

The director provides updated templates to register your overcloud through a HTTP proxy.

The director provides the ability to create a roles_data file from individual custom role files. This simplifies the management of individual custom roles. The director also includes a default set of role files to help you get started.

The director now accepts a node blacklist using the DeploymentServerBlacklist parameter. This parameter isolates a list of nodes from receiving updated parameters and resources during the execution of openstack overcloud deploy. This parameter is useful to scale additional nodes while the existing nodes remain untouched during the deployment process.

Previously, the Bare Metal service could only use networks defined in the director templates. It is now possible to compose custom networks for the director to create during an overcloud deployment or update. You can also now assign custom labels to the director's template-defined networks.

The director's web UI now provides more detail for each node and additional functions to manage nodes. You can view this additional information on the Nodes screen of the director's web UI.

The director's web UI includes a simplified role assignment for nodes. The UI uses a spinner to automatically assign a selected number of nodes per role. You can also manually assign specific nodes to roles in the Nodes screen of the director's web UI.