Change index and handle project renames

Change-Id: I928f710f973e62e4778f08975a29d2d3227189cb

.gitignore

@@ -17,6 +17,10 @@ draft/
 /.tox
 /doc/build
 
+# User driven backup files #
+############################
+*.bak
+
 # Generated by pbr while building docs
 ######################################
 AUTHORS

doc/source/index.rst

@@ -1,10 +1,39 @@
-.. OS-Ansible-Deployment documentation master file
+.. OpenStack-Ansible documentation master file
 
-============================================
-OS-Ansible-Deployment Project Specifications
-============================================
+OpenStack-Ansible Project Specifications
+========================================
 
-Contents:
+`Specification Template <specs/template.rst>`_
+
+Mitaka Specifications
+---------------------
+
+.. toctree::
+   :glob:
+   :maxdepth: 1
+
+   specs/mitaka/*
+
+Liberty Specifications
+----------------------
+
+.. toctree::
+   :glob:
+   :maxdepth: 1
+
+   specs/liberty/*
+
+Kilo Specifications
+-------------------
+
+.. toctree::
+   :glob:
+   :maxdepth: 1
+
+   specs/kilo/*
+
+Index and tables
+================
 
 .. toctree::
    :glob:
@@ -12,16 +41,4 @@ Contents:
 
    specs/*
 
-.. toctree::
-   :glob:
-   :maxdepth: 1
-
-   specs/kilo/*
-   specs/liberty/*
-   specs/mitaka/*
-
-================
-Index and tables
-================
-
 * :ref:`search`

specs/kilo/ceph-block-devices.rst

@@ -4,7 +4,7 @@ Ceph Block Devices
 :tags: storage, ceph
 
 This spec is a proposal to add the ability to configure cinder, glance, and
-nova running in an os-ansible-deployment installation to use an existing Ceph
+nova running in an openstack-ansible installation to use an existing Ceph
 cluster for the creation of volumes, images, and instances using Ceph block
 devices.
 
@@ -146,7 +146,7 @@ Work items
 Testing
 =======
 
-No gate-related adjustments will be made to os-ansible-deployment to support
+No gate-related adjustments will be made to openstack-ansible to support
 this change as no default configurations are being changed here.  Additionally,
 that there are strict limitations on what can run in the all-in-one (AIO) gate
 instance.

specs/kilo/developer-docs.rst

@@ -1,9 +1,9 @@
-os-ansible-deployment overview documentation
-############################################
+openstack-ansible overview documentation
+########################################
 :date: 2015-04-13 13:00
 :tags: documentation, docs, developer
 
-Currently, the os-ansible-deployment repository does not have any cohesive
+Currently, the openstack-ansible repository does not have any cohesive
 developer documentation. This proposal aims to begin such documentation,
 providing a overview and reference for new contributors.
 
@@ -35,7 +35,7 @@ Proposed change
 This proposal recommends making a new docs repo, which would contain Sphinx
 documentation on the following documentation:
 
-* Overview of doing deployments using os-ansible-deployment
+* Overview of doing deployments using openstack-ansible
 
 * Variable files, for knowing which variable files are used where in the process.
 
@@ -48,14 +48,14 @@ documentation on the following documentation:
   hosts, create containers, and install OpenStack.
 
 * Repository role/playbook. Since the repository is fairly unique to
-  os-ansible-deployment, this should be probably be a bit more detailed than
+  openstack-ansible, this should be probably be a bit more detailed than
   the rest of the of the documentation. The openstack_services.yml and
   openstack_other.yml files are of particular interest here.
 
 * Inventory management. This section should discuss the dynamic_inventory.py
   file and and the inventory_management.py files.
 
-* Extending os-ansible-deployment. This would cover using the conf.d and env.d
+* Extending openstack-ansible. This would cover using the conf.d and env.d
   directories, as well as user_extras.yml files. Changes to ansible.cfg
   necessary might be useful, too.
 
@@ -69,7 +69,7 @@ Some topics are explicitly out of scope for this changes. In particular:
 
 * Individual roles. The individual roles should not be documented as part of
   this. There are too many roles and too many changes to be able to keep up with
-  those changes at the os-ansible-deployment level.
+  those changes at the openstack-ansible level.
 
 * End user documentation. For this specification, the 'end user' is a deployer
   or user of the deployed OpenStack system. The installation guide, operations

specs/kilo/keystone-federation.rst

@@ -4,7 +4,7 @@ Keystone Federation
 :tags: federation, scalability
 
 This spec is to propose adding support for Keystone federation to
-os-ansible-deployment.
+openstack-ansible.
 
 Launchpad blueprint: https://blueprints.launchpad.net/openstack-ansible/+spec/keystone-federation
 

specs/kilo/keystone-sp-adfs-idp.rst

@@ -3,7 +3,7 @@ Keystone Service Provider with ADFS Identity Provider Deployment
 :date: 2015-06-22 10:00
 :tags: federation, scalability
 
-This spec is to propose adding support to os-ansible-deployment for Keystone
+This spec is to propose adding support to openstack-ansible for Keystone
 federation using an Active Directory Federation Service (ADFS) Identity
 Provider.
 

specs/kilo/master-kilofication.rst

@@ -3,7 +3,7 @@ Master Kilofication
 :date: 2015-03-23 13:00
 :tags: kilo, update,
 
-Update the various os-ansible-deployment playbooks and roles in the master
+Update the various openstack-ansible playbooks and roles in the master
 branch with the changes necessary to implement a fully functional and updated
 kilo deployment.
 
@@ -77,7 +77,7 @@ Security impact
 These changes will initially be based on BETA code (k3 and rc1 tags of kilo)
 which may have consequences regarding security, but work will be done to test
 against production kilo when it is released (and prior to the 11.0.0 release
-of os-ansible-deployment being tagged)
+of openstack-ansible being tagged)
 
 
 Performance impact

specs/kilo/multi-region-swift.rst

@@ -88,11 +88,11 @@ Proposed change
    between swift storage hosts across multiple locations and "deployments".
 
 4. Document the use of the read_affinity, write_affinity and
-   write_affinity_node_count settings within os-ansible-deployment and provide
+   write_affinity_node_count settings within openstack-ansible and provide
    guidance around how to implement the specified Use Cases.
 
 5. Document the process of setting up a global swift cluster within
-   os-ansible-deployment.
+   openstack-ansible.
 
 6. Adjust settings to allow the use of keystone v3 API for swift, in the swift
    configuration files.
@@ -188,11 +188,11 @@ Work items
    between swift storage hosts across multiple locations and "deployments".
 
 4. Document the use of the read_affinity, write_affinity and
-   write_affinity_node_count settings within os-ansible-deployment and provide
+   write_affinity_node_count settings within openstack-ansible and provide
    guidance around how to implement the specified Use Cases.
 
 5. Document the process of setting up a global swift cluster within
-   os-ansible-deployment.
+   openstack-ansible.
 
 6. Adjust settings to allow the use of keystone v3 API.
 

specs/mitaka/build-facts-archive.rst

@@ -142,7 +142,7 @@ References
 
 If you look at the current scripts located in the scripts directory
 
-* https://github.com/stackforge/os-ansible-deployment/blob/master/scripts/scripts-library.sh#L217-L269
+* https://github.com/openstack/openstack-ansible/blob/master/scripts/scripts-library.sh#L226-L279
 
 a lot of this information is already gathered about the host that the script
 is run on. This proposal should use the information that is gathered as a

specs/mitaka/security-hardening.rst

@@ -1,5 +1,5 @@
-Security Hardening for OSAD Hosts
-#################################
+Security Hardening for Hosts
+############################
 :date: 2015-09-10 00:00
 :tags: security
 

specs/mitaka/standalone-swift.rst

@@ -102,7 +102,7 @@ Work items
 
 * add test to project_config
 
-* enable test in os-ansible-deployment
+* enable test in openstack-ansible
 
 
 Testing