Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1065168 - [RFE][ironic]: Auto-discovery and register IPMI nodes
Summary: [RFE][ironic]: Auto-discovery and register IPMI nodes
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_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-14 05:04 UTC by RHOS Integration
Modified: 2015-03-19 17:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:20:49 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2014-02-14 05:04:43 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ironic/+spec/ipminode-auto-discovery.

Description:

Our Ironic need an utility tool to do the out-band auto-discovery the IPMI physical node and auto-register to Ironic. We send the IPMI request to the inputted IPs or subnet, based on the response, if target is IPMI node, the reply indicates whether the device supports version 1.5 or 2.0 and what forms of authentication are supported.  So we can use these IP/MAC to create ironic node to auto-register them. If use provide the IPMI credential, we can verify it and auto-config to our node info. The driver should be pxe_ipmitool or pxe_ipminative which can be another input for user.

And at the same time, we can check arp list to get the IPMI MAC address which is used to register node.

Specification URL (additional information):

None


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