Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1056098 - [RFE][ironic]: A more advanced driver API
Summary: [RFE][ironic]: A more advanced driver API
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Keith Basil
QA Contact: Shai Revivo
URL: https://blueprints.launchpad.net/iron...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-21 14:19 UTC by RHOS Integration
Modified: 2016-05-19 23:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2016-05-19 23:24:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description RHOS Integration 2014-01-21 14:19:25 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ironic/+spec/advanced-driver-api.


Drivers may need to expose certain functionality via the API service which is unique to that driver, or which is not part of the Manager service's usual capabilities. For example, the IPMIControlDriver may expose a "discover" or "scan network range" method.

The implementation details of this need to be worked out -- drivers are loaded by the ResourceManager currently, but to handle RPC, they need to be part of a service. Consideration must also be given to the context, security, and performance aspects, as well as request queuing and API response. Eg, how do we handle multiple requests? Can such methods be asynchronous, and if so, how does the answer get back to the API client when there is no instance or node associated to the request?

This is not needed for Ironic's first RC, but I'm putting this up here for further discussion and thought.

Specification URL (additional information):


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