Merge pull request #1123 from CiscoCloud/fix/rename-mi-mantl

rename microservices-infrastructure to Mantl
mantl · Feb 16, 2016 · 7f1c042 · 7f1c042
2 parents 1869a94 + 303ddcb
commit 7f1c042
Show file tree

Hide file tree

Showing 17 changed files with 30 additions and 30 deletions.
diff --git a/README.md b/README.md
@@ -9,7 +9,7 @@ Existing Developer? For information on how the rename affects you, [see our hand
 
 # Overview
 
-[![Join the chat at https://gitter.im/CiscoCloud/microservices-infrastructure](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/CiscoCloud/microservices-infrastructure?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![Join the chat at https://gitter.im/CiscoCloud/mantl](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/CiscoCloud/microservices-infrastructure?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 [![Stories in Ready](https://badge.waffle.io/CiscoCloud/microservices-infrastructure.png?label=ready&title=Ready)](https://waffle.io/CiscoCloud/microservices-infrastructure)
 
 
@@ -94,7 +94,7 @@ Edge nodes are responsible for proxying external traffic into services running i
 All development is done on the `master` branch. Tested, stable versions are identified via git tags.
 
 ```
-    git clone https://github.com/CiscoCloud/microservices-infrastructure.git
+    git clone https://github.com/CiscoCloud/mantl.git
 
 ```
 
@@ -129,11 +129,11 @@ Requirements for running the project are listed in `requirements.txt`. Of note:
 
 ### Deploying on multiple servers
 
-Please refer to the [Getting Started Guide](https://microservices-infrastructure.readthedocs.org/en/latest/getting_started/index.html), which covers multi-server and OpenStack deployments.
+Please refer to the [Getting Started Guide](http://docs.mantl.io/en/latest/getting_started/index.html), which covers multi-server and OpenStack deployments.
 
 ## Documentation
 
-All documentation is located at [https://microservices-infrastructure.readthedocs.org](https://microservices-infrastructure.readthedocs.org/en/latest).
+All documentation is located at [http://docs.mantl.io](http://docs.mantl.io/en/latest).
 
 To build the documentation locally, run:
 
@@ -205,19 +205,19 @@ Mantl is always in the [mantl-universe repo](https://github.com/CiscoCloud/mantl
 - [ ] Apache CloudStack
 - [x] Digital Ocean
 
-Please see [milestones](https://github.com/CiscoCloud/microservices-infrastructure/milestones) for more details on the roadmap.
+Please see [milestones](https://github.com/CiscoCloud/mantl/milestones) for more details on the roadmap.
 
 ## Development
 
 If you're interested in contributing to the project, install [Terraform](https://www.terraform.io/downloads.html) and the Python modules listed in `requirements.txt` and follow the Getting Started instructions. To build the docs, enter the `docs` directory and run `make html`. The docs will be output to `_build/html`.
 
-Good issues to start with are marked with the [low hanging fruit](https://github.com/CiscoCloud/microservices-infrastructure/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) tag.
+Good issues to start with are marked with the [low hanging fruit](https://github.com/CiscoCloud/mantl/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) tag.
 
 ## Getting Support
 
-If you encounter any issues, please open a [Github Issue](https://github.com/CiscoCloud/microservices-infrastructure) against the project. We review issues daily.
+If you encounter any issues, please open a [Github Issue](https://github.com/CiscoCloud/mantl) against the project. We review issues daily.
 
-We also have a [gitter chat room](https://gitter.im/CiscoCloud/microservices-infrastructure). Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
+We also have a [gitter chat room](https://gitter.im/CiscoCloud/mantl). Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
 
 [Cisco Intercloud Services](https://developer.cisco.com/cloud) provides support for OpenStack based deployments of Mantl.
 

diff --git a/docs/conf.py b/docs/conf.py
@@ -113,7 +113,7 @@
 extensions += ['alabaster']
 html_theme_options = {
     'github_user': 'ciscocloud',
-    'github_repo': 'microservices-infrastructure',
+    'github_repo': 'mantl',
     'logo': 'cisco.png',
     'logo_name': True,
 }

diff --git a/docs/faq.rst b/docs/faq.rst
@@ -35,5 +35,5 @@ as a cluster manager for microservices. The Mantl team is in the process of
 evaluating Kubernetes as a cluster manager. The `Mantl roadmap`_ will be
 used to provide details if/when Kubernetes is supported.
 
-.. _Mantl roadmap: http://microservices-infrastructure.readthedocs.org/en/latest/roadmap.html
+.. _Mantl roadmap: http://docs.mantl.io/en/latest/roadmap.html
 .. _OpenStack Provider : https://www.terraform.io/docs/providers/openstack/index.html
diff --git a/docs/getting_started/aws.rst b/docs/getting_started/aws.rst
@@ -3,7 +3,7 @@ Amazon Web Services
 
 .. versionadded:: 1.0 multi-az support and terraform modularization
 
-As of microservices-infrastructure 0.3 you can bring up Amazon Web Services
+As of Mantl 0.3 you can bring up Amazon Web Services
 environments using Terraform. You can `download Terraform from terraform.io
 <http://www.terraform.io/downloads.html>`_.
 
@@ -177,7 +177,7 @@ Once you're all set up with the provider, customize your modules (for
 Terraform to provision your cluster, ``terraform plan`` to see what will be
 created, and ``terraform apply`` to provision the cluster. Afterwards, you can
 use the instructions in :doc:`getting started <index>` to install
-microservices-infrastructure on your new cluster.
+Mantl on your new cluster.
 
 Terraform State
 ^^^^^^^^^^^^^^^^^^^^^^

diff --git a/docs/getting_started/digitalocean.rst b/docs/getting_started/digitalocean.rst
@@ -103,4 +103,4 @@ Once you're all set up with the provider, customize your modules (for
 Terraform to provision your cluster, ``terraform plan`` to see what will be
 created, and ``terraform apply`` to provision the cluster. Afterwards, you can
 use the instructions in :doc:`getting started <index>` to install
-microservices-infrastructure on your new cluster.
+Mantl on your new cluster.
diff --git a/docs/getting_started/gce.rst b/docs/getting_started/gce.rst
@@ -4,7 +4,7 @@ Google Compute Engine
 .. 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
+Terraform. Mantl uses Terraform to provision hosts. You
 can `download Terraform from terraform.io
 <http://www.terraform.io/downloads.html>`_.
 
@@ -120,7 +120,7 @@ by the Terraform provisioner. Run ``ssh-add ~/.ssh/id_rsa`` to add your ssh key.
 Run ``terraform get`` to prepare Terraform to provision your cluster, ``terraform plan`` to see what will be
 created, and ``terraform apply`` to provision the cluster. Afterwards, you can
 use the instructions in :doc:`getting started <index>` to install
-microservices-infrastructure on your new cluster.
+Mantl on your new cluster.
 
 .. note:: If you get the below when running terraform plan or apply, 
   you will need to add : ``account_file = ""`` to the provider section of your gce.tf file.::

diff --git a/docs/getting_started/openstack.rst b/docs/getting_started/openstack.rst
@@ -1,7 +1,7 @@
 OpenStack
 =========
 
-microservices-infrastructure uses Terraform to provision hosts in OpenStack. You
+Mantl uses Terraform to provision hosts in OpenStack. You
 can `download Terraform from terraform.io
 <http://www.terraform.io/downloads.html>`_.
 
@@ -92,7 +92,7 @@ OpenStack Security Group
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
 In order for terraform to apply correctly, you need to create a security group
-in openstack for microservices-infrastructure.
+in openstack for Mantl.
 
 You can either login to the Web UI to perform this task or use the openstack
 commmand line interface as below.
@@ -131,4 +131,4 @@ Once you're all set up there, run ``terraform get`` to prepare Terraform to
 provision your cluster, ``terraform plan`` to see what will be created, and
 ``terraform apply`` to provision the cluster. Afterwards, you can use the
 instructions in :doc:`getting started <index>` to install
-microservices-infrastructure on your new cluster.
+Mantl on your new cluster.
diff --git a/docs/getting_started/softlayer.rst b/docs/getting_started/softlayer.rst
@@ -53,4 +53,4 @@ Once you're all set up with the provider, customize your modules (for
 Terraform to provision your cluster, ``terraform plan`` to see what will be
 created, and ``terraform apply`` to provision the cluster. Afterwards, you can
 use the instructions in :doc:`getting started <index>` to install
-microservices-infrastructure on your new cluster.
+Mantl on your new cluster.
diff --git a/docs/getting_started/vsphere.rst b/docs/getting_started/vsphere.rst
@@ -84,6 +84,6 @@ Once you're all set up with the provider, customize your module, run ``terraform
 
 Afterwards, you can
 use the instructions in :doc:`getting started <index>` to install
-microservices-infrastructure on your new cluster. 
+Mantl on your new cluster. 
 
 
diff --git a/docs/index.rst b/docs/index.rst
@@ -2,10 +2,10 @@ Mantl documentation
 ==========================================
 
 .. image:: /_static/gitter.svg
-   :alt: Join the chat at https://gitter.im/CiscoCloud/microservices-infrastructure
-   :target: https://gitter.im/CiscoCloud/microservices-infrastructure
+   :alt: Join the chat at https://gitter.im/CiscoCloud/mantl
+   :target: https://gitter.im/CiscoCloud/mantl
 
-.. image:: https://badge.waffle.io/CiscoCloud/microservices-infrastructure.png?label=ready&title=Ready
+.. image:: https://badge.waffle.io/CiscoCloud/mantl.png?label=ready&title=Ready
    :alt: Stories in Ready
    :target: https://waffle.io/CiscoCloud/microservices-infrastructure
 

diff --git a/docs/license-documentation.rst b/docs/license-documentation.rst
@@ -46,7 +46,7 @@ roles/logstash: `Apache 2.0 <https://github.com/elastic/logstash/blob/master/LIC
 
 roles/lvm: license: `Apache 2.0 <https://github.com/CiscoCloud/mantl/blob/master/LICENSE>`_
 
-roles/mantlui: `Apache 2.0 <http://microservices-infrastructure.readthedocs.org/en/latest/license.html>`_
+roles/mantlui: `Apache 2.0 <http://docs.mantl.io/en/latest/license.html>`_
 
 roles/marathon: `Apache 2.0 <https://github.com/mesosphere/marathon/blob/master/LICENSE>`_
 

diff --git a/examples/README.md b/examples/README.md
@@ -55,7 +55,7 @@ which is the password used for Marathon.
 ### Other Clusters
 
 If you want to dive right into a cloud cluster go through
-[Getting Started](https://microservices-infrastructure.readthedocs.org/en/latest/getting_started/index.html)
+[Getting Started](https://docs.mantl.io/en/latest/getting_started/index.html)
 at the Documentation site. You can then change the relevant parts of the
 following instructions.
 

diff --git a/roles/docker/README.rst b/roles/docker/README.rst
@@ -7,7 +7,7 @@ Docker
 their words, it "allows you to package an application with all of its
 dependencies into a standardized unit for software development." Their site has
 `more on what Docker is <https://www.docker.com/whatisdocker>`_. We use it in
-microservices-infrastructure to ship units of work around the cluster, combined
+Mantl to ship units of work around the cluster, combined
 with :doc:`marathon`'s scheduling.
 
 Using a private Docker registry

diff --git a/roles/docker/tasks/main.yml b/roles/docker/tasks/main.yml
@@ -1,5 +1,5 @@
 ---
-# Workaround for https://github.com/CiscoCloud/microservices-infrastructure/issues/161
+# Workaround for https://github.com/CiscoCloud/mantl/issues/161
 - name: install latest device-mapper-libs
   sudo: yes
   yum:

diff --git a/roles/glusterfs/README.rst b/roles/glusterfs/README.rst
@@ -43,7 +43,7 @@ Cloud Configuration
 -------------------
 
 On Google Compute Engine, Amazon Web Services, and OpenStack the
-microservices-infrastructure Terraform modules will create an external volume.
+Mantl Terraform modules will create an external volume.
 By default, this volume will be 100gb, but you can change this with the
 Terraform ``glusterfs_volume_size`` variable. The attached disk will be
 formatted as an XFS volume and mounted on the control nodes.

diff --git a/roles/lvm/tasks/volume.yml b/roles/lvm/tasks/volume.yml
@@ -1,5 +1,5 @@
 ---
-# Workaround for https://github.com/CiscoCloud/microservices-infrastructure/issues/161
+# Workaround for https://github.com/CiscoCloud/mantl/161
 - name: install latest device-mapper-libs
   sudo: yes
   yum:

diff --git a/terraform.sample.yml b/terraform.sample.yml
@@ -8,7 +8,7 @@
 # increase stability and enable service discovery. You can look at the
 # documentation for each of these components in their README file in the
 # `roles/` directory, or by checking the online documentation at
-# microservices-infrastructure.readthedocs.org.
+# docs.mantl.io.
 - hosts: all
   vars:
     # consul_acl_datacenter should be set to the datacenter you want to control