Bug 1337739

Summary: Manual cleaning support for Ironic.
Product: Red Hat OpenStack Reporter: Keith Basil <kbasil>
Component: openstack-ironicAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED ERRATA QA Contact: Raviv Bar-Tal <rbartal>
Severity: medium Docs Contact:
Priority: low    
Version: 9.0 (Mitaka)CC: jjoyce, mburns, mlopes, rbartal, rhel-osp-director-maint, sclewis, srevivo
Target Milestone: gaKeywords: FutureFeature, Triaged
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-ironic-5.1.2-3.el7ost Doc Type: Enhancement
Doc Text:
This enhancement adds manual cleaning, which allows operators to move a node directly into a cleaning state, from a manageable state. This was added because operators may run cleaning steps for various reasons, including: Building RAID, erasing devices, among others. As a result, operators are now able to use the OpenStack Bare Metal (ironic) API to manually start the cleaning process for the ironic nodes, choosing exactly which steps should be run.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-11 12:22:04 UTC Type: Bug
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: 1418564    

Description Keith Basil 2016-05-20 00:32:46 UTC 
Manual cleaning (as opposed to automated cleaning) encompasses all long running, manual, destructive tasks an operator may want to perform either between workloads, or before the first workload has been assigned to a node.

This feature had previously been called “Zapping” and this specification copies a lot of the zapping specification. (Thank you Josh Gachnang!)

Problem description
Automated cleaning has been available in ironic since the kilo cycle. It lets operators choose which clean steps are automatically done prior to the first time a node is deployed and each time after a node is released.

However, operators may want certain operations or tasks to only run on demand, rather than in every clean cycle. Things like firmware updates, setting up new RAID levels, or burning in nodes often need to be done before a user is given a server, but take too long to reasonably do at deploy time.

Many of the above tasks could provide useful scheduling hints to nova once hardware capabilities are introduced. Operators could use these scheduling hints to create flavors, such as a nova compute flavor that requires a node with RAID 1 for extra durability.

Upstream:
[1] - https://blueprints.launchpad.net/ironic/+spec/manual-cleaning
Comment 2 Lucas Alvares Gomes 2016-05-26 12:31:57 UTC 
Upstream documentation for it: http://docs.openstack.org/developer/ironic/deploy/cleaning.html?highlight=manual%20cleaning#manual-cleaning
Comment 6 Raviv Bar-Tal 2016-07-31 08:06:42 UTC 
Hi Scott,
I tested the clean steps on OSPD 9  (Mitaka)
with the following ironic packages:

openstack-ironic-inspector-3.2.2-4.el7ost.noarch
openstack-ironic-conductor-5.1.2-3.el7ost.noarch
openstack-ironic-api-5.1.2-3.el7ost.noarch
openstack-ironic-common-5.1.2-3.el7ost.noarch
Comment 9 errata-xmlrpc 2016-08-11 12:22:04 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-1597.html