Jump to: navigation, search

Difference between revisions of "Meetings/TroveMeeting"

(Trove Meeting, May 6, 2015)
m (Trove Meeting, May 6, 2015)
Line 21: Line 21:
* [SlickNik] Trove pulse update:
* [SlickNik] Trove pulse update:
** https://etherpad.openstack.org/p/trove-pulse-update
** https://etherpad.openstack.org/p/trove-pulse-update
* [SlickNik] Summit sessions overview
* [schang]
** We need to discuss this patchset, vote for an implementation option, and move forward: https://review.openstack.org/#/c/164640/9
** '''Option 1:''' Define a default usage_timeout setting at the global level, the setting is optional at the datastore level, used only for the purpose of overriding the global default value.
** '''Option 2:''' Define a mandatory usage_timeout option for each datastore.
** These two options are mutually exclusive, meaning if we've already defined the option at the global level, and if the datastore is OK with the default value, it shouldn't be mandatory to re-specify the same default value at the datastore level.
** The current patchset is implementing BOTH option 1 and 2.

Revision as of 07:23, 13 May 2015

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 6, 2015

Meeting Agenda History
Meeting Chat Logs