Difference between revisions of "Meetings/Kolla"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
Line 9: | Line 9: | ||
* Roll-call | * Roll-call | ||
* Announcements | * Announcements | ||
+ | * fixed uid/gid | ||
+ | * Zero-downtime upgrade support in Kolla - duonghq | ||
* 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? | * 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? | ||
− | * kolla-kubernetes UX for service layers | + | * kolla-kubernetes UX for service layers - portdirect� |
− | * kolla-kubernetes Documentation | + | * kolla-kubernetes Documentation - portdirect |
− | * kolla-kubernetes helm/k8s versioning and compatibility with | + | * kolla-kubernetes helm/k8s versioning and compatibility with upstream - portdirect |
− | |||
* Open Discussion | * Open Discussion | ||
</pre> | </pre> |
Revision as of 07:56, 14 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 * Zero-downtime upgrade support in Kolla - duonghq * 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? * kolla-kubernetes UX for service layers - portdirect� * kolla-kubernetes Documentation - portdirect * kolla-kubernetes helm/k8s versioning and compatibility with upstream - portdirect * 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]