5df024e716
This approach was used instead of fetching the latest version number at build time because that meant a CoreOS update could break our gates at any given time. A new CoreOS make target, 'pin_latest', was made available. This target bumps the "pinned" version to the latest. An eventual proposal bot will call this target to ensure we stay up to date. This also offers the possibility for downstream operators that want to build the latest version to call this target before building. This leads to the same result as fetching directly in the python build script, but with more flexibility. This is a second attempt to merge this change, as before it caused frequent CI failures/timeouts. The expectation is that with CoreOS only gating on IPA, this would be lower impact and easier to mitigate. Change-Id: I78cb2efff2293b1591b30b7e39df9fc2af98d0b2 Closes-bug: 1581673 Co-Authored-By: Arun S A G <sagarun@gmail.com> Co-Authored-By: Jim Rollenhagen <jim@jimrollenhagen.com>
ironic-python-agent
An agent for controlling and deploying Ironic controlled baremetal nodes.
The ironic-python-agent works with the agent driver in Ironic to provision the node. Starting with ironic-python-agent running on a ramdisk on the unprovisioned node, Ironic makes API calls to ironic-python-agent to provision the machine. This allows for greater control and flexibility of the entire deployment process.
The ironic-python-agent may also be used with the original Ironic pxe drivers as of the Kilo OpenStack release.
Building the IPA deployment ramdisk
For more information see the Image Builder section of the Ironic Python Agent developer guide.
Using IPA with devstack
This is covered in the Deploying Ironic with DevStack section of the Ironic dev-quickstart guide.
Project Resources
Project status, bugs, and blueprints are tracked on Launchpad:
Developer documentation can be found here:
Additional resources are linked from the project wiki page:
- IRC channel:
-
#openstack-ironic
To contribute, start here: Openstack: How to contribute.