[openstack-dev] [Ironic] A ramdisk agent

Vladimir Kozhukalov vkozhukalov at mirantis.com
Fri Mar 7 16:26:28 UTC 2014

As far as I understand, there are 4 projects which are connected with this
topic. Another two projects which were not mentioned by Devananda are

Vladimir Kozhukalov

On Fri, Mar 7, 2014 at 4:41 AM, Devananda van der Veen <
devananda.vdv at gmail.com> wrote:

> All,
> The Ironic team has been discussing the need for a "deploy agent" since
> well before the last summit -- we even laid out a few blueprints along
> those lines. That work was deferred  and we have been using the same deploy
> ramdisk that nova-baremetal used, and we will continue to use that ramdisk
> for the PXE driver in the Icehouse release.
> That being the case, at the sprint this week, a team from Rackspace shared
> work they have been doing to create a more featureful hardware agent and an
> Ironic driver which utilizes that agent. Early drafts of that work can be
> found here:
> https://github.com/rackerlabs/teeth-agent
> https://github.com/rackerlabs/ironic-teeth-driver
> I've updated the original blueprint and assigned it to Josh. For reference:
> https://blueprints.launchpad.net/ironic/+spec/utility-ramdisk
> I believe this agent falls within the scope of the baremetal provisioning
> program, and welcome their contributions and collaboration on this. To that
> effect, I have suggested that the code be moved to a new OpenStack project
> named "openstack/ironic-python-agent". This would follow an independent
> release cycle, and reuse some components of tripleo (os-*-config). To keep
> the collaborative momentup up, I would like this work to be done now (after
> all, it's not part of the Ironic repo or release). The new driver which
> will interface with that agent will need to stay on github -- or in a
> gerrit feature branch -- until Juno opens, at which point it should be
> proposed to Ironic.
> The agent architecture we discussed is roughly:
> - a pluggable JSON transport layer by which the Ironic driver will pass
> information to the ramdisk. Their initial implementation is a REST API.
> - a collection of hardware-specific utilities (python modules, bash
> scripts, what ever) which take JSON as input and perform specific actions
> (whether gathering data about the hardware or applying changes to it).
> - and an agent which routes the incoming JSON to the appropriate utility,
> and routes the response back via the transport layer.
> -Devananda
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140307/68f40ae8/attachment.html>

More information about the OpenStack-dev mailing list