Jump to: navigation, search

Difference between revisions of "Meetings/TroveMeeting"

(Trove pulse update)
(Newton release schedule)
Line 33: Line 33:
  
 
[http://releases.openstack.org/newton/schedule.html Release Schedule]
 
[http://releases.openstack.org/newton/schedule.html Release Schedule]
* Review changes that we will merge by the end of the week (add entries here before the meeting)
+
 
 +
Review changes that we would like to merge by the end of the week (add entries here before the meeting), can we? Are they ready?
 +
 
 +
* [https://review.openstack.org/#/c/366466 Regression in cmd/guest.py]
 +
* [https://review.openstack.org/#/c/364431 Implement full online backups for DB2]
 +
* [https://review.openstack.org/#/c/352786 Display more flavor information in trove flavor-list command]
 +
* [https://review.openstack.org/#/c/354134 Add availability zone to launch instance]
 +
* [https://review.openstack.org/#/c/286159 Add support for instance datastore-flavors]
 +
* [https://review.openstack.org/#/c/358874 Add support for affinity/anti-affinity]
 +
* [https://review.openstack.org/#/c/267736 Add support for Trove configuration groups]
 +
* [https://review.openstack.org/#/c/361920 Implement configuration management for DB2]
 +
* [https://review.openstack.org/#/c/331323 Quota Management]
 +
* [https://review.openstack.org/#/c/288712 Postgresql Streaming Replication]
 +
* [https://review.openstack.org/#/c/301936 Locality support for clusters]
 +
* [https://review.openstack.org/#/c/326064 Implement Instance Upgrade]
 +
* [https://review.openstack.org/#/c/329627 Trove workbook for scheduled backups]
 +
* [https://review.openstack.org/#/c/356124 Add nic to cluster grow]
  
 
==== <big>Open Discussion</big>====
 
==== <big>Open Discussion</big>====

Revision as of 12:12, 7 September 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, September 7 2016

Action items from last week's meeting

None

Trove pulse update

Pulse update

Top 5 list

  • If you have a change, or changes that you'd like to see merged for Newton, please do your part and do some reviews as well.

Newton release schedule

Release Schedule

Review changes that we would like to merge by the end of the week (add entries here before the meeting), can we? Are they ready?

Open Discussion


Meeting Agenda History
Meeting Chat Logs

Running The Meeting

  • To start the meeting, use #startmeeting trove
  • Send a courtesy ping to attendees peterstac johnma dougshelley66 pmalik vgnbkr mvandijk trevormc aliadil spilla songjian trevormc
  • Use #agenda https://wiki.openstack.org/wiki/Meetings/TroveMeeting
  • Use #topic to mark each topic change.
  • Use #link to mark links.
  • 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