Weekly Heat (Orchestration) meeting

The heat Orchestration project team holds a meeting in #openstack-meeting:

Everyone is welcome.

The blueprints that are used as a basis for the heat project can be found at https://blueprints.launchpad.net/heat

Next meeting

Review last week's actions
- shardy post agenda before meeting
Packaging priorities/timeline
- PyPi (requested by user on IRC)
- packaging for Ubuntu?
State of ubuntu host/guest support
- Many (most?) users are using ubuntu, but most of our testing in on Fedora
- Many (most?) key-features don't work with ubuntu guest images
- Add ubuntu host/guest as primary targets for integration testing?
- Need an improved getting started for ubuntu (packaged openstack not devstack)
RHEL/CentOS support?
- Do we want/need to support RHEL/CentOS (packages via EPEL?) yet?
- Getting started for RHEL6+RHOS should hopefully be pretty similar to the existing Fedora one, testing needed
Way forward for integration tests
- mentioned last meeting but no conclusion reached - how to get better value from the effort invested in integration tests? Tempest? Shared responsibility for maintaining/monitoring tests manually? Email spam on failure? Other?
jpeeler to update re state of snapshot/prebuild investigation, decide what approach if any should be pursued

Publish the agenda 24h in advance
Mail the agenda to the list and invite participants
Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
Use http://meetbot.debian.net/Manual.html to get an automatic summary
Prepare an outline for the meeting to speed things up (see http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html for an actual example)