https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Adrian+Otto&feedformat=atomOpenStack - User contributions [en]2024-03-28T16:52:10ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=155207Meetings/Containers2017-07-11T15:58:14Z<p>Adrian Otto: /* Agenda for 2017-06-13 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on alternating Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-06-27 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170627T16<br />
|-<br />
| 2017-07-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170711T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-07-17 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** 1) adrian_otto to target https://blueprints.launchpad.net/magnum/+spec/integrate-kuryr-kubernetes for Pike, with a comment that it's okay for this to slip to Queens if needed.<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** strigazi: Flatten attributes bp is stuck, what to do next. We can copy over the most important parameters in cluster for now. More during the meeting. Related patch for docker_volume_size : https://review.openstack.org/#/c/471766/<br />
** strigazi: Input for the swarm-mode driver https://review.openstack.org/#/c/427761/<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=154662Meetings/Containers2017-06-13T16:35:03Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on alternating Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-06-27 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170627T16<br />
|-<br />
| 2017-07-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170711T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-06-13 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** 1) adrian_otto to target https://blueprints.launchpad.net/magnum/+spec/integrate-kuryr-kubernetes for Pike, with a comment that it's okay for this to slip to Queens if needed.<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** strigazi: Flatten attributes bp is stuck, what to do next. We can copy over the most important parameters in cluster for now. More during the meeting. Related patch for docker_volume_size : https://review.openstack.org/#/c/471766/<br />
** strigazi: Input for the swarm-mode driver https://review.openstack.org/#/c/427761/<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=154380Meetings/Containers2017-05-30T16:39:35Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on alternating Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-06-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170613T16<br />
|-<br />
| 2017-06-27 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170627T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-06-13 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** 1) adrian_otto to target https://blueprints.launchpad.net/magnum/+spec/integrate-kuryr-kubernetes for Pike, with a comment that it's okay for this to slip to Queens if needed.<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=153558Meetings/Containers2017-04-25T16:27:05Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on alternating Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-05-16 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170516T16<br />
|-<br />
| 2017-05-30 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170530T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-05-16 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=153554Meetings/Containers2017-04-25T15:58:42Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-04-25 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** strigazi: 30mb compressed / uncompressed 111mb containerized heat-agent based on alpine linux. https://hub.docker.com/r/strigazi/heat-container-agent/tags/<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152791Meetings/Containers2017-03-28T16:49:55Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-04-04 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170404T16<br />
|-<br />
| 2017-04-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170411T16<br />
|-<br />
| 2017-04-18 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170418T16<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-28 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152789Meetings/Containers2017-03-28T15:58:02Z<p>Adrian Otto: /* Agenda for 2017-03-21 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
| 2017-04-04 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170404T16<br />
|-<br />
| 2017-04-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170411T16<br />
|-<br />
| 2017-04-18 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170418T16<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-28 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152514Meetings/Containers2017-03-20T22:56:18Z<p>Adrian Otto: /* Agenda for 2017-03-21 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
| 2017-04-04 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170404T16<br />
|-<br />
| 2017-04-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170411T16<br />
|-<br />
| 2017-04-18 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170418T16<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-21 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** I have appointed Spyros Tigazis as our release liaison for Magnum.<br />
*** #link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management Release Management<br />
* Review Action Items<br />
** (none)<br />
* What should we call Magnum's generic OSC name stem?<br />
** <code>openstack cluster</code> is taken by Senlin, so we need an alternative.<br />
*** #link https://review.openstack.org/#/c/446179/3/setup.cfg@33<br />
*** Choices:<br />
**** <code>coe cluster</code><br />
**** <code>coe</code><br />
**** <code>infra</code><br />
**** <code>mcluster</code> (May not fit guidelines, not sure)<br />
**** Eliminated from consideration <code>c_cluster</code>, <code>coe_cluster</code>, <code>coe-cluster</code>, <code>magnum</code>, <code>magnum cluster</code>, <code>ccluster</code><br />
*** Dean Troyer suggested "infra" as reflected in the above review.<br />
*** Note: An OSC noun may have spaces in it, but no dashes or underscores. So if we select "coe cluster" as the name it will yield commands like this:<br />
**** <code>openstack coe cluster create ...</code><br />
*** Note: Our catalog name will remain <code>container_infra</code> and our Service Type Authority service_type will probably be <code>coe-cluster</code>.<br />
**** #link https://review.openstack.org/447694 Add coe-cluster service type<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152511Meetings/Containers2017-03-20T22:01:39Z<p>Adrian Otto: /* Agenda for 2017-03-21 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
| 2017-04-04 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170404T16<br />
|-<br />
| 2017-04-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170411T16<br />
|-<br />
| 2017-04-18 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170418T16<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-21 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** I have appointed Spyros Tigazis as our release liaison for Magnum.<br />
*** #link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management Release Management<br />
* Review Action Items<br />
** (none)<br />
* What should we call Magnum's generic OSC name stem?<br />
** <code>openstack cluster</code> is taken by Senlin, so we need an alternative.<br />
*** #link https://review.openstack.org/#/c/446179/3/setup.cfg@33<br />
*** Choices:<br />
**** <code>coe cluster</code><br />
**** <code>coe</code><br />
**** <code>infra</code><br />
**** <code>mcluster</code> (May not fit guidelines, not sure)<br />
**** Eliminated from consideration <code>c_cluster</code>, <code>coe_cluster</code>, <code>coe-cluster</code>, <code>magnum</code>, <code>magnum cluster</code>, <code>ccluster</code><br />
*** Dean Troyer suggested "infra" as reflected in the above review.<br />
*** Note that an OSC noun may have spaces in it, but no dashes or underscores. So if we select "coe cluster" as the name it will yield commands like this:<br />
**** <code>openstack coe cluster create ...</code><br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152493Meetings/Containers2017-03-20T19:33:18Z<p>Adrian Otto: /* Agenda for 2017-03-21 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
| 2017-04-04 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170404T16<br />
|-<br />
| 2017-04-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170411T16<br />
|-<br />
| 2017-04-18 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170418T16<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-21 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** I have appointed Spyros Tigazis as our release liaison for Magnum.<br />
*** #link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management Release Management<br />
* Review Action Items<br />
** (none)<br />
* What should we call Magnum's generic OSC name stem?<br />
** `openstack cluster` is taken by Senlin, so we need an alternative.<br />
*** #link https://review.openstack.org/#/c/446179/3/setup.cfg@33<br />
*** Choices:<br />
**** c_cluster<br />
**** coe_cluster<br />
**** coe<br />
**** mcluster<br />
**** infra<br />
*** Dean Troyer suggested "infra" as reflected in the above review. Adrian Otto does not like it, but will yield his POV if there is consensus to the contrary.<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152489Meetings/Containers2017-03-20T18:45:54Z<p>Adrian Otto: /* Agenda for 2017-03-28 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
| 2017-04-04 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170404T16<br />
|-<br />
| 2017-04-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170411T16<br />
|-<br />
| 2017-04-18 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170418T16<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-21 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** I have appointed Spyros Tigazis as our release liaison for Magnum.<br />
*** #link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management Release Management<br />
* Review Action Items<br />
** (none)<br />
* What should we call Magnum's generic OSC name stem?<br />
** `openstack cluster` is taken by Senlin, so we need an alternative.<br />
*** #link https://review.openstack.org/#/c/446179/3/setup.cfg@33<br />
*** Choices:<br />
**** c_cluster<br />
**** coe_cluster<br />
**** mcluster<br />
**** infra<br />
*** Dean Troyer suggested "infra" as reflected in the above review. Adrian Otto does not like it, but will yield his POV if there is consensus to the contrary.<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152434Meetings/Containers2017-03-16T17:05:46Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
| 2017-04-04 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170404T16<br />
|-<br />
| 2017-04-11 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170411T16<br />
|-<br />
| 2017-04-18 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170418T16<br />
|-<br />
| 2017-04-25 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170425T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-28 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** I have appointed Spyros Tigazis as our release liaison for Magnum.<br />
*** #link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management Release Management<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=152433CrossProjectLiaisons2017-03-16T17:02:27Z<p>Adrian Otto: /* Release management */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| I18n || Ian Y. Choi || ianychoi<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Victor Morales || electrocucaracha<br />
|-<br />
| Nova || || <br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Ian Cordasco || sigmavirus<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || Ian Y. Choi || ianychoi<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Monasca || Witek Bedyk || witek<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Dariusz Smigiel || dasm<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| Oslo || ChangBo Guo || gcb<br />
|-<br />
| PuppetOpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega || tenobreg/tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Storlets || Eran Rom || eranrom<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Alexander Chadin || alexchadin<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || - || -<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Aimee Ukasick || aimeeu<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Alexander Bashmakov || abashmak<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Richard Jones || r1chardj0n3s<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Richard Avelar || ravelar<br />
|-<br />
| Kolla || Sayantani Goswami || sayantani01<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || John Davidge || john-davidge<br />
|-<br />
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || Trevor McCasland || trevormc<br />
|-<br />
| Watcher || Prudhvi Rao Shedimbi || pshedimb<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Manila || Tom Barron || tbarron<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco|| flaper87<br />
|-<br />
| I18n || Ian Y. Choi || ianychoi<br />
|-<br />
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || - || -<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Megan Rossetti || MeganR<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer (or a person who is not a core reviewer but agreed & approved by PTL) for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Watcher || Yumeng Bao || Yumeng <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Kevin Benton || kevinbenton || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || || ||<br />
|-<br />
| || Jim Rollenhagen || jroll || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Akihiro Motoki || amotoki || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|-<br />
| TripleO / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO<br />
|-<br />
| Nova / Watcher || || ||<br />
|-<br />
| || Ed Leafe || edleafe || Nova liaison for Watcher<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=152141Meetings/Containers2017-03-14T16:00:05Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170314T16<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-14 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=151888Meetings/Containers2017-03-07T16:00:53Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-07 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170307T16<br />
|-<br />
| 2017-03-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170314T16<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-03-07 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
** Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
*** #link https://releases.openstack.org/reference/release_models.html<br />
** Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated.<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=151886Meetings/Containers2017-03-07T15:51:08Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-07 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170307T16<br />
|-<br />
| 2017-03-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170314T16<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-02-28 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
** Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
*** #link https://releases.openstack.org/reference/release_models.html<br />
** Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated.<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=151885Meetings/Containers2017-03-07T15:49:53Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-03-07 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170307T16<br />
|-<br />
| 2017-03-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170314T16<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-02-28 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** (none)<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
** Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated.<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=151577Meetings/Containers2017-02-28T16:00:25Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2017-02-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170228T16<br />
|-<br />
| 2017-03-07 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170307T16<br />
|-<br />
| 2017-03-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170314T16<br />
|-<br />
| 2017-03-21 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170321T16<br />
|-<br />
| 2017-03-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170328T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-02-28 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) Fedora Atomic will be making a release tomorrow to address a kernel CVE.<br />
** 2) We have a new policy document:<br />
*** #link https://docs.openstack.org/developer/magnum/policies.html<br />
*** This document details our development philosophy, links to our guiding principles and community code of conduct, as well as details about how we make decisions and manage our team. If you have not reviewed the final version yet, I ask that you please do so, as we are all expected to conform to it. Some key takeaways are: that we value incremental iterative improvement, and a willingness to merge code before it's perfect in the interest of continued forward advancement. Unanimous consent is not required to reach Team Consensus. Our PTL decides when Team Consensus is reached as needed.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Open Discussion<br />
** Architecture Image is Outdated on Magnum wiki: https://wiki.openstack.org/wiki/Magnum, danil has created an image(http://imgur.com/a/af5BP) which can be reviewed and magnum wiki can be updated.<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=PTG/Pike/Etherpads&diff=151391PTG/Pike/Etherpads2017-02-22T13:58:07Z<p>Adrian Otto: /* Wednesday -> Friday */</p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Atlanta. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
The [https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms discussion rooms spreadsheet] can be used to schedule time in a collaboration room with a projector.<br />
<br />
=== Only Monday ===<br />
<br />
* Stewardship workgroup: https://etherpad.openstack.org/p/AtlantaPTG-SWG<br />
* API workgroup: https://etherpad.openstack.org/p/ptg-architecture-workgroup<br />
<br />
<br />
=== Monday -> Tuesday ===<br />
<br />
* Community App Catalog<br />
* Documentation / I18n: https://etherpad.openstack.org/p/docs-i18n-ptg-pike<br />
* Horizon: https://etherpad.openstack.org/p/horizon-ptg-pike<br />
* Infrastructure: https://etherpad.openstack.org/p/infra-ptg-pike<br />
* Kolla: https://etherpad.openstack.org/p/kolla-pike-ptg-schedule<br />
* OpenStackAnsible: https://etherpad.openstack.org/p/osa-ptg-pike<br />
* OpenStackClient: https://etherpad.openstack.org/p/osc-ptg-pike<br />
* OpenStack Charms: https://etherpad.openstack.org/p/openstack-charms-ptg-pike<br />
* Oslo: https://etherpad.openstack.org/p/oslo-ptg-pike<br />
* Packaging RPM: https://etherpad.openstack.org/p/ptg-atlanta-packaging-rpm<br />
* Quality Assurance: https://etherpad.openstack.org/p/qa-ptg-pike<br />
* Rally / Performance workgroup: https://etherpad.openstack.org/p/ptg-performance-team<br />
* RefStack / Interop workgroup: https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG<br />
* Release Goal: python 3.5 support: https://etherpad.openstack.org/p/ptg-pike-python35<br />
* Release Goal: WSGI supportː https://etherpad.openstack.org/p/ptg-pike-wsgi<br />
* Release Mgmt / Stable maint / Requirements: https://etherpad.openstack.org/p/relmgt-stable-requirements-ptg-pike<br />
* Security: https://etherpad.openstack.org/p/ptg-security-team<br />
<br />
=== Only Tuesday ===<br />
<br />
* Architecture workgroup (+API WG): https://etherpad.openstack.org/p/ptg-architecture-workgroup<br />
<br />
<br />
=== Wednesday -> Thursday ===<br />
<br />
* Congress: https://etherpad.openstack.org/p/congress-ptg-pike<br />
* Dragonflow<br />
* Karbor: https://etherpad.openstack.org/p/karbor-ptg-pike<br />
* Magnum: https://etherpad.openstack.org/p/magnum-ptg-pike<br />
* Manila: https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
* Sahara https://etherpad.openstack.org/p/sahara-ptg-pike<br />
* Storlets: https://etherpad.openstack.org/p/storlets-pike-design-summit<br />
* Tricircle: https://etherpad.openstack.org/p/tricircle-pike-design-topics<br />
* Trove: https://etherpad.openstack.org/p/trove-pike-ptg-topics<br />
* Watcher: https://etherpad.openstack.org/p/pike-watcher-ptg<br />
<br />
<br />
=== Wednesday -> Friday ===<br />
<br />
* Barbican: https://etherpad.openstack.org/p/ptg-barbican-pike<br />
* Cinder: https://etherpad.openstack.org/p/ATL-cinder-ptg-planning<br />
* Glance: https://etherpad.openstack.org/p/glance-pike-ptg-planning , https://etherpad.openstack.org/p/glance-pike-ptg-schedule<br />
* Heat: https://etherpad.openstack.org/p/heat-pike-ptg-sessions<br />
* Ironic: https://etherpad.openstack.org/p/ironic-pike-ptg<br />
* Keystone: https://etherpad.openstack.org/p/keystone-pike-ptg<br />
* Magnum: https://etherpad.openstack.org/p/magnum-ptg-pike<br />
* Mistral: https://etherpad.openstack.org/p/mistral-ptg-pike<br />
* Neutron: https://etherpad.openstack.org/p/neutron-ptg-pike<br />
* Nova: https://etherpad.openstack.org/p/nova-ptg-pike<br />
* Octavia: https://etherpad.openstack.org/p/octavia-ptg-pike<br />
* Swift: https://etherpad.openstack.org/p/swift-ptg-pike<br />
* TripleO: https://etherpad.openstack.org/p/tripleo-ptg-pike</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=PTG/Pike/Etherpads&diff=151387PTG/Pike/Etherpads2017-02-22T13:54:50Z<p>Adrian Otto: </p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Atlanta. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
The [https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms discussion rooms spreadsheet] can be used to schedule time in a collaboration room with a projector.<br />
<br />
=== Only Monday ===<br />
<br />
* Stewardship workgroup: https://etherpad.openstack.org/p/AtlantaPTG-SWG<br />
* API workgroup: https://etherpad.openstack.org/p/ptg-architecture-workgroup<br />
<br />
<br />
=== Monday -> Tuesday ===<br />
<br />
* Community App Catalog<br />
* Documentation / I18n: https://etherpad.openstack.org/p/docs-i18n-ptg-pike<br />
* Horizon: https://etherpad.openstack.org/p/horizon-ptg-pike<br />
* Infrastructure: https://etherpad.openstack.org/p/infra-ptg-pike<br />
* Kolla: https://etherpad.openstack.org/p/kolla-pike-ptg-schedule<br />
* OpenStackAnsible: https://etherpad.openstack.org/p/osa-ptg-pike<br />
* OpenStackClient: https://etherpad.openstack.org/p/osc-ptg-pike<br />
* OpenStack Charms: https://etherpad.openstack.org/p/openstack-charms-ptg-pike<br />
* Oslo: https://etherpad.openstack.org/p/oslo-ptg-pike<br />
* Packaging RPM: https://etherpad.openstack.org/p/ptg-atlanta-packaging-rpm<br />
* Quality Assurance: https://etherpad.openstack.org/p/qa-ptg-pike<br />
* Rally / Performance workgroup: https://etherpad.openstack.org/p/ptg-performance-team<br />
* RefStack / Interop workgroup: https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG<br />
* Release Goal: python 3.5 support: https://etherpad.openstack.org/p/ptg-pike-python35<br />
* Release Goal: WSGI supportː https://etherpad.openstack.org/p/ptg-pike-wsgi<br />
* Release Mgmt / Stable maint / Requirements: https://etherpad.openstack.org/p/relmgt-stable-requirements-ptg-pike<br />
* Security: https://etherpad.openstack.org/p/ptg-security-team<br />
<br />
=== Only Tuesday ===<br />
<br />
* Architecture workgroup (+API WG): https://etherpad.openstack.org/p/ptg-architecture-workgroup<br />
<br />
<br />
=== Wednesday -> Thursday ===<br />
<br />
* Congress: https://etherpad.openstack.org/p/congress-ptg-pike<br />
* Dragonflow<br />
* Karbor: https://etherpad.openstack.org/p/karbor-ptg-pike<br />
* Magnum: https://etherpad.openstack.org/p/magnum-ptg-pike<br />
* Manila: https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
* Sahara https://etherpad.openstack.org/p/sahara-ptg-pike<br />
* Storlets: https://etherpad.openstack.org/p/storlets-pike-design-summit<br />
* Tricircle: https://etherpad.openstack.org/p/tricircle-pike-design-topics<br />
* Trove: https://etherpad.openstack.org/p/trove-pike-ptg-topics<br />
* Watcher: https://etherpad.openstack.org/p/pike-watcher-ptg<br />
<br />
<br />
=== Wednesday -> Friday ===<br />
<br />
* Barbican: https://etherpad.openstack.org/p/ptg-barbican-pike<br />
* Cinder: https://etherpad.openstack.org/p/ATL-cinder-ptg-planning<br />
* Glance: https://etherpad.openstack.org/p/glance-pike-ptg-planning , https://etherpad.openstack.org/p/glance-pike-ptg-schedule<br />
* Heat: https://etherpad.openstack.org/p/heat-pike-ptg-sessions<br />
* Ironic: https://etherpad.openstack.org/p/ironic-pike-ptg<br />
* Keystone: https://etherpad.openstack.org/p/keystone-pike-ptg<br />
* Magnum: https://etherpad.openstack.org/p/magnum-pike-ptg-sessions<br />
* Mistral: https://etherpad.openstack.org/p/mistral-ptg-pike<br />
* Neutron: https://etherpad.openstack.org/p/neutron-ptg-pike<br />
* Nova: https://etherpad.openstack.org/p/nova-ptg-pike<br />
* Octavia: https://etherpad.openstack.org/p/octavia-ptg-pike<br />
* Swift: https://etherpad.openstack.org/p/swift-ptg-pike<br />
* TripleO: https://etherpad.openstack.org/p/tripleo-ptg-pike</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=151066Meetings/Containers2017-02-13T20:01:40Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2017-02-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170214T16<br />
|-<br />
| 2017-02-21 || No Meeting || We are skipping this meeting because of the PTG<br />
|-<br />
| 2017-02-28 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170228T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-02-14 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) Reminder: We will not have an IRC team meeting on 2017-02-21 because of the Atlanta PTG event.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Changing magnum projects from cycle-with-intermediary to cycle-with-milestones<br />
** #link https://releases.openstack.org/reference/release_models.html<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=150800Meetings/Containers2017-02-07T16:06:10Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2017-02-07 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170207T16<br />
|-<br />
| 2017-02-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170214T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-02-07 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) We will not have an IRC team meeting on 2017-02-21 because of the Atlanta PTG event.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Magnum&diff=150747Magnum2017-02-07T00:33:18Z<p>Adrian Otto: /* Getting Started / Download */</p>
<hr />
<div>Magnum is an OpenStack API service developed by the [[Teams/Containers|OpenStack Containers Team]] making container orchestration engines such as Docker Swarm, Kubernetes, and Apache Mesos available as first class resources in OpenStack. Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs that image in either virtual machines or bare metal in a cluster configuration. Click below for a ~2 minute demo of how the Magnum CLI works.<br />
<br />
<center><br />
[[File:Demo-Preview-Frame.png|none|link=https://vimeo.com/177327412|frame|400px]]<br />
</center><br />
<br />
__TOC__<br />
<br />
= Getting Started / Download =<br />
To get started with Magnum, see: [http://docs.openstack.org/developer/magnum/dev/quickstart.html Our Quickstart Guide]<br />
<br />
Downloads: <br />
* [http://tarballs.openstack.org/magnum/ magnum] <br />
* [http://tarballs.openstack.org/python-magnumclient/ python-magnumclient]<br />
<br />
= Contributing =<br />
<br />
The project is under active development by our OpenStack Containers Team. We [[Meetings/Containers|meet weekly by IRC]]. <br />
<br />
* We want you to [[Magnum/Contributing|contribute to Magnum]]!<br />
<br />
= Architecture =<br />
<br />
[[File:Magnum_architecture.png|center|800px|Magnum Architeture Diagram]]<br />
Bay Create/Update/Delete<br />
<br />
= Resources =<br />
* Launchpad Project Pages<br />
** [http://launchpad.net/magnum Magnum Launchpad Project] for Blueprints<br />
** [http://launchpad.net/python-magnumclient python-magnumclient Launchpad Project] for Blueprints<br />
* Mailing List<br />
** [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack Mailing List] for project related discussion<br />
*** Add [Magnum] to the subject line of new posts about this project.<br />
** [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Mailing List Archives] for current discussion.<br />
* Code Reviews<br />
** [https://review.openstack.org/#/q/status:open+magnum,n,z Gerrit Reviews]<br />
* Code Repository<br />
** git clone git://git.openstack.org/openstack/magnum<br />
* References<br />
**[[Magnum/Acronyms|Acronyms]]<br />
**[http://eavesdrop.openstack.org/irclogs/%23openstack-containers/ IRC Logs - OpenStack Containers]<br />
**[http://eavesdrop.openstack.org/meetings/containers/2016/ Meeting Minutes - OpenStack Containers]<br />
<br />
= IRC =<br />
<br />
Our developers use IRC in #openstack-containers on freenode for development discussion.<br />
<br />
= Meetings =<br />
<br />
* The weekly Containers [[Meetings/Containers|IRC meeting]] is held on Tuesdays at 1600 UTC [[Meetings/Containers|[schedule]]].<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Meeting Archive]<br />
<br />
= Users =<br />
* [http://home.cern CERN] - details on the [http://openstack-in-production.blogspot.fr blog]<br />
* (your group or organization here)<br />
<br />
= Frequently Asked Questions =<br />
'''1) How is Magnum is different from Nova?''' <br />
<br />
Magnum provides a purpose built API to manage application containers orchestration engines, which have a distinctly different life cycle and operations than Nova (machine) Instances. We actually use Nova instances to compose our Bays.<br />
<br />
'''2) How is Magnum different than Docker or Kubernetes?'''<br />
<br />
Magnum offers an asynchronous API that's compatible with Keystone, and a complete multi-tenancy implementation. It does not perform orchestration internally, and instead relies on OpenStack Orchestration. Magnum does leverage both Kubernetes and Docker as components.<br />
<br />
'''3) Is this the same thing as Nova-Docker?'''<br />
<br />
No, Nova-Docker is a virt driver for Nova that allows containers to be created as Nova instances. This is suitable for use cases when you want to treat a container like a lightweight machine. Magnum provides container orchestration engine management that is beyond the scope of Nova's API, and implements its own API to surface these features in a way that is consistent with other OpenStack services. Containers started on Magnum Bays are run on top of Nova instances that are created using Heat.<br />
<br />
'''4) Who is Magnum for?'''<br />
<br />
Magnum is for OpenStack cloud operators (public or private) who want to offer a self-service solution to provide a hosted containers service to their cloud users. Magnum simplifies the required integration with OpenStack, and allows for cloud users who can already launch cloud resources such as Nova Instances, Cinder Volumes, Trove Databases, etc. to also create container clusters (Bays) to run applications in an environment that provides advanced features that are beyond the scope of existing cloud resources. <br />
<br />
'''5) Will I get the same thing if I use the Docker resource in Heat?'''<br />
<br />
No, the Docker Heat resource does not provide a resource scheduler, or a choice of container technology used. It is specific to Docker, and uses Glance to store container images. It does not currently allow for layered image features, which can cause containers to take longer to start than if layered images are used with a locally cached base image. Magnum leverages all of the speed benefits that Docker offers, and implements Kubernetes and Mesos as alternate choices to Docker Swarm for container orchestration.<br />
<br />
'''6) What does multi-tenancy mean in Magnum (Is Magnum Secure)?'''<br />
<br />
Resources such as Bays started by Magnum can only be viewed and accessed by users of the tenant that created them. Bays are not shared, meaning that containers will not run on the same kernel as neighboring tenants. This is a key security feature that allows containers belonging to the same tenant to be tightly packed within the same Pods and Bays, but runs separate kernels (in separate Nova Instances) between different tenants. This is different than using a system like Kubernetes without Magnum, which was originally designed to be used only by a single tenant, and leaves the security isolation design up to the implementer. Using Magnum provides the same level of security isolation as Nova provides when running Virtual Machines belonging to different tenants on the same compute nodes.</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=150134Meetings/Containers2017-01-18T18:41:54Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2017-01-24 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170124T16<br />
|-<br />
| 2017-01-31 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170131T16<br />
|-<br />
| 2017-02-07 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170207T16<br />
|-<br />
| 2017-02-14 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170214T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-01-24 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) We are in feature freeze as of 2017-01-23<br />
** 2) We will not have an IRC team meeting on 2017-02-21 because of the Atlanta PTG event.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=150051Meetings/Containers2017-01-17T16:08:23Z<p>Adrian Otto: /* Agenda for 2017-01-17 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2017-01-17 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170117T16<br />
|-<br />
| 2017-01-24 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170124T16<br />
|-<br />
| 2017-01-31 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170131T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-01-17 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nodegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=150048Meetings/Containers2017-01-17T15:57:22Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2017-01-17 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170117T16<br />
|-<br />
| 2017-01-24 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170124T16<br />
|-<br />
| 2017-01-31 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170131T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-01-17 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=149027Meetings/Containers2017-01-03T16:45:23Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2017-01-10 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170110T16<br />
|-<br />
| 2017-01-17 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170117T16<br />
|-<br />
| 2017-01-24 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170124T16<br />
|-<br />
| 2017-01-31 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170131T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-01-10 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** 1) ACTION: adrian_otto to respond to http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html with a reference to this chat. (adrian_otto, 16:20:07)<br />
*** Status: Complete<br />
*** http://lists.openstack.org/pipermail/openstack-dev/2017-January/109558.html<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=149006Meetings/Containers2017-01-03T15:58:21Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2017-01-03 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170103T16<br />
|-<br />
| 2017-01-10 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170110T16<br />
|-<br />
| 2017-01-17 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170117T16<br />
|-<br />
| 2017-01-24 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170124T16<br />
|-<br />
| 2017-01-31 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20170131T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-01-03 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** 1) ACTION: adrian_otto to add http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html to our 2012-01-03 team meeting agenda.<br />
*** Status: Complete<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Managing cluster drivers as individual distro packages<br />
** #link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=149003Meetings/Containers2017-01-03T15:55:48Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2017-01-03 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** 1) ACTION: adrian_otto to add http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html to our 2012-01-03 team meeting agenda.<br />
*** Status: Complete<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
* Managing cluster drivers as individual distro packages<br />
** #link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2017/ 2017 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=144637Meetings/Containers2016-12-08T01:24:11Z<p>Adrian Otto: /* Agenda for 2016-12-13 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-12-13 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) Reminder, there will be no meeting on 2016-12-27<br />
* Review Action Items<br />
** 1) ACTION: adrian_otto to ask swatson about claiming https://bugs.launchpad.net/magnum/+bug/1489908<br />
*** Status: Emailed swatson<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
*** #link https://review.openstack.org/391537 Specification for Magnum cluster stats API [vijendar]<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=144636Meetings/Containers2016-12-08T01:21:22Z<p>Adrian Otto: /* Agenda for 2016-12-13 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-12-13 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) Reminder, there will be no meeting on 2016-12-27<br />
* Review Action Items<br />
** 1) ACTION: adrian_otto to ask swatson about claiming https://bugs.launchpad.net/magnum/+bug/1489908<br />
*** Status: Pending<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
*** #link https://review.openstack.org/391537 Specification for Magnum cluster stats API [vijendar]<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=144635Meetings/Containers2016-12-08T01:20:12Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-12-13 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) Reminder, there will be no meeting on 2016-12-27<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin]<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi]<br />
** Other Work Items<br />
*** #link https://review.openstack.org/391537 Specification for Magnum cluster stats API [vijendar]<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=144492Meetings/Containers2016-12-06T16:05:15Z<p>Adrian Otto: /* Agenda for 2016-12-06 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-12-06 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161206T16<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-12-06 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) Reminder, there will be no meeting on 2016-12-27<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes (strigazi)<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups (drago)<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/template-versioning (jvgrant)<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe (yatin)<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=144491Meetings/Containers2016-12-06T16:04:56Z<p>Adrian Otto: /* Agenda for 2016-12-06 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-12-06 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161206T16<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-12-06 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
1) Reminder, there will be no meeting on 2016-12-27<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Essential Blueprints<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes (strigazi)<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/nodegroups (drago)<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/template-versioning (jvgrant)<br />
*** #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe (yatin)<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=144489Meetings/Containers2016-12-06T16:00:53Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-12-06 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161206T16<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-12-06 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=143404Meetings/Containers2016-11-29T16:56:58Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-11-29 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161129T16<br />
|-<br />
| 2016-12-06 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161206T16<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
| 2016-12-27 || No Meeting || We will not hold a meeting this week because of planned vacations.<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-29 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=143392Meetings/Containers2016-11-29T16:00:53Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| 2016-11-29 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161129T16<br />
|-<br />
| 2016-12-06 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161206T16<br />
|-<br />
| 2016-12-13 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161213T16<br />
|-<br />
| 2016-12-20 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161220T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-29 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=143391Meetings/Containers2016-11-29T15:58:21Z<p>Adrian Otto: /* Agenda for 2016-11-15 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2016-11-15 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-22 || NONE || NO MEETING DUE TO US HOLIDAY<br />
|-<br />
| 2016-11-29 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20162901T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-29 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=139984Meetings/Containers2016-11-15T15:07:13Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2016-11-15 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-22 || NONE || NO MEETING DUE TO US HOLIDAY<br />
|-<br />
| 2016-11-29 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20162901T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-15 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) New Core Reviewers<br />
** 2) Reminder: No team meeting next week 2016-11-22.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=139981Meetings/Containers2016-11-15T15:06:19Z<p>Adrian Otto: /* Agenda for 2016-11-08 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2016-11-08 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-15 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-22 || NONE || NO MEETING DUE TO US HOLIDAY<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-15 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) New Core Reviewers<br />
** 2) Reminder: No team meeting next week 2016-11-22.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Magnum/Contributing&diff=138976Magnum/Contributing2016-11-12T08:44:12Z<p>Adrian Otto: /* Advice and Requirements for Reviewers */</p>
<hr />
<div>__TOC__<br />
<br />
= Before You Begin =<br />
To familiarize yourself with Magnum, try it out using the information in our [http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/quickstart.rst Dev Quickstart Guide] and [https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-manual-devstack.rst Manually Adding Magnum to DevStack Guide]. When you are ready to start contributing, you will need to execute an [[How_To_Contribute#Contributors_License_Agreement|OpenStack CLA]]. This is required before you can submit reviews to our [https://github.com/openstack/magnum Magnum Repo]. For information about how prepare for contribution, please consult the [[How_To_Contribute |How To Contribute]] wiki page.<br />
<br />
We strongly recommend that you spend 40 minutes watching the [https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/7-habits-of-highly-effective-contributors 7 Habits of Highly Effective Contributors] video. This is Adrian Otto's philosophy on the behaviors that you should exhibit to become a valued member of our contributor community. Adrian is the founding PTL of Magnum.<br />
<br />
== Sign Up for the OpenStack Development Mailing List ==<br />
Head on over to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack Dev Mailing List], fill out the fields under "Subscribing to OpenStack-dev" and click Subscribe.<br />
<br />
== Learn About Gerrit ==<br />
Be sure to read the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide] for information about how to submit your commit for review so it can be merged into the Magnum code base.<br />
<br />
If you do not have a gerrit username setup or do not remember it,<br />
verify and configure it here: https://review.openstack.org/#/settings/<br />
<br />
Keep that handy for the "git review -s" command later in the https://wiki.openstack.org/wiki/Magnum/Contributing#Setting_up_your_git_review_settings and https://wiki.openstack.org/wiki/Magnum/Contributing#Set_up_your_local_branch sections below...<br />
<br />
You'll also need to upload an SSH public key, specifically for Gerrit:<br />
https://review.openstack.org/#/settings/ssh-keys<br />
<br />
== Setting up your git review settings ==<br />
New to git? Try the 15-minute high-level interactive Git demo [http://try.github.com/ GitHub Demo]<br />
<br />
Need a git refresher? Download a git reference direct from the source: [https://training.github.com/kit/downloads/github-git-cheat-sheet.pdf GitHub Git Cheat Sheet]<br />
<br />
Then:<br />
<br />
git config --global user.name "Firstname Lastname"<br />
git config --global user.email "your_email@youremail.com"<br />
<br />
In the event your launchpad and gerrit usernames are identical: <br />
git config --global gitreview.username "your_launchpad_username"<br />
In the event your launchpad and gerrit usernames are not identical: <br />
git config --global gitreview.username "your_gerrit_username"<br />
<br />
To check your git configuration:<br />
<br />
git config --list<br />
<br />
== Installing git-review ==<br />
On Ubuntu, MacOSx, or most other Unix-like systems, it is as simple as:<br />
pip install git-review<br />
<br />
There are other installation options detailed in the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide]. You can now check out the Magnum code and begin working on it:<br />
<br />
= Your first commit =<br />
<br />
== Set up your local branch ==<br />
<br />
<br />
git clone git://git.openstack.org/openstack/magnum<br />
cd magnum<br />
git checkout -b [branch name (see below...)]<br />
git review -s<br />
<br />
To find out what branch names are valid, try out one of the useful git branch commands here: http://gitready.com/intermediate/2009/02/13/list-remote-branches.html<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
We don't know where your gerrit is. Please manually create a remote<br />
named "gerrit" and try again.<br />
<br />
Perform the following (substituting <your gerrit username> with your specific gerrit username...):<br />
git remote add gerrit ssh://<your gerrit username>@review.openstack.org:29418/openstack/magnum.git<br />
git review -s<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
Agent admitted failure to sign using the key<br />
<br />
See this support page: https://help.github.com/articles/error-agent-admitted-failure-to-sign/<br />
<br />
== Identify bugs ==<br />
Observe a bug? Report it here: https://launchpad.net/magnum<br />
# Click the '''Report a Bug''' button.<br />
# Enter a Summary in the field and click Next. Here's an example: Stale link to Gerrit Workflow<br />
# Review the choices you've been given. If you spot your bug, click on the bug and review its status; proceed to the awesome code section below if there's more to do.. If you do not spot your bug, proceed to the next step.<br />
# Click the '''No, I need to report a new bug''' button.<br />
# Type in a detailed description of the bug in the "Further information" field and click '''Submit bug report'''. Here's an example description for our previous example: In doc/source/dev/quickstart.rst the link to the Gerrit workflow is incorrect. It should be: http://docs.openstack.org/infra/manual/developers.html<br />
<br />
NOTE: If you are fixing something trivial, that is not actually a functional defect in the software, you can do that without filing a bug ticket, if you don't want it to be tracked when we tally this work between releases. If you do this, just mention it in the commit message that it's a trivial change that does not require a bug ticket. You can reference this guideline if it comes up in discussion during the review process. Functional defects should be tracked in bug tickets. New features should be tracked in blueprints. Trivial features may be tracked using a bug ticket marked as 'Wishlist' importance.<br />
<br />
== Write some awesome code ==<br />
<br />
At this point can write your code and push it to Gerrit for review. <br />
<br />
git add <list of files you added/changed><br />
<br />
<br />
If you submitted a bug in the previous section, be sure to add the bug link in the commit message.<br />
<br />
Each commit line should conform with the OpenStack message structure guidelines found at<br />
https://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_Git_commit_message_structure<br />
<br />
Highlights include:<br />
* There should be no whitespace at the end of the lines<br />
* The order of the lines is important<br />
** The first line of the commit message should be <=50 characters<br />
** The next line is blank<br />
** The next section is a verbose description of the commit (lines must be <= 72 characters)<br />
** The next line is blank<br />
** The next lines contain the bug number or the blueprint name and possibly other information:<br />
*** Closes-Bug/Partial-Bug/Related-Bug: '''hash symbol (#)''' followed by a bug number (e.g. ''Closes-Bug: #111111'')<br />
*** Blueprint: blueprint name (e.g., "Implements: blueprint libvirt-xml-cpu-model")<br />
** Once the change is submitted with ''git review'' a "Change-Id:" line will be appended with an identifier generated by Gerrit<br />
<br />
<br />
An example of a commit message:<br />
Adjust Gerrit workflow Link<br />
''<blank_line>''<br />
The Gerrit workflow link in the previous version is no longer valid.<br />
This patch updates documentation to the current link.<br />
''<blank_line>''<br />
Closes-Bug: ''#<launchpad_bug_number>''<br />
Change-Id: ''<generated_by_gerrit>''<br />
<br />
<br />
This is but one example. You can find more detailed information about commit messages at<br />
https://wiki.openstack.org/wiki/GitCommitMessages<br />
<br />
<br />
Once you organize the above information, perform the following command to type it in:<br />
git commit -a<br />
<br />
<br />
Then, submit the review:<br />
git review -v --draft<br />
<br />
<br />
Once you are happy with your code and want it to be reviewed you want to convert it from a Draft. "Sign In" at https://review.openstack.org/ and after verifying the review yourself hit the "Publish" button on the page.<br />
<br />
If you know you are ready for others to review your code, you can skip the draft step and just do:<br />
git review -v<br />
<br />
<br />
By this point, your code will be reviewed by the Openstack automatic testing frameworks and, potentially, your peers on the project.<br />
<br />
If you want to revise your patchset in the review system in response to feedback, first navigate back to your development area:<br />
cd ~/magnum [or wherever that is for your setup...]<br />
<br />
<br />
Download the change. Be sure to use the review number and NOT the bug number:<br />
git review -d <review number><br />
<br />
<br />
Then, make your changes, and update the commit message using the aforementioned commit guidelines:<br />
git commit --amend<br />
<br />
<br />
Then:<br />
git review -v<br />
<br />
<br />
Upon approval of the review your code will be automatically merged.<br />
<br />
=== Need somewhere to start writing code? ===<br />
<br />
You can also contribute to the quality of the code by looking at the coverage of current Magnum unit tests and improving the code coverage. You can review the code coverage of your currently checked out code with:<br />
$ tox -e cover<br />
<br />
This will produce a '''cover''' directory that provides HTML output showing the code coverage as well as the specific lines of code that are not covered.<br />
<br />
==== Low Hanging Fruit ====<br />
Some bugs have been identified by the bug manager as appropriate for first time contributors. These bugs should require small patches, and don't require an extensive understanding of Magnum to work on. Find them [https://bugs.launchpad.net/magnum/+bugs?field.tag=low-hanging-fruit tagged with the low-hanging-fruit tag in the bug system].<br />
<br />
= How to Resolve Merge Conflicts =<br />
<br />
If another patch changes the same line of code as your patch, and it gets merged before yours, your patch may get a <code>patch in merge conflict</code> status in red. If that happens, here is how you can resolve it. You will need the patch number from the Gerrit URL https://review.openstack.org/NNNNN to make your rebase a revision of the previous review.<br />
<br />
git clone https://github.com/openstack/magnum<br />
cd magnum<br />
git review -d NNNNN<br />
git rebase master<br />
<br />
Now edit all files with merge conflicts to resolve them by making the code look the way it should both with the recently merged code, and your own. Then <code>git add</code> each of the files you edited.<br />
<br />
git add path/to/file/you/edited<br />
git rebase --continue<br />
git review -v<br />
<br />
That will resubmit your patch with the original commit message, and the rebased code with your merge fix as a new patch set.<br />
<br />
= Reviews =<br />
<br />
The OpenStack CI system uses the concept of core reviewers. These are individuals who have consistently reviewed code for the project, and helped over a considerable period of time to improve the quality and consistency of what we merge into the code base. Project contributors will feel that this reviewer is a positive influence on the team and that they maintain the values and traditions of the OpenStack development community. <br />
<br />
== Policies ==<br />
Existing core reviewers may nominate new ones in an ML thread. Consent among the current reviewers shall result in the declaration of the new core reviewer by the PTL. Lack of unanimous consent shall be carefully considered, and a final decision informed by input from from active team members shall be made by the PTL. Core reviewers who are judged by their peers in the core review group to fall short of the expectations for contribution of a core reviewer may be nominated for return to regular reviewer status.<br />
<br />
Patches require a core reviewer to mark a review as "Approved" before they are merged.<br />
<br />
== Review Guidelines ==<br />
=== Code Approval for Merge ===<br />
* For Approval, two core reviewers shall supply a <code>+2</code>. <br />
=== Continuing Someone Else's Contribution ===<br />
* If a patch submitted by one contributor is picked up and completed by another contributor, [http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg05998.html special handling] of the resolution should be used.<br />
=== Advice and Requirements for Reviewers ===<br />
We are a team, and it's extremely important that we treat each other with respect and courtesy. Reviewers shall align their actions with the [https://www.openstack.org/legal/community-code-of-conduct/ OpenStack Community Code of Conduct]. <br />
<br />
The following workflow states may by applied to each review:<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''State''' || '''Meaning''' || '''Detail'''<br />
|-<br />
| <code>workflow-1</code> || Work in progress || This patch is submitted for team input, but should not yet be considered for merge.<br />
|-<br />
| <code>workflow-0</code> || Ready for reviews || This patch should be considered for merge.<br />
|-<br />
| <code>workflow+1</code> || Approved || This patch has received at least two +2 votes, and is approved for merge.<br />
|-<br />
|}<br />
<br />
The following votes may be applied to a review.<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''Vote''' || '''Meaning''' || '''Detail'''<br />
|-<br />
| <code>-2</code> || Do Not Merge || <br />
* <code>WARNING</code>: Use extreme caution applying this vote, because contributors perceive this action as hostile unless it is accompanied with a genuine offer to help remedy a critical concern collaboratively.<br />
* This vote is a veto that indicates a critical problem with the contribution. It is ''sticky'', meaning it must be removed by the individual who added it, even if further revisions are made. <br />
* All <code>-2</code> votes shall be accompanied with a polite comment that clearly states what can be changed by the contributor to result in reversal of the vote. <br />
* Core reviewers may use this vote:<br />
** In an emergency to prevent breaking the gate. This vote works to halt a merge even after a <code>2*+2,+A</code> approval, but before the patch reaches MERGED state. <br />
** To indicate a critical problem to address, such as a security vulnerability that other core reviewers may be unable to recognize.<br />
* The PTL may use this vote:<br />
** To indicate a decision that the patch is not consistent with the direction of the project. <br />
** While coordinating a release to prevent incompatible changes from merging before the release is tagged.<br />
** To address a critical concern with the contribution.<br />
* To avoid a <code>-2</code> vote on your contribution, discuss your plans with the development team prior to writing code, and post a WIP (workflow-1) patch while you are working on it, and ask for input before you submit it for merge review.<br />
|-<br />
| <code>-1</code> || This patch needs further work before it can be merged || <br />
* This vote indicates an opportunity to make our code better before it is merged. <br />
* It asks the submitter to make a revision in accordance with your feedback before core reviewers should consider this code for merge. <br />
* This vote shall be accompanied with constructive and actionable feedback for ''how'' to improve the submission.<br />
* If you use a <code>-1</code> vote to ask a question, and the contributor answers the question, please respond acknowledging the answer. Either change your vote or follow up with additional rationale for why this should remain a <code>-1</code> comment.<br />
* These votes will be cleared when you make a revision to a patch set, and resubmit it for review.<br />
|-<br />
| <code>0</code> || No Score || <br />
* Used to make remarks or ask questions that may not require a revision to answer.<br />
|-<br />
| <code>+1</code> || Looks good to me, but someone else must approve || <br />
* Used to validate the quality of a contribution and express agreement with the implementation. <br />
* Resist the temptation to blindly <code>+1</code> code without reviewing it in sufficient detail to form an opinion.<br />
|-<br />
| <code>+2</code> || Looks good to me (core reviewer) || <br />
* Used by core reviewers to indicate acceptance of the patch in its current form. <br />
* Two of these votes are required for <code>+A</code>.<br />
|-<br />
| <code>+A</code> || Approval for Merge || <br />
* This means setting the <code>workflow+1</code> state, and is typically added together with the final <code>+2</code> vote. <br />
* The approving reviewer is responsible for verifying that all open questions and concerns have been adequately addressed prior to taking this action.<br />
|-<br />
|}<br />
<br />
If these guidelines and requirements are not clear, or if you have suggestions for how to improve them, please contact the PTL for help.</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Magnum/Contributing&diff=138960Magnum/Contributing2016-11-12T01:30:45Z<p>Adrian Otto: /* Advice and Requirements for Reviewers */</p>
<hr />
<div>__TOC__<br />
<br />
= Before You Begin =<br />
To familiarize yourself with Magnum, try it out using the information in our [http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/quickstart.rst Dev Quickstart Guide] and [https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-manual-devstack.rst Manually Adding Magnum to DevStack Guide]. When you are ready to start contributing, you will need to execute an [[How_To_Contribute#Contributors_License_Agreement|OpenStack CLA]]. This is required before you can submit reviews to our [https://github.com/openstack/magnum Magnum Repo]. For information about how prepare for contribution, please consult the [[How_To_Contribute |How To Contribute]] wiki page.<br />
<br />
We strongly recommend that you spend 40 minutes watching the [https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/7-habits-of-highly-effective-contributors 7 Habits of Highly Effective Contributors] video. This is Adrian Otto's philosophy on the behaviors that you should exhibit to become a valued member of our contributor community. Adrian is the founding PTL of Magnum.<br />
<br />
== Sign Up for the OpenStack Development Mailing List ==<br />
Head on over to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack Dev Mailing List], fill out the fields under "Subscribing to OpenStack-dev" and click Subscribe.<br />
<br />
== Learn About Gerrit ==<br />
Be sure to read the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide] for information about how to submit your commit for review so it can be merged into the Magnum code base.<br />
<br />
If you do not have a gerrit username setup or do not remember it,<br />
verify and configure it here: https://review.openstack.org/#/settings/<br />
<br />
Keep that handy for the "git review -s" command later in the https://wiki.openstack.org/wiki/Magnum/Contributing#Setting_up_your_git_review_settings and https://wiki.openstack.org/wiki/Magnum/Contributing#Set_up_your_local_branch sections below...<br />
<br />
You'll also need to upload an SSH public key, specifically for Gerrit:<br />
https://review.openstack.org/#/settings/ssh-keys<br />
<br />
== Setting up your git review settings ==<br />
New to git? Try the 15-minute high-level interactive Git demo [http://try.github.com/ GitHub Demo]<br />
<br />
Need a git refresher? Download a git reference direct from the source: [https://training.github.com/kit/downloads/github-git-cheat-sheet.pdf GitHub Git Cheat Sheet]<br />
<br />
Then:<br />
<br />
git config --global user.name "Firstname Lastname"<br />
git config --global user.email "your_email@youremail.com"<br />
<br />
In the event your launchpad and gerrit usernames are identical: <br />
git config --global gitreview.username "your_launchpad_username"<br />
In the event your launchpad and gerrit usernames are not identical: <br />
git config --global gitreview.username "your_gerrit_username"<br />
<br />
To check your git configuration:<br />
<br />
git config --list<br />
<br />
== Installing git-review ==<br />
On Ubuntu, MacOSx, or most other Unix-like systems, it is as simple as:<br />
pip install git-review<br />
<br />
There are other installation options detailed in the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide]. You can now check out the Magnum code and begin working on it:<br />
<br />
= Your first commit =<br />
<br />
== Set up your local branch ==<br />
<br />
<br />
git clone git://git.openstack.org/openstack/magnum<br />
cd magnum<br />
git checkout -b [branch name (see below...)]<br />
git review -s<br />
<br />
To find out what branch names are valid, try out one of the useful git branch commands here: http://gitready.com/intermediate/2009/02/13/list-remote-branches.html<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
We don't know where your gerrit is. Please manually create a remote<br />
named "gerrit" and try again.<br />
<br />
Perform the following (substituting <your gerrit username> with your specific gerrit username...):<br />
git remote add gerrit ssh://<your gerrit username>@review.openstack.org:29418/openstack/magnum.git<br />
git review -s<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
Agent admitted failure to sign using the key<br />
<br />
See this support page: https://help.github.com/articles/error-agent-admitted-failure-to-sign/<br />
<br />
== Identify bugs ==<br />
Observe a bug? Report it here: https://launchpad.net/magnum<br />
# Click the '''Report a Bug''' button.<br />
# Enter a Summary in the field and click Next. Here's an example: Stale link to Gerrit Workflow<br />
# Review the choices you've been given. If you spot your bug, click on the bug and review its status; proceed to the awesome code section below if there's more to do.. If you do not spot your bug, proceed to the next step.<br />
# Click the '''No, I need to report a new bug''' button.<br />
# Type in a detailed description of the bug in the "Further information" field and click '''Submit bug report'''. Here's an example description for our previous example: In doc/source/dev/quickstart.rst the link to the Gerrit workflow is incorrect. It should be: http://docs.openstack.org/infra/manual/developers.html<br />
<br />
NOTE: If you are fixing something trivial, that is not actually a functional defect in the software, you can do that without filing a bug ticket, if you don't want it to be tracked when we tally this work between releases. If you do this, just mention it in the commit message that it's a trivial change that does not require a bug ticket. You can reference this guideline if it comes up in discussion during the review process. Functional defects should be tracked in bug tickets. New features should be tracked in blueprints. Trivial features may be tracked using a bug ticket marked as 'Wishlist' importance.<br />
<br />
== Write some awesome code ==<br />
<br />
At this point can write your code and push it to Gerrit for review. <br />
<br />
git add <list of files you added/changed><br />
<br />
<br />
If you submitted a bug in the previous section, be sure to add the bug link in the commit message.<br />
<br />
Each commit line should conform with the OpenStack message structure guidelines found at<br />
https://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_Git_commit_message_structure<br />
<br />
Highlights include:<br />
* There should be no whitespace at the end of the lines<br />
* The order of the lines is important<br />
** The first line of the commit message should be <=50 characters<br />
** The next line is blank<br />
** The next section is a verbose description of the commit (lines must be <= 72 characters)<br />
** The next line is blank<br />
** The next lines contain the bug number or the blueprint name and possibly other information:<br />
*** Closes-Bug/Partial-Bug/Related-Bug: '''hash symbol (#)''' followed by a bug number (e.g. ''Closes-Bug: #111111'')<br />
*** Blueprint: blueprint name (e.g., "Implements: blueprint libvirt-xml-cpu-model")<br />
** Once the change is submitted with ''git review'' a "Change-Id:" line will be appended with an identifier generated by Gerrit<br />
<br />
<br />
An example of a commit message:<br />
Adjust Gerrit workflow Link<br />
''<blank_line>''<br />
The Gerrit workflow link in the previous version is no longer valid.<br />
This patch updates documentation to the current link.<br />
''<blank_line>''<br />
Closes-Bug: ''#<launchpad_bug_number>''<br />
Change-Id: ''<generated_by_gerrit>''<br />
<br />
<br />
This is but one example. You can find more detailed information about commit messages at<br />
https://wiki.openstack.org/wiki/GitCommitMessages<br />
<br />
<br />
Once you organize the above information, perform the following command to type it in:<br />
git commit -a<br />
<br />
<br />
Then, submit the review:<br />
git review -v --draft<br />
<br />
<br />
Once you are happy with your code and want it to be reviewed you want to convert it from a Draft. "Sign In" at https://review.openstack.org/ and after verifying the review yourself hit the "Publish" button on the page.<br />
<br />
If you know you are ready for others to review your code, you can skip the draft step and just do:<br />
git review -v<br />
<br />
<br />
By this point, your code will be reviewed by the Openstack automatic testing frameworks and, potentially, your peers on the project.<br />
<br />
If you want to revise your patchset in the review system in response to feedback, first navigate back to your development area:<br />
cd ~/magnum [or wherever that is for your setup...]<br />
<br />
<br />
Download the change. Be sure to use the review number and NOT the bug number:<br />
git review -d <review number><br />
<br />
<br />
Then, make your changes, and update the commit message using the aforementioned commit guidelines:<br />
git commit --amend<br />
<br />
<br />
Then:<br />
git review -v<br />
<br />
<br />
Upon approval of the review your code will be automatically merged.<br />
<br />
=== Need somewhere to start writing code? ===<br />
<br />
You can also contribute to the quality of the code by looking at the coverage of current Magnum unit tests and improving the code coverage. You can review the code coverage of your currently checked out code with:<br />
$ tox -e cover<br />
<br />
This will produce a '''cover''' directory that provides HTML output showing the code coverage as well as the specific lines of code that are not covered.<br />
<br />
==== Low Hanging Fruit ====<br />
Some bugs have been identified by the bug manager as appropriate for first time contributors. These bugs should require small patches, and don't require an extensive understanding of Magnum to work on. Find them [https://bugs.launchpad.net/magnum/+bugs?field.tag=low-hanging-fruit tagged with the low-hanging-fruit tag in the bug system].<br />
<br />
= How to Resolve Merge Conflicts =<br />
<br />
If another patch changes the same line of code as your patch, and it gets merged before yours, your patch may get a <code>patch in merge conflict</code> status in red. If that happens, here is how you can resolve it. You will need the patch number from the Gerrit URL https://review.openstack.org/NNNNN to make your rebase a revision of the previous review.<br />
<br />
git clone https://github.com/openstack/magnum<br />
cd magnum<br />
git review -d NNNNN<br />
git rebase master<br />
<br />
Now edit all files with merge conflicts to resolve them by making the code look the way it should both with the recently merged code, and your own. Then <code>git add</code> each of the files you edited.<br />
<br />
git add path/to/file/you/edited<br />
git rebase --continue<br />
git review -v<br />
<br />
That will resubmit your patch with the original commit message, and the rebased code with your merge fix as a new patch set.<br />
<br />
= Reviews =<br />
<br />
The OpenStack CI system uses the concept of core reviewers. These are individuals who have consistently reviewed code for the project, and helped over a considerable period of time to improve the quality and consistency of what we merge into the code base. Project contributors will feel that this reviewer is a positive influence on the team and that they maintain the values and traditions of the OpenStack development community. <br />
<br />
== Policies ==<br />
Existing core reviewers may nominate new ones in an ML thread. Consent among the current reviewers shall result in the declaration of the new core reviewer by the PTL. Lack of unanimous consent shall be carefully considered, and a final decision informed by input from from active team members shall be made by the PTL. Core reviewers who are judged by their peers in the core review group to fall short of the expectations for contribution of a core reviewer may be nominated for return to regular reviewer status.<br />
<br />
Patches require a core reviewer to mark a review as "Approved" before they are merged.<br />
<br />
== Review Guidelines ==<br />
=== Code Approval for Merge ===<br />
* For Approval, two core reviewers shall supply a <code>+2</code>. <br />
=== Continuing Someone Else's Contribution ===<br />
* If a patch submitted by one contributor is picked up and completed by another contributor, [http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg05998.html special handling] of the resolution should be used.<br />
=== Advice and Requirements for Reviewers ===<br />
We are a team, and it's extremely important that we treat each other with respect and courtesy. Reviewers shall align their actions with the [https://www.openstack.org/legal/community-code-of-conduct/ OpenStack Community Code of Conduct]. <br />
<br />
The following workflow states may by applied to each review:<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''State''' || '''Meaning''' || '''Detail'''<br />
|-<br />
| <code>workflow-1</code> || Work in progress || This patch is submitted for team input, but should not yet be considered for merge.<br />
|-<br />
| <code>workflow-0</code> || Ready for reviews || This patch should be considered for merge.<br />
|-<br />
| <code>workflow+1</code> || Approved || This patch has received at least two +2 votes, and is approved for merge.<br />
|-<br />
|}<br />
<br />
The following votes may be applied to a review.<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''Vote''' || '''Meaning''' || '''Detail'''<br />
|-<br />
| <code>-2</code> || Do Not Merge || <br />
* <code>WARNING</code>: Use extreme caution applying this vote, because contributors perceive this action as hostile unless it is accompanied with a genuine offer to help remedy a critical concern collaboratively.<br />
* This vote is a veto that indicates a critical problem with the contribution. It is ''sticky'', meaning it must be removed by the individual who added it, even if further revisions are made. <br />
* All <code>-2</code> votes shall be accompanied with a polite comment that clearly states what can be changed by the contributor to result in reversal of the vote. <br />
* Core reviewers may use this vote:<br />
** In an emergency to prevent breaking the gate. This vote works to halt a merge even after a <code>2*+2,+A</code> approval, but before the patch reaches MERGED state. <br />
** To indicate a critical problem to address, such as a security vulnerability that other core reviewers may be unable to recognize.<br />
* The PTL may use this vote:<br />
** To indicate a decision that the patch is not consistent with the direction of the project. <br />
** While coordinating a release to prevent incompatible changes from merging before the release is tagged.<br />
** To address a critical concern with the contribution.<br />
* To avoid a <code>-2</code> vote on your contribution, discuss your plans with the development team prior to writing code, and post a WIP (workflow-1) patch while you are working on it, and ask for input before you submit it for merge review.<br />
|-<br />
| <code>-1</code> || This patch needs further work before it can be merged || <br />
* This vote indicates an opportunity to make our code better before it is merged. <br />
* It asks the submitter to make a revision in accordance with your feedback before core reviewers should consider this code for merge. <br />
* This vote shall be accompanied with constructive and actionable feedback for ''how'' to improve the submission.<br />
* If you use a <code>-1</code> vote to ask a question, and the contributor answers the question, please respond acknowledging the answer. Either change your vote or follow up with additional rationale for why this should remain a <code>-1</code> comment.<br />
|-<br />
| <code>0</code> || No Score || <br />
* Used to make remarks or ask questions that may not require a revision to answer.<br />
|-<br />
| <code>+1</code> || Looks good to me, but someone else must approve || <br />
* Used to validate the quality of a contribution and express agreement with the implementation. <br />
* Resist the temptation to blindly <code>+1</code> code without reviewing it in sufficient detail to form an opinion.<br />
|-<br />
| <code>+2</code> || Looks good to me (core reviewer) || <br />
* Used by core reviewers to indicate acceptance of the patch in its current form. <br />
* Two of these votes are required for <code>+A</code>.<br />
|-<br />
| <code>+A</code> || Approval for Merge || <br />
* This means setting the <code>workflow+1</code> state, and is typically added together with the final <code>+2</code> vote. <br />
* The approving reviewer is responsible for verifying that all open questions and concerns have been adequately addressed prior to taking this action.<br />
|-<br />
|}<br />
<br />
If these guidelines and requirements are not clear, or if you have suggestions for how to improve them, please contact the PTL for help.</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Magnum/Contributing&diff=138263Magnum/Contributing2016-11-09T22:01:38Z<p>Adrian Otto: /* Advice for Reviewers */</p>
<hr />
<div>__TOC__<br />
<br />
= Before You Begin =<br />
To familiarize yourself with Magnum, try it out using the information in our [http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/quickstart.rst Dev Quickstart Guide] and [https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-manual-devstack.rst Manually Adding Magnum to DevStack Guide]. When you are ready to start contributing, you will need to execute an [[How_To_Contribute#Contributors_License_Agreement|OpenStack CLA]]. This is required before you can submit reviews to our [https://github.com/openstack/magnum Magnum Repo]. For information about how prepare for contribution, please consult the [[How_To_Contribute |How To Contribute]] wiki page.<br />
<br />
We strongly recommend that you spend 40 minutes watching the [https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/7-habits-of-highly-effective-contributors 7 Habits of Highly Effective Contributors] video. This is Adrian Otto's philosophy on the behaviors that you should exhibit to become a valued member of our contributor community. Adrian is the founding PTL of Magnum.<br />
<br />
== Sign Up for the OpenStack Development Mailing List ==<br />
Head on over to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack Dev Mailing List], fill out the fields under "Subscribing to OpenStack-dev" and click Subscribe.<br />
<br />
== Learn About Gerrit ==<br />
Be sure to read the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide] for information about how to submit your commit for review so it can be merged into the Magnum code base.<br />
<br />
If you do not have a gerrit username setup or do not remember it,<br />
verify and configure it here: https://review.openstack.org/#/settings/<br />
<br />
Keep that handy for the "git review -s" command later in the https://wiki.openstack.org/wiki/Magnum/Contributing#Setting_up_your_git_review_settings and https://wiki.openstack.org/wiki/Magnum/Contributing#Set_up_your_local_branch sections below...<br />
<br />
You'll also need to upload an SSH public key, specifically for Gerrit:<br />
https://review.openstack.org/#/settings/ssh-keys<br />
<br />
== Setting up your git review settings ==<br />
New to git? Try the 15-minute high-level interactive Git demo [http://try.github.com/ GitHub Demo]<br />
<br />
Need a git refresher? Download a git reference direct from the source: [https://training.github.com/kit/downloads/github-git-cheat-sheet.pdf GitHub Git Cheat Sheet]<br />
<br />
Then:<br />
<br />
git config --global user.name "Firstname Lastname"<br />
git config --global user.email "your_email@youremail.com"<br />
<br />
In the event your launchpad and gerrit usernames are identical: <br />
git config --global gitreview.username "your_launchpad_username"<br />
In the event your launchpad and gerrit usernames are not identical: <br />
git config --global gitreview.username "your_gerrit_username"<br />
<br />
To check your git configuration:<br />
<br />
git config --list<br />
<br />
== Installing git-review ==<br />
On Ubuntu, MacOSx, or most other Unix-like systems, it is as simple as:<br />
pip install git-review<br />
<br />
There are other installation options detailed in the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide]. You can now check out the Magnum code and begin working on it:<br />
<br />
= Your first commit =<br />
<br />
== Set up your local branch ==<br />
<br />
<br />
git clone git://git.openstack.org/openstack/magnum<br />
cd magnum<br />
git checkout -b [branch name (see below...)]<br />
git review -s<br />
<br />
To find out what branch names are valid, try out one of the useful git branch commands here: http://gitready.com/intermediate/2009/02/13/list-remote-branches.html<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
We don't know where your gerrit is. Please manually create a remote<br />
named "gerrit" and try again.<br />
<br />
Perform the following (substituting <your gerrit username> with your specific gerrit username...):<br />
git remote add gerrit ssh://<your gerrit username>@review.openstack.org:29418/openstack/magnum.git<br />
git review -s<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
Agent admitted failure to sign using the key<br />
<br />
See this support page: https://help.github.com/articles/error-agent-admitted-failure-to-sign/<br />
<br />
== Identify bugs ==<br />
Observe a bug? Report it here: https://launchpad.net/magnum<br />
# Click the '''Report a Bug''' button.<br />
# Enter a Summary in the field and click Next. Here's an example: Stale link to Gerrit Workflow<br />
# Review the choices you've been given. If you spot your bug, click on the bug and review its status; proceed to the awesome code section below if there's more to do.. If you do not spot your bug, proceed to the next step.<br />
# Click the '''No, I need to report a new bug''' button.<br />
# Type in a detailed description of the bug in the "Further information" field and click '''Submit bug report'''. Here's an example description for our previous example: In doc/source/dev/quickstart.rst the link to the Gerrit workflow is incorrect. It should be: http://docs.openstack.org/infra/manual/developers.html<br />
<br />
NOTE: If you are fixing something trivial, that is not actually a functional defect in the software, you can do that without filing a bug ticket, if you don't want it to be tracked when we tally this work between releases. If you do this, just mention it in the commit message that it's a trivial change that does not require a bug ticket. You can reference this guideline if it comes up in discussion during the review process. Functional defects should be tracked in bug tickets. New features should be tracked in blueprints. Trivial features may be tracked using a bug ticket marked as 'Wishlist' importance.<br />
<br />
== Write some awesome code ==<br />
<br />
At this point can write your code and push it to Gerrit for review. <br />
<br />
git add <list of files you added/changed><br />
<br />
<br />
If you submitted a bug in the previous section, be sure to add the bug link in the commit message.<br />
<br />
Each commit line should conform with the OpenStack message structure guidelines found at<br />
https://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_Git_commit_message_structure<br />
<br />
Highlights include:<br />
* There should be no whitespace at the end of the lines<br />
* The order of the lines is important<br />
** The first line of the commit message should be <=50 characters<br />
** The next line is blank<br />
** The next section is a verbose description of the commit (lines must be <= 72 characters)<br />
** The next line is blank<br />
** The next lines contain the bug number or the blueprint name and possibly other information:<br />
*** Closes-Bug/Partial-Bug/Related-Bug: '''hash symbol (#)''' followed by a bug number (e.g. ''Closes-Bug: #111111'')<br />
*** Blueprint: blueprint name (e.g., "Implements: blueprint libvirt-xml-cpu-model")<br />
** Once the change is submitted with ''git review'' a "Change-Id:" line will be appended with an identifier generated by Gerrit<br />
<br />
<br />
An example of a commit message:<br />
Adjust Gerrit workflow Link<br />
''<blank_line>''<br />
The Gerrit workflow link in the previous version is no longer valid.<br />
This patch updates documentation to the current link.<br />
''<blank_line>''<br />
Closes-Bug: ''#<launchpad_bug_number>''<br />
Change-Id: ''<generated_by_gerrit>''<br />
<br />
<br />
This is but one example. You can find more detailed information about commit messages at<br />
https://wiki.openstack.org/wiki/GitCommitMessages<br />
<br />
<br />
Once you organize the above information, perform the following command to type it in:<br />
git commit -a<br />
<br />
<br />
Then, submit the review:<br />
git review -v --draft<br />
<br />
<br />
Once you are happy with your code and want it to be reviewed you want to convert it from a Draft. "Sign In" at https://review.openstack.org/ and after verifying the review yourself hit the "Publish" button on the page.<br />
<br />
If you know you are ready for others to review your code, you can skip the draft step and just do:<br />
git review -v<br />
<br />
<br />
By this point, your code will be reviewed by the Openstack automatic testing frameworks and, potentially, your peers on the project.<br />
<br />
If you want to revise your patchset in the review system in response to feedback, first navigate back to your development area:<br />
cd ~/magnum [or wherever that is for your setup...]<br />
<br />
<br />
Download the change. Be sure to use the review number and NOT the bug number:<br />
git review -d <review number><br />
<br />
<br />
Then, make your changes, and update the commit message using the aforementioned commit guidelines:<br />
git commit --amend<br />
<br />
<br />
Then:<br />
git review -v<br />
<br />
<br />
Upon approval of the review your code will be automatically merged.<br />
<br />
=== Need somewhere to start writing code? ===<br />
<br />
You can also contribute to the quality of the code by looking at the coverage of current Magnum unit tests and improving the code coverage. You can review the code coverage of your currently checked out code with:<br />
$ tox -e cover<br />
<br />
This will produce a '''cover''' directory that provides HTML output showing the code coverage as well as the specific lines of code that are not covered.<br />
<br />
==== Low Hanging Fruit ====<br />
Some bugs have been identified by the bug manager as appropriate for first time contributors. These bugs should require small patches, and don't require an extensive understanding of Magnum to work on. Find them [https://bugs.launchpad.net/magnum/+bugs?field.tag=low-hanging-fruit tagged with the low-hanging-fruit tag in the bug system].<br />
<br />
= How to Resolve Merge Conflicts =<br />
<br />
If another patch changes the same line of code as your patch, and it gets merged before yours, your patch may get a <code>patch in merge conflict</code> status in red. If that happens, here is how you can resolve it. You will need the patch number from the Gerrit URL https://review.openstack.org/NNNNN to make your rebase a revision of the previous review.<br />
<br />
git clone https://github.com/openstack/magnum<br />
cd magnum<br />
git review -d NNNNN<br />
git rebase master<br />
<br />
Now edit all files with merge conflicts to resolve them by making the code look the way it should both with the recently merged code, and your own. Then <code>git add</code> each of the files you edited.<br />
<br />
git add path/to/file/you/edited<br />
git rebase --continue<br />
git review -v<br />
<br />
That will resubmit your patch with the original commit message, and the rebased code with your merge fix as a new patch set.<br />
<br />
= Reviews =<br />
<br />
The OpenStack CI system uses the concept of core reviewers. These are individuals who have consistently reviewed code for the project, and helped over a considerable period of time to improve the quality and consistency of what we merge into the code base. Project contributors will feel that this reviewer is a positive influence on the team and that they maintain the values and traditions of the OpenStack development community. <br />
<br />
== Policies ==<br />
Existing core reviewers may nominate new ones in an ML thread. Consent among the current reviewers shall result in the declaration of the new core reviewer by the PTL. Lack of unanimous consent shall be carefully considered, and a final decision informed by input from from active team members shall be made by the PTL. Core reviewers who are judged by their peers in the core review group to fall short of the expectations for contribution of a core reviewer may be nominated for return to regular reviewer status.<br />
<br />
Patches require a core reviewer to mark a review as "Approved" before they are merged.<br />
<br />
== Review Guidelines ==<br />
=== Code Approval for Merge ===<br />
* For Approval, two core reviewers shall supply a <code>+2</code>. <br />
=== Continuing Someone Else's Contribution ===<br />
* If a patch submitted by one contributor is picked up and completed by another contributor, [http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg05998.html special handling] of the resolution should be used.<br />
=== Advice and Requirements for Reviewers ===<br />
* Reviewers shall align their actions with the [https://www.openstack.org/legal/community-code-of-conduct/ OpenStack Community Code of Conduct].<br />
* A <code>-1</code> vote is an opportunity to make our code better before it is merged. Please do your best to make helpful, actionable <code>-1</code> votes. <br />
* Avoid the temptation to blindly <code>+1</code> code without reviewing it in sufficient detail to form an opinion.<br />
* When voting <code>-1</code> on a patch, it means that you want the submitter to make a revision in accordance with your feedback before core reviewers should consider this code for merge.<br />
* If you ask a question, you should vote <code>0</code> unless you anticipate that the answer to that question is likely to cause you to vote against the patch without further revisions.<br />
* If you use a <code>-1</code> vote for a question, and the contributor answers the question, please respond acknowledging the question. Either change your vote or follow up with additional rationale for why this should remain a <code>-1</code> comment.<br />
* A <code>-2</code> vote is a veto by a single core reviewer. It is sticky. That means that even if you revise your patch, that vote will persist. To allow your patch to merge, that same reviewer must clear the <code>-2</code> vote first. This vote is used when you have contributed something that is not in alignment with the current project vision, or is implemented in a way that can not be accepted. For example, security concerns that a core reviewer wants to individually re-evaluate before allowing the contribution to continue. It can also be used as a way to halt further gate testing of a patch, if something is included that may break the gate. It works even after a <code>2*+2,+A</code> approval for merge, but before the patch reaches MERGED state. <br />
* A reviewer casting a <code>-2</code> vote shall include a review comment that clearly states what can be changed by the contributor to result in removal of the <code>-2</code>. Use caution applying this vote, because contributors perceive this action as hostile unless it is accompanied with a genuine offer to help remedy the concern collaboratively.<br />
* To avoid a <code>-2</code> vote, discuss your plans with the development team prior to writing code, and post a WIP (workflow-1) patch while you are working on it, and ask for input before you submit it for merge review.</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Magnum/Contributing&diff=138254Magnum/Contributing2016-11-09T21:40:32Z<p>Adrian Otto: Removing dated information about code coverage</p>
<hr />
<div>__TOC__<br />
<br />
= Before You Begin =<br />
To familiarize yourself with Magnum, try it out using the information in our [http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/quickstart.rst Dev Quickstart Guide] and [https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-manual-devstack.rst Manually Adding Magnum to DevStack Guide]. When you are ready to start contributing, you will need to execute an [[How_To_Contribute#Contributors_License_Agreement|OpenStack CLA]]. This is required before you can submit reviews to our [https://github.com/openstack/magnum Magnum Repo]. For information about how prepare for contribution, please consult the [[How_To_Contribute |How To Contribute]] wiki page.<br />
<br />
We strongly recommend that you spend 40 minutes watching the [https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/7-habits-of-highly-effective-contributors 7 Habits of Highly Effective Contributors] video. This is Adrian Otto's philosophy on the behaviors that you should exhibit to become a valued member of our contributor community. Adrian is the founding PTL of Magnum.<br />
<br />
== Sign Up for the OpenStack Development Mailing List ==<br />
Head on over to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack Dev Mailing List], fill out the fields under "Subscribing to OpenStack-dev" and click Subscribe.<br />
<br />
== Learn About Gerrit ==<br />
Be sure to read the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide] for information about how to submit your commit for review so it can be merged into the Magnum code base.<br />
<br />
If you do not have a gerrit username setup or do not remember it,<br />
verify and configure it here: https://review.openstack.org/#/settings/<br />
<br />
Keep that handy for the "git review -s" command later in the https://wiki.openstack.org/wiki/Magnum/Contributing#Setting_up_your_git_review_settings and https://wiki.openstack.org/wiki/Magnum/Contributing#Set_up_your_local_branch sections below...<br />
<br />
You'll also need to upload an SSH public key, specifically for Gerrit:<br />
https://review.openstack.org/#/settings/ssh-keys<br />
<br />
== Setting up your git review settings ==<br />
New to git? Try the 15-minute high-level interactive Git demo [http://try.github.com/ GitHub Demo]<br />
<br />
Need a git refresher? Download a git reference direct from the source: [https://training.github.com/kit/downloads/github-git-cheat-sheet.pdf GitHub Git Cheat Sheet]<br />
<br />
Then:<br />
<br />
git config --global user.name "Firstname Lastname"<br />
git config --global user.email "your_email@youremail.com"<br />
<br />
In the event your launchpad and gerrit usernames are identical: <br />
git config --global gitreview.username "your_launchpad_username"<br />
In the event your launchpad and gerrit usernames are not identical: <br />
git config --global gitreview.username "your_gerrit_username"<br />
<br />
To check your git configuration:<br />
<br />
git config --list<br />
<br />
== Installing git-review ==<br />
On Ubuntu, MacOSx, or most other Unix-like systems, it is as simple as:<br />
pip install git-review<br />
<br />
There are other installation options detailed in the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide]. You can now check out the Magnum code and begin working on it:<br />
<br />
= Your first commit =<br />
<br />
== Set up your local branch ==<br />
<br />
<br />
git clone git://git.openstack.org/openstack/magnum<br />
cd magnum<br />
git checkout -b [branch name (see below...)]<br />
git review -s<br />
<br />
To find out what branch names are valid, try out one of the useful git branch commands here: http://gitready.com/intermediate/2009/02/13/list-remote-branches.html<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
We don't know where your gerrit is. Please manually create a remote<br />
named "gerrit" and try again.<br />
<br />
Perform the following (substituting <your gerrit username> with your specific gerrit username...):<br />
git remote add gerrit ssh://<your gerrit username>@review.openstack.org:29418/openstack/magnum.git<br />
git review -s<br />
<br />
If you receive the following error when running the "git review -s" command:<br />
Agent admitted failure to sign using the key<br />
<br />
See this support page: https://help.github.com/articles/error-agent-admitted-failure-to-sign/<br />
<br />
== Identify bugs ==<br />
Observe a bug? Report it here: https://launchpad.net/magnum<br />
# Click the '''Report a Bug''' button.<br />
# Enter a Summary in the field and click Next. Here's an example: Stale link to Gerrit Workflow<br />
# Review the choices you've been given. If you spot your bug, click on the bug and review its status; proceed to the awesome code section below if there's more to do.. If you do not spot your bug, proceed to the next step.<br />
# Click the '''No, I need to report a new bug''' button.<br />
# Type in a detailed description of the bug in the "Further information" field and click '''Submit bug report'''. Here's an example description for our previous example: In doc/source/dev/quickstart.rst the link to the Gerrit workflow is incorrect. It should be: http://docs.openstack.org/infra/manual/developers.html<br />
<br />
NOTE: If you are fixing something trivial, that is not actually a functional defect in the software, you can do that without filing a bug ticket, if you don't want it to be tracked when we tally this work between releases. If you do this, just mention it in the commit message that it's a trivial change that does not require a bug ticket. You can reference this guideline if it comes up in discussion during the review process. Functional defects should be tracked in bug tickets. New features should be tracked in blueprints. Trivial features may be tracked using a bug ticket marked as 'Wishlist' importance.<br />
<br />
== Write some awesome code ==<br />
<br />
At this point can write your code and push it to Gerrit for review. <br />
<br />
git add <list of files you added/changed><br />
<br />
<br />
If you submitted a bug in the previous section, be sure to add the bug link in the commit message.<br />
<br />
Each commit line should conform with the OpenStack message structure guidelines found at<br />
https://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_Git_commit_message_structure<br />
<br />
Highlights include:<br />
* There should be no whitespace at the end of the lines<br />
* The order of the lines is important<br />
** The first line of the commit message should be <=50 characters<br />
** The next line is blank<br />
** The next section is a verbose description of the commit (lines must be <= 72 characters)<br />
** The next line is blank<br />
** The next lines contain the bug number or the blueprint name and possibly other information:<br />
*** Closes-Bug/Partial-Bug/Related-Bug: '''hash symbol (#)''' followed by a bug number (e.g. ''Closes-Bug: #111111'')<br />
*** Blueprint: blueprint name (e.g., "Implements: blueprint libvirt-xml-cpu-model")<br />
** Once the change is submitted with ''git review'' a "Change-Id:" line will be appended with an identifier generated by Gerrit<br />
<br />
<br />
An example of a commit message:<br />
Adjust Gerrit workflow Link<br />
''<blank_line>''<br />
The Gerrit workflow link in the previous version is no longer valid.<br />
This patch updates documentation to the current link.<br />
''<blank_line>''<br />
Closes-Bug: ''#<launchpad_bug_number>''<br />
Change-Id: ''<generated_by_gerrit>''<br />
<br />
<br />
This is but one example. You can find more detailed information about commit messages at<br />
https://wiki.openstack.org/wiki/GitCommitMessages<br />
<br />
<br />
Once you organize the above information, perform the following command to type it in:<br />
git commit -a<br />
<br />
<br />
Then, submit the review:<br />
git review -v --draft<br />
<br />
<br />
Once you are happy with your code and want it to be reviewed you want to convert it from a Draft. "Sign In" at https://review.openstack.org/ and after verifying the review yourself hit the "Publish" button on the page.<br />
<br />
If you know you are ready for others to review your code, you can skip the draft step and just do:<br />
git review -v<br />
<br />
<br />
By this point, your code will be reviewed by the Openstack automatic testing frameworks and, potentially, your peers on the project.<br />
<br />
If you want to revise your patchset in the review system in response to feedback, first navigate back to your development area:<br />
cd ~/magnum [or wherever that is for your setup...]<br />
<br />
<br />
Download the change. Be sure to use the review number and NOT the bug number:<br />
git review -d <review number><br />
<br />
<br />
Then, make your changes, and update the commit message using the aforementioned commit guidelines:<br />
git commit --amend<br />
<br />
<br />
Then:<br />
git review -v<br />
<br />
<br />
Upon approval of the review your code will be automatically merged.<br />
<br />
=== Need somewhere to start writing code? ===<br />
<br />
You can also contribute to the quality of the code by looking at the coverage of current Magnum unit tests and improving the code coverage. You can review the code coverage of your currently checked out code with:<br />
$ tox -e cover<br />
<br />
This will produce a '''cover''' directory that provides HTML output showing the code coverage as well as the specific lines of code that are not covered.<br />
<br />
==== Low Hanging Fruit ====<br />
Some bugs have been identified by the bug manager as appropriate for first time contributors. These bugs should require small patches, and don't require an extensive understanding of Magnum to work on. Find them [https://bugs.launchpad.net/magnum/+bugs?field.tag=low-hanging-fruit tagged with the low-hanging-fruit tag in the bug system].<br />
<br />
= How to Resolve Merge Conflicts =<br />
<br />
If another patch changes the same line of code as your patch, and it gets merged before yours, your patch may get a <code>patch in merge conflict</code> status in red. If that happens, here is how you can resolve it. You will need the patch number from the Gerrit URL https://review.openstack.org/NNNNN to make your rebase a revision of the previous review.<br />
<br />
git clone https://github.com/openstack/magnum<br />
cd magnum<br />
git review -d NNNNN<br />
git rebase master<br />
<br />
Now edit all files with merge conflicts to resolve them by making the code look the way it should both with the recently merged code, and your own. Then <code>git add</code> each of the files you edited.<br />
<br />
git add path/to/file/you/edited<br />
git rebase --continue<br />
git review -v<br />
<br />
That will resubmit your patch with the original commit message, and the rebased code with your merge fix as a new patch set.<br />
<br />
= Reviews =<br />
<br />
The OpenStack CI system uses the concept of core reviewers. These are individuals who have consistently reviewed code for the project, and helped over a considerable period of time to improve the quality and consistency of what we merge into the code base. Project contributors will feel that this reviewer is a positive influence on the team and that they maintain the values and traditions of the OpenStack development community. <br />
<br />
== Policies ==<br />
Existing core reviewers may nominate new ones in an ML thread. Consent among the current reviewers shall result in the declaration of the new core reviewer by the PTL. Lack of unanimous consent shall be carefully considered, and a final decision informed by input from from active team members shall be made by the PTL. Core reviewers who are judged by their peers in the core review group to fall short of the expectations for contribution of a core reviewer may be nominated for return to regular reviewer status.<br />
<br />
Patches require a core reviewer to mark a review as "Approved" before they are merged.<br />
<br />
== Review Guidelines ==<br />
=== Code Approval for Merge ===<br />
* For Approval, two core reviewers shall supply a <code>+2</code>. <br />
=== Continuing Someone Else's Contribution ===<br />
* If a patch submitted by one contributor is picked up and completed by another contributor, [http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg05998.html special handling] of the resolution should be used.<br />
=== Advice for Reviewers ===<br />
* A <code>-1</code> vote is an opportunity to make our code better before it is merged. Please do your best to make helpful, actionable -1 votes. <br />
* Avoid the temptation to blindly <code>+1</code> code without reviewing it in sufficient detail to form an opinion.<br />
* When voting <code>-1</code> on a patch, it means that you want the submitter to make a revision in accordance with your feedback before core reviewers should consider this code for merge.<br />
* If you ask a question, you should vote <code>0</code> unless you anticipate that the answer to that question is likely to cause you to vote against the patch without further revisions.<br />
* If you use a <code>-1</code> vote for a question, and the contributor answers the question, please respond acknowledging the question. Either change your vote or follow up with additional rationale for why this should remain a <code>-1</code> comment.<br />
* A <code>-2</code> vote is a veto by a single core reviewer. It is sticky. That means that even if you revise your patch, that vote will persist. To allow your patch to merge, that same reviewer must clear the <code>-2</code> vote first. This vote is used when you have contributed something that is not in alignment with the current project vision, or is implemented in a way that can not be accepted. For example, security concerns that a core reviewer wants to individually re-evaluate before allowing the contribution to continue. It can also be used as a way to halt further gate testing of a patch, if something is included that may break the gate. It works even after a <code>2*+2,+A</code> approval for merge, but before the patch reaches MERGED state. <br />
* To avoid a <code>-2</code> vote, discuss your plans with the development team prior to writing code, and post a WIP (workflow-1) patch while you are working on it, and ask for input before you submit it for merge review.</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=137575Meetings/Containers2016-11-07T20:15:44Z<p>Adrian Otto: /* Agenda for 2016-11-08 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2016-11-08 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-15 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-22 || NONE || NO MEETING DUE TO US HOLIDAY<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-08 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) #link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106889.html New Core Reviewers<br />
** 2) No team meeting on 2016-11-22.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** 1) #link https://review.openstack.org/389835 Add cluster driver encapsulation spec (randallburt)<br />
* Ocata Blueprints<br />
** Which additional blueprints would we like to target for this release?<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=137573Meetings/Containers2016-11-07T20:12:31Z<p>Adrian Otto: /* Weekly Containers Team Meeting */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2016-11-08 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-15 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-22 || NONE || NO MEETING DUE TO US HOLIDAY<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-08 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** 1) #link http://lists.openstack.org/pipermail/openstack-dev/2016-November/106889.html New Core Reviewers<br />
** 2) No team meeting on 2016-11-22.<br />
* Review Action Items<br />
** (none)<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** 1) #link https://review.openstack.org/389835 Add cluster driver encapsulation spec (randallburt)<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=137198CrossProjectLiaisons2016-11-03T17:46:36Z<p>Adrian Otto: </p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Lin Tan || lintan<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Omar Shykhkerimov || oshykhkerimov<br />
|-<br />
| Neutron || Henry Gessau || HenryG<br />
|-<br />
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Ethan Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Ian Cordasco || sigmavirus<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Dariusz Smigiel || dasm<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| Oslo || Joshua Harlow || harlowja<br />
|-<br />
| PuppetOpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Alexander Bashmakov || abashmak<br />
|-<br />
| Heat || Randall Burt || randallburt<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_mb<br />
|-<br />
| Neutron || Matthew Kassawara || Sam-I-Am <br />
|-<br />
| Nova || Michael Still and Sean Dague (api-ref and api-guide) || mikal and sdague<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || Chad Roberts, Michael Ionkin || crobertsrh mionkin<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || Laurel Michaels || laurelm<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Devananda van der Veen || devananda<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || Nikolay Starodubtsev || Nikolay_St<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Nate Johnston, Armando Migliaccio, Doug Wiegley|| njohnston, armax, dougwig<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Carol Barrett || barrett1<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || <br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Doug Fish / Akihiro Motoki || doug-fish / amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || Tetiana Lashchova || tlashchova<br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean M. Collins || sc68cal || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Jim Rollenhagen || jroll || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Sahara / Trove || || ||<br />
|-<br />
| || Ethan Gafford || egafford || Sahara liaison for Trove<br />
|-<br />
| || Amrith Kumar || amrith || Trove liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=136993Meetings/Containers2016-11-01T15:55:30Z<p>Adrian Otto: /* Agenda for 2016-11-01 1600 UTC */</p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2016-11-01 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-08 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-15 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-01 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** Daylight savings time ends in the US on Sunday Nov 6th at 2:00 AM. This will cause our meeting to take place an hour earlier in most local timezones because we track UTC. Check your calendar reminders to make sure they reflect the correct timezone.<br />
* Review Action Items<br />
** 1) adrian_otto to email Magnum/Kuryr teams with details about joint meetup plans prior to summit. Status: COMPLETE<br />
** 2) strigazi to create a magnum-specs repo<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Should we have a team meeting on Nov 22, or skip that date due to US holidays (Thanksgiving, Nov 24)?<br />
** (Drago) Magnum API reference<br />
*** There was an effort that went on to have a swagger API doc, but it was abandoned. Magnum still doesn't have an API reference. Can we just go with what all the other projects are doing so we can finally have this?<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Meetings/Containers&diff=136992Meetings/Containers2016-11-01T15:54:01Z<p>Adrian Otto: </p>
<hr />
<div>= Weekly Containers Team Meeting =<br />
<br />
The [[Teams/Containers|OpenStack Containers Team]] holds public meetings. We meet in <code>#openstack-meeting-alt</code> on Tuesdays on the following schedule:<br />
<br />
{| class="wikitable"<br />
|-<br />
| 2016-11-01 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-08 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
| 2016-11-15 || UTC 1600 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Containers+Team+Meeting&iso=20161101T16<br />
|-<br />
|}<br />
<br />
Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Agenda for 2016-11-01 1600 UTC ==<br />
* Roll Call<br />
* Announcements<br />
** Daylight savings time ends in the US on Sunday Nov 6th at 2:00 AM. This will cause our meeting to take place an hour earlier in most local timezones because we track UTC. Check your calendar reminders to make sure they reflect the correct timezone.<br />
* Review Action Items<br />
* Blueprints/Bugs/Reviews/Ideas<br />
** Should we have a team meeting on Nov 22, or skip that date due to US holidays (Thanksgiving, Nov 24)?<br />
** (Drago) Magnum API reference<br />
*** There was an effort that went on to have a swagger API doc, but it was abandoned. Magnum still doesn't have an API reference. Can we just go with what all the other projects are doing so we can finally have this?<br />
* Open Discussion<br />
<br />
== Backlog ==<br />
<br />
== Agenda Template ==<br />
* Roll Call<br />
* Announcements<br />
* Review Action Items<br />
* Essential Blueprint Review<br />
* Other Blueprints/Bugs/Reviews/Ideas<br />
* Open Discussion<br />
<br />
== Previous Meetings ==<br />
* [http://eavesdrop.openstack.org/meetings/containers/2016/ 2016 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2015/ 2015 Containers Team Meeting Archive]<br />
* [http://eavesdrop.openstack.org/meetings/containers/2014/ 2014 Containers Team Meeting Archive]<br />
<br />
== Container Networking Subteam Meeting ==<br />
<br />
The [https://wiki.openstack.org/wiki/ContainersTeam#Container_Networking_Subteam OpenStack Container Networking Subteam] no longer holds public meetings. The subteam has merged back into the general Magnum community. Magnum networking related topics and discussions will occur in the Magnum weekly [https://wiki.openstack.org/wiki/Meetings/Containers#Weekly_Containers_Team_Meeting IRC meeting] and the Magnum #openstack-containers irc channel. A big thank you to everyone who participated in the networking subteam.<br />
<br />
=== Previous Meetings ===<br />
* [http://eavesdrop.openstack.org/meetings/container_networking/2015/ 2015 Container Networking Subteam Meeting Archive]<br />
<br />
[[Category: Magnum]]<br />
[[category: meetings]]</div>Adrian Ottohttps://wiki.openstack.org/w/index.php?title=Design_Summit/Ocata/Etherpads&diff=136674Design Summit/Ocata/Etherpads2016-10-28T14:36:39Z<p>Adrian Otto: </p>
<hr />
<div>[[Category:Summit]]<br />
[[Category:Ocata]]<br />
[[Category:Etherpad]]<br />
<br />
The grand list of all the Ocata Design Summit sessions. Please include Date, Time, and links to etherpads when adding new content.<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__TOC__<br />
</div><br />
<br />
== Event intro/closure ==<br />
* Tue Oct 26 11:25am - Design Summit 101 - https://etherpad.openstack.org/p/ocata-design-summit-101<br />
* Fri Oct 29 12:30pm - Barcelona feedback session - https://etherpad.openstack.org/p/BCN-summit-feedback<br />
<br />
<br />
==Architecture Working Group==<br />
<br />
'''Wednesday, October 26'''<br />
* 11:25am-12:05pm - Cross Project workshops: Architecture Working Group Fishbowl - https://etherpad.openstack.org/p/ocata-summit-arch-wg<br />
<br />
==Barbican==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Barbican<br />
<br />
'''Thursday, October 27'''<br />
* 11:00am-11:40am - (128) Barbican: User and Operator Feedback Fishbowl - https://etherpad.openstack.org/p/barbican-ocata-summit-roadmap<br />
* 11:50am-12:30pm - (Montjuic) Barbican: Work Session (Roadmap) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50pm-02:30pm - (130) Barbican: Work Session (Cross Project)- https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
'''Friday, October 28'''<br />
* 09:00am-09:40am - (129) Barbican: Work Session (Security) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 09:50am-10:30am - (129) Barbican: Work Session (TBD) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:00am-11:40am - (129) Barbican: Work Session (Resources) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50am-12:30pm - (129) Barbican: Work Session (Planning) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
==Cinder==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cinder<br />
<br />
'''Wednesday October 26'''<br />
* 3:05pm-3:45pm - Cinder Test Working Group progress and status - https://etherpad.openstack.org/p/Cinder-testing<br />
* 3:55-4:35 - Driver bug fixes for unsupported OpenStack releases - https://etherpad.openstack.org/p/ocata-cinder-summit-stabledriverfixes<br />
* 5:05-5:45 - Stand alone Cinder service - https://etherpad.openstack.org/p/ocata-cinder-summit-standalonecinder<br />
* 5:55-6:35 - Pike (and beyond) planning - https://etherpad.openstack.org/p/ocata-cinder-summit-pikeplanning<br />
'''Thursday October 27'''<br />
* 9:00-9:40 - Replication - https://etherpad.openstack.org/p/ocata-cinder-summit-replication<br />
* 9:50-10:30 - Cinder-Nova API changes - https://etherpad.openstack.org/p/ocata-cinder-summit-attachdetach<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 11:00am-11:40am - NFS snapshots - https://etherpad.openstack.org/p/ocata-cinder-summit-nfssnapshots<br />
* 11:50am-12:30pm - Cinder backup improvements - https://etherpad.openstack.org/p/ocata-cinder-summit-backupimprovements<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-cinder-summit-meetup<br />
<br />
==Cross Project Sessions==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cross+Project<br />
<br />
'''Tuesday October 25'''<br />
<br />
* 3:55 PM - 4:35 PM -- Experiences with Project Decomposition, Scaling Review Teams and Subsystem Maintainers (Part 1) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 3.55PM - 4.35 PM -- Cross-Service Communication -- https://etherpad.openstack.org/p/ocata-xp-cross-service-communication<br />
* 5:05 PM - 5:45 PM -- Discuss Community-Wide Release Goals -- https://etherpad.openstack.org/p/ocata-summit-xp-community-wide-goals <br />
* 5:05 PM - 5:45 PM -- Unified Capabilities Discovery API -- https://etherpad.openstack.org/p/ocata-xp-unified-capabilities-api<br />
* 5:55 PM - 6:35 PM -- Python 3 Integration Testing -- https://etherpad.openstack.org/p/ocata-python-3<br />
* 5:55 PM - 6:35 PM -- Where to Draw the Line for Proprietary Code with Drivers -- https://etherpad.openstack.org/p/ocata-xp-proprietary-drivers<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 11:25 AM - 12:05 PM -- Architecture Working Group Fishbowl -- https://etherpad.openstack.org/p/BCN-architecture-wg<br />
* 11:25 AM - 12:05 PM -- Ocata goal: Remove Incubated Oslo Code -- https://etherpad.openstack.org/p/ocata-goal-oslo<br />
* 12:15 PM - 12:55 PM -- "Re-Inventing the TC", the Stewardship Working Group Discussion -- https://etherpad.openstack.org/p/Barcelona-SWG-cp<br />
* 12:15 PM - 12:55 PM -- Rolling Upgrades, and the Road to Zero-Downtime -- https://etherpad.openstack.org/p/ocata-xp-upgrades<br />
* 2:15 PM - 2:55 PM -- Experiences with project decomposition, scaling review teams and subsystem maintainers (part 2) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 2:15 PM - 2:55 PM -- Driver Log Validation -- https://etherpad.openstack.org/p/driverlog-validation<br />
<br />
==Documentation==<br />
<br />
Documentation sessions in schedule: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Documentation<br />
<br />
'''Tuesday, October 25'''<br />
* 5:05pm-6:35pm - Ops: Documentation - https://etherpad.openstack.org/p/BCN-ops-docs_(double_session)<br />
'''Wednesday, October 26'''<br />
* 5:05pm-5:45pm - User Guides Working Group - https://etherpad.openstack.org/p/BCN-Docs-UserGuidesWG<br />
'''Thursday October 27'''<br />
* 2:40pm-3:20pm - Newton Retrospective - https://etherpad.openstack.org/p/BCN-Docs-NewtonRetro <br />
* 3:30pm-4:10pm - Social Things - https://etherpad.openstack.org/p/BCN-Docs-Social <br />
* 4:40pm-5:20pm - Training Labs - https://etherpad.openstack.org/p/BCN-Docs-Training <br />
* 5:30pm-6:10pm - Toolchain - https://etherpad.openstack.org/p/BCN-Docs-Toolchain <br />
'''Friday October 28'''<br />
* 11:00am-11:40am - API Working Group - https://etherpad.openstack.org/p/BCN-Docs-APIWG <br />
* 11:50am-12:30pm - Ocata Planning Working Group - https://etherpad.openstack.org/p/BCN-Docs-OcataPlanningWG <br />
* 2:00pm-6:00pm - Contributors Meetup - no etherpad<br />
<br />
==Glance==<br />
* https://etherpad.openstack.org/p/ocata-glance-glance-store-refactoring<br />
* https://etherpad.openstack.org/p/ocata-glance-image-locations<br />
* https://etherpad.openstack.org/p/ocata-glance-service-tokens<br />
* https://etherpad.openstack.org/p/ocata-glance-prioritization-and-roadmap<br />
* https://etherpad.openstack.org/p/ocata-glance-contributors-meetup<br />
<br />
== Gluon ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Gluon%3A<br />
<br />
Fri 28, 9:50am-10:30am: Gluon Work Session https://etherpad.openstack.org/p/ocata-gluon-work-plan<br />
<br />
==Heat==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Heat<br />
<br />
'''Thursday October 27'''<br />
<br />
* 11:00am-11:40am - Convergence Phase 1 - What worked, What didn't - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-1<br />
* 11:50am-12:30pm - Performance Scalability Improvements - I (Issues with very large stacks) - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-1<br />
* 2:40pm-3:20pm - Performance Scalability Improvements - II - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-2<br />
* 3:30pm-4:10pm - Convergence Phase 2 - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-2<br />
* 4:40pm-5:20pm - Validation Improvements - https://etherpad.openstack.org/p/heat-ocata-validation-improvements<br />
<br />
'''Friday October 28'''<br />
<br />
* 9:00am-9:40am - RPC versioning and hitless upgrades - https://etherpad.openstack.org/p/heat-ocata-hitless-upgrades<br />
* 9:50am-10:30am - API Microversions - https://etherpad.openstack.org/p/heat-ocata-api-microversions<br />
* 11:00am-11:40am - Heat Integration tests, Tempest and test candidates for DefCore Interop Testing - https://etherpad.openstack.org/p/heat-ocata-test-coverage<br />
* 11:50am-12:30pm - Improve maturity of heat - https://etherpad.openstack.org/p/heat-ocata-improve-maturity<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-heat-contributor-meetup<br />
<br />
<br />
==Horizon==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Horizon%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 16:55-17:35 - Cross-project meeting with Horizon and Keystone - https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00-09:40 - Operator/ Plugin feedback - https://etherpad.openstack.org/p/horizon-ocata-feedback<br />
* 09:50-10:30 - Newton retrospective, Ocata timeline, Dependencies, Testing!! and Selenium :-( - https://etherpad.openstack.org/p/horizon-ocata-planning<br />
* 16:40-17:20 - Cross-project topics; Glance, Identity, K2K Federation, Quotas - https://etherpad.openstack.org/p/horizon-ocata-cross-project<br />
* 17:30-18:10 - AngularJS state of play (where we're going, status of panels, what CORS means, do we want a thin service proxy, deprecations, etc.) -https://etherpad.openstack.org/p/horizon-ocata-angularjs<br />
<br />
'''Friday October 28'''<br />
<br />
* 11:50-12:30 - Priority setting (and TODO review if we have time) - https://etherpad.openstack.org/p/horizon-ocata-priorities<br />
* 14:00-18:00 - General project discussion (Newton retrospective, how to improve our organisation and use of tooling)<br />
<br />
== I18n ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=I18n%3A<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/barcelona-i18n-meetup<br />
<br />
==Infrastructure==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Infrastructure%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 3:05pm-3:45pm: ''Work Session: Firehose'' in AC Hotel - P3 - Montjuic<br />
** https://etherpad.openstack.org/p/ocata-infra-firehose<br />
<br />
'''Thursday October 27'''<br />
<br />
* 2:40pm-3:20pm: ''Fishbowl: Status update and plans for task tracking'' in AC Hotel - P1 - Salon Barcelona<br />
** https://etherpad.openstack.org/p/ocata-infra-community-task-tracking<br />
<br />
'''Friday October 28'''<br />
<br />
All the sessions on Friday are taking place at CCIB - Centre de Convencions Internacional de Barcelona - P1<br />
<br />
* 9:00am-9:40am: ''Work Session: Next steps for infra-cloud'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud<br />
* 9:50am-10:30am: ''Work Session: Interactive infra-cloud debugging'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud-debugging<br />
* 11:00am-11:40am: ''Work Session: Test environment expectations'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-test-env-expectations<br />
* 11:50am-12:30pm: ''Work Session: Xenial jobs transition for stable/newton'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-xenial-stable-newton<br />
* 2:00pm-6:00pm: ''Contributors Meetup'' in Room 121<br />
** https://etherpad.openstack.org/p/ocata-infra-contributors-meetup<br />
<br />
==Ironic==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ironic:<br />
<br />
'''Wednesday October 26'''<br />
* 5ː05pm-5ː45pm - API Evolution - https://etherpad.openstack.org/p/ironic-ocata-summit-api-evolution<br />
* 5:55pm-6:35pm - Deploy-time RAID and Advanced Partitioning (w/ Nova) - https://etherpad.openstack.org/p/ironic-ocata-summit-deploy-time-raid<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Task Framework - https://etherpad.openstack.org/p/ironic-ocata-summit-task-framework<br />
* 9:50am-10:30am - QA/CI - https://etherpad.openstack.org/p/ironic-ocata-summit-qa<br />
* 1:50pm-2:30pm - Synchronizing Events with Neutron - https://etherpad.openstack.org/p/ironic-ocata-summit-neutron-events<br />
* 2:40pm-3:20pm - Ocata Priorities - https://etherpad.openstack.org/p/ironic-ocata-summit-priorities<br />
'''Friday October 28'''<br />
* 11:00am-11:40am - VNC Console - https://etherpad.openstack.org/p/ironic-ocata-summit-vnc-console<br />
* 11:50am-12:30pm - Unblocking Priority Features - https://etherpad.openstack.org/p/ironic-ocata-summit-unblock-priorities<br />
* 2:00pm-6:00pm - Contributors Meetup - https://etherpad.openstack.org/p/ironic-ocata-summit-contributor-meetup<br />
<br />
<br />
== Karbor ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Karbor<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-5:45pm - Use Case Round Table - https://etherpad.openstack.org/p/karbor-ocata-use-cases<br />
'''Thursday October 27'''<br />
* 4:40pm-5:20pm - Ocata Roadmap - https://etherpad.openstack.org/p/karbor-ocata-roadmap<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Karbor Essentials and Internals - https://etherpad.openstack.org/p/karbor-ocata-essentials-internals<br />
* 9:50am-10:30am - Karbor Integration - https://etherpad.openstack.org/p/karbor-ocata-integration<br />
* 11:00am-11:40am - Cross-Site Backup and Restore - https://etherpad.openstack.org/p/karbor-ocata-cross-site<br />
* 11:50am-12:30pm - Additional Protectables - https://etherpad.openstack.org/p/karbor-ocata-additional-protectables<br />
<br />
<br />
== Keystone ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Keystone%3A<br />
<br />
Wed 26, 3:05pm-3:45pm<br />
Keystone: Newton retrospective (Fishbowl)<br />
https://etherpad.openstack.org/p/keystone-newton-retrospective<br />
<br />
Wed 26, 3:55pm-4:35pm<br />
Keystone: keystone/horizon integration<br />
https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
Thu 27, 11:00pm-11:40pm<br />
Keystone: Unconference (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-unconference<br />
<br />
Thu 27, 11:50pm-12:30pm<br />
Keystone: Ocata priorities (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-priorities<br />
<br />
Thu 27, 1:50pm-2:30pm<br />
Keystone: Work session (Federation)<br />
https://etherpad.openstack.org/p/ocata-keystone-federation<br />
<br />
Thu 27, 2:40pm-3:20pm<br />
Keystone: Work session (Testing)<br />
https://etherpad.openstack.org/p/ocata-keystone-testing<br />
<br />
Thu 27, 3:30pm-4:10pm<br />
Keystone: Work session (Documentation)<br />
https://etherpad.openstack.org/p/ocata-keystone-documentation<br />
<br />
Fri 28, 9:00am-9:40am<br />
Keystone: Work session (Authorization)<br />
https://etherpad.openstack.org/p/ocata-keystone-authorization<br />
<br />
Fri 28, 9:50am-10:30am<br />
Keystone: Work session (Authentication)<br />
https://etherpad.openstack.org/p/ocata-keystone-authentication<br />
<br />
Fri 28, 11:00pm-11:40pm<br />
Keystone: Work session (Scaling and Performance)<br />
https://etherpad.openstack.org/p/ocata-keystone-scaling<br />
<br />
Fri 28, 11:50pm-12:30pm<br />
Keystone: Work session (Integration)<br />
https://etherpad.openstack.org/p/ocata-keystone-integration<br />
<br />
Fri 28, 2:00pm-6:00pm<br />
Keystone: Contributors meetup<br />
(No etherpad)<br />
<br />
== Kolla ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Kolla%3A<br />
<br />
Kolla Ocata Summit Master Etherpad - https://etherpad.openstack.org/p/kolla-o-summit-schedule<br />
<br />
'''Wed October 26'''<br />
<br />
* 3:55pm - 4:35pm - Operator experiences - https://etherpad.openstack.org/p/kolla-o-summit-op-experiences<br />
* 5:05pm - 5:45pm - Community roadmap planning for O - https://etherpad.openstack.org/p/kolla-o-summit-community-planning<br />
* 5:55pm - 6:35pm - Goals for Ocata - https://etherpad.openstack.org/p/kolla-o-summit-roadmap<br />
<br />
'''Thu October 27'''<br />
<br />
* 9:00am - 9:40am - Kolla-Kubernetes Architecture - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-architecture<br />
* 9:50am - 10:30am - High availability - https://etherpad.openstack.org/p/kolla-o-summit-high-availability<br />
* 1:50pm - 2:30pm - 3rd Party Plugins - https://etherpad.openstack.org/p/kolla-o-summit-3rd-party-plugins<br />
* 2:40pm - 3:20pm - Distro requirements, deprecation, levels of support - https://etherpad.openstack.org/p/kolla-o-summit-support-and-deprecation<br />
* 3:30pm - 4:10pm - Improving the CI system - https://etherpad.openstack.org/p/kolla-o-summit-improving-ci<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Documentation - https://etherpad.openstack.org/p/kolla-o-summit-documentation<br />
* 9:50am - 10:30am - OSIC review - https://etherpad.openstack.org/p/kolla-o-summit-OSIC-review<br />
* 11:00am - 11:40am - Kolla-Kubernetes Roadmap - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-road-map<br />
* 11:50am - 12:30pm - Security VMT threat - https://etherpad.openstack.org/p/kolla-ocata-summit-threat-analysis<br />
* 2:00pm - 6:00pm - Afternoon Contributor Meetup - https://etherpad.openstack.org/p/kolla-ocata-summit-contrib-meetup<br />
<br />
==Magnum==<br />
* Next Generation Clusters with NodeGroup Pools https://etherpad.openstack.org/p/magnum-ocata-nodegroup<br />
* Lifecycle Operations, Cluster Maintenance, and Trust https://etherpad.openstack.org/p/magnum-ocata-lifecycle (Same etherpad for upgrades)<br />
* Magnum Scalability https://etherpad.openstack.org/p/magnum-ocata-scalability<br />
* Magnum Work Session: Creds/Certs Management https://etherpad.openstack.org/p/ocata-magnum-tls<br />
* Magnum: COE Support in Magnum Cluster Drivers https://etherpad.openstack.org/p/ocata-magnum-coe-support<br />
* Magnum Container Monitoring https://etherpad.openstack.org/p/ocata-magnum-monitoring<br />
* Magnum Contributor Meetup https://etherpad.openstack.org/p/magnum-ocata-summit-meetup<br />
<br />
==Manila==<br />
<br />
'''Thu October 27'''<br />
<br />
* 11:00 - 11:40 - Race Conditions (FB) - https://etherpad.openstack.org/p/ocata-manila-race-conditions<br />
* 11:50 - 12:30 - Data Service Jobs Table (FB) - https://etherpad.openstack.org/p/ocata-manila-data-service-jobs-table<br />
* 14:40 - 15:20 - High Availability (WS) - https://etherpad.openstack.org/p/ocata-manila-high-availability<br />
<br />
'''Fri April 28'''<br />
<br />
* 11:00 - 11:40 - Access Rules (WS) - https://etherpad.openstack.org/p/ocata-manila-access-rules<br />
* 11:50 - 12:30 - Tempest Direction (WS) - https://etherpad.openstack.org/p/ocata-manila-tempest-direction<br />
* 14:00 - 18:00 - Contributor Meetup (CM) - https://etherpad.openstack.org/p/ocata-manila-contributor-meetup<br />
<br />
==Monasca==<br />
<br />
'''Fri October 28'''<br />
<br />
* 9:00 - 9:40 - Multi-tenancy for logging - https://etherpad.openstack.org/p/monasca-ocata-log-multitenancy<br />
<br />
==Neutron==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 17:05 - 17:45 - Nova/Neutron cross-project session Nova - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
* 17:55 - 18:35 - LBaaS retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-octavia-lbaas-session<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00 - 09:40 - Completing the Newton backlog - https://etherpad.openstack.org/p/ocata-neutron-core-newton-backlog<br />
* 09:50 - 10:30 - Upstream and dowstream CI and testing efforts - https://etherpad.openstack.org/p/ocata-neutron-testing<br />
* 11:00 - 11:40 - End user and operator feedback - https://etherpad.openstack.org/p/ocata-neutron-end-user-operator-feedback<br />
* 11:50 - 12:30 - Neutronclient retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-client<br />
* 17:30 - 18:10 - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
<br />
'''Friday October 28'''<br />
<br />
* 09:00 - 09:40 (Sagrada Familia) Fishbowl Neutron: Neutron-lib retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-lib-next-steps<br />
* 09:50 - 10:30 (Sagrada Familia) Fishbowl Neutron: Neutron server: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-server-next<br />
* 11:00 - 11:40 (Sagrada Familia) Fishbowl Neutron: Neutron agents: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-agents<br />
* 11:50 - 12:30 (Sagrada Familia) Fishbowl Neutron: Stadium update - https://etherpad.openstack.org/p/ocata-nova-neutron-stadium<br />
* 14:00 - 18:00 (Room 114) Meetup Neutron: Contributors meetup - https://etherpad.openstack.org/p/ocata-neutron-contributor-meetup<br />
<br />
==Nomad==<br />
<br />
https://etherpad.openstack.org/p/nomad-ocata-design-session<br />
<br />
== Nova ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Nova%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-5:45pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Newton placement service retrospective - https://etherpad.openstack.org/p/ocata-nova-summit-placement-retrospective<br />
* 9:50am-10:30am - Scheduler / resource providers (quantitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-quantitative<br />
* '''Break'''<br />
* 11:00am-11:40am - Scheduler / resource provider traits (qualitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-qualitative<br />
* 11:50am-12:30pm - Organizing API work for Ocata - https://etherpad.openstack.org/p/ocata-nova-summit-api<br />
* '''Lunch'''<br />
* 1:50pm-2:30pm - Unconference - https://etherpad.openstack.org/p/ocata-nova-summit-unconference<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
* 3:30pm-4:10pm - Cells v2 (quotas) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-quotas<br />
* '''Break'''<br />
* 4:40pm-5:20pm - Completing vendordata v2 - https://etherpad.openstack.org/p/ocata-nova-summit-vendoradatav2<br />
* 5:30pm-6:10pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 9:50am-10:30am - Security specs and testing - https://etherpad.openstack.org/p/ocata-nova-summit-security<br />
* '''Break'''<br />
* 11:00am-11:40am - Planning the libvirt imagebackend refactor work - https://etherpad.openstack.org/p/ocata-nova-summit-libvirt-imagebackend<br />
* 11:50am-12:30pm - Ocata priorities and schedule - https://etherpad.openstack.org/p/ocata-nova-summit-priorities<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-nova-summit-meetup<br />
<br />
== OpenStack-Ansible ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=openstackansible%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-6:35pm - OpenStack-Ansible prioritization/work discussion - https://etherpad.openstack.org/p/ocata-osa-summit-work-prioritization<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - OpenStack-Ansible Newton cycle overview & Ocata preview- https://etherpad.openstack.org/p/ocata-osa-summit-overview<br />
* 9:50am-10:30am - How to get involved in OpenStack-Ansible - https://etherpad.openstack.org/p/ocata-osa-summit-onboarding<br />
* '''Break'''<br />
* 11:00am-12:30am - Upgrade improvements and discussion - https://etherpad.openstack.org/p/ocata-osa-summit-upgrades<br />
* '''Lunch'''<br />
* '''Break'''<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Inventory improvements/discussion - https://etherpad.openstack.org/p/ocata-osa-summit-inventory<br />
* 9:50am-10:30am - Testing/gating discussion - https://etherpad.openstack.org/p/ocata-osa-summit-testing<br />
* '''Break'''<br />
* 11:00am-11:40am - If we had a clean slate, what would we do differently - Ideas session - https://etherpad.openstack.org/p/ocata-osa-summit-cleanslate<br />
* 11:50am-12:30pm - Configuration/role discussion and improvements - https://etherpad.openstack.org/p/ocata-osa-summit-config<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-osa-summit-contributors-meetup<br />
<br />
== Ops ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ops%3A<br />
<br />
'''Tuesday October 25'''<br />
<br />
3:05pm-3:45pm<br />
<br />
https://etherpad.openstack.org/p/BCN-ops-openstack-cli<br />
<br />
== Oslo ==<br />
<br />
'''Tuesday October 25'''<br />
<br />
3:05pm-3:45pm<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16217/live-from-oslo <br />
<br />
3:55pm-4:35pm<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15683/message-routing-a-next-generation-alternative-to-rabbitmq<br />
<br />
'''Wednesday October 26'''<br />
<br />
11:25am-12:05pm<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16941/cross-project-workshops-ocata-goal-remove-incubated-oslo-code<br />
<br />
https://etherpad.openstack.org/p/ocata-goal-oslo<br />
<br />
'''Thursday October 27'''<br />
<br />
9:00am-9:40am<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16980/oslo-bring-your-library-ideas-any-ideas-welcome-2-for-1<br />
<br />
https://etherpad.openstack.org/p/ocata-oslo-bring-ideas<br />
<br />
11:00am-11:40am<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16969/oslo-deep-dive-into-implementation-of-the-amqp-1-0-driver<br />
<br />
https://etherpad.openstack.org/p/ocata-oslo-deep-dive-amqp1<br />
<br />
1:50pm-2:30pm<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16997/oslo-consistent-apis-across-different-oslo-messaging-backends<br />
<br />
https://etherpad.openstack.org/p/ocata-oslo-consistent-mq-backends<br />
<br />
2:40pm-3:20pm<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17124/oslo-work-session<br />
<br />
'''Friday October 28'''<br />
<br />
Work sessions:<br />
<br />
9:00am-9:40am<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17184/oslo-work-session<br />
<br />
https://etherpad.openstack.org/p/ocata-oslo-mq-perms<br />
<br />
9:50am-10:30am<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17185/oslo-work-session<br />
<br />
https://etherpad.openstack.org/p/ocata-oslo-policy-code<br />
<br />
11:00am-11:40am<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17186/oslo-work-session<br />
<br />
https://etherpad.openstack.org/p/ocata-oslo-zmq-deeper<br />
<br />
11:50am-12:30pm<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17187/oslo-work-session<br />
<br />
https://etherpad.openstack.org/p/ocata-oslo-jepsen<br />
<br />
Contributors meetup:<br />
<br />
2:00pm-6:00pm<br />
<br />
== Rally ==<br />
<br />
''' Friday October 28'''<br />
<br />
https://etherpad.openstack.org/p/rally-roadmap-ocata<br />
<br />
== Release Management ==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 5:55 PM - 6:35 PM -- Work session -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
'''Thursday October 27'''<br />
<br />
* 1:50 PM - 2:30 PM -- Newton Retrospective & Ocata Schedule -- https://etherpad.openstack.org/p/ocata-release-fishbowl<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00 PM - 6:00 PM -- Contributors Meetup -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
== RPM Packaging ==<br />
<br />
'''Thursday October 27'''<br />
<br />
* 4:40 PM - 5:20 PM -- Fishbowl -- https://etherpad.openstack.org/p/ocata-rpm-packaging-fishbowl<br />
<br />
'''Friday October 28'''<br />
<br />
* 9:00 AM - 10:30 AM -- Fishbowl -- https://etherpad.openstack.org/p/ocata-rpm-packaging-work-session<br />
<br />
== Searchlight ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Searchlight<br />
<br />
'''Thursday October 27'''<br />
* 9:50 - 10:30 - Fishbowl: Adding service plugins to Searchlight and what it can add to UIs - https://etherpad.openstack.org/p/ocata-searchlight-summit-plugins-fishbowl<br />
* 11:00 - 11:40 - Improving ease of use for searching - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 11:50 - 12:30 - Error handling during notifications - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
<br />
== Senlin ==<br />
<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Senlin work session: policy/profile versioning - https://etherpad.openstack.org/p/ocata-summit-senlin-profile-policy-versioning<br />
* 9:50am-10:30am - Senlin work session: versioned everything - https://etherpad.openstack.org/p/ocata-summit-senlin-versioned-everything<br />
* '''Break'''<br />
* 11:00am-11:40am - Senlin work session: container cluster - https://etherpad.openstack.org/p/ocata-summit-senlin-container-cluster<br />
* 11:50am-12:30am - Senlin work session: HA - https://etherpad.openstack.org/p/ocata-summit-senlin-HA<br />
<br />
== Stewardship Working Group ==<br />
<br />
'''Wed October 26'''<br />
<br />
*12:15pm - 12:55pm - Cross Project workshops: "Re-inventing the TC", the Stewardship Working Group discussion - https://etherpad.openstack.org/p/Barcelona-SWG-cp<br />
<br />
== Telemetry ==<br />
<br />
'''Thursday October 27'''<br />
<br />
* 11:00am-11:40am – Deprecating Ceilometer API (part 1) – https://etherpad.openstack.org/p/ocata-summit-telemetry-deprecating-ceilometer-api<br />
* 11:50am-12:30pm – Deprecating Ceilometer API (part 2) – https://etherpad.openstack.org/p/ocata-summit-telemetry-deprecating-ceilometer-api<br />
* 1:50pm-2:30pm – Ceilometer roadmap – https://etherpad.openstack.org/p/ocata-summit-telemetry-ceilometer<br />
<br />
<br />
'''Friday October 28'''<br />
* 11:00am-11:40am – Aodh roadmap – https://etherpad.openstack.org/p/ocata-summit-telemetry-aodh<br />
* 11:50am-12:30pm – Gnocchi roadmap – https://etherpad.openstack.org/p/ocata-summit-telemetry-gnocchi<br />
<br />
<br />
== QA (Quality Assurance) ==<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00am-09:40am - Workroom QA: Work session – https://etherpad.openstack.org/p/ocata-qa-tempest-cloud-testing<br />
* 09:50am-10:30am - (Devstack) devstack-plugin additional-pkg-repos – https://etherpad.openstack.org/p/ocata-qa-devstack-plugin<br />
* 11:00am-11:40am - (New project) Destructive testing (os-fault, etc) - https://etherpad.openstack.org/p/ocata-qa-destructive-testing<br />
* 13:50am-14:30am - (Tempest) Plugins: roadmap for the projects and TC proposal - https://etherpad.openstack.org/p/ocata-qa-tempest-plugin-repos<br />
* 16:40am-17:20am - (New project) Policy testing - https://etherpad.openstack.org/p/ocata-qa-policy-testing<br />
<br />
'''Friday October 28'''<br />
* 11:00am-11:40am - (OpenStack-Health) What should we add/chage features? - https://etherpad.openstack.org/p/ocata-qa-openstack-health<br />
* 11:50am-12:30am - Ocata Priorities - https://etherpad.openstack.org/p/ocata-qa-priorities<br />
<br />
== Tricircle ==<br />
<br />
Venue: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tricircle%3A<br />
<br />
ideas: https://etherpad.openstack.org/p/ocata-tricircle-sessions-planning<br />
<br />
'''Thu October 27'''<br />
<br />
* 5:30pm - 6:10pm - Cross Neutron networking automation: feature review and what's to do in Ocata : https://etherpad.openstack.org/p/ocata-tricircle-feature-review-priorities-roadmap<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Ocata work session: https://etherpad.openstack.org/p/ocata-tricircle-work-session<br />
* 9:40am - 12:00am - Tricricle contributors meetup<br />
<br />
== TripleO ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tripleo%3A<br />
<br />
https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
===== TripleO: Containers - Current Status and Roadmap =====<br />
Wed 26 3:55pm-4:35pm<br />
https://etherpad.openstack.org/p/ocata-tripleo-containers<br />
<br />
=====TripleO: Work Session - Growing the team=====<br />
Wed 26 5:05pm-5:45pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-team-growing<br />
<br />
===== TripleO: Work Session - CI - current status and roadmap=====<br />
Wed 26 5:55pm-6:35pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-ci<br />
<br />
===== TripleO: Upgrades - current status and roadmap=====<br />
Thu 27 1:50pm-2:30pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-upgrades<br />
<br />
===== TripleO: Work Session - Composable Undercloud deployment with Heat=====<br />
Fri 28 9:00am-9:20am -<br />
https://etherpad.openstack.org/p/tripleo-composable-undercloud<br />
<br />
===== TripleO: Work Session - GUI, CLI, Validations current status, roadmap, requirements=====<br />
Fri 28 9:20am-9:40am -<br />
https://etherpad.openstack.org/p/gui-ocata<br />
<br />
===== TripleO: Work Session - Multiple topics=====<br />
Fri 28 9:50am-10:30am -<br />
Blueprints, specs, tools and Ocata summary.<br />
See bottom of https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
== Trove ==<br />
<br />
https://etherpad.openstack.org/p/trove-barcelona-sessions <br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Trove<br />
<br />
==Watcher==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Watcher<br />
<br />
'''Wed October 26'''<br />
<br />
* 5.55pm - 6.35pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Existing & new infrastructure optimization strategies]<br />
<br />
'''Thu October 27'''<br />
<br />
* 9.50am - 10.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Watcher Newton retrospective]<br />
<br />
'''Fri April 28'''<br />
<br />
* 11am - 12.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Ocata priorities & roadmap]<br />
* 2pm - 6pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Contributors meetup]<br />
<br />
==Zaqar==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Zaqar<br />
<br />
'''Thursday, October 27'''<br />
<br />
9:50am-10:30am [https://etherpad.openstack.org/p/zaqar-ocata-performance Zaqar's profile and performance gate]<br />
<br />
4:40pm-5:00pm [https://etherpad.openstack.org/p/zaqar-ocata-notification-delivery-policy Notification delivery policy]<br />
<br />
5:00pm-5:20pm [https://etherpad.openstack.org/p/zaqar-ocata-purge-queue Purge queue]<br />
<br />
5:30pm-6:10pm [https://etherpad.openstack.org/p/zaqar-ocata-subscription-confirmation-email Subscription Confirmation - Email]<br />
<br />
==Storlets==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Storlets<br />
<br />
https://etherpad.openstack.org/p/storlets-otaca-design-summit<br />
<br />
'''Wednesday, October 26'''<br />
<br />
3:05pm-3:45pm Spark-Storlets and Storlets Deep-Dive<br />
<br />
3:55pm-4:35pm [https://etherpad.openstack.org/p/storlets-ocata-work-session Work session]<br />
<br />
==Meghdwar==<br />
"Friday, October 28"<br />
11.50am-12.30am - Meghdwar Work Session <br />
Please follow up on Infra work session at P1-115 f2f decide on how to work with Senlin and Infra team to get meghdwar Edge Gateway services moving<br />
https://etherpad.openstack.org/p/meghdwar<br />
...</div>Adrian Otto