The only weird part is how the output is structured, I'm wondering if we can make it a bit more like the other OSC commands:
steve:keystone$ nova availability-zone-list +-----------------------+----------------------------------------+ | Name | Status | +-----------------------+----------------------------------------+ | internal | available | | |- ubuntuvm | | | | |- nova-conductor | enabled :-) 2014-12-09T08:48:11.000000 | | | |- nova-consoleauth | enabled :-) 2014-12-09T08:48:15.000000 | | | |- nova-scheduler | enabled :-) 2014-12-09T08:48:16.000000 | | | |- nova-cert | enabled :-) 2014-12-09T08:48:13.000000 | | | |- nova-network | enabled :-) 2014-12-09T08:48:18.000000 | | nova | available | | |- ubuntuvm | | | | |- nova-compute | enabled :-) 2014-12-09T08:48:19.000000 | +-----------------------+----------------------------------------+
The only weird part is how the output is structured, I'm wondering if we can make it a bit more like the other OSC commands:
steve:keystone$ nova availability- zone-list ------- ------- ---+--- ------- ------- ------- ------- ------- --+ ------- ------- ---+--- ------- ------- ------- ------- ------- --+ 09T08:48: 11.000000 | 09T08:48: 15.000000 | 09T08:48: 16.000000 | 09T08:48: 13.000000 | 09T08:48: 18.000000 | 09T08:48: 19.000000 | ------- ------- ---+--- ------- ------- ------- ------- ------- --+
+------
| Name | Status |
+------
| internal | available |
| |- ubuntuvm | |
| | |- nova-conductor | enabled :-) 2014-12-
| | |- nova-consoleauth | enabled :-) 2014-12-
| | |- nova-scheduler | enabled :-) 2014-12-
| | |- nova-cert | enabled :-) 2014-12-
| | |- nova-network | enabled :-) 2014-12-
| nova | available |
| |- ubuntuvm | |
| | |- nova-compute | enabled :-) 2014-12-
+------