<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Steven,<br>
<br>
Thank you for continuing to pursue this. Adding this functionality
and having it consistent will be a good thing.<br>
<br>
The plan for Cinder looks good to me and is consistent with Mike and
Duncan's input.<br>
<br>
I look forward to seeing patches for Cinder.<br>
<br>
Jay<br>
<br>
<div class="moz-cite-prefix">On 01/06/2015 10:03 AM, Steven Kaufer
wrote:<br>
</div>
<blockquote
cite="mid:OFE60A3ADF.9630A1D3-ON87257DC5.00543A4D-86257DC5.00582E7B@us.ibm.com"
type="cite">
<p><font face="sans-serif" size="2">This is a follow up thread to
[1]</font><br>
<br>
<font face="sans-serif" size="2">In order to have consistency
across clients, I am proposing that the client side sorting
has the following syntax: --sort
<key>[:<direction>]</font><br>
<br>
<font face="sans-serif" size="2">Where the --sort parameter is
comma-separated and is used to specify one or more sort keys
and directions. The direction defaults to 'desc' for each sort
key and the user can supply 'asc' to override.</font><br>
<br>
<font face="sans-serif" size="2">For example:</font><br>
<br>
<font face="sans-serif" size="2"> nova list --sort display_name</font><br>
<font face="sans-serif" size="2"> nova list --sort
display_name,vm_state</font><br>
<font face="sans-serif" size="2"> nova list --sort
display_name:asc,vm_state:asc</font><br>
<br>
<font face="sans-serif" size="2">If approved, then the following
changes are needed for glance and cinder (note that nova
already uses this syntax):</font><br>
<br>
<font face="sans-serif" size="2"> Cinder: Deprecate --sort_key
and --sort_dir and add support for --sort</font><br>
<font face="sans-serif" size="2"> Glance: Modify [2] to this
new syntax</font><br>
<br>
<font face="sans-serif" size="2">I have not verified how all
other projects handle sorting, there may be other projects
that would also need to be changed.</font><br>
<br>
<font face="sans-serif" size="2">Thoughts? Objections?</font><br>
<br>
<font face="sans-serif" size="2">Also, if there is a more formal
way to propose/review this standard please let me know.</font><br>
<br>
<font face="sans-serif" size="2">[1] </font><a
moz-do-not-send="true"
href="http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg42854.html"><font
face="sans-serif" size="2">http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg42854.html</font></a><br>
<font face="sans-serif" size="2">[2] </font><a
moz-do-not-send="true"
href="https://review.openstack.org/#/c/120777/"><font
face="sans-serif" size="2">https://review.openstack.org/#/c/120777/</font></a><br>
<br>
<font face="sans-serif" size="2">Thanks,</font><br>
<font face="sans-serif" size="2">Steven Kaufer</font>
<br>
</p>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>