Difference between revisions of "Ironic-python-agent"
Vkozhukalov (talk | contribs) (→Ironic python agent) |
Vkozhukalov (talk | contribs) (→Preliminary architecture diagram) |
||
| Line 10: | Line 10: | ||
==Preliminary architecture diagram== | ==Preliminary architecture diagram== | ||
* Drow.io editable diagram https://drive.google.com/file/d/0BybDDjx4oqkYOVZ5a2hURUViblk/edit?usp=sharing | * Drow.io editable diagram https://drive.google.com/file/d/0BybDDjx4oqkYOVZ5a2hURUViblk/edit?usp=sharing | ||
| − | < | + | <left>[[File:Ironic python agent.png|650px]]</left> |
Revision as of 18:46, 7 March 2014
Ironic python agent
What is ironic python agent?
- It supposed to be a built-in component of so called utility ramdisk.
- Ironic conductor drivers are supposed to be able to interact with this component via REST API.
- It is supposed to use JSON as a transport layer.
- It is supposed to have a pluggable architecture in order to make user able to easily add their own functionality (whether gathering data about the hardware or applying changes to it). Plugins are supposed to be JSON driven components (python modules, bash scripts, what ever).
- Agent itself is supposed to route the incoming JSON to the appropriate plugin, and to route the response back via the transport layer.
Preliminary architecture diagram
- Drow.io editable diagram https://drive.google.com/file/d/0BybDDjx4oqkYOVZ5a2hURUViblk/edit?usp=sharing
<left>
</left>
