Difference between revisions of "Meetings/HeatAgenda"
< Meetings
(→Next meeting) |
(→Weekly Heat (Orchestration) meeting) |
||
| Line 18: | Line 18: | ||
* h3 blueprint status | * h3 blueprint status | ||
* (asalkeld) Single Config file? https://review.openstack.org/#/c/43406/ | * (asalkeld) Single Config file? https://review.openstack.org/#/c/43406/ | ||
| − | + | (shardy) yes, seems to be causing considerable confusion: http://lists.openstack.org/pipermail/openstack-dev/2013-August/014305.html | |
| − | |||
* (SpamapS) moving rackspace cloud server specific resources out of heat tree | * (SpamapS) moving rackspace cloud server specific resources out of heat tree | ||
* Open discussion | * Open discussion | ||
Revision as of 18:25, 27 August 2013
Contents
Weekly Heat (Orchestration) meeting
The heat Orchestration project team holds a meeting in #openstack-meeting:
- Wednesdays at 2000 UTC
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
The next meeting will be:
- Wed Aug 28 2013 at 2000 UTC
Agenda
- Review last week's actions
- Reminder re Havana_Release_Schedule FeatureProposalFreeze
- h3 blueprint status
- (asalkeld) Single Config file? https://review.openstack.org/#/c/43406/
(shardy) yes, seems to be causing considerable confusion: http://lists.openstack.org/pipermail/openstack-dev/2013-August/014305.html
- (SpamapS) moving rackspace cloud server specific resources out of heat tree
- Open discussion
Previous meetings
Meeting organizers
- 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
- Mail the automatic summary as a reply to the invitation
