In this bare metal SIG video I'm explaining why ironic-python-agent-builder was created, how to use it and how to cusomise the resulting images.
We've had a very successful meetup about Ironic in Russian. This post is a short summary of what we discussed and what I learned.
If you understand Russian and have 3 hours of free time, you can just follow the recording:
The slides (also in Russian) are here: https://owlet.today/talks/ironic-wallaby-ru/
This post is a follow-up to the earlier deploy steps tutorial, where I showed how to create a deploy step for injecting arbitrary files. I promised to bring that that particular deploy step upstream, and I've delivered on that promise!
This post is talking about a recently (Feb 22, 2021) merged feature. If you don't have a master deployment, you may need to wait until the Wallaby release.
In this tutorial I'm showing how to create a custom deploy step for Ironic, how to build a ramdisk with in and how to use it when deploying a node.
Deploy steps are an answer to question "how do I run non-standard actions during deployment". Out-of-band steps run from your control plane and can talk to the BMC. More interesting for us are in-band steps that run from within the machine and offer nearly infinite opportunity for customization.
Today we'll create a solution for the following story:
As an operator, I would like to inject small files into the root partition of the final instance through the bare metal API.
There are, of course, numerous way of implementing it, cloud-init being probably the most popular. But we will concentrate on using a deploy step. The complete source code for this tutorial can be found here: https://github.com/dtantsur/ironic-inject-files/
I am (slightly) sorry for interrupting technical posts with politics, but, as all responsible adults know, even when you're not interested in politics, politics may get interested in you (insert your favorite "In Soviet Russia" joke).
In this post I'm presenting the ramdisk deploy interface, explaining how to use it to run ephemeral workloads and how to provide configuration data for them.
Ironic has been actively explored by the scientific community as a way to automate running calculations without incurring the costs of virtualization. This sort of workloads does not necessarily require installing anything on the machine's hard drive, which may instead be used for caching, swap or not used at all. The results are posted back via HTTP(s) or stored on a network share.