<div dir="ltr">I support the latest as well. I will make it so.<div><br></div><div>Thanks</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 8:16 AM, Daniel Salinas <span dir="ltr"><<a href="mailto:imsplitbit@gmail.com" target="_blank">imsplitbit@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I agree. This keeps everything identical to our current routing scheme. </p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Jan 23, 2014 7:31 AM, "Denis Makogon" <<a href="mailto:dmakogon@mirantis.com" target="_blank">dmakogon@mirantis.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>+1 to Greg.<br></div>Given schema is more preferable for API routes<br><div><div>/datastores/<datastore>/parameters</div>
<div>/datastores/<datastore>/parameters/<parameters></div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014/1/23 Greg Hill <span dir="ltr"><<a href="mailto:greg.hill@rackspace.com" target="_blank">greg.hill@rackspace.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
To be more consistent with other APIs in trove, perhaps:
<div><br>
</div>
<div>/datastores/<datastore>/parameters</div>
<div>
<div>
<div>/datastores/<datastore>/parameters/<parameters></div><span><font color="#888888">
<div><br>
</div>
<div>Greg</div></font></span><div><div>
<div><br>
</div>
<div>On Jan 22, 2014, at 4:52 PM, Kaleb Pomeroy <<a href="mailto:kaleb.pomeroy@rackspace.com" target="_blank">kaleb.pomeroy@rackspace.com</a>> wrote:</div>
<br>
<blockquote type="cite">
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="direction:ltr;font-family:Tahoma;font-size:10pt"><span style="font-size:13px;font-family:Tahoma">I think that may have been a slight oversite. We will likely have the following two routes<br>
<br>
/datastores/<datastore>/configuration/</span><span style="font-size:13px;font-family:Tahoma"><span> </span>would be the collection of all parameters</span><br>
<span style="font-size:13px;font-family:Tahoma">/datastores/<datastore>/configuration/</span><span style="font-size:13px;font-family:Tahoma">:parameter would be an individual setting.<span> </span><br>
<br>
- kpom<br>
<br>
</span>
<div style="font-family:'Times New Roman';font-size:16px">
<hr>
<div style="direction:ltr"><font face="Tahoma"><b>From:</b><span> </span>Craig Vyvial [<a href="mailto:cp16net@gmail.com" target="_blank">cp16net@gmail.com</a>]<br>
<b>Sent:</b><span> </span>Wednesday, January 22, 2014 4:11 PM<br>
<b>To:</b><span> </span>OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b><span> </span>Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Ok with overwhelming support for #3.
<div>What if we modified #3 slightly because looking at it again seems like we could shorten the path since <span style="font-family:Tahoma;font-size:13px">/datastores/<datastore>/configuration</span> doesnt do anything.
<div><br>
</div>
<div>instead of </div>
<div>#1</div>
<div><span style="font-size:13px;font-family:Tahoma">/datastores/<datastore>/configuration/</span><span style="font-size:13px;font-family:Tahoma">parameters</span></div>
<div><span style="font-size:13px;font-family:Tahoma"><br>
</span></div>
<div><span style="font-size:13px;font-family:Tahoma">maybe:</span></div>
<div><span style="font-size:13px;font-family:Tahoma">#2</span></div>
<div><span style="font-size:13px;font-family:Tahoma">/datastores/<datastore>/</span><span style="font-size:13px;font-family:Tahoma">parameters</span><br>
</div>
</div>
<div><span style="font-size:13px;font-family:Tahoma"><br>
</span></div>
<div><span style="font-size:13px;font-family:Tahoma">#3</span></div>
<div><span style="font-size:13px;font-family:Tahoma">/datastores/<datastore>/configuration</span><span style="font-size:13px;font-family:Tahoma">parameters</span><span style="font-size:13px;font-family:Tahoma"><br>
</span></div>
<div><span style="font-size:13px;font-family:Tahoma"><br>
</span></div>
<div><span style="font-size:13px;font-family:Tahoma"><br>
</span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon<span> </span><span dir="ltr"><<a href="mailto:dmakogon@mirantis.com" target="_blank">dmakogon@mirantis.com</a>></span><span> </span>wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Goodday to all.
<div><br>
</div>
<div>#3 looks more than acceptable. </div>
<div><span style="font-family:Tahoma;font-size:13px">/datastores/<datastore>/</span><span style="font-family:Tahoma;font-size:13px">configuration/parameters.</span><br>
</div>
<div><span style="font-family:Tahoma;font-size:13px">According to configuration parameters design, </span><span style="font-family:Tahoma;font-size:13px">a configuration set must be associated to exactly one datastore.</span></div>
<div><span style="font-family:Tahoma;font-size:13px"><br>
</span></div>
<div><span style="font-family:Tahoma;font-size:13px">Best regards, Denis Makogon.</span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014/1/22 Michael Basnight<span> </span><span dir="ltr"><<a href="mailto:mbasnight@gmail.com" target="_blank">mbasnight@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div>
<div>On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote:<br>
<br>
> My thoughts so far:<br>
><br>
> /datastores/<datastore>/configuration/parameters (Option Three)<br>
> + configuration set without an associated datastore is meaningless<br>
> + a configuration set must be associated to exactly one datastore<br>
> + each datastore must have 0-1 configuration set<br>
> + All above relationships are immediately apparent<br>
> - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern)<br>
<br>
</div>
+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.<br>
<br>
<br>
</div>
</div>
<div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</blockquote>
</div></div></div>
<br>
</div>
</div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>