-
Mark Goddard authored
Also better organise the 'tips and tricks' section. Change-Id: If20a89ae93b64b5a1b5895bb9dc73c4e70adaba7 Related-Bug: #1862649
Mark Goddard authoredAlso better organise the 'tips and tricks' section. Change-Id: If20a89ae93b64b5a1b5895bb9dc73c4e70adaba7 Related-Bug: #1862649
Operating Kolla
Versioning
Kolla uses the x.y.z
semver nomenclature for
naming versions. Kolla's initial Pike release was 5.0.0
and the initial
Queens release is 6.0.0
. The Kolla community commits to release z-stream
updates every 45 days that resolve defects in the stable version in use and
publish those images to the Docker Hub registry.
To prevent confusion, the Kolla community recommends using an alpha identifier
x.y.z.a
where a
represents any customization done on the part of the
operator. For example, if an operator intends to modify one of the Docker files
or the repos from the originals and build custom images for the Pike version,
the operator should start with version 5.0.0.0 and increase alpha for each
release. Alpha tag usage is at discretion of the operator. The alpha identifier
could be a number as recommended or a string of the operator's choosing.
To customize the version number uncomment openstack_release
in globals.yml
and specify the version number desired. If openstack_release
is not
specified, Kolla will deploy or upgrade using the version number information
contained in the kolla-ansible package.
Upgrade procedure
Note
If you have set enable_cells
to yes
then you should read the
upgrade notes in the :ref:`Nova cells guide<nova-cells-upgrade>`.
Kolla's strategy for upgrades is to never make a mess and to follow consistent patterns during deployment such that upgrades from one environment to the next are simple to automate.