Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
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 [cp16...@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. ONE: /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. https://gist.github.com/cp16net/8547197 TWO: /configurations/parameters - list of datastores that have configuration parameters /configurations/parameters/datastore - list of parameters for datastore THREE: /datastores/datastore/configuration/parameters - list the parameters for the datastore FOUR: /datastores/datastore - add an href on the return to the configuration parameter list for the datastore /configurations/parameters/datastore - list of parameters for datastore FIVE: * 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. Thanks, Craig Vyvial ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom From: Craig Vyvial [cp16...@gmail.com] Sent: Wednesday, January 22, 2014 4:11 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.commailto:dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.commailto:mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: 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) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
