Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Agenda for the next meeting) |
(→Agenda for the next meeting) |
||
Line 25: | Line 25: | ||
* Update to Action items (http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-18-20.01.html) | * Update to Action items (http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-18-20.01.html) | ||
* ML or die | * ML or die | ||
+ | * voting out of band | ||
* capabilities (example, mysql+redis, under same api server, one having volumes and one not) | * capabilities (example, mysql+redis, under same api server, one having volumes and one not) |
Revision as of 18:33, 23 September 2013
Weekly Trove (DBaaS) team meeting
For those interested, we have meetings in #openstack-meeting-alt Weekly, Wednesdays at 3pm CDT / 1pm PDT, or 20:00 UTC. Feel free to add items in the agenda below.
Agenda from the previous meeting
- Launchpad blueprints can only be edited by core members, sooper inconvenient (esp)
- databases/users validation or api change
- Cluster API. Provisioning part specs (dmakogon)
- Rollback on failre. ForceDelete (dmakogon)
- Anoying fails in reddwarf-jenkins due to memory exceeded exceptions (dmakogon)
- my.cnf Configurations changes (cp16net)
- Scheduled task wiki update (cp16net)
- Open Discussion
Agenda for the next meeting
- Update to Action items (http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-18-20.01.html)
- ML or die
- voting out of band
- capabilities (example, mysql+redis, under same api server, one having volumes and one not)