Difference between revisions of "Ironic-python-agent"
Vkozhukalov (talk | contribs) (→Preliminary architecture diagram) |
Vkozhukalov (talk | contribs) (→Ironic python agent) |
||
| Line 1: | Line 1: | ||
=Ironic python agent= | =Ironic python agent= | ||
| + | |||
| + | ==Motivation== | ||
| + | At the moment Ironic uses exactly the same deployment ramdisk as nova baremetal driver does. Current implementation of deployment agent exposes a hard drive via ISCSI and then conductor driver mounts it and copies OS image to it. However, there are a number of other possible much more scalable mechanisms such as downloading OS images via HTTP or BitTorrent or any kind of multicast protocols. Besides, default Ironic approach at the moment is to avoid installing bootloader on a node hard drive, but it is better to have such a possibility as well. Another point is that user often wants to have a comprehensive disk partitioning scheme with support of LVM, MD (software RAID), plain partitions, msdos and gpt partition tables, etc. User often needs to have a convenient mechanism of updating firmware, configuring hardware RAIDs, etc. As a conclusion, we need to have a comprehensive pluggable agent to deal with all that stuff. | ||
==What is ironic python agent?== | ==What is ironic python agent?== | ||
| Line 11: | Line 14: | ||
* 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 | ||
[[File:Ironic python agent.png|650px]] | [[File:Ironic python agent.png|650px]] | ||
| + | |||
| + | ==On conductor side== | ||
| + | Currently all that stuff about provisioning is implemented as a part of Ironic pxe driver. | ||
Revision as of 19:09, 7 March 2014
Contents
Ironic python agent
Motivation
At the moment Ironic uses exactly the same deployment ramdisk as nova baremetal driver does. Current implementation of deployment agent exposes a hard drive via ISCSI and then conductor driver mounts it and copies OS image to it. However, there are a number of other possible much more scalable mechanisms such as downloading OS images via HTTP or BitTorrent or any kind of multicast protocols. Besides, default Ironic approach at the moment is to avoid installing bootloader on a node hard drive, but it is better to have such a possibility as well. Another point is that user often wants to have a comprehensive disk partitioning scheme with support of LVM, MD (software RAID), plain partitions, msdos and gpt partition tables, etc. User often needs to have a convenient mechanism of updating firmware, configuring hardware RAIDs, etc. As a conclusion, we need to have a comprehensive pluggable agent to deal with all that stuff.
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
On conductor side
Currently all that stuff about provisioning is implemented as a part of Ironic pxe driver.
