Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1069456

Summary:	[Doc] [RFE][cinder]: Add currently used resources to already existing absolute-limits command
Product:	Red Hat OpenStack	Reporter:	Summer Long <slong>
Component:	doc-CLI_Reference	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Summer Long <slong>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	adahms, ddomingo, dnavale, eharney, yeylon
Target Milestone:	---	Keywords:	Documentation, FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	docs-rhos5-ups docs-ups-blocked
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1041491	Environment:
Last Closed:	2015-02-27 06:49:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1041491
Bug Blocks:

Description Summer Long 2014-02-25 04:01:45 UTC

+++ This bug was initially created as a clone of Bug #1041491 +++
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/cinder-used-resources-in-absolute-limits.

Description:
Actually, the absolute-limits command only returns the maximum usable limits for a tenant. Nova has the same call but returns the currently used resources of a tenant. The goal is to do the same thing in Cinder so an api user can get the same kind of information from a similar call.

Comment 2 Summer Long 2014-02-25 05:04:50 UTC

This bug is being assigned to Don Domingo, who is now the designated docs specialist for Block Storage.

Comment 3 Don Domingo 2014-02-26 00:04:20 UTC

Checked the upstream and downstream  documentation, the only place where cinder's "absolute-limit" subcommand is mentioned is in the CLI Reference and Training Guides. In both docs, they're pulled in from what looks like a page auto-generated from the --help of the cinder client.

As such, any change relating to this has to happen at the app level (i.e. change the output of 'openstack-cinder absolute-limits --help' or similar). Setting the component accordingly.

Comment 4 Don Domingo 2014-02-26 00:06:14 UTC

for reference:
http://docs.openstack.org/cli-reference/content/cinderclient_commands.html#cinderclient_subcommand_absolute-limits

(In reply to Don Domingo from comment #3)
> Checked the upstream and downstream  documentation, the only place where
> cinder's "absolute-limit" subcommand is mentioned is in the CLI Reference
> and Training Guides. In both docs, they're pulled in from what looks like a
> page auto-generated from the --help of the cinder client.
> 
> As such, any change relating to this has to happen at the app level (i.e.
> change the output of 'openstack-cinder absolute-limits --help' or similar).
> Setting the component accordingly.

Comment 5 Don Domingo 2014-02-27 01:32:06 UTC

Reassigning back to me. Checked the change again, looks like it was completely pulled in from upstream. The change seems to include a change in the 'cinder help absolute-limits' output as well, it'll probably just need some time for the upstream CLI Reference Guide to pick it up. 

Will have to check the CLI Reference Guide upstream again later on to see if the change has been cycled in.

Comment 6 Don Domingo 2014-05-01 01:38:14 UTC

Already there:
http://docs.openstack.org/cli-reference/content/cinderclient_commands.html#cinderclient_subcommand_absolute-limits

Setting to MODIFIED.

Comment 8 Summer Long 2014-06-23 06:01:15 UTC

Yup, it's there. But missing a full stop, and says nothing about 'maximum usable limits'.

Comment 10 Andrew Dahms 2015-02-27 06:49:08 UTC

The requested content is included in the latest version of the guide, which is now available on the Customer Portal.

Closing.