<html><body>
<p><font size="2" face="sans-serif">The cinder client supports passing a sort key via the --sort_key argument. The client restricts the sort keys that the user can supply to the following: </font><a href="https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/volumes.py#L28-L29"><font size="2" face="sans-serif">https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/volumes.py#L28-L29</font></a><br>
<br>
<font size="2" face="sans-serif">This list of sort keys is not complete. As far I know, all attributes on this class are valid: </font><a href="https://github.com/openstack/cinder/blob/master/cinder/db/sqlalchemy/models.py#L104"><font size="2" face="sans-serif">https://github.com/openstack/cinder/blob/master/cinder/db/sqlalchemy/models.py#L104</font></a><br>
<br>
<font size="2" face="sans-serif">I noticed that the 'name' key is incorrect and it should instead be 'display_name'. Before I create a bug/fix to address this, I have the following questions:</font><br>
<br>
<font size="2" face="sans-serif">Does anyone know the rational behind the client restricting the possible sort keys?</font><br>
<font size="2" face="sans-serif">Why not allow the user to supply any sort key (assuming that invalid keys are gracefully handled)?</font><br>
<br>
<font size="2" face="sans-serif">Note, if you try this out at home, you'll notice that the client table is not actually sorted, fixed under: </font><a href="https://review.openstack.org/#/c/141964/"><font size="2" face="sans-serif">https://review.openstack.org/#/c/141964/</font></a><br>
<br>
<font size="2" face="sans-serif">Thanks,</font><br>
<font size="2" face="sans-serif">Steven Kaufer</font></body></html>