Wallaby Series Release Notes¶
An ephemeral Heat process is now used by default for overcloud deployment. On each overcloud management operation (deploy/update/upgrade), a containerized Heat process will be started, the stack will be created new, and then the Heat process will be stopped. The enable_heat option is undercloud.conf is now defaulted to False.
Setting enable_heat=True in undercloud.conf is deprecated.
Using –heat-type=installed is deprecated with the openstack overcloud commands.
New configuration options for enable_neutron and enable_heat are added to the standalone and undercloud installers. These options default to true, and can be used to selectively disable these services.
A new cli argument, –heat-type is added to openstack overcloud deploy. Available options are “installed”, “pod”, “container”, and “native”. The default is “installed”. The argument specifies the type of Heat process to use for the deployment.
The “openstack tripleo deploy” and “openstack undercloud install” commands now save their generated artifacts from the deployment under a single consistent directory, which by default is located at ~/tripleo-deploy/<stack>. For the undercloud, this location is ~/tripleo-deploy/undercloud. The directory can be overridden with the –output-dir option.
enable_frrto enable the TripleO FRR service in standalone and undercloud deployments.
The –setup-only option has been added to facilitate the generation of ansible content and ensure the environment is accessible via the current stack.
A consistent working directory is now used by the openstack overcloud deploy command. The directory contains input files, generated files, and log files, among others. The directory defaults to ~/overcloud-deploy/<stack>. The old default config-download directory at ~/config-download/<stack> is now a symlink to the new location at ~/overcloud-deploy/<stack>/config-download/<stack> for backwards compatibility.
The container image build command now has the ability to inject labels into various images being constructed. To add labels into a container, the argument –label can be specified multiple times. The value is always a key=value pair and each key must be unique.
Adds auth_token_lifetime to undercloud.conf with a default of 14400. This configuration option exposes the keystone token expirataion as a top level configuration since it may need to be increased to handle larger clouds.
openstack overcloud parameters setcommand has been removed. It was used to update the plan parameters. Now that we use sever side parameter merging and no plan, this is not relevant anymore.
openstack overcloud plan *commands have been removed. These commands are irrelevant as overcloud deploy/update/upgrade does not create/update swift plan anymore. Also, some of the
openstack overcloud rolecommands that use swift plan have been removed.
With the move to Nova-less provisioning and Neutron network management being removed from being managed via Heat, the undercloud minion functionality is now deprecated.
The –plan-environment-file option of openstack tripleo deploy command is now deprecated and not used.
Removing the deprecated
--templatesswitches to overcloud node delete. This is causing confusion to the operators.
The container image build label agument has the ability to do simple string replacements following the python standard. Available options for string replacement are registry, namespace, prefix, image, tag, and name. Example usage –label component=”%(prefix)s-%(name)s-container”.
A dnf installation of tripleo-common, tripleo-ironic-python-agent-builder, openstack-tripleo-image-elements, openstack-tripleo-puppet-elements, and xfsprogs has been included as part of the openstack overcloud image build command. This allows us to drop these as always required dependencies for tripleoclient.
docker_bip has been removed from the undercloud.conf
--*-flavoroptions and the
--*-countoptions were removed from the
Remove undercloud_update_packages option in undercloud.conf.
upgrade_cleanup has been removed from the undercloud.conf as it hasn’t had any effect after the initial containerized undercloud back in Rocky or FFU upgrade in Train.
Removed experimental designation from tripleo deploy since we’ve used it for several releases now and we’re unlikely to change how it works.