Merge pull request #1122 from CiscoCloud/docs/0.6-1.0

change 0.6 references to 1.0
mantl · Feb 16, 2016 · 1869a94 · 1869a94
2 parents 2d6ecb7 + 580a77f
commit 1869a94
Show file tree

Hide file tree

Showing 11 changed files with 21 additions and 21 deletions.
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -1,7 +1,7 @@
 Changelog
 =========
 
-0.6.0 (February 5, 2016)
+1.0.0 (February 16, 2016)
 -------------------------
 
 Features and Improvements

diff --git a/docs/conf.py b/docs/conf.py
@@ -56,9 +56,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '0.6'
+version = '1.0'
 # The full version, including alpha/beta/rc tags.
-release = '0.6'
+release = '1.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

diff --git a/docs/getting_started/aws.rst b/docs/getting_started/aws.rst
@@ -1,7 +1,7 @@
 Amazon Web Services
 =====================
 
-.. versionadded:: 0.6 multi-az support and terraform modularization
+.. versionadded:: 1.0 multi-az support and terraform modularization
 
 As of microservices-infrastructure 0.3 you can bring up Amazon Web Services
 environments using Terraform. You can `download Terraform from terraform.io

diff --git a/docs/getting_started/gce.rst b/docs/getting_started/gce.rst
@@ -1,7 +1,7 @@
 Google Compute Engine
 =====================
 
-.. versionadded:: 0.6 multi-zone support and terraform modularization
+.. versionadded:: 1.0 multi-zone support and terraform modularization
 
 As of Mantl 0.3 you can bring up Google Compute Engine environments using
 Terraform. microservices-infrastructure uses Terraform to provision hosts. You
@@ -188,4 +188,4 @@ You can set up your DNS records with Terraform:
 .. toctree::
    :maxdepth: 1
 
-   dns.rst
+   dns.rst
diff --git a/docs/upgrading/index.rst b/docs/upgrading/index.rst
@@ -4,7 +4,7 @@ Upgrading
 Overview
 --------
 
-Beginning with Mantl 0.6,  our goal is to support a straightforward upgrade path
+Beginning with Mantl 1.0,  our goal is to support a straightforward upgrade path
 from a cluster running a previous release.
 
 However, upgrade support should be considered alpha at this time; it has not
@@ -21,15 +21,15 @@ second upgrades each node serially. You want the use the rolling upgrade on a
 cluster that is already running consul; otherwise, you will likely lose quorum
 and destabilize your cluster.
 
-Upgrading from 0.5.1 to 0.6
+Upgrading from 0.5.1 to 1.0
 ---------------------------
 
 If you have a running 0.5.1 cluster, you need to perform the following steps:
 
 Update security.yml
 ~~~~~~~~~~~~~~~~~~~
 
-Mantl 0.6 requires some additional settings in the ``security.yml`` file that
+Mantl 1.0 requires some additional settings in the ``security.yml`` file that
 you generated when you built your cluster. To auto-generate the necessary
 settings, you simply need to re-run ``security-setup``:
 
@@ -49,7 +49,7 @@ For your reference, the following settings have been added:
 A note on consul_dns_domain
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Prior to 0.6, the ansible ``consul_dns_domain`` variable was defined in a number
+Prior to 1.0, the ansible ``consul_dns_domain`` variable was defined in a number
 of different playbooks. It is now included in ``security.yml`` and can be
 customized from a single location. This simplifies the configuration and reduces
 the likelihood of mistakes. If you are working with a customized
@@ -67,10 +67,10 @@ Upgrade Distributive, Consul, Mesos, and Marathon
 This playbook performs a Distributive upgrade and includes a couple of other
 playbooks that perform a rolling upgrade of Consul, Mesos, and Marathon.
 
-Upgrade to Mantl 0.6
+Upgrade to Mantl 1.0
 ~~~~~~~~~~~~~~~~~~~~
 
-At this point, you can now upgrade the rest of the components to 0.6 with the
+At this point, you can now upgrade the rest of the components to 1.0 with the
 standard provisioning playbook:
 
 .. code-block:: shell

diff --git a/roles/consul/README.rst b/roles/consul/README.rst
@@ -9,11 +9,11 @@ discovery, specifically using the inbuilt DNS server.
 Upgrading
 ---------
 
-.. versionadded:: 0.6
+.. versionadded:: 1.0
 
-Mantl 0.6 includes Consul v0.6.3. If you are running Mantl 0.5.1, you'll need to
+Mantl 1.0 includes Consul v0.6.3. If you are running Mantl 0.5.1, you'll need to
 run the ``playbooks/upgrade-consul.yml`` playbook before reprovisioning your
-cluster to 0.6 in order to ensure a smooth upgrade.
+cluster to 1.0 in order to ensure a smooth upgrade.
 
 Upgrades from releases prior to Mantl 0.5.1 have not been tested.
 

diff --git a/roles/mesos/README.rst b/roles/mesos/README.rst
@@ -39,11 +39,11 @@ counts in the cluster.
 Upgrading
 ---------
 
-.. versionadded:: 0.6
+.. versionadded:: 1.0
 
 If you are running Mantl 0.5.1, you'll need to run the
 ``playbooks/upgrade-mesos-marathon.yml`` playbook before reprovisioning your
-cluster to 0.6. The packaging format changed in the 0.6 release, this will
+cluster to 1.0. The packaging format changed in the 1.0 release, this will
 ensure a smooth upgrade.
 
 Upgrades from releases prior to Mantl 0.5.1 have not been tested.

diff --git a/terraform/openstack/hosts-floating/main.tf b/terraform/openstack/hosts-floating/main.tf
@@ -1,4 +1,4 @@
-# WARNING: This module has been deprecated as of Mantl 0.6
+# WARNING: This module has been deprecated as of Mantl 1.0
 
 variable auth_url { }
 variable control_count {}

diff --git a/terraform/openstack/hosts/main.tf b/terraform/openstack/hosts/main.tf
@@ -1,4 +1,4 @@
-# WARNING: This module has been deprecated as of Mantl 0.6
+# WARNING: This module has been deprecated as of Mantl 1.0
 
 variable auth_url { }
 variable control_count {}

diff --git a/terraform/openstack/keypair/main.tf b/terraform/openstack/keypair/main.tf
@@ -1,4 +1,4 @@
-# WARNING: This module has been deprecated as of Mantl 0.6
+# WARNING: This module has been deprecated as of Mantl 1.0
 
 variable auth_url {}
 variable tenant_id {}

diff --git a/vagrant/README.rst b/vagrant/README.rst
@@ -1,7 +1,7 @@
 Vagrant
 =======
 
-.. versionadded:: 0.6
+.. versionadded:: 1.0
 
 `Vagrant <https://vagrantup.com/>`_ is used to "Create and configure
 lightweight, reproducible, and portable development environments." We use it