openstack/kolla
Code Issues Proposed changes

Update liberty deployment warning

Browse Source 
Tell folks about the state of liberty 1.0.0 and to use
1.1.0 for production deployments.

Change-Id: Iea824e8fc6489d8222e089199161ca3fb30a8310
This commit is contained in:
Steven Dake 2016-05-11 09:00:39 -07:00
parent e2a7accaab
commit f6e1786563
1 changed files with 21 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
doc/liberty-deployment-warning.rst
View File

@ -3,6 +3,12 @@ Liberty 1.0.0 Deployment Warning
Warning Overview Warning Overview
---------------- ----------------
Please use Liberty 1.1.0 tag or later when using Kolla. No data loss
occurs with this version. stable/liberty is also fully functional and
suffers no data loss.
Data loss with 1.0.0
--------------------
The Kolla community discovered in the of middle Mitaka development that it The Kolla community discovered in the of middle Mitaka development that it
was possible for data loss to occur if the data container is rebuilt. In was possible for data loss to occur if the data container is rebuilt. In
this scenario, Docker pulls a new container, and the new container doesn't this scenario, Docker pulls a new container, and the new container doesn't
@ -12,17 +18,19 @@ problems*.
Resolution Resolution
---------- ----------
To rectify this problem, we plan to have a release of 1.1.0-rc1 on To rectify this problem, the OpenStack release and infrastructure teams
April 1st, 2016. We plan our final releae of 1.1.0 on April 15th, 2016. The in coordination with the Kolla team executed the following actions:
work going into this version will be:
* Move forward to Docker 1.10.z as a minimum dependency. * Deleted the stable/liberty branch (where 1.0.0 was tagged from)
* Move to named volumes to remove data loss scenario. * Created a tag liberty-early-demise at the end of the broken stable/liberty
* Backport upgrade playbooks from Mitaka so Operators may effectively manage branch development.
OSSA and CVE advisories in their OpenStack cloud without being forced to * Created a new stable/liberty branch based upon stable/mitaka.
migrate to Mitaka. * Corrected stable/liberty to deploy Liberty.
* Backport thin-containers for Neutron agents. * Released Kolla 1.1.0 from the newly created stable/liberty branch.
* Backport Kolla's docker integration module to remove the hard pin on
Docker 1.8.2. End Result
* The Kolla community expects the docker containers themselves to be ----------
minimally modified. A fully functional Liberty OpenStack deployment based upon the two years of
testing that went into the development that went into stable/mitaka.
The docker-engine 1.10.0 or later is required.