|
|
| (165 intermediate revisions by 10 users not shown) |
| Line 1: |
Line 1: |
| − | = Weekly Trove Team Meeting =
| |
| | | | |
| − | We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt
| + | == Weekly Trove Meeting == |
| | | | |
| − | Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:
| + | We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt. |
| | | | |
| − | ==== Guidelines for Writing Clear Agenda Items ====
| + | Previous meeting logs can be found here: http://eavesdrop.openstack.org/meetings/trove/ |
| − | An agenda item should have a clearly defined objective.
| |
| − |
| |
| − | * [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.
| |
| − | * Bad: Discuss blueprint ‘xyz’
| |
| − | * Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.
| |
| | | | |
| | + | === Meeting agendas === |
| | | | |
| − | When referring to previous conversations or competing viewpoints, be sure to summarize them.
| + | Meeting agendas is now maintained at: https://etherpad.openstack.org/p/trove-stein-meeting-agendas. |
| | | | |
| − | Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.
| + | Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it. |
| | | | |
| − | == Trove Meeting, March 30, 2016 ==
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
| − | | |
| − | * Action items from last week's meeting
| |
| − | ** [all] If you have a patch set that you intend to resume work on, please put an update in it to that effect so we don't go abandon it under you ...
| |
| − | ** [all] if any of the abandoned patches looks like something you would like to pick up feel free
| |
| − | ** cp16net reply to trove-dashboard ML question for RC2
| |
| − | ** [all] please review changes [ https://review.openstack.org/#/c/262289/], [ https://review.openstack.org/#/c/262287/], and link [ http://openstack.markmail.org/thread/jepcqu335mrb5c7l] in agenda and update the reviews
| |
| − | ** flaper87 to WF+1 the patches in question [ https://review.openstack.org/#/c/262289/] and [ https://review.openstack.org/#/c/262287/] [DONE]
| |
| − | * Trove pulse update
| |
| − | ** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
| |
| − | * Announcements
| |
| − | ** [http://releases.openstack.org/newton/schedule.html Newton release schedule has been published ]
| |
| − | *** Some things I've learned from the Mitaka cycle
| |
| − | **** The schedule is known so far in advance that it is prudent to plan for it
| |
| − | **** The dates for things that are listed as "Final" are in fact final and not subject to FFE's
| |
| − | ***** If we want to push any code into OSLO, R-6 is a hard deadline.
| |
| − | ***** R-5, is the '''hard''' freeze for the python-troveclient. We '''must''' get all new functionality we need in the client into a version by that date or it won't be available for the release.
| |
| − | ***** R-5 is the '''target date''' by which all new functionality should be in, you need to request FFE's for anything that does not merge by that date
| |
| − | ***** R-3 is the RC1 '''target date''', not a hard date. In the Mitaka cycle, I mistakenly believed that R-3 is a hard RC1 date. My mistake.
| |
| − | ** [https://review.openstack.org/#/c/164035/ Getting rid of eventlet and replacing it with something else]
| |
| − | | |
| − | * Ongoing review of projects. At the mid-cycle in Raleigh, one of the action items that we took away was that we should start tracking and monitoring all projects under way to completion through the release cycle. I'm going to start this up with the projects that we know are under way, and begin to highlight them so that people can focus time on reviewing them.
| |
| − | ** [pmackinn] [https://review.openstack.org/#/c/295274/ Separate trove image build project based on libguestfs tools]
| |
| − | ** [tellesnóbrega/vkmc] [https://review.openstack.org/#/c/256057/ Implementing CEPH as a backend for backups]
| |
| − | ** [sonali/vkmc] [https://review.openstack.org/#/c/263980/ Configuration Groups for Couchdb]
| |
| − | ** [johnma] [https://review.openstack.org/#/c/255437/ Enable CouchDB replication in Trove]
| |
| − | ** [amrith] [https://review.openstack.org/#/c/256079/ Add support for hbase in Trove]
| |
| − | ** [peterstac] [https://blueprints.launchpad.net/trove/+spec/replication-cluster-locality Locality for cluster/replication sets]
| |
| − | ** [petmal] [https://blueprints.launchpad.net/trove/+spec/couchbase-cluster-support Couchbase clusters]
| |
| − | ** [vgnbkr] Guest instance upgrade - BP coming
| |
| − | ** [petmal] [https://blueprints.launchpad.net/trove/+spec/postgresql-incremental-backup PostgreSQL incremental backup/restore]
| |
| − | ** [petmal] [https://blueprints.launchpad.net/trove/+spec/replication-affinity PostgreSQL replication]
| |
| − | ** [mvandijk] [https://blueprints.launchpad.net/trove/+spec/associate-volume-type-datastore Associate volume-type with datastore]
| |
| − | ** [vgnbkr] [https://review.openstack.org/#/c/294213/ Multi-Region Support]
| |
| − | * Summit planning
| |
| − | ** [https://etherpad.openstack.org/p/trove-newton-proposed-sessions Propose sessions for the summit]
| |
| − | ** [http://markmail.org/message/avbqqzwhog36tme2 Conference room allocations announced] (Trove: 3fb, 6wr, cm:half)
| |
| − | ** [http://openstack.markmail.org/thread/yeg57r5yyddveoka Austin Design Summit track layout] The Trove sessions are as follows, please mark your calendars.
| |
| − | *** (WR1) Wednesday 0950 to 1030
| |
| − | *** (WR2) Wednesday 1350 to 1430
| |
| − | *** (WR3) Wednesday 1530 to 1610
| |
| − | *** (WR4) Thursday 1150 to 1230
| |
| − | *** (WR5) Thursday 1330 to 1410
| |
| − | *** (WR6) Thursday 1420 to 1500
| |
| − | *** (FB1) Wednesday 1720 to 1800
| |
| − | *** (FB2) Thursday 0950 to 1030
| |
| − | *** (FB3) Thursday 1100 to 1140
| |
| − | *** (CM) Friday 0900 to 1230.
| |
| − | * Planning for mid-cycle
| |
| − | ** It seems like this is a long way off but it really isn't.
| |
| − | ** I'd like to propose R-7, in the New York City area.
| |
| − | * Recent instability in the gate/check
| |
| − | * Open Discussion
| |
| − | | |
| − | <br/>
| |
| − | [https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory Meeting Agenda History]
| |
| − | <br/>
| |
| − | [http://eavesdrop.openstack.org/meetings/trove/2016 Meeting Chat Logs]
| |
| − | | |
| − | ==Running The Meeting==
| |
| − | * To start the meeting, use <code><nowiki>#startmeeting trove</nowiki></code>
| |
| − | * Then, publish the link to the agenda for the meeting (this page).
| |
| − | * Use <code><nowiki>#topic</nowiki></code> to mark each topic change.
| |
| − | * You can find the near-full list of Meetbot commands [https://wiki.debian.org/MeetBot here]. Instructions for voting (which can be useful for a quick show of hands) live [http://docs.openstack.org/infra/system-config/irc.html#voting here].
| |
| − | * During the meeting, don't forget to liberally use <code><nowiki>#info</nowiki></code>, <code><nowiki>#agreed</nowiki></code>, <code><nowiki>#action</nowiki></code> or <code><nowiki>#link</nowiki></code> to make sure the critical discussion points will be highlighted in the meeting log. Attendees can use these Meetbot keywords as well.
| |
| − | * To end the meeting, use <code><nowiki>#endmeeting</nowiki></code>
| |
We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt.
Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it.
