Add documentation about critical data loss

There is a critical data loss in Liberty 1.0.0.  It is only fair we
warn Operators not to use 1.0.0 and then revert this change once
1.1.0 is released.

Change-Id: I65a18ddbbdbf2fc5f62f62ff7a1650049b61fada

2 files changed, 29 insertions, 0 deletions

diff --git a/doc/index.rst b/doc/index.rst
index 83b3708e0..69f7d4be6 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -40,6 +40,7 @@ Kolla Overview
    advanced-configuration
    operating-kolla
    selinux
+   liberty-deployment-warning
 
 
 Kolla Services
diff --git a/doc/liberty-deployment-warning.rst b/doc/liberty-deployment-warning.rst
new file mode 100644
index 000000000..ab6482843
--- /dev/null
+++ b/doc/liberty-deployment-warning.rst
@@ -0,0 +1,28 @@
+Liberty 1.0.0 Deployment Warning
+================================
+
+Warning Overview
+----------------
+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
+contain the data from the old container.  Kolla stable/liberty and Kolla
+1.0.0 are not to be used at this time, as they result in *critical data loss
+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:
+
+* 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.