A more advanced driver API

Registered by devananda on 2013-05-28

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.

Blueprint information

Status:
Complete
Approver:
devananda
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Jim Rollenhagen on 2015-10-15

Related branches

Sprints

Whiteboard

This looks like vendor passthru to me, I'm pretty sure we don't need this blueprint anymore but verifying with deva.
// jroll 2015-10-15

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.