Meetings/TroveMeeting

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, Aug 5, 2015

• Trove pulse update:
  • https://etherpad.openstack.org/p/trove-pulse-update

Meeting Agenda History
Meeting Chat Logs

• [sushilkm] Datastore registration spec open questions
  • We talked a little about this in last week but want to bring this around to close on it.
  • Question which need to be answered to move on this spec.
    • Should the api be simple CRUD operations on each object? (i.e. CRUD on datastores and versions separate) or make the API simplified where we really only care about the version when we update the image on an existing version or create a new version?
  • Thoughts from SlickNik and cp16net were there on last weeks agenda too, https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Meeting.2C_July_29.2C_2015,