Meetings/TroveMeeting
< Meetings
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, Jan 6, 2016
- [cp16net] Trove pulse update
- trove-dashboard reporting bugs/bp
- Announcements
- Looking for comments (Trove meets HBase)
- https://review.openstack.org/#/c/256079/
- I am not looking for comments on the spec in the meeting. Rather there seems to be an issue about whether Trove should even go hear HBase or whether we should just say that's Sahara's turf. A question was raised in the spec review of whether this has been discussed on the ML. I'm happy to post the question on the ML but before I did that, I wanted to poll the team to see what people felt. It is my belief that HBase is a database and offering support for HBase through Trove, where Trove provisions and manages the instances independent of Sahara, is something of value. I realize that there are others who feel differently. The code is up there for review as well (see https://review.openstack.org/#/c/262048/ and https://review.openstack.org/#/c/262815).
- Open Discussion
