Revision as of 14:23, 20 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]
  • Top 5 list [2]

• 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
    • Code awaiting reviews [3], and [4]
  • [petmal] Couchbase clusters
    • Waiting for spec and code
  • [vgnbkr] Guest instance upgrade
    • [5]
  • [petmal] PostgreSQL incremental backup/restore
    • Is this change set still the right one? [6] It needs some TLC.
  • [petmal] PostgreSQL replication
    • Is this change set still the right one? [7] 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

• Work on branches other than master
  • Bug fixes for Mitaka and Liberty

• 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