Jump to: navigation, search

Difference between revisions of "Meetings/TroveMeeting"

m (Trove Meeting, June 22 2016)
m (Trove Meeting, June 22 2016)
Line 46: Line 46:
 
** <strike>https://review.openstack.org/#/c/331136/ - Use correct message for missing default datastore</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/331136/ - Use correct message for missing default datastore</strike> (Approved)
 
** https://review.openstack.org/#/c/313791/ - Persist error messages and display on 'show'
 
** https://review.openstack.org/#/c/313791/ - Persist error messages and display on 'show'
** https://review.openstack.org/#/c/300669/ - Locality support for replication
+
** <strike>https://review.openstack.org/#/c/300669/ - Locality support for replication</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/331284/ - Have Trove plugin install dashboard</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/331284/ - Have Trove plugin install dashboard</strike> (Approved)
** https://review.openstack.org/#/c/331283/ - Have Trove plugin install dashboard
+
** <strike>https://review.openstack.org/#/c/331283/ - Have Trove plugin install dashboard</strike> (Approved)
** https://review.openstack.org/#/c/300659/ - Locality support for replication
+
** <strike>https://review.openstack.org/#/c/300659/ - Locality support for replication</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/330230/ - Mock detector run only once for each testcase</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/330230/ - Mock detector run only once for each testcase</strike> (Approved)
** https://review.openstack.org/#/c/301342/ - Locality support for clusters
+
** <strike>https://review.openstack.org/#/c/301342/ - Locality support for clusters</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/329254/ - fix wrong id for render default config param 'server_id'</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/329254/ - fix wrong id for render default config param 'server_id'</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/326131/ - Delete with fail nova instance tries to stop DB</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/326131/ - Delete with fail nova instance tries to stop DB</strike> (Approved)
Line 60: Line 60:
 
** <strike>https://review.openstack.org/#/c/323060/ - Break apart instance create/actions scenario tests</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/323060/ - Break apart instance create/actions scenario tests</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/303935/ - Move the rabbit/rpc options to its own section</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/303935/ - Move the rabbit/rpc options to its own section</strike> (Approved)
** https://review.openstack.org/#/c/322290/ - Break apart replication scenario tests
+
** <strike>https://review.openstack.org/#/c/322290/ - Break apart replication scenario tests</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/326676/ - Support running Mistral under Redstack</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/326676/ - Support running Mistral under Redstack</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/316566/ - Add another 'fault' flavor</strike> (Approved)
 
** <strike>https://review.openstack.org/#/c/316566/ - Add another 'fault' flavor</strike> (Approved)

Revision as of 20:28, 24 June 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, June 22 2016

  • Action items from last week's meeting
  • Announcements
  • Specs that are up for review
  • Proposal for review
  • Newton Project Updates
  • 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