Merge "Fix up the compute starter kit tag"

reference/projects.yaml

@@ -18,6 +18,7 @@ Nova:
         - name: release:at-6mo-cycle-end
         - name: release:has-stable-branches
         - name: type:service
+        - name: starter-kit:compute
     - repo: openstack/python-novaclient
       tags:
         - name: release:independent
@@ -74,6 +75,7 @@ Glance:
         - name: release:at-6mo-cycle-end
         - name: release:has-stable-branches
         - name: type:service
+        - name: starter-kit:compute
     - repo: openstack/glance-specs
     - repo: openstack/python-glanceclient
       tags:
@@ -107,6 +109,7 @@ Keystone:
         - name: release:at-6mo-cycle-end
         - name: release:has-stable-branches
         - name: type:service
+        - name: starter-kit:compute
     - repo: openstack/keystoneauth
       tags:
         - name: release:independent
@@ -288,6 +291,7 @@ Cinder:
         - name: release:at-6mo-cycle-end
         - name: release:has-stable-branches
         - name: type:service
+        - name: starter-kit:compute
     - repo: openstack/cinder-specs
     - repo: openstack/python-cinderclient
       tags:

reference/tags/compute_starter_kit.rst

@@ -4,6 +4,8 @@
   Unported License.
   http://creativecommons.org/licenses/by/3.0/legalcode
 
+.. _`tag-starter-kit:compute`:
+
 ===================
 compute starter kit
 ===================
@@ -12,6 +14,13 @@ A common starting point for a Compute oriented OpenStack cloud that
 can be expanded over time to include more of the OpenStack universe.
 
 
+Application to current projects
+===============================
+
+
+.. tagged-projects:: starter-kit:compute
+
+
 Rationale
 =========
 
@@ -117,7 +126,7 @@ journey. These are people that do not yet have use cases, and probably
 won't until they experiment some with a starter kit.
 
 For those people starting their journey into cloud computing, enabling
-suppport for persistent volumes allows them to more easily transition
+support for persistent volumes allows them to more easily transition
 from virtualization or managed hosting environments and
 experiences. It also provides an easy way to get used to API driven
 ephemeral computes. This allows them to see how existing workloads
@@ -172,20 +181,17 @@ Requirements
   projects into such a deployment over time.
 
   Rationale: we'd like this to be a solid bit of 'seed corn' from
-  which a larger and richer OpenStack deployement can be built out
+  which a larger and richer OpenStack deployment can be built out
   over time. Starting small with the ability to grow helps OpenStack adoption.
 
 
 Tag application process
 =======================
 
-Under the current criteria the tag would apply to:
-
-- keystone
-- glance
-- nova (using nova-network multi host)
-- cinder
+The TC is responsible for maintaining the tags in the 'starter kit' category.
 
+There is no need to apply for addition/removal. Changes externally proposed
+will be reviewed and approved by the TC.
 
 Deprecation
 ===========
@@ -201,17 +207,6 @@ Attributes
 No attributes
 
 
-Application to current projects
-===============================
-
-As part of the application you need to go through the exercise of applying
-the proposed tag to at least some subset of the current project list. This
-will serve as an example of how the tag should be applied in the real world.
-You may also submit (as a subsequent change) the corresponding governance
-change to immediately apply the proposed tag to projects.
-
-.. tagged-projects:: <tag name>
-
 References
 ==========
 [1] - http://superuser.openstack.org/articles/openstack-users-share-how-their-deployments-stack-up