|
|
| (158 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, April 13, 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
| |
| − | None
| |
| − | | |
| − | * Trove pulse update
| |
| − | ** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
| |
| − | | |
| − | * Announcements
| |
| − | ** python-troveclient v2.2.0 has been released and is now on pypi. For newton, g-r and u-c have been set to v2.2.0
| |
| − | | |
| − | * Proposal for review
| |
| − | ** [amrith] Changes from the proposal bot (requirements, translations) can be approved on master by a single +2.
| |
| − | ** [amrith] I propose that we approve [https://review.openstack.org/#/c/304030/ make python34 job gating]
| |
| − | | |
| − | * Clearing up the review backlog
| |
| − | ** [amrith] the review backlog is building again, we need to pick up the pace on reviews
| |
| − | | |
| − | * Ongoing review of projects. Any updates from project owners (list of Newton projects is below)
| |
| − | ** [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]
| |
| − | ** [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]
| |
| − | ** [amrith] [https://review.openstack.org/302952 extending trove to better utilize storage capabilities]
| |
| − | ** [haypo] Python 3 support
| |
| − | *** [https://blueprints.launchpad.net/trove/+spec/trove-python3 Blueprint]
| |
| − | *** [https://review.openstack.org/225912 Port run_tests.py to Python 3] Merged
| |
| − | *** [https://review.openstack.org/279098 Add a minimal py34 test environment] Merged
| |
| − | *** [https://review.openstack.org/300491 encrypt_data(): don't encode IV to base64] Merged
| |
| − | *** [https://review.openstack.org/279108 Add non-voting gate-trove-python34-db check] Merged
| |
| − | *** [https://review.openstack.org/279119 Port test_template unit test to Python 3]
| |
| − | *** [https://review.openstack.org/298952 Port more common unit tests to Python 3]
| |
| − | *** [https://review.openstack.org/297888 Port crypto_utils to Python 3]
| |
| − | | |
| − | | |
| − | * Summit planning
| |
| − | | |
| − | * Planning for mid-cycle
| |
| − | ** Tentative date week of R-7, New York City
| |
| − | | |
| − | * 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.
