d528728090
This patch is adding a new cleaning step called "erase_devices_metadata" to the GenericHardwareManager. This step is responsible for erasing the metadata of the disks present in the node (partition tables, signatures, filesystem identifiers etc...). It's important to note that the "erase_devices" cleaning step will also remove all these metadatas (because it will zero/shred the whole disk) but, it takes a lot of time to run and for some usages of Ironic only cleaning the device metadata and leaving the data from previous tenants on the disk after the machine is recycled is fine. That's the use case for systems using Ironic just to install the same base image onto many nodes which will run another cloud on top afterwards (TripleO). The new cleaning step has a default priority of 99, so it should run before the "erase_devices" cleaning step so that we can guarantee that the metadata was removed even in case of a failure when cleaning the disks. The version of the GenericHardwareManager was bumped to "1.1" with the addition of this new clean step. This patch make use of the "destroy_disk_metadata" method from ironic-lib to get rid of the metadata. Closes-Bug: #1603411 Change-Id: I3d7b39d5ee3e03ce63185e4168b1ac954a896c93
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.