Difference between revisions of "Meetings/TroveBPMeeting"
< Meetings
Line 20: | Line 20: | ||
* Add created/updated timestamps and instance count to configuration groups list and details calls [tvoran and iccha] | * Add created/updated timestamps and instance count to configuration groups list and details calls [tvoran and iccha] | ||
** https://blueprints.launchpad.net/trove/+spec/minor-config-edits | ** https://blueprints.launchpad.net/trove/+spec/minor-config-edits | ||
+ | * Pluggable conductor manager [boden] | ||
+ | ** https://blueprints.launchpad.net/trove/+spec/pluggable-conductor-manager | ||
+ | * Configurable DB plugins [boden] | ||
+ | ** https://blueprints.launchpad.net/trove/+spec/configurable-db-plugins | ||
+ | * Multiple API extension paths [boden] | ||
+ | ** https://blueprints.launchpad.net/trove/+spec/extensions-update | ||
<br /> | <br /> | ||
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Blueprint_Meeting_Agenda_History<br/> | Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Blueprint_Meeting_Agenda_History<br/> | ||
Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/ | Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/ |
Revision as of 17:24, 30 May 2014
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 if you want to bring a blueprint up for approval.
Please follow the BP template at https://wiki.openstack.org/wiki/TroveBlueprint
May 26 Meeting Cancelled (Memorial Day)
Agenda for Jun 2
- Trove should use Keystone Trusts for Authentication instead of hard coding the credentials in configuration files.
- Please refer to this blueprint https://blueprints.launchpad.net/trove/+spec/trove-keystone-trusts
- Changes are similar to Keystone trusts blueprint in Tuskar https://blueprints.launchpad.net/tuskar/+spec/tuskar-keystone-trusts
- Using keystone trusts will eliminate the risk of keeping login credentials in a configuration file.
- Can be seen as Security Enchantment by better practice.
- Flavor per datastore association [iccha]
- Conductor phase 2 [denis_makogon]
- Upgrade resource types for default heat templates for each datastore [denis_makogon and pschelo/pa-sha]
- Add created/updated timestamps and instance count to configuration groups list and details calls [tvoran and iccha]
- Pluggable conductor manager [boden]
- Configurable DB plugins [boden]
- Multiple API extension paths [boden]
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Blueprint_Meeting_Agenda_History
Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/