openstack/kolla-ansible
Code Issues Proposed changes

Minor Readability Adjustments to Operating Kolla

Browse Source 
Minor adjustments to operating-kolla.rst.

Change-Id: If08e59cedb4a8d6e36db743f670288221e79b3c8
This commit is contained in:
Kenny Johnston 2016-07-25 22:00:05 -05:00
parent a06a57ba54
commit ba62df4fff
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/operating-kolla.rst
View File

@ -6,9 +6,9 @@ Operating Kolla
Upgrading Upgrading
========= =========
Kolla's strategy for upgrades is to never make a mess and follow consistent 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 patterns during deployment such that upgrades from one environment to the next
the next are simple to automate. are simple to automate.
Kolla implements a one command operation for upgrading an existing deployment Kolla implements a one command operation for upgrading an existing deployment
consisting of a set of containers and configuration data to a new deployment. consisting of a set of containers and configuration data to a new deployment.
@ -16,15 +16,15 @@ consisting of a set of containers and configuration data to a new deployment.
Kolla uses the ``x.y.z`` semver nomenclature for naming versions. Kolla's Kolla uses the ``x.y.z`` semver nomenclature for naming versions. Kolla's
Liberty version is ``1.0.0`` and the Mitaka version is ``2.0.0``. The Kolla Liberty version is ``1.0.0`` and the Mitaka version is ``2.0.0``. The Kolla
community commits to release z-stream updates every 45 days that resolve 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 defects in the stable version in use and publish those images to the Docker Hub
Docker Hub registry. To prevent confusion, the Kolla community recommends registry. To prevent confusion, the Kolla community recommends using an alpha
using an alpha identifier ``x.y.z.a`` where ``a`` represents any customization identifier ``x.y.z.a`` where ``a`` represents any customization done on the
done on the part of the operator. For example, if an operator intends part of the operator. For example, if an operator intends to modify one of the
to modify one of the Docker files or the repos from where the originals and Docker files or the repos from the originals and build custom images for the
build custom images and using Liberty, the operator should start with Liberty version, the operator should start with version 1.0.0.0 and increase
version 1.0.0.0 and increase alpha for each release. Alpha tag usage is alpha for each release. Alpha tag usage is at discretion of the operator. The
at discretion of the operator. The alpha identifier could be a number as alpha identifier could be a number as recommended or a string of the operator's
recommended or a string of the operator's choosing. choosing.
If the alpha identifier is not used, Kolla will deploy or upgrade using the If the alpha identifier is not used, Kolla will deploy or upgrade using the
version number information contained in the release. To customize the version number information contained in the release. To customize the