Return hypervisor node status

Registered by jiang, yunhong

When return hypervisor node for hypervisor nova cmd, it will be better to return the status also, because the corresponding service may be down or disabled already.

Blueprint information

Status:
Complete
Approver:
John Garbutt
Priority:
Low
Drafter:
jiang, yunhong
Direction:
Approved
Assignee:
jiang, yunhong
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
John Garbutt
Completed by
jiang, yunhong

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:return-status-for-hypervisor-node,n,z

Addressed by: https://review.openstack.org/90172
    Return status for hypervisor node

Gerrit topic: https://review.openstack.org/#q,topic:bp/return-status-for-hypervisor-node,n,z

Addressed by: https://review.openstack.org/80707
    Return status for compute node.

Addressed by: https://review.openstack.org/80708
    Not count disabled compute node for statistics

nova-specs has been already approved/merged, so this blueprint also should be approved. - oomichi - 2014/05/30

Yes, I need to sync those again, its usually one of my friday jobs. Since the code us up for review, I can approve this for Juno-1 --johnthetubaguy (30th May 2014)

Sorry, this has not got enough positive reviews to make it in time for juno-1, moving to juno-2 --johnthetubaguy 10th June 2014

This should make Juno-2. All changes now approved, just final push left --johnthetubaguy 21 July 2014

Unit tests no longer passing, so this is likely to be delayed, pushing to juno-3 --johnthetubaguy 22 July 2014

Fixed the unit test failure, hope it will work for juno-2 -- yjiang5 22 July 2014

I think we need tempest test for it, right? -- yjiang5

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.