Bug 1261096

Summary: [RFE][nova]: New nova API call to mark nova-compute down.
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED ERRATA QA Contact: Gabriel Szasz <gszasz>
Severity: medium Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: berrange, dasmith, eglynn, fdinitto, gszasz, jschluet, kchamart, mgrac, ndipanov, nlevinki, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone: betaKeywords: FutureFeature
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/mark-host-down
Whiteboard: upstream_milestone_liberty-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-nova-12.0.0-1.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 21:07:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1178665    

Description Stephen Gordon 2015-09-08 14:48:34 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/mark-host-down.

Description:

New API call is needed to change the state of compute service "down"
immediately. This allows usage of evacuate API without a delay. Also as
external system will make sure host is down and no VMs left running, there
will be no possibility to break shared storage or use same IPs again.

Specification URL (additional information):

http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/mark-host-down.html

Comment 3 Stephen Gordon 2015-09-09 14:51:01 UTC
Hi Fabio,

How would you like to track the need to also update the agent(s) to take advantage of this API if it's available?

Thanks,

Steve

Comment 4 Fabio Massimo Di Nitto 2015-09-09 15:28:12 UTC
(In reply to Stephen Gordon from comment #3)
> Hi Fabio,
> 
> How would you like to track the need to also update the agent(s) to take
> advantage of this API if it's available?
> 
> Thanks,
> 
> Steve

As soon as the API is available in RDO we can clone the bz for fence-agents but we need to keep in mind that fence-agents is in RHEL Base OS and follows a different schedule. so we need to be a bit smart in landing the code to avoid sync issues.

Comment 9 errata-xmlrpc 2016-04-07 21:07:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0603.html