Revision as of 13:15, 19 April 2016

Weekly Trove Team Meeting

We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt

Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:

Guidelines for Writing Clear Agenda Items

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.

When referring to previous conversations or competing viewpoints, be sure to summarize them.

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.

Trove Meeting, April 20, 2016

Action items from last week's meeting

None

Trove pulse update
- http://bit.ly/1VQyg00 [1]

Announcements
- We won't have the IRC meeting next week as many of us will be at summit

Proposal for review

Ongoing review of projects. Any updates from project owners (list of Newton projects is below)
- [pmackinn] Separate trove image build project based on libguestfs tools
- [tellesnóbrega/vkmc] Implementing CEPH as a backend for backups
  - Has multiple -1's and appears to be in need of responses/updates
- [sonali/vkmc] Configuration Groups for Couchdb
  - spec fails the check and needs to be updated [vkmc?]
- [peterstac] Locality for cluster/replication sets
  - [2]
  - [3]
- [petmal] Couchbase clusters
  - Waiting for spec and code
- [vgnbkr] Guest instance upgrade
  - [4]
- [petmal] PostgreSQL incremental backup/restore
  - Is this change set still the right one? [5] It needs some TLC.
- [petmal] PostgreSQL replication
  - Is this change set still the right one? [6] It needs some TLC.
- [mvandijk] Associate volume-type with datastore
  - Waiting for spec and code
- [vgnbkr] Multi-Region Support
  - Spec is currently WIP
- [amrith] extending trove to better utilize storage capabilities
  - Looking for reviews
- [haypo] Python 3 support
  - Moving along well, change sets need reviews

Summit planning
- Please update your etherpads

Planning for mid-cycle
- Tentative date week of R-7, New York City

Open Discussion

Meeting Agenda History
Meeting Chat Logs

Running The Meeting

To start the meeting, use #startmeeting trove
Then, publish the link to the agenda for the meeting (this page).
Use #topic to mark each topic change.
You can find the near-full list of Meetbot commands here. Instructions for voting (which can be useful for a quick show of hands) live here.
During the meeting, don't forget to liberally use #info, #agreed, #action or #link 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 #endmeeting

@@ Line 17: / Line 17: @@
 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.
-== Trove Meeting, April 13, 2016 ==
+== Trove Meeting, April 20, 2016 ==
 * Action items from last week's meeting
@@ Line 26: / Line 26: @@
 * 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
+** We won't have the IRC meeting next week as many of us will be at summit
 * 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]
+*** Has multiple -1's and appears to be in need of responses/updates
 ** [sonali/vkmc] [https://review.openstack.org/#/c/263980/ Configuration Groups for Couchdb]
-** [johnma] [https://review.openstack.org/#/c/255437/ Enable CouchDB replication in Trove]
+*** spec fails the check and needs to be updated [vkmc?]
 ** [peterstac] [https://blueprints.launchpad.net/trove/+spec/replication-cluster-locality Locality for cluster/replication sets]
+*** [https://review.openstack.org/#/c/300669/]
+*** [https://review.openstack.org/#/c/301936/]
 ** [petmal] [https://blueprints.launchpad.net/trove/+spec/couchbase-cluster-support Couchbase clusters]
-** [vgnbkr] Guest instance upgrade - BP coming
+*** Waiting for spec and code
+** [vgnbkr] Guest instance upgrade
+*** [https://review.openstack.org/#/c/302416/]
 ** [petmal] [https://blueprints.launchpad.net/trove/+spec/postgresql-incremental-backup PostgreSQL incremental backup/restore]
+*** Is this change set still the right one? [https://review.openstack.org/#/c/259167/] It needs some TLC.
 ** [petmal] [https://blueprints.launchpad.net/trove/+spec/replication-affinity PostgreSQL replication]
+*** Is this change set still the right one? [https://review.openstack.org/#/c/288712/] It needs some TLC.
 ** [mvandijk] [https://blueprints.launchpad.net/trove/+spec/associate-volume-type-datastore Associate volume-type with datastore]
+*** Waiting for spec and code
 ** [vgnbkr] [https://review.openstack.org/#/c/294213/ Multi-Region Support]
+*** Spec is currently WIP
 ** [amrith] [https://review.openstack.org/302952 extending trove to better utilize storage capabilities]
+*** Looking for reviews
 ** [haypo] Python 3 support
-*** [https://blueprints.launchpad.net/trove/+spec/trove-python3 Blueprint]
+*** Moving along well, change sets need reviews
-*** [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
+** Please update your etherpads
 * Planning for mid-cycle

Difference between revisions of "Meetings/TroveMeeting"

Revision as of 13:15, 19 April 2016

Contents

Weekly Trove Team Meeting

Guidelines for Writing Clear Agenda Items

Trove Meeting, April 20, 2016

Running The Meeting