Bug 1122773 - [RFE][ironic]: iLO Node Discovery
Summary: [RFE][ironic]: iLO Node Discovery
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/iron...
Whiteboard: upstream_milestone_none upstream_defi...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-24 04:02 UTC by RHOS Integration
Modified: 2015-03-19 17:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description RHOS Integration 2014-07-24 04:02:53 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ironic/+spec/ilo-node-discovery.

Description:

Problem description
===================

Today, Ironic does not have the out-of-band node discovery.
It cannot discover the nodes with in a subnet range or for a
specific driver.

Proposal:
=========
This proposal adds the ability to perform out-of-band
node discovery via multicast search for ProLiant nodes.
Multicast search will be faster than broadcast search.



Proposed change
===============

The proposal is to do node discovery via iLO driver.

* ironic driver-vendor-passthru <driver_name> <method>
         [<arg=value> [<arg=value> ...]]

where driver_name=ilo
    method = node_discovery()
    arg=value pairs can be like:
["manufacturer"="hp", "node_model" = ["SL", "DL", "BL"]

It discovers all ProLiant nodes' iLO IP address that matches the node search
identifiers.   A deployer can then use the returned node iLO IP address to
create nodes.  This feature can be used with Node property discovery
during node create feature to automate node create.


Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.