Difference between revisions of "Meetings/TroveMeeting"
< Meetings
| Line 1: | Line 1: | ||
| − | = Weekly Trove | + | = Weekly Trove Team Meeting = |
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt | We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt | ||
| Line 19: | Line 19: | ||
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory | Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory | ||
| − | == Agenda for | + | === Agenda for Weekly Trove Team Meeting - April 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. | ||
| + | ** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 07:13, 17 April 2014 (UTC): Result: majority vote agrees that each agenda item should have an objective and be goal-oriented. as a result, guidelines for agenda items have been added to the top of this wiki and the core team has agreed to shepherd folks for the next few weeks on how to fine tune their agenda items. | ||
* Datastore and Datastore Version Concat in Trove Horizon Dashboard [michael-yu] | * 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? | ** 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 . | ** 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 . | ||
| + | ** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 07:13, 17 April 2014 (UTC): Result: majority vote agrees that datastore-type and datastore-version should be consolidated into one dropdown for the launch-instance workflow and one column for list-view. long-term, many believe this to be a hint/indication that datastore-type and datastore-version should be combined into a single field for the v2 api, but this is yet to be seen. next steps include michael updating his horizon patch-set (https://review.openstack.org/#/c/75269/) to be single dropdown/column and updating trove-integration to default to a naming scheme that plays well with this model (https://review.openstack.org/#/c/88119/) | ||
* Perform integration testing for the heat based instances [Shivamshukla] | * Perform integration testing for the heat based instances [Shivamshukla] | ||
** https://blueprints.launchpad.net/openstack/?searchtext=test-heat-based-instance-workflow | ** https://blueprints.launchpad.net/openstack/?searchtext=test-heat-based-instance-workflow | ||
| Line 35: | Line 37: | ||
** https://launchpad.net/bugs/1287684 | ** https://launchpad.net/bugs/1287684 | ||
| − | = Weekly Trove | + | |
| + | = Weekly Trove 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. | 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 | + | === Agenda for Weekly Trove Blueprint Meeting - April 21 === |
* Unify common code in guest agent configurations [amrith and snowdust] | * Unify common code in guest agent configurations [amrith and snowdust] | ||
** https://blueprints.launchpad.net/trove/+spec/trove-unify-common-code-for-config-of-guest-agent-variants | ** https://blueprints.launchpad.net/trove/+spec/trove-unify-common-code-for-config-of-guest-agent-variants | ||
Revision as of 07:13, 17 April 2014
Contents
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:
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 Weekly Trove Team Meeting - April 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.
- amcrn (talk) 07:13, 17 April 2014 (UTC): Result: majority vote agrees that each agenda item should have an objective and be goal-oriented. as a result, guidelines for agenda items have been added to the top of this wiki and the core team has agreed to shepherd folks for the next few weeks on how to fine tune their agenda items.
- 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 .
- amcrn (talk) 07:13, 17 April 2014 (UTC): Result: majority vote agrees that datastore-type and datastore-version should be consolidated into one dropdown for the launch-instance workflow and one column for list-view. long-term, many believe this to be a hint/indication that datastore-type and datastore-version should be combined into a single field for the v2 api, but this is yet to be seen. next steps include michael updating his horizon patch-set (https://review.openstack.org/#/c/75269/) to be single dropdown/column and updating trove-integration to default to a naming scheme that plays well with this model (https://review.openstack.org/#/c/88119/)
- 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 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 Weekly Trove Blueprint Meeting - April 21
- 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]
