Revision as of 13:05, 2 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 6, 2016

• Action items from last week's meeting
  • [cp16net] Confirm sending email to Horizon team re: RC2 [DONE]
  • [amrith] Fill out the schedule for summit sessions [In Progress]

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

• Announcements
  • We released Trove RC2 last week to address issues with Routes 3.2

• 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
  • [sonali/vkmc] Configuration Groups for Couchdb
  • [johnma] Enable CouchDB replication in Trove
  • [amrith] Add support for hbase in Trove
  • [peterstac] Locality for cluster/replication sets
  • [petmal] Couchbase clusters
  • [vgnbkr] Guest instance upgrade - BP coming
  • [petmal] PostgreSQL incremental backup/restore
  • [petmal] PostgreSQL replication
  • [mvandijk] Associate volume-type with datastore
  • [vgnbkr] Multi-Region Support
  • [haypo] Python 3 support
    • Blueprint
    • Port run_tests.py to Python 3 Merged
    • Add a minimal py34 test environment Merged
    • encrypt_data(): don't encode IV to base64 Merged
    • Add non-voting gate-trove-python34-db check Merged
    • Port test_template unit test to Python 3
    • Port more common unit tests to Python 3
    • Port crypto_utils to Python 3

• Summit planning
  • Propose sessions for the summit
  • Conference room allocations announced (Trove: 3fb, 6wr, cm:half)
  • 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
  • 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