[openstack-dev] Grizzly volume quotas

Pat Bredenberg patrick.bredenberg at oracle.com
Wed Feb 5 22:43:31 UTC 2014


On 02/ 5/14 03:24 PM, John Griffith wrote:
> On Wed, Feb 5, 2014 at 3:09 PM, Jay S Bryant<jsbryant at us.ibm.com>  wrote:
>> Joe,
>>
>> Ah!  So, those aren't for Cinder Volume but for nova-volume.  Ok, so there
>> isn't really a bug then.
>>
> Yep, this is left over from when volumes were in nova.
     Thank you all for your comments.  After Jay's initial response, I 
did file bug 1276828: 
https://bugs.launchpad.net/python-novaclient/+bug/1276828.  Joe Gordon's 
comment made it sound like a bug is still present.  But if that's no 
longer the case, please close that bug as you see fit.  Minimally, I see 
this as something that could be addressed in documentation, if it hasn't 
already.
     I'll step back and let you decide the appropriate action with the 
bug.  Thank you again.

Sincerely,
Pat
>
>> Sorry for speaking too quickly.  Thanks for the info!
>>
>>
>> Jay S. Bryant
>>         IBM Cinder Subject Matter Expert&   Cinder Core Member
>> Department 7YLA, Building 015-2, Office E125, Rochester, MN
>> Telephone: (507) 253-4270, FAX (507) 253-6410
>> TIE Line: 553-4270
>> E-Mail:  jsbryant at us.ibm.com
>> --------------------------------------------------------------------
>> All the world's a stage and most of us are desperately unrehearsed.
>>                    -- Sean O'Casey
>> --------------------------------------------------------------------
>>
>>
>>
>> From:        Joe Gordon<joe.gordon0 at gmail.com>
>> To:        "OpenStack Development Mailing List (not for usage questions)"
>> <openstack-dev at lists.openstack.org>,
>> Date:        02/05/2014 04:03 PM
>> Subject:        Re: [openstack-dev] Grizzly volume quotas
>> ________________________________
>>
>>
>>
>> On Wed, Feb 5, 2014 at 1:21 PM, Jay S Bryant<jsbryant at us.ibm.com>  wrote:
>>> Pat,
>>>
>>> I see the same behavior on an Icehouse level install.  So, I think you may
>>> have found a bug.
>> So the bug here isn't what you expect.
>>
>> First a bit of background.
>>
>> * python-novaclient isn't part of the integrated release and needs to
>> support most releases (not just the most recent).
>> * python-novaclient doesn't have any mechanism to detect what commands
>> a cloud supports and hide the other commands  [This is the bug].
>>
>> So nova client needs to support nova-volume, which is why we still
>> have the volume quota options.
>>
>>> I would open the bug to python-novaclient to start with, but it may end up
>>> coming back to Cinder.
>>>
>>>
>>> Jay S. Bryant
>>>         IBM Cinder Subject Matter Expert&   Cinder Core Member
>>> Department 7YLA, Building 015-2, Office E125, Rochester, MN
>>> Telephone: (507) 253-4270, FAX (507) 253-6410
>>> TIE Line: 553-4270
>>> E-Mail:  jsbryant at us.ibm.com
>>> --------------------------------------------------------------------
>>> All the world's a stage and most of us are desperately unrehearsed.
>>>                    -- Sean O'Casey
>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>> From:        Pat Bredenberg<patrick.bredenberg at oracle.com>
>>> To:        openstack-dev at lists.openstack.org,
>>> Date:        02/05/2014 03:05 PM
>>> Subject:        [openstack-dev] Grizzly volume quotas
>>> ________________________________
>>>
>>>
>>>
>>> Dear all,
>>>
>>>      I'm part of the team bringing OpenStack to Solaris and am confused
>>> about how volume quotas appear according to nova(1).  We're using
>>> Grizzly 2013.1.4 for both Nova and Cinder; please let me know what other
>>> configuration information you need.  The raw data itself is available
>>> here: http://paste.openstack.org/show/62667/.
>>>      Is it a bug that "volumes" appears as a configurable quota via
>>> nova(1), according to its help menu?  I'll apologize in advance if this
>>> has already been documented elsewhere and/or addressed in Havana or
>>> Icehouse.  I searched but didn't see it mentioned.  If it's a bug that
>>> has yet to be filed and should be addressed, please let me know and I'll
>>> gladly file the bug.  Otherwise, I'll chalk it up as a learning
>>> experience.  Your guidance is greatly appreciated.
>>>
>>> Very respectfully,
>>> Pat Bredenberg
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




More information about the OpenStack-dev mailing list