OpenStack - User contributions [en]

Meetings/TroveMeeting

2015-01-21T08:57:25Z

Denis M.: /* Agenda for Jan 21st */

Denis M.: /* API Matrix */

This page will detail which datastores have which functions, either core or extension form.

== API Matrix ==

{| border="1" cellpadding="2" cellspacing="0"
| '''Feature'''
| '''MySQL'''
| '''Redis'''
| '''Cassandra'''
| '''MongoDB'''
| '''PostgreSQL'''
|-
| Launch
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Reboot
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Terminate
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Resize
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Backup
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Restore
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| Replication
| ✔
| -
| -
| -
| ✔
|-
| Clustering
| -
| -
| ✔
| ✔
| -
|}

== Extensions Matrix ==
This covers items that are not considered part of the core api (yet). As more datastores start to use extensions, we can move them to core.

{| border="1" cellpadding="2" cellspacing="0"
| '''Feature'''
| '''MySQL'''
| '''Redis'''
| '''Cassandra'''
| '''MongoDB'''
| '''PostgreSQL'''
|-
| Users
| ✔
| style="color: red" | ✗
| style="color: red" | ✗
| style="color: red" | ✗
| ✔
|-
| Schemas
| ✔
| style="color: red" | ✗
| style="color: red" | ✗
| style="color: red" | ✗
| ✔*
|-
| Root
| ✔
| style="color: red" | ✗
| style="color: red" | ✗
| style="color: red" | ✗
| ✔**
|-
|}
<nowiki>* PostgreSQL supports has separate constructs for schemas and databases.</nowiki> 

<nowiki>** PostgreSQL supports superusers but does not have a "root" user.</nowiki>

TroveBlueprint

2014-09-17T09:41:09Z

Denis M.:

== Description ==
Describe the purpose of the enhancement

== Justification/Benefits ==
* What is the driving force behind this change?
* Does it allow for great flexibility? Stability? Security?

== Impacts ==

=== Configuration ===
* Does this impact any configuration files? If so, which ones?

=== Database ===
* Does this impact any existing tables? If so, which ones?
* Are the changes forward and backward compatible?
* Be sure to include the expected migration process

=== Public API ===
* Does this change any API that an end-user has access to?
* Are there any exceptions in terms of consistency with other APIs?

==== CLI interface====
* How the command will look like?
* Does it extends the already existed command interfaces ?

==== ReST Part ====
* Which HTTP methods added ?
* Which routes were added/modified/extended?
* How does the Request body look like?
* How does the Response object look like?

=== Internal API ===
* Does this change any internal messages between API and Task Manager or Task Manager to Guest
==== RPC API description====
* Method name.
* Method parameters.
* Message type (cast/call).

=== Guest Agent ===
* Does this change behavior on the Guest Agent? If so, is it backwards compatible with API and Task Manager?

= Datastore Configuration feature spec template =
*https://wiki.openstack.org/wiki/Trove/Configurations

= Datastore Clustering feature spec template =
*https://wiki.openstack.org/wiki/Trove/Clusters-MongoDB

2014-09-04T15:48:03Z

Denis M.: /* Configuration */

Trove/cassandra-clustering

2014-09-04T15:47:49Z

Denis M.: /* Impacts */

Trove/cassandra-clustering

2014-09-04T15:46:58Z

Denis M.: /* Justification/Benefits */

2014-08-25T16:27:07Z

Denis M.: /* Aug 25 Meeting */

= 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 

== Aug 18 Meeting CANCELED ==
* Most trove folks traveling for Trove Day + Midcycle event in Cambridge, MA

== Aug 25 Meeting ==
* [amrith]
** What do we do about SuSE? There are bugs coming in at a steady clip fixing little things that don't work in SuSE but in some cases, no test cases are being proposed nor is there a clear plan to get SuSE on the supported platform list. How do we want to proceed? I raise this question because I don't want to use the review process as the place to discuss on a patch-by-patch basis whether a certain code change should be considered or not; rather raise it and address it as a larger issue of how we get to a supported SuSE platform including testing on an ongoing basis, etc.,

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/

Meetings/TroveBPMeeting

2014-08-19T14:39:23Z

Denis M.: /* Aug 25 Meeting */