|
|
(244 intermediate revisions by 15 users not shown) |
Line 1: |
Line 1: |
− | = Weekly Trove Team Meeting =
| |
| | | |
− | We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt
| + | == Weekly Trove Meeting == |
| | | |
− | Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:
| + | We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt. |
| | | |
− | ==== Guidelines for Writing Clear Agenda Items ====
| + | Previous meeting logs can be found here: http://eavesdrop.openstack.org/meetings/trove/ |
− | 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.
| |
| | | |
| + | === Meeting agendas === |
| | | |
− | When referring to previous conversations or competing viewpoints, be sure to summarize them.
| + | Meeting agendas is now maintained at: https://etherpad.openstack.org/p/trove-stein-meeting-agendas. |
| | | |
− | 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.
| + | Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it. |
| | | |
− | == Trove Meeting, Sept 30, 2015 ==
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
− | * Trove pulse update:
| |
− | ** https://etherpad.openstack.org/p/trove-pulse-update
| |
− | * Action items
| |
− | ** cp16net look into troveclient tempest gate failures
| |
− | ** peterstac put together a graph for week over week
| |
− | * Bugs that could be back ported for Liberty
| |
− | ** [trove] Fix promote for Redis datastore
| |
− | *** https://review.openstack.org/#/c/226075/
| |
− | ** [trove] Fix publish_exists_event authentication exception
| |
− | *** https://review.openstack.org/#/c/228696/
| |
− | ** [troveclient] Accepting network and availability zone for instances in cluster
| |
− | *** https://review.openstack.org/#/c/184349/
| |
− | * Mitaka Summit Design Sessions
| |
− | ** https://etherpad.openstack.org/p/mitaka-trove-summit
| |
− | * Assert follows standard deprication
| |
− | ** http://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html
| |
− | * Open Discussion
| |
− | | |
− | == Trove Meeting, Oct 7, 2015 ==
| |
− | * mlowery Trove community and containers
| |
− | ** Is there any plan to adopt containers (e.g. Docker) in any way in Trove within the community?
| |
− | *** 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.
| |
− | ** Is there any plan to adopt container orchestration (e.g. Kubernetes) in any way in Trove within the community?
| |
− | *** 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?
| |
− | <br/>
| |
− | [https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]
| |
− | <br/>
| |
− | [http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]
| |
We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt.
Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it.