Seems like there are actually a few variants to this,
steve:keystone$ nova usage-list
Usage from 2014-11-18 to 2014-12-17:
+----------------------------------+---------+--------------+-----------+---------------+
| Tenant ID | Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |
+----------------------------------+---------+--------------+-----------+---------------+
| 7390ee47b3c642cf86ed2e0501cab352 | 1 | 384.43 | 0.75 | 0.75 |
| ebab58588b9046a699057a51ac43133f | 1 | 57.88 | 0.11 | 0.11 |
+----------------------------------+---------+--------------+-----------+---------------+
steve:keystone$ nova usage
Usage from 2014-11-18 to 2014-12-17:
+---------+--------------+-----------+---------------+
| Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |
+---------+--------------+-----------+---------------+
| 1 | 384.84 | 0.75 | 0.75 |
+---------+--------------+-----------+---------------+
steve:keystone$ nova usage --tenant ebab58588b9046a699057a51ac43133f
Usage from 2014-11-18 to 2014-12-17:
+---------+--------------+-----------+---------------+
| Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |
+---------+--------------+-----------+---------------+
| 1 | 60.23 | 0.12 | 0.12 |
+---------+--------------+-----------+---------------+
I vote we just implement 'nova usage' and have it default to the current auth project, or have a flag for a specific project Id, and another flag to list all projects (it takes priority over the specified one). This way we always have the project id in the returned data.
Seems like there are actually a few variants to this,
steve:keystone$ nova usage-list ------- ------- ------- ------- +------ ---+--- ------- ----+-- ------- --+---- ------- ----+ ------- ------- ------- ------- +------ ---+--- ------- ----+-- ------- --+---- ------- ----+ f86ed2e0501cab3 52 | 1 | 384.43 | 0.75 | 0.75 | 699057a51ac4313 3f | 1 | 57.88 | 0.11 | 0.11 | ------- ------- ------- ------- +------ ---+--- ------- ----+-- ------- --+---- ------- ----+
Usage from 2014-11-18 to 2014-12-17:
+------
| Tenant ID | Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |
+------
| 7390ee47b3c642c
| ebab58588b9046a
+------
steve:keystone$ nova usage ---+--- ------- ----+-- ------- --+---- ------- ----+ ---+--- ------- ----+-- ------- --+---- ------- ----+ ---+--- ------- ----+-- ------- --+---- ------- ----+
Usage from 2014-11-18 to 2014-12-17:
+------
| Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |
+------
| 1 | 384.84 | 0.75 | 0.75 |
+------
steve:keystone$ nova usage --tenant ebab58588b9046a 699057a51ac4313 3f ---+--- ------- ----+-- ------- --+---- ------- ----+ ---+--- ------- ----+-- ------- --+---- ------- ----+ ---+--- ------- ----+-- ------- --+---- ------- ----+
Usage from 2014-11-18 to 2014-12-17:
+------
| Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |
+------
| 1 | 60.23 | 0.12 | 0.12 |
+------
I vote we just implement 'nova usage' and have it default to the current auth project, or have a flag for a specific project Id, and another flag to list all projects (it takes priority over the specified one). This way we always have the project id in the returned data.
+1 on making this show command instead of list.