Blueprint changed by Ryan Beisner: Whiteboard changed: [USER STORIES] - Charlie wants to use the OpenStack charms to run CI in a multi-node scalable environment against every upstream commit to master. Charlie needs to set up CI in house to deploy from source and run tempest or other tests on every commit. + Johnny is an OpenStack charm developer who plans to propose and land changes to the OpenStack charms in alignment with product strategy, new toolchain features, bug fixes, and related work items. He seeks confidence that his changes do not cause regression of functionality, as well as confirmation of the new features or fixes. He will add unit and functional test coverage to represent his contributions as he seeks timely feedback through automated unit, lint, integrated and functional testing of each proposed change. + + Charlene is an OpenStack package maintainer who is responsible for + building and releasing new Ubuntu packages in cadence with upstream + releases. Prior to pushing packages into the archives, she seeks + confidence in his proposed packages, that they are functional and free + of regression. She also seeks confirmation of bug resolution via + automated deployment testing. + + Emmanuel is an Openstack Administrator who wants to upgrade from Juno to + Kilo. He needs confidence that the upgrade path is well-tested. + + Bob is a Cloud Consultant who wants to have common customer topologies + exercised against OpenStack charm development. Bob provides cloud + configurations, expressed as juju-deployer bundles, so that they may be + included in automated testing. + + Shawn is a Juju Core developer who works on a team that provides new + features in proposed and development versions of Juju, to ultimately be + released into Juju stable. He seeks confidence that the new features do + not cause regression of functionality, and that the new features + function as intended with regard to the OpenStack charms. + + Charlie wants to use the OpenStack charms to run CI in a multi-node + scalable environment against every upstream commit to master. Charlie + needs to set up CI in house to deploy from source and run tempest or + other tests on every commit. [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG]
-- OpenStack QA for 15.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-w-openstack-qa -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
