Difference between revisions of "Meetings/TroveMeeting"
< Meetings
Mat-lowery (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | = Weekly Trove (DBaaS) | + | = Weekly Trove (DBaaS) 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: | |
| − | + | An agenda item should have a clearly defined objective. | |
| + | |||
| + | * 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. | ||
| − | == Agenda for the | + | |
| + | When referring to previous conversations or competing viewpoints, be sure to summarize them. | ||
| + | |||
| + | Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/ | ||
| + | |||
| + | Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory | ||
| + | |||
| + | == Agenda for the Weekly Meeting Apr.16 == | ||
* Discuss the expectations of an agenda item for the weekly meeting [core/amcrn] | * Discuss the expectations of an agenda item for the weekly meeting [core/amcrn] | ||
** Goal: Explain what is expected of an agenda item to guarantee the conversation stays on topic and is headed toward meeting a goal or resolving an issue. | ** Goal: Explain what is expected of an agenda item to guarantee the conversation stays on topic and is headed toward meeting a goal or resolving an issue. | ||
Revision as of 06:58, 17 April 2014
Contents
Weekly Trove (DBaaS) 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:
An agenda item should have a clearly defined objective.
- 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.
Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory
Agenda for the Weekly Meeting Apr.16
- Discuss the expectations of an agenda item for the weekly meeting [core/amcrn]
- Goal: Explain what is expected of an agenda item to guarantee the conversation stays on topic and is headed toward meeting a goal or resolving an issue.
- Datastore and Datastore Version Concat in Trove Horizon Dashboard [michael-yu]
- Question to Answer: Should there be two columns in list-view, and two dropdowns in launch-view, for datastore and datastore-version respectively? Or should they be concatenated into one?
- See the ongoing conversation at https://review.openstack.org/#/c/75269/14/openstack_dashboard/dashboards/project/databases/tables.py and https://review.openstack.org/#/c/75269/14/openstack_dashboard/dashboards/project/databases/workflows/create_instance.py .
- Perform integration testing for the heat based instances [Shivamshukla]
- https://blueprints.launchpad.net/openstack/?searchtext=test-heat-based-instance-workflow
- What could be the way to test instance workflow through heat.
- Neutron Support, SecGroup Management, and Networking [annashen, denis_makogon]
- Refactoring backup/restore strategies (re-visiting from previous meeting) [denis_makogon]
Weekly Trove (DBaaS) blueprint meeting
For those interested, we have blueprint meetings in #openstack-trove weekly, Mondays at 18:00 UTC. Feel free to add items in the agenda below.
Agenda for Apr. 21 (blueprint meeting)
- Unify common code in guest agent configurations [amrith and snowdust]
- Adding datastore and version to the backup API [robertmyers]
- Move the Trove Guest Agent to its own module [robertmyers]
- Database log files manipulations [denis_makogon]
- Resource management driver [denis_makogon]
