Difference between revisions of "Meetings/Kolla"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
Line 15: | Line 15: | ||
* we're overloading the term "pod" in a way that can make devs/ops assume they are less functional then they are. What should we do? - this is a old one, which may not talked in last meet, we can skip it if no one care. | * we're overloading the term "pod" in a way that can make devs/ops assume they are less functional then they are. What should we do? - this is a old one, which may not talked in last meet, we can skip it if no one care. | ||
* kolla-kubernetes UX for service layers - portdirect | * kolla-kubernetes UX for service layers - portdirect | ||
− | |||
* ad-hoc meetings related discussion | * ad-hoc meetings related discussion | ||
* Open Discussion | * Open Discussion |
Revision as of 15:40, 21 December 2016
Contents
Weekly Kolla team meeting
MEETING TIME: Wednesdays at 16:00 UTC #openstack-meeting-4
.
Agenda for next meeting
* Roll-call * Announcements * fixed uid/gid - jeffrey4l * replace heka with fluentd - zhubingbing * Zero-downtime upgrade support in Kolla - duonghq * Is the Nova Bug Dashboard (http://kolla.betacloud.io/bugs-dashboard.html) useful for us? - berendt * we're overloading the term "pod" in a way that can make devs/ops assume they are less functional then they are. What should we do? - this is a old one, which may not talked in last meet, we can skip it if no one care. * kolla-kubernetes UX for service layers - portdirect * ad-hoc meetings related discussion * Open Discussion
Regular agenda
Copy/Paste into IRC to kick the meeting off:
#startmeeting kolla
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
Previous meetings
- IRC logs [1]