<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Aug 8, 2014, at 6:55 AM, Dean Troyer <<a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Aug 8, 2014 at 12:36 AM, Ganapathy, Sandhya <span dir="ltr"><<a href="mailto:sandhya.ganapathy@hp.com" target="_blank">sandhya.ganapathy@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div><p class="MsoNormal"><span style="font-size:10pt">This is to discuss Bug #1231298 –
</span><a href="https://bugs.launchpad.net/cinder/+bug/1231298" target="_blank" style="font-size:10pt">https://bugs.launchpad.net/cinder/+bug/1231298</a></p></div></div></blockquote><div>... </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple"><p class="MsoNormal"><span style="font-size:10pt">Conclusion reached with this bug is that, we need to modify cinder client in order to accept optional size parameter (as the cinder’s API allows) and calculate the size automatically during
volume creation from image.</span><br></p><p class="MsoNormal"><span style="font-size:10.0pt;background:white">There is also an opinion that size should not be an optional parameter during volume creation – does this mean, Cinder’s API should be changed in order to make size a mandatory parameter.</span></p>
</div></blockquote><div><br></div><div>In cinderclient I think you're stuck with size as a mandatory argument to the 'cinder create' command, as you must be backward-compatible for at least a deprecation period.[0]</div>
<div><br></div><div>Your option here[1] is to use a sentinel value for size that indicates the actual volume size should be calculated and let the client do the right thing under the hood to feed the server API. Other project CLIs have used both 'auto' and '0' in situations like this. I'd suggest '0' as it is still an integer and doesn't require potentially user-error-prone string matching to work.</div></div></div></div></blockquote><div><br></div>We did this for novaclient volume attach and allowed device to be ‘auto' or the argument to be omitted. I don’t see a huge problem turning size into an optional parameter as long as it doesn’t break older scripts. Turning it from an arg into a kwarg would definitely require deprecation.</div><div><br></div><div>Vish</div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><div>FWIW, this is why OSC changed 'volume create' to make --size an option and make the volume name be the positional argument.</div><div><br></div><div>[0] The deprecation period for clients is ambiguous as the release cycle isn't timed but we think of deprecations that way. Using integrated release cycles is handy but less than perfect to correlate to the client's semver releases.</div>
</div>[1] Bad pun alert...or is there such a thing as a bad pun???<br clear="all"><div><br></div><div>dt</div><div><br></div>-- <br><br>Dean Troyer<br><a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a><br>
</div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>