Revision as of 16:40, 10 March 2015

Weekly Containers Team Meeting

The OpenStack Containers Team holds public meetings. We meet in #openstack-meeting-alt on alternating Tuesdays on the following schedule:

2015-03-10	UTC 2200 Tuesday	http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20150310T22
2015-03-17	UTC 1600 Tuesday	http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20150317T16
2015-03-24	UTC 2200 Tuesday	http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20150324T22
2015-03-31	UTC 1600 Tuesday	http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20150331T16

Please feel free to add items to the agenda below with your name and we'll cover them.

Roll Call
Announcements
- 1) Proposal to add Magnum to the OpenStack git namespace
  - #link https://review.openstack.org/161080 Magnum Governance Review
- 2) Magnum Release #2
  - #link about:blank Second Release Announcement for Magnum
Review Action Items (From Midcycle)
- sdake: To think of a name for new stackforge heat-kubernetes repo.
- sdake: To schedule a meeting with Lars to discuss new repo, and what it means to keep-it-simple.
  - Status: COMPLETE. Scheduled for 2015-03-11.
Blueprint/Task Review
- Discuss how to implement Bay status
  - When creating a bay, we use Heat to deploy Nova instances. There is not currently an event feed from Heat that we can subscribe to. Polling Heat for status changes is not elegant. How would we like to address this? Current discussion to reference:
  - #link http://lists.openstack.org/pipermail/openstack-dev/2015-March/058619.html Expression of Bay Status
  - #link Expression of Bay Status When polling heat set bay status
Open Discussion

@@ Line 26: / Line 26: @@
 ** sdake: To think of a name for new stackforge heat-kubernetes repo.
 ** sdake: To schedule a meeting with Lars to discuss new repo, and what it means to keep-it-simple.
-* Blueprint Review
+*** Status: COMPLETE. Scheduled for 2015-03-11.
+* Blueprint/Task Review
+** Discuss how to implement Bay status
+*** When creating a bay, we use Heat to deploy Nova instances. There is not currently an event feed from Heat that we can subscribe to. Polling Heat for status changes is not elegant. How would we like to address this? Current discussion to reference:
+*** #link http://lists.openstack.org/pipermail/openstack-dev/2015-March/058619.html Expression of Bay Status
+*** #link Expression of Bay Status When polling heat set bay status
 * Open Discussion