Blueprint changed by James Page: Whiteboard changed: [USER STORIES] - TBC + Tobias wants to add support for a new Neutron plugin to the OpenStack charms; he's able to quickly and easily add this by writing a new subordinate for L2 management. + James is completely paranoid about regressing functionality in the + OpenStack charms during development - he can sleep sound knowing that + all charms have amulet and bundle tests! + + Jane has an existing vSphere deployment; she's able to deploy OpenStack + ontop of vSphere using a few manually created VM's using the manual + provider and the OpenStack charms so that her users can consume compute + and block storage services from the underlying vSphere cloud - inception + FTW! + + Greg works in a big POWER shop; he's able to deploy OpenStack with + Ubuntu and Charm making use of his big-iron servers for hypervisors (yes + - even without Ubuntu on them). + + Tina wants to write a new openstack charm; she gets started by typing: + + charm create -t openstack + + and it has all the standard scaffolding that the openstack-charmers team + likes to see! [ASSUMPTIONS] + [RISKS] + Regression in functionality - /next branch approach should help mitigate this. + [IN SCOPE] + All charms owned by the openstack-charmers team. + [OUT OF SCOPE] + Execution of tests on a per-commit/merge basis. + Regular testing. + (the above covered elsewhere) + [USER ACCEPTANCE] + Use cases can be fulfilled using the OpenStack charms and associated tooling. + [RELEASE NOTE/BLOG] + TBC
-- OpenStack Charm work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-openstack-charms -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
