Open Stack

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 <dmakogon at 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 <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
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140122/80153c1f/attachment.html>