[openstack-dev] [Trove] how to list available configuration parameters for datastores
cp16net at gmail.com
Wed Jan 22 22:11:10 UTC 2014
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
On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon <dmakogon at mirantis.com>wrote:
> Goodday to all.
> #3 looks more than acceptable.
> According to configuration parameters design, a configuration set must be
> associated to exactly one datastore.
> Best regards, Denis Makogon.
> 2014/1/22 Michael Basnight <mbasnight at 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 at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev