Blueprint changed by James Page:

Whiteboard changed:
  [USER STORIES]
+ Karolina is a Cloud Consultant who needs help from 2nd/3rd line support with 
a bug in an Openstack service. She needs a way to gather all pertinent data and 
logs from an errant unit.
+ 
+ Bob is a Cloud Consultant who wants to demonstrate to a customer that
+ the cloud he has just deployed is healthy. He would like a health action
+ which reports the status of the deployed service unit.
+ 
+ Abigail is an Openstack Administrator who needs to periodically take
+ down machines for hardware maintenance. She has to manually relocate any
+ resources assigned to the machine, before powering it off, to limit any
+ service disruption. Abigail would like a Juju action for each Openstack
+ service which gracefully achieves this and a corresponding action to
+ take the service out of maintenance mode once it is back.
+ 
+ Sarah administers a large Ceph cluster and regularly needs to replace
+ failed hard disks. She needs an action to manage this process.
+ 
+ Kahled is an Openstack Administrator who periodically needs to restart
+ Openstack services on a given unit. He needs an action to enable him to
+ do this.
+ 
+ Lukas is a DBA who manages a percona installation. In the event of
+ multiple failure he needs a way to recover the database cluster. He also
+ needs to report on space and quota usage within the database
+ 
+ Nerea is an OIL Devop who needs to benchmark charms when deployed with
+ different components. She needs a benchmark she can run for each
+ service.
+ 
+ Emmanuel is an Openstack Administrator who wants to upgrade from Juno to
+ Kilo. He wants to do a rolling upgrade.
+ 
  [ASSUMPTIONS]
  [RISKS]
  [IN SCOPE]
  [OUT OF SCOPE]
  [USER ACCEPTANCE]
  [RELEASE NOTE/BLOG]

-- 
OpenStack Charms - 15.07 and 15.10
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-w-openstack-charms

-- 
Ubuntu-server-bugs mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to