Difference between revisions of "Meetings/HeatAgenda"

Latest revision as of 08:56, 25 September 2019

Weekly Heat (Orchestration) meeting
The heat Orchestration project (see also wiki) team holds weekly meeting at:

Wednesdays at 1300 UTC in #heat

Everyone is welcome, feel free to add topics before or at the beginning of meetings.

Meeting minutes

Meeting Agendas

Agenda (2019-09-25 1300 UTC)

Designate V1 resource types
Release Heat 13.0.0rc1
Summit and PTG plan

Agenda (2019-04-03 1300 UTC)

Agenda (2019-03-20 1400 UTC)

Agenda (2019-03-06 1400 UTC)

Single group type for all
FF and FFE https://storyboard.openstack.org/#!/worklist/563
Converting legacy Zuul jobs
Endpoint type configuration

Agenda (2019-02-20 0800 UTC)

Single group type for all

Agenda (2019-02-13 0800 UTC)

Heat-Stein-Target-List . A working list for targets
Hidden personality property from OS::Nova::Server

Agenda (2019-01-30 0800 UTC)

Do we have a way of tagging high-priority stories for the release?
This seems like it would be a good feature for Stein

Agenda (2019-01-23 0800 UTC)

Propose to Deprecate OS::Heat::DeployedServer
PTG survey
Features

@@ Line 1: / Line 1: @@
-= Weekly Heat (Orchestration) meeting =
+<b>Weekly Heat (Orchestration) meeting</b><br>
-The [https://launchpad.net/heat heat] Orchestration project (see also [https://wiki.openstack.org/wiki/Heat wiki]) team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code> at alternating times:
+The [https://launchpad.net/heat heat] Orchestration project (see also [https://wiki.openstack.org/wiki/Heat wiki]) team holds weekly meeting at:
-* Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=20&min=0&sec=0 2000 UTC]
+* Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=13&min=0&sec=0 1300 UTC] in <code><nowiki>#heat</nowiki></code>
-* Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=12&min=0&sec=0 1200 UTC]
-Our first 1200 UTC meeting is Wednesday 28th May, 2014.
+Everyone is welcome, feel free to add topics before or at the beginning of meetings.
-Everyone is welcome.
-The blueprints that are used as a basis for [https://launchpad.net/heat the heat project] can be found at https://blueprints.launchpad.net/heat
+== Meeting minutes ==
+* [http://eavesdrop.openstack.org/meetings/heat/2019/ 2019 Heat meeting archive]
+* [http://eavesdrop.openstack.org/meetings/heat/2018/ 2018 Heat meeting archive]
-=== Agenda (2014-09-17 1200 UTC) ===
+== Meeting Agendas ==
-* Review action items from last meeting
-* Adding items to the agenda
-* Critical issues sync
-=== Agenda (2014-09-10 2000 UTC) ===
+=== Agenda (2019-09-25 1300 UTC) ===
-* Review action items from last meeting
+* Designate V1 resource types
-* Adding items to the agenda
+* Release Heat 13.0.0rc1
-* Critical issues sync
+* Summit and PTG plan
-* FFE status
-* Integration tests
-=== Agenda (2014-09-03 1200 UTC) ===
+=== Agenda (2019-04-03 1300 UTC) ===
-* Review action items from last meeting
+* [https://review.openstack.org/#/c/645472/ Stein Template version?]
-* Adding items to the agenda
+* [https://review.openstack.org/#/c/648479/ technical vision reflection]
-* Can we have a grenade testing update (it would be good to know where we stand before releasing)?
+* [https://review.openstack.org/#/c/649220/ multi-clouds doc]
-* <other stuff>
-=== Agenda (2014-08-27 2000 UTC) ===
+=== Agenda (2019-03-20 1400 UTC) ===
-* Review action items from last meeting
+* [https://etherpad.openstack.org/p/legacy-job-bionic Converting legacy Zuul jobs]
-* Adding items to the agenda
+* Cycle highlights
-* [https://launchpad.net/heat/+milestone/juno-3 Juno blueprint status]
+* [https://review.openstack.org/#/q/topic:release-heat+(status:open+OR+status:merged) Heat Release]
-* juno-3 milestone release management
+* [https://governance.openstack.org/tc/reference/technical-vision.html Technical Vision Reflection]
-* [https://review.openstack.org/#/c/116703/ Mission Statement]
-* Critical issues sync
-=== No Meeting 2014-08-20 ===
+=== Agenda (2019-03-06 1400 UTC) ===
-This meeting is cancelled because a lot of Heat folks will be at the mid-cycle meetup
+* Single group type for all
+* FF and FFE https://storyboard.openstack.org/#!/worklist/563
+* [https://etherpad.openstack.org/p/legacy-job-bionic Converting legacy Zuul jobs]
+* [http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002925.html Endpoint type configuration]
-=== Agenda (2014-08-13 2000 UTC) ===
+=== Agenda (2019-02-20 0800 UTC) ===
-* Review action items from last meeting
+* Single group type for all
-* Adding items to the agenda
-* Mid-cycle meet-up
-* Feature Proposal Freeze
-* Update replace with dependencies
-* Critical issues sync
-=== Agenda (2014-08-06 1200 UTC) ===
+=== Agenda (2019-02-13 0800 UTC) ===
-* Review action items from last meeting
+* [https://storyboard.openstack.org/#!/worklist/563 Heat-Stein-Target-List] . A working list for targets
-* Adding items to the agenda
+* Hidden personality property from OS::Nova::Server
-* Keeping up to date on the Heat mid-cycle meet-up
-* Critical issues sync
-=== Agenda (2014-07-30 2000 UTC) ===
+=== Agenda (2019-01-30 0800 UTC) ===
-* Review action items from last meeting
-* Adding items to the agenda
-* Spec approval criteria - (suggest we *can* approve after 3 * +2)
-* [[Governance/TechnicalCommittee/Heat_Gap_Coverage|Heat Gap Coverage]] plan
-* Scaling group member health maintenance
-* Using rally for Heat benchmark and quotas patches
-* Critical issues sync
-== Meeting minutes ==
+* Do we have a way of tagging high-priority stories for the release?
-* [http://eavesdrop.openstack.org/meetings/heat/2014/ 2014 Heat meeting archive]
+* [https://storyboard.openstack.org/#!/story/2003579 This] seems like it would be a good feature for Stein
-* [http://eavesdrop.openstack.org/meetings/heat/2013/ 2013 Heat meeting archive]
-* [http://eavesdrop.openstack.org/meetings/heat/2012/ 2012 Heat meeting archive]
+=== Agenda (2019-01-23 0800 UTC) ===
-== Meeting organizers ==
+* Propose to Deprecate OS::Heat::DeployedServer
-* Publish the agenda 24h in advance
+* PTG survey
-* Mail the agenda to the list and invite participants
+* Features
-* 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