Stein Series Release Notes¶
Introduce new “–inflight-validations” option in order to activate those validations. It defaults to “False”, since we don’t want them by default.
The TripleO Validator CLI doesn’t support Mistral anymore for listing and running the Validations. Ansible is now the way to run them.
The TripleO Validator was using Mistral to get all the Validations available on the Undercloud. From now, The CLI is parsing the Validations directly from the filesystem and the Mistral support has been removed.
The MTU setting was not configured for Ironic Inspector DHCP (dnsmasq) service. This caused inspection to fail when operating on a network with < 1500 bytes MTU. See bug: 1845487.
The ‘openstack tripleo validator list’ subcommand can only display all the available parameters for the validations using the new –parameters argument and extract them to a file using the new –create-vars-file argument.
The validations can now be performed by calling Mistral or by calling
ansible-playbook. By default, the latter is used. The new
--use-mistraloption allows to execute either groups or a set of specific validations by calling Mistral instead of using the default mechanism, ie.
The operator is now able to pass extra variables while executing validations through the command line. The command line will accept either a Dict with the new –extra-vars argument or the absolute path of a file (JSON or YAML when using ansible and JSON only when using Mistral) with the new –extra-vars-file argument.
The verbosity of the config-download ansible tasks for deployment are now controlled by the verbosity level specified on the command line.
A new option
host_routesare now available for subnet defenitions in
Host routes specified for the local_subnet will be added to the routing table on the Undercloud.
Host routes for all subnets are passed to tripleo-heat-templates so that the host_routes property of the ctlplane subnets are set accordingly when installing the Undercloud.
Adds new commands to run BIOS cleaning on nodes:
openstack overcloud node bios configure \ --configuration <..> [--all-manageable|uuid1,uuid2,..] openstack overcloud node bios reset \ [--all-manageable|uuid1,uuid2,..]
The first command configures given BIOS settings on given nodes or all manageable nodes; the second command reset BIOS settings to factory default on given nodes or all manageable nodes.
Running and listing the validations was only possible by executing the Mistral workflow associated with those tasks. Now we have the possibility of running and listing the validations using the TripleO CLI. The commands added are ‘openstack tripleo validator run’ and ‘openstack tripleo validator list’ with its corresponding parameters.
The routes defined using
host_routesoption for subnet definitions in the Undercloud configuration is now also configured in ironic inspeactors dnsmasq on the Undercloud. The advanced routing options will be pushed to the inspection ramdisk similar to the way they are already pushed to IPA (ironic-python-agent).
enable_ui is deprecated for removal in Train.
The overcloudrc.v3 file is no longer generated. The same contents are available in overcloudrc.
Automatically enables ironic BIOS management interfaces based on enabled ironic hardware types supporting BIOS management.
Automatically enables ironic inspection interfaces for enabled ironic hardware types supporting out-of-band inspection.
Standalone deployment now support for custom networks data (
network_data.yaml). By default Standalone deploys with no networks data (all services on the ctlplane network). The new option
networks_filecan be used to provide custom networks data.
docker_bip undercloud configuration option will be removed.
docker_insecure_registries has been deprecated for container_insecure_registries
docker_registry_mirror has been deprecated for container_registry_mirror
Added new exclude option to the container build command that allows the user to skip building a specific container. This option can be specified muiltiple times to skip building multiple containers.
dhcp_endoptions are now optional for subnet definitions in the Undercloud configuration (
undercloud.conf). The the allocation_pools are calculated by removing the
inspection_iprangefrom the subnets full IP range. Allocation pools for all remaining ranges will be configured. Additionally the new option
dhcp_exlcudecan be used to exclude additional IP addresses and/or IP address ranges, for example to exclude
172.20.0.105and the range
dhcp_exclude = 172.20.0.105,172.20.0.210-172.20.0.219
dhcp_startis defined any addresses prior to this address is also removed from the allocation pools.
dhcp_endis defined any addresses after this address is also removed from the allocation pools.
If the default cidr (
192.168.24.0/24) is used for the local subnet the
dhcp_endcannot simply be removed to utilize the full address space of the subnet. This due to the default values of
It is now possible to configure non-contiguous allocation pools for the Undercloud ctlplane subnets. The
dhcp_endoptions have been extended to allow a list of start and end address pairs. For example to create allocation pools
dhcp_start = 172.20.0.100,172.20.0.200 dhcp_end = 172.20.0.150,172.20.0.250
This changes the upgrade workflow for the standalone and undercloud where we now run the post_upgrade_tasks after the deployment. So the order is upgrade_tasks, deployment steps (docker/puppet), then post_upgrade_tasks which is the same order as the overcloud. It will allow us to execute some specific post upgrade tasks on standalone and undercloud, like removing Docker containers when upgrading to Podman.
Host timezone can be managed during the undercloud installation. The default timezone is the timezone already configured for the system. The timezone can be configured by setting undercloud_timezone in undercloud.conf
Host timezone can be managed during the undercloud upgrade. The default timezone is the timezone already configured for the system. The timezone can be configured by setting undercloud_timezone in undercloud.conf and it is recommended to set this going forward.
Upgrades and updates are now use tripleo-admin user to connect to the overcloud by default, which makes it work the same in this regard as fresh deployment.
The –ssh-user parameter for overcloud upgrade run command and similar commands is now deprecated and will be removed. In the future, tripleo-admin user will be used always, which will make it work the same as deployment workflow.
openstack overcloud delete PLAN_NAME now instead of deleting the stack and the plan instead it undeploys the plan to maintain the correct status internally and deletes the stack. This is a backwards incompatible change because we are no longer deleting the plan as it was done previously.
Switch the Heat Launcher to use Podman instead of Docker when heat_native is disabled.
When requesting the deployment status of a non-existant plan, instead of showing a traceback, show a helpful message indicating there is no status.
Instack undercloud legacy passwords should be customized by its original
undercloud-passwords.conflocation, when upgrading from instack UC. Those passwords will be automatically transitioned to
tripleo-undercloud-passwords.yamlduring upgrade. Changes made to the legacy location become ignored after that. Use
tripleo-undercloud-passwords.yamlto manually update UC passwords further on.
The –use-heat option from undercloud install has been removed along with the ability to deploy an undercloud on baremetal using instack-undercloud via ‘openstack undercloud install’. Manual deployment may still be possible by directly invoking the instack-undercloud scripts but it is no longer available via the ‘openstack undercloud install’ command.
The timeout specified with –timeout will now be honored with config-download. An additional cli arg, –config-download-timeout is also added that can be used to specify a specific timeout (in minutes) just for the config-download part of the deployment.
Fixes a validation issue, validation would fail when multiple ctlplane subnets were defined in
undercloud.conf. Bug: 1791088.