Blueprint changed by Chuck Short: Whiteboard changed: UDS Discussion Points: Welcome to Ubuntu Developer Summit! #uds-p #track #topic What was done? - Setup of Openstack Continous Integration What needs to be done? - Testing swift - Functional Testing - + Things that will help going fowards: - Centralised dependency management upstream. - - Formalise discussion - + - Formalise discussion + Plans for Quantal Three versions: - - precise-essex - - precise-folsom - - quantal-folsom - + - precise-essex + - precise-folsom + - quantal-folsom + Full testing of swift - - Rewrite of charm to support deployment on two nodes (fits in the lab). + - Rewrite of charm to support deployment on two nodes (fits in the lab). Upgrade testing - Research good framework for automated/coordinated upgrade tests - - DB migration testing with different DB backends. - - activity upstream to support upgrade testing. - - Essex -> Folsom - - 12.04 - quantal - - Just 12.04 + - DB migration testing with different DB backends. + - activity upstream to support upgrade testing. + - Essex -> Folsom + - 12.04 - quantal + - Just 12.04 Burn testing - - Instance cycling - part of tempest. - + - Instance cycling - part of tempest. + Posting back to gerrit for pre-commit: - - +1/-1. - - Need to find a good way of reporting back to ensure that we don't get to many false positives. + - +1/-1. + - Need to find a good way of reporting back to ensure that we don't get to many false positives. Different deployment options: Testing of different database backends Image testing in the lab: - - Benchmarking. - - Function. - + - Benchmarking. + - Function. + API testing: - - mgz - contact for collaborative effort to test ec2 compatibility. - - space on openstack API testing. - https://wiki.ubuntu.com/ServerTeam/OpenStack + - mgz - contact for collaborative effort to test ec2 compatibility. + - space on openstack API testing. + https://wiki.ubuntu.com/ServerTeam/OpenStack ACTIONS: Document tested and referenced deployment configs. Deploy release cloud images as part of overall testing. Split database migrations out of deployment charms and into own tests. Clean up Juju deployment tool, move to its own project Integration of reporting to gerrit upstream. Enable burn/load/performance testing on a regular basis in the lab (or on new hardware). Sort out way forward with current Openstack dev on current Ubuntu stable. [zulcss] communicate what we are testing and current results on a regular basis. Setup testing of swift in the lab. Investigate testing of awsome on the lab Setup testing of juju against deployed openstack in the lab. + + User Stories + + Alex is a developer who wants to test the very latest cutting edge Ubuntu packages on his test server. + Chuck is an ubuntu developer who want to test his packaging changes before merging them into the Archive. + + Assumptions: + - Essex/Precise will be tested + - Folsom/Precise will be tested + - Folsom/Quantal will be tested
-- Openstack QA https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-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
