Jump to: navigation, search

Difference between revisions of "Meetings/Kolla"

m (Agenda for next meeting (Dec. 13th, 2017))
(Agenda for next meeting (Dec. 20th, 2017))
Line 3: Line 3:
 
'''MEETING TIME: Wednesdays at 16:00 UTC  <code><nowiki>#openstack-meeting-4</nowiki></code>.
 
'''MEETING TIME: Wednesdays at 16:00 UTC  <code><nowiki>#openstack-meeting-4</nowiki></code>.
  
== Agenda for next meeting (Dec. 20th, 2017) ==
+
== Agenda for next meeting (Jan. 10th, 2018) ==
  
 
<pre>
 
<pre>
 
* Roll-call
 
* Roll-call
 
* Announcements
 
* Announcements
* Image containers lifecycle: how to differentiate on docker registry between tested/untested images? Staging/stable? (gema)
+
* mariadb 10.1
* State of deploying on AArch64 (hrw)
 
* Docker name for Debian - https://review.openstack.org/#/c/522712/ (for "kolla-ansible bootstrap-servers")
 
* cpu_mode for Nova - https://review.openstack.org/#/c/529270/ (to get VMs running)
 
* mariadb bootstrap - https://review.openstack.org/#/c/529199/ (for "kolla-ansible deploy" to succeed)
 
 
</pre>
 
</pre>
  

Revision as of 08:12, 8 January 2018

Weekly Kolla team meeting

MEETING TIME: Wednesdays at 16:00 UTC #openstack-meeting-4.

Agenda for next meeting (Jan. 10th, 2018)

* Roll-call
* Announcements
* mariadb 10.1

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