Ocata Series Release Notes¶
- The overcloud generate fencing command no longer carries a default value for the action parameter. Advice from upstream Pacemaker is that this value should no longer be passed to fencing agents as it may cause inconsistent behaviour. The parameter remains, but is now optional, and its use is discouraged.
- Removed setting NeutronDhcpAgentsPerNetwork based on controller count. If not overridden by the user, it should be calculated based on the number of neutron DHCP agents that are actually deployed.
- overcloud deploy correctly returns an error code when failing during the pre-deployment verifications (before the stack is launched) (bug 1672790).
6.0.0 is the final release for Ocata. It’s the first release where release notes are added.
- Use the overcloudrc generated in a Mistral action so both CLI and UI can use the same file when interacting with the deployed OpenStack.
- Default image build to use yaml files. If no args are given to the overcloud image build, it will default to using the CentOS yaml files in /usr/share/openstack-tripleo-common/image-yaml.
- Simplify fetching the passwords from Mistral.
- Add –disable-validations argument that will disable the run of validations completely. This feature is useful when we deploy TripleO with multinode and deployed-server features.
- Adds overcloud generate fencing command, which outputs an environment file which can be used to configure node fencing in HA deployments. Currently IPMI and virtual (non-production) deployments are supported.
openstack overcloud deployand
openstack overcloud plan createcommands now have a
--disable-password-generationargument, to allow operators to disable password generation and only use passwords provided by them instead. By default, password generation remains enabled.
- Add new command
openstack overcloud raid createfor building RAID on given nodes.
- Adds the ability for external TripleO validations to be called during a deployment workflow.
- Adds the ability for external TripleO validations to be called during an introspection workflow.
- Some packages previously built into the default overcloud-full image to support vendor integration have been removed due to difficulties related to CI stability. To add these packages for the vendor support you require you can either build a custom image containing the packages (see http://docs.openstack.org/developer/tripleo-docs/basic_deployment/basic_deployment_cli.html#get-images) or you can use virt-customize (http://libguestfs.org/virt-customize.1.html) to install the required extra packages in a pre-built overcloud-full image.
openstack baremetal show capabilitieshas been broken for some time due to conflict with
openstack baremetal showfrom Ironic. This command was removed.
openstack baremetal import,
openstack baremetal introspect bulk startand
openstack baremetal configureare now deprecated in favour of
openstack overcloud node import,
openstack overcloud node introspectand
openstack overcloud node configurerespectively. See bug 1649541.
- Fixes bug 1649588 so exceptions are not swallowed anymore which was leading to 0 exit code. Now, it returns a proper exit code when plan deletion fails.
- Add new hiera agent hook to legacy image build. The change Ia1864933235152b7e899c4442534879f8e22240d added these to the newer overcloud-images.yaml method of building images. Unfortunately because the old ‘openstack overcloud image build –all’ method does not leverage this file yet, it leads to a timeout in deployment because the heat agents are not available. It fixes bug 1651616.
- Fixes bug 1637474 so we manage –initial-state flag for register_or_update.
- Fixes bug 1657461 so the overcloud stack is actually deleted. This calls the newly created stack delete workflow.
- Fixes bug 1614928 Moves the package update command to use a workflow.
- Remove the keystone_pki cert generation, which is not needed anymore.
- Allow client to support whole disk images. Client will now accept a –whole-disk flag on the overcloud image upload command. When this flag is set, it will only look for qcow2 image, not enforcing the upload of initrd and vmlinuz images. It will also not set these properties on the qcow2 image on glance. This will allow Ironic to consider the uploaded image as full disk image, giving the possibility to provide full disk images in TripleO instead of single partition ones. Please look at Ironic documentation for reference