Revision as of 12:27, 9 May 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, May 11, 2016

• Action items from last week's meeting

None

• Trove pulse update
  • Pulse update
  • Top 5 list

• Announcements
  • Newton release schedule updated
  • Deadline for proposing specs for Newton is R-17 (Week of June 13 to 17)
  • Deadline for specs for Newton to be merged is R-12 (Week of July 11 to 15)

• Specs that are up for review

• • [1] Using Cinder snapshot as Trove backups
  • [2] Image Upgrade
  • [3] Replication/cluster locality
  • [4] Add support for dsv-volume-type mappings
  • [5] Separate trove image build project based on libguestfs tools
  • [6] Persist last error message and display on 'show'
  • [7] Configuration groups for CouchDB
  • [8] extending trove to better utilize storage capabilities
  • [9] Add support for hbase in Trove

• Proposal for review

• Newton Projects

• [amrith] Updating the API documentation

• 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