Jump to: navigation, search

Difference between revisions of "Meetings/Kolla"

(Agenda for next meeting (Mar 1st 2017))
(Agenda for next meeting (11th December 2019))
 
(241 intermediate revisions by 21 users not shown)
Line 1: Line 1:
  
 
= Weekly Kolla team meeting =
 
= Weekly Kolla team meeting =
'''MEETING TIME: Wednesdays at 16:00 UTC  <code><nowiki>#openstack-meeting-4</nowiki></code>.
+
'''MEETING TIME: Wednesdays at 15:00 UTC  <code><nowiki>#openstack-kolla</nowiki></code>.
  
== Agenda for next meeting (Mar 1st 2017) ==
+
We track CI, release, and feature status in the [https://etherpad.openstack.org/p/KollaWhiteBoard whiteboard].
 +
 
 +
== Agenda for next meeting (11th December 2019) ==
  
 
<pre>
 
<pre>
 
* Roll-call
 
* Roll-call
 
* Announcements
 
* Announcements
* Applying for the Stable project maturity tag (reference: https://review.openstack.org/#/c/435067/29/tests/bin/common_iscsi_config.sh) [timebox 20 mins]
+
* Review action items from last meeting
* serial in kolla-ansible ( jeffrey4l) https://review.openstack.org/438374
+
* CI status
* ks-rolling-upgrade discussion for better way of its implementation (duonghq, sp)
+
* Train release planning
* post-ptg bps
+
* Ussuri release planning
* Open Discussion
+
** Support for Train redeployment on C8, we are already diverging with support for Train
 +
* Review priorities
 
</pre>
 
</pre>
  
Line 19: Line 22:
 
<pre>
 
<pre>
 
#startmeeting kolla
 
#startmeeting kolla
</pre>
+
</pre>Kolla target BPs and revision of release for every deliverable
  
 
Then, once the bot has caught up and everyone is settled:
 
Then, once the bot has caught up and everyone is settled:
Line 38: Line 41:
 
* https://bugs.launchpad.net/kolla/
 
* https://bugs.launchpad.net/kolla/
 
* https://blueprints.launchpad.net/kolla
 
* https://blueprints.launchpad.net/kolla
 +
* https://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-coKolla target BPs and revision of release for every deliverablentainers
 +
* https://review.openstack.org/#/c/434946/
 +
* https://review.openstack.org/#/c/504801
 +
 
<pre>
 
<pre>
 
#link https://bugs.launchpad.net/kolla
 
#link https://bugs.launchpad.net/kolla
 
#link https://blueprints.launchpad.net/kolla
 
#link https://blueprints.launchpad.net/kolla
 +
#link https://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-containers
 +
#link https://review.openstack.org/#/c/434946/
 
</pre>
 
</pre>
  
Line 46: Line 55:
  
 
* IRC logs [http://eavesdrop.openstack.org/meetings/kolla]
 
* IRC logs [http://eavesdrop.openstack.org/meetings/kolla]
 +
 +
== 10 minute warning ==
 +
 +
Please add your name to the following list if you would like a 10 minute warning in #openstack-kolla.
 +
<pre>
 +
mgoddard mnasiadka hrw egonzalez yoctozepto rafaelweingartne
 +
</pre>

Latest revision as of 08:27, 10 December 2019

Weekly Kolla team meeting

MEETING TIME: Wednesdays at 15:00 UTC #openstack-kolla.

We track CI, release, and feature status in the whiteboard.

Agenda for next meeting (11th December 2019)

* Roll-call
* Announcements
* Review action items from last meeting
* CI status
* Train release planning
* Ussuri release planning
 ** Support for Train redeployment on C8, we are already diverging with support for Train
* Review priorities

Regular agenda

Copy/Paste into IRC to kick the meeting off:

#startmeeting kolla
Kolla target BPs and revision of release for every deliverable

Then, once the bot has caught up and everyone is settled:

#topic rollcall

Once folks have checked in, run the agenda by the group present:

#topic agenda
cut and paste agenda from above

Copy/Paste for IRC

#link https://bugs.launchpad.net/kolla
#link https://blueprints.launchpad.net/kolla
#link https://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-containers
#link https://review.openstack.org/#/c/434946/

Previous meetings

10 minute warning

Please add your name to the following list if you would like a 10 minute warning in #openstack-kolla.

mgoddard mnasiadka hrw egonzalez yoctozepto rafaelweingartne