Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Agenda for the next meeting) |
|||
| Line 22: | Line 22: | ||
** Need a type of configuration that can not be modified by the user or (our default template) | ** Need a type of configuration that can not be modified by the user or (our default template) | ||
** This could get get complicated for each flavor type if the configuration is not able to scale with the flavor size. | ** This could get get complicated for each flavor type if the configuration is not able to scale with the flavor size. | ||
| − | |||
* https://review.openstack.org/#/c/41055/ (yogesh) | * https://review.openstack.org/#/c/41055/ (yogesh) | ||
* Trove-Conductor updates (datsun180b) | * Trove-Conductor updates (datsun180b) | ||
Revision as of 20:27, 2 October 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
- ML or die
- voting out of band
- capabilities (example, mysql+redis, under same api server, one having volumes and one not)
- decision on servicetype/flavor in trove (yet again :-)), https://gist.github.com/mehrayogesh/1dfac0b4ffaf97fb885b (yogesh)
- Configuration API update https://gist.github.com/cp16net/6704590
Agenda for the next meeting
- Update to Action items (http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-18-20.01.html)
- Discussion on rolling back resources
- Cloud-init service extensions for easy deployment in Trove (dmakogon)
- Configuration + service type and versions
- Need a type of configuration that can not be modified by the user or (our default template)
- This could get get complicated for each flavor type if the configuration is not able to scale with the flavor size.
- https://review.openstack.org/#/c/41055/ (yogesh)
- Trove-Conductor updates (datsun180b)
- Trove-Heat Integration (yogesh)
