Adds swift_standalone for Juno spec

Spec to add a play to setup swift_standalone on Juno

Change-Id: I3a494bd7a478c5df84bcde897af36f373a207c5c

specs/juno/swift_standalone.rst

@@ -0,0 +1,128 @@
+Swift standalone for Juno
+#################################
+:date: 2015-03-23 13:00
+:tags: juno, swift
+
+Add an openstack play that will handle the installation of a swift standalone
+deploy.
+
+  * https://blueprints.launchpad.net/openstack-ansible/+spec/swift-standalone-juno
+
+In Juno the keystone-all play sets up all service endpoints including users and
+passwords, these are not required and will fail if the appropriate "password"
+variables are not specified.
+
+Problem description
+===================
+
+In Juno the keystone-all play sets up all service endpoints including users and
+passwords, these are not required and will fail if the appropriate "password"
+variables are not specified.
+
+Additionally, the support plays that setup nova/neutron specific configuration
+will also fail.
+
+Proposed change
+===============
+
+Add a new openstack-setup_swift_standalone.yml which will only setup the
+appropriate services, and won't require variables that are not used or setup
+keystone users that are not required.
+
+
+Alternatives
+------------
+
+We could add the unrequired variables and live with having unrequired keystone
+users/passwords - but this would result in an unclean setup. 
+
+Alternatively we could manually pick the plays to run instead of running an
+overarching "openstack-all" play, but this would require knowing which plays
+should/shouldn't be run and would mean not running the keystone-all play,
+making it taxing from a support and docuemntation perspective.
+
+
+Playbook impact
+---------------
+
+Minimal - it would only involve adding a new playbook, and wouldn't impact on
+existing playbooks at all. Running the incorrect "all" play would just result
+in a failure.
+
+
+Upgrade impact
+--------------
+
+For new deploys only.
+
+Security impact
+---------------
+
+Increases security by removing unneeded keystone users from swift only deploys.
+
+Performance impact
+------------------
+
+Increases performance of swift only installs since installation of additional
+services would not even be attempted.
+
+End user impact
+---------------
+
+None
+
+Deployer impact
+---------------
+
+Having knowledge of a swift-only play may add extra requirements from a
+deployer perspective, but it does help with regards to deployments.
+
+Developer impact
+----------------
+
+No real impact, except for new playbook.
+
+Dependencies
+------------
+
+N/A
+
+Implementation
+==============
+
+Assignee(s)
+-----------
+
+Primary assignee:
+  https://launchpad.net/~andrew-mccrae
+
+IRC: andymccr
+
+
+Work items
+----------
+
+There is one item that needs to be done:
+
+* `#1435350`_  We need a swift_standalone play for Juno
+
+.. _#1435350: https://bugs.launchpad.net/openstack-ansible/+bug/1435350
+
+
+Testing
+=======
+
+This change won't impact gating, but also won't be tested as a swift_standlone
+is a currently untested install path.
+
+
+Documentation impact
+====================
+
+The docs will need to be adjusted to include swift stand alone
+
+
+References
+==========
+
+N/A