Jump to: navigation, search

Difference between revisions of "Meetings/TroveMeeting"

(Trove Meeting, Oct 7, 2015)
(Trove Meeting, Oct 7, 2015)
Line 17: Line 17:
 
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.
 
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, Oct 7, 2015 ==
+
== Trove Meeting, Oct 14, 2015 ==
* Trove pulse update:
+
* Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
+
** [cp16net working on graphs] link to come
* Trove community and containers [mlowery]
+
* [cp16net] Mitaka Summit Sessions
** Is there any plan to adopt containers (e.g. Docker) in any way in Trove within the community?
+
** https://etherpad.openstack.org/p/mitaka-trove-summit
*** Example: Put the guest agent in a container. Upgrade it by replacing the container. (You no longer have to care about the current state of the guest (the existing bits)--just replace it.) The same approach could be taken with the datastore itself: put it in a container.
+
* [cp16net] Mitaka Mid-Cycle proposed dates (Feb 9-11 2016)
** Is there any plan to adopt container orchestration (e.g. Kubernetes) in any way in Trove within the community?
+
** [make wiki page info on mid-cycle]
*** Example: Kubernetes handles scheduling, updating, and scaling (including auto-healing). Some of these are Nova/Heat-like. Some of these (like auto-healing) don't exist. Is auto-healing in Trove's charter? Could Kubernetes or Magnum be a pluggable "orchestration driver" within Trove?
 
 
 
* Refactor of Manager class [peterstac]
 
** We have previously discussed the merits of refactoring the Manager class structure (and there are many good reasons why we should), however the consensus has been that it would need to be done at the beginning of a cycle.  We're now at the beginning of a (Mitaka) cycle :).  As such, I'd like to draw some attention to the spec and make sure that the proposed solution has no glaring issues.
 
*** Blueprint: https://blueprints.launchpad.net/trove/+spec/datastore-manager-refactor
 
*** Spec: https://review.openstack.org/#/c/231572
 
** The refactor also addresses the issue of the instance state changing erroneously.  I have tested the proposed solution internally and it does fix the issue.
 
*** See https://bugs.launchpad.net/trove/+bug/1482795
 
*** See https://bugs.launchpad.net/trove/+bug/1487233
 
 
 
* Is it time to merge https://review.openstack.org/#/c/220288/1 [amrith]
 
** This change was made during the end of the last cycle to kick up the timeout for some jobs that were failing
 
** Is it time to merge this change (revert the earlier one) and work on the timeout issue properly?
 
  
 
<br/>
 
<br/>

Revision as of 17:31, 13 October 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, Oct 14, 2015


Meeting Agenda History
Meeting Chat Logs