[Blueprint servercloud-v-openstack-charms] OpenStack Charm work for Vivid

[Liam Young]

Blueprint changed by Liam Young:

Whiteboard changed:
  [USER STORIES]
  Dean is a developer on a product that makes use of the OpenStack charms; he's able to keep introducing new features alongside charm updates every three months, instead of having to wait for six months.
  
  James is deploying neutron and wants to try out the new HA features
  introduced in juno; he's able to enable these in his deployment with:
  
      juju set neutron-api router-ha=true distributed-virtual-router=true
  
  Emma is debugging a problem with her OpenStack charm deployment; she's
  able to easily parse the debug logs and understand what's causing her
  problems.
  
  Corey wants to use the OpenStack charms to deploy his current WIP on a
  refatoring in the upstream OpenStack codebase; he's able to deploy
  OpenStack componets from git repositories in an easy to use fashion
  which feels very similar to devstack stack/unstack.
+ 
+ Bob wants to be able to do an ha deployment with a single deployer
+ config rather than used a phased deployment.
  
  [ASSUMPTIONS]
  3 month release cycle is only supportable with appropriate QA (esp HA).
  
  [RISKS]
  Insufficent resource to delivery scope for cycle.
  
  [IN SCOPE]
  OpenStack charms + mysql, rabbitmq-server, percona-cluster, mongodb, redis
  
  [OUT OF SCOPE]
  Any other charms.
  
  [USER ACCEPTANCE]
  No features should land into next without a) appropriate unit tests b) amulet tests and c) deployer configurations for fully automated testing.
  
  Features should consider HTTPS and HA requirements.
  
  [RELEASE NOTE/BLOG]
  Neutron DVR/HA
  ZeroMQ support (inc Redis)
  Ceilometer HA + HTTPS
  Heat HTTPS (no HA this cycle)
  Keystone PKI support
  HA improvements
  Deploy from git.

-- 
OpenStack Charm work for Vivid
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-v-openstack-charms