On 11 August 2014 21:03, Dean Troyer wrote:
> On Mon, Aug 11, 2014 at 5:34 PM, Duncan Thomas
> wrote:
>>
>> Making an previously mandatory parameter optional, at least on the
>> command line, does break backward compatibility though, does it?
>> Everything that worked before will still work.
>
>
On Mon, Aug 11, 2014 at 5:34 PM, Duncan Thomas
wrote:
>
> Making an previously mandatory parameter optional, at least on the
> command line, does break backward compatibility though, does it?
> Everything that worked before will still work.
>
By itself, maybe that is ok. You're right, nothing _s
On 8 August 2014 07:55, Dean Troyer wrote:
> 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]
Making an previously mandatory parameter optional, at least on the
comma
On Aug 8, 2014, at 6:55 AM, Dean Troyer wrote:
> On Fri, Aug 8, 2014 at 12:36 AM, Ganapathy, Sandhya
> wrote:
> This is to discuss Bug #1231298 –
> https://bugs.launchpad.net/cinder/+bug/1231298
>
> ...
> Conclusion reached with this bug is that, we need to modify cinder client in
> order
On Fri, Aug 8, 2014 at 12:36 AM, Ganapathy, Sandhya <
sandhya.ganapa...@hp.com> wrote:
> This is to discuss Bug #1231298 –
> https://bugs.launchpad.net/cinder/+bug/1231298
>
...
> Conclusion reached with this bug is that, we need to modify cinder client
> in order to accept optional size paramet
Hi,
This is to discuss Bug #1231298 - https://bugs.launchpad.net/cinder/+bug/1231298
Bug description : When one creates a volume from a snapshot or another volume,
the size argument is calculated automatically. In the case of an image it needs
to be specified though, for something larger than t
