Difference between revisions of "Meetings/TechnicalCommittee/Heat Gap Coverage"
(Created page with "The following issues were identified as part of the [https://etherpad.openstack.org/p/heat-gap-analysis Heat Gap Analysis] that was [http://eavesdrop.openstack.org/meetings/tc...") |
(No difference)
|
Revision as of 13:14, 17 July 2014
The following issues were identified as part of the Heat Gap Analysis that was discussed by the Technical Committee on 15 July 2014.
Mission statement
Heat has a mission statement on its wiki page, but it needs to be proposed formally to the governance repo.
- Owner: zaneb
- Milestone: juno-3
Upgrade testing with Grenade
In order to verify upgradability to new versions of Heat, we need to add it to the Grenade test suite. A patch has already been proposed, and work is ongoing to get it ready to be merged.
- Owner: shardy
- Milestone: juno-3
Improved functional testing with Tempest
Because we have since only recently had the ability to launch full-featured images in the gate test, Heat is not well covered by functional (scenario) Tempest tests. There are a number of plans in place to address this:
- Core team members will write more tests
- Rackspace QE will contribute some of their tests to Tempest
- HP developers will work partly on Tempest tests as they get up to speed on Heat
There are a number of proposed patches already under review:
- https://review.openstack.org/#/c/69726/
- https://review.openstack.org/#/c/81909/
- https://review.openstack.org/#/c/82282/
- https://review.openstack.org/#/c/89564/
- https://review.openstack.org/#/c/89656/
- https://review.openstack.org/#/c/89790/
- https://review.openstack.org/#/c/90143/
- https://review.openstack.org/#/c/92731/
- https://review.openstack.org/#/c/94551/
- https://review.openstack.org/#/c/94590/
- https://review.openstack.org/#/c/100142/
- https://review.openstack.org/#/c/103198/
- https://review.openstack.org/#/c/103467/
- https://review.openstack.org/#/c/103775/
While many are awaiting a response to feedback, it also appears that a lack of review bandwidth in Tempest is delaying progress. A possible future move to having projects own their own functional tests would likely help alleviate this.
- Owner:
- Milestone: