Open Stack

Another +1 for option 3.

Greg

On Jan 22, 2014, at 2:27 PM, Denis Makogon <dmakogon at mirantis.com<mailto: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<mailto: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<mailto: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<mailto: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/815eb590/attachment-0001.html>