Instead of duplicating the same log statement throughout
the code, the same logic can be provided by a shared decorator
that abstracts away the logging capability and unifies it behind
a common function instead.
Change-Id: Icc63bced7347c8bbf0299a4c5821425a10892a79
Running limits show without --absolute or --rate returns nothing and
the user is left to figure out what they need to provide to get the
correct data back. This patch prints an error and help output by making
at least one of the arguments required.
Change-Id: I576cf8ec0e05524ee67d46c48b56da8d44258667
Looks like the option to show limits of a specific project was
missing. This resulted in always using the authenticated project.
Change-Id: I512a05df20860ffb52af34f3b64c9eb81dae8c61
Closes-Bug: 1438379
There are files containing string format arguments inside
logging messages. Using logging function parameters should
be preferred.
Change-Id: Ic749ac9eb55564ed631d57055a5a4dfc3aebd169
* This is a combination of the compute and volume API limits as they are
very similar. As such, the command lives in a new command group
'openstack.common' that is unversioned.
* Implements 'limits show [--absolute|--rate]
Updated for https://review.openstack.org/#/c/36772/
Bug: 1172057
Change-Id: I2bd181cd0d098f7143360ae67944c2f221379af5
