Skip to content
Snippets Groups Projects
Commit f6e17865 authored by Steven Dake's avatar Steven Dake
Browse files

Update liberty deployment warning

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

Change-Id: Iea824e8fc6489d8222e089199161ca3fb30a8310
parent e2a7acca
No related branches found
No related tags found
No related merge requests found
......@@ -3,6 +3,12 @@ Liberty 1.0.0 Deployment Warning
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
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
......@@ -12,17 +18,19 @@ problems*.
Resolution
----------
To rectify this problem, we plan to have a release of 1.1.0-rc1 on
April 1st, 2016. We plan our final releae of 1.1.0 on April 15th, 2016. The
work going into this version will be:
To rectify this problem, the OpenStack release and infrastructure teams
in coordination with the Kolla team executed the following actions:
* Deleted the stable/liberty branch (where 1.0.0 was tagged from)
* Created a tag liberty-early-demise at the end of the broken stable/liberty
branch development.
* Created a new stable/liberty branch based upon stable/mitaka.
* Corrected stable/liberty to deploy Liberty.
* Released Kolla 1.1.0 from the newly created stable/liberty branch.
End Result
----------
A fully functional Liberty OpenStack deployment based upon the two years of
testing that went into the development that went into stable/mitaka.
* Move forward to Docker 1.10.z as a minimum dependency.
* Move to named volumes to remove data loss scenario.
* Backport upgrade playbooks from Mitaka so Operators may effectively manage
OSSA and CVE advisories in their OpenStack cloud without being forced to
migrate to Mitaka.
* Backport thin-containers for Neutron agents.
* Backport Kolla's docker integration module to remove the hard pin on
Docker 1.8.2.
* The Kolla community expects the docker containers themselves to be
minimally modified.
The docker-engine 1.10.0 or later is required.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment