Support for openstack-status utility
OpenStack Client should have support for the openstack-status utility feature (used to be found in earlier releases till mitaka) in OpenStack Client.
It shows the status of all the daemons(services) required by OpenStack System.
Summary
=======
OpenStack Client should support openstack-status utility(used to be found till mitaka release).
Using openstack-status utility, user can start/stop/
# openstack status
If we pass status as an argument to the openstack utility, it will return the status of all the openstack system services, whether they are running or stopped or other. It will help user to pass a single command to check the status of the whole openstack system.
Motivation
========
By this utility, it will become convenient for admin, to check the status of whole openstack system in one go. Sample output of the openstack-status command in Mitaka Release:
# openstack-status
== Nova services ==
openstack-nova-api: active
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
== Glance services ==
openstack-
openstack-
== Keystone service ==
openstack-keystone: inactive (disabled on boot)
== Horizon service ==
openstack-
== neutron services ==
neutron-server: active
neutron-dhcp-agent: active
neutron-l3-agent: failed
neutron-
neutron-
neutron-
== Swift services ==
openstack-
openstack-
openstack-
openstack-
== Cinder services ==
openstack-
openstack-
openstack-
openstack-
== Ceilometer services ==
openstack-
openstack-
openstack-
openstack-
openstack-
== Support services ==
mysqld: inactive (disabled on boot)
openvswitch: active
dbus: active
target: active
rabbitmq-server: active
memcached: active
== Keystone users ==
+------
| id | name | enabled | email |
+------
| 07c4f5c30896459
| bea63aa11f234be
| 36019c80e94146a
| 74842cfc27d64c0
| 8c962fefacad4bb
| d6915999562a475
| f2a1dd8378e5445
| df82707342e5474
| d5d1f4afbae14d0
| 08dca9c12e1d447
| 0340d02dd04e44f
+------
== Glance images ==
+------
| ID | Name |
+------
| 0127ea30-
+------
== Nova managed services ==
+----+-
| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+----+-
| 3 | nova-cert | localhost.
| 4 | nova-consoleauth | localhost.
| 5 | nova-scheduler | localhost.
| 6 | nova-conductor | localhost.
| 7 | nova-compute | localhost.
| 8 | nova-conductor | localhost.
| 9 | nova-cert | localhost.
| 10 | nova-scheduler | localhost.
| 11 | nova-consoleauth | localhost.
| 12 | nova-compute | localhost.
| 13 | nova-compute | compute2 | nova | enabled | down | 2016-04-
| 14 | nova-scheduler | osmitaka | internal | enabled | up | 2016-09-
| 15 | nova-conductor | osmitaka | internal | enabled | up | 2016-09-
| 16 | nova-consoleauth | osmitaka | internal | enabled | up | 2016-09-
| 17 | nova-cert | osmitaka | internal | enabled | up | 2016-09-
| 18 | nova-compute | osmitaka | nova | enabled | up | 2016-09-
| 19 | nova-conductor | 192.168.52.107 | internal | enabled | down | - | - |
| 20 | nova-consoleauth | 192.168.52.107 | internal | enabled | down | - | - |
| 21 | nova-scheduler | 192.168.52.107 | internal | enabled | down | - | - |
| 22 | nova-cert | 192.168.52.107 | internal | enabled | down | - | - |
+----+-
== Nova networks ==
+------
| ID | Label | Cidr |
+------
| 1f9fea71-
| 978b1aac-
| c811578e-
+------
== Nova instance flavors ==
+----+-
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+----+-
| 1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True |
| 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True |
| 3 | m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True |
| 4 | m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True |
| 5 | m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True |
| 6 | new_flavor | 512 | 1 | 0 | | 1 | 1.0 | True |
+----+-
== Nova instances ==
+------
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+------
| b5d116e7-
| 8b99e339-
| 211e452e-
+------
Testing
======
Proper Tests would be added to check the system's behavior after adding this feature.
Outside Dependencies
==================
Functionality must be added to openstack cli.
Requirements Update Required
=======
No specific Update is required for this change, if some external module is planned to be used for this functionality, then we only we will have to update the requirements list.
Doc Impact
=========
OpenStack User Manual Utility will also needs to be updated for this feature. OpenStack CLI Documentation will be updated in order to inform the user about the changes that will be introduced.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- sandeep nandal
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by