Openstack Integration Testing
Since Diablo, Openstack continues to grow at a rapid pace. As it will likely continue its pace throughout the Essex & P cycles, we need to determine which components, functionality and configurations matter most to us and how to test. With Juju driving automated complex deployment testing, we should drill down on specific areas of the stack that are critical to the success Ubuntu Cloud LTS. We should also consider how our testing can make use of upstream's existing QA infrastructure and how our efforts can benefit the Openstack community as a whole.
Blueprint information
- Status:
- Complete
- Approver:
- Dave Walker
- Priority:
- High
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Adam Gandelman
- Definition:
- Approved
- Series goal:
- Accepted for precise
- Implementation:
-
Implemented
- Milestone target:
-
ubuntu-12.04-beta-2
- Started by
- Adam Gandelman
- Completed by
- Robbie Williamson
Whiteboard
Work items:
[gandelman-a] Deploy openstack-
Define re-testing triggers and implement as designed: DONE
Collaborate on defining charm use workflow between OpenStack and Ubuntu @ UDS Q: POSTPONED
Port or rewrite existing stress tests and push upstream: POSTPONED
[smoser] devstack working from ubuntu packages proper: POSTPONED
Work Items
Dependency tree

* Blueprints in grey have been implemented.