[openstack-dev] [Trove] how to list available configuration parameters for datastores

Kaleb Pomeroy kaleb.pomeroy at rackspace.com
Wed Jan 22 18:19:08 UTC 2014

My thoughts so far:

/datastores/<datastore>/configuration/parameters (Option Three)
+ configuration set without an associated datastore is meaningless
+ a configuration set must be associated to exactly one datastore
+ each datastore must have 0-1 configuration set
+ All above relationships are immediately apparent
- Listing all configuration sets becomes more difficult (which I don't think that is a valid concern)

/configurations/<config_id>/parameters (Option Five)
+ Smaller, canonical route to a configuration set
- datastore/config relationshiop is much more ambiguous

I'm planning on working a blueprint for this feature soon, so I'd like any feedback anyone has.

- kpom

From: Craig Vyvial [cp16net at gmail.com]
Sent: Wednesday, January 22, 2014 10:10 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Trove] how to list available configuration parameters for datastores

Hey everyone I have run into an issue with the configuration parameter URI. I'd like some input on what the URI might look like for getting the list configuration parameters for a specific datastore.

Problem: Configuration parameters need to be selected per datastore.

Currently: Its setup to use the default(mysql) datastore and this wont work for other datastores like redis/cassandra/etc.

/configurations/parameters - parameter list for mysql
/configurations/parameters/<parameter_name> - details of parameter

We need to be able to request the parameter list per datastore. Here are some suggestions that outlines how each method may work.


/configurations/parameters?datastore=mysql - list parameter for mysql
/configurations/parameters?datastore=redis - list parameter for redis

- we do not use query parameters for anything other than pagination (limit and marker)
- this requires some finagling with the context to add the datastore.


/configurations/parameters - list of datastores that have configuration parameters
/configurations/parameters/<datastore> - list of parameters for datastore


/datastores/<datastore>/configuration/parameters - list the parameters for the datastore


/datastores/<datastore> - add an href on the return to the configuration parameter list for the datastore
/configurations/parameters/<datastore> - list of parameters for datastore


* Require a configuration be created with a datastore.
Then a user may list the configuration parameters allowed on that configuration.

/configurations/<config_id>/parameters - parameter list for mysql

- after some thought i think this method (5) might be the best way to handle this.

I've outlined a few ways we could make this work. Let me know if you agree or why you may disagree with strategy 5.

Craig Vyvial
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140122/53118171/attachment.html>

More information about the OpenStack-dev mailing list