Bareon-based driver for Ironic

Go to file

Doug Szumski 65f5f65984 Support stable/mitaka Add support for stable/mitaka including new patches for ironic and nova. Change-Id: Ie566dd22aaddc30858438a98767ef962182e97d9		2016-11-23 16:14:31 +00:00
bareon_ironic	Support stable/mitaka	2016-11-23 16:14:31 +00:00
doc/source	Change the way we use sphinx(autodocs)	2016-11-23 17:09:06 +02:00
etc/ironic	Initial commit	2016-04-15 11:36:28 +03:00
patches	Support stable/mitaka	2016-11-23 16:14:31 +00:00
.gitreview	Added .gitreview	2016-03-01 08:52:43 +00:00
.testr.conf	Change the way we use sphinx(autodocs)	2016-11-23 17:09:06 +02:00
LICENSE	Initial commit	2016-04-15 11:36:28 +03:00
README.rst	Initial commit	2016-04-15 11:36:28 +03:00
requirements.txt	Initial commit	2016-04-15 11:36:28 +03:00
setup.cfg	Change the way we use sphinx(autodocs)	2016-11-23 17:09:06 +02:00
setup.py	Initial commit	2016-04-15 11:36:28 +03:00
test-requirements.txt	Change the way we use sphinx(autodocs)	2016-11-23 17:09:06 +02:00
tox.ini	Change the way we use sphinx(autodocs)	2016-11-23 17:09:06 +02:00

README.rst

Bareon-based deployment driver for Ironic

bareon_ironic package adds support for Bareon to OpenStack Ironic. Ironic¹ is baremetal provisioning service with support of multiple hardware types. Ironic architecture is able to work with deploy agents. Deploy agent is a service that does provisioning tasks on the node side. Deploy agent is integrated into bootstrap ramdisk image. bareon_ironic contains pluggable drivers code for Ironic that uses Bareon² as deploy agent. Current implementation requires and tested with Ironic/Nova Stable Kilo release.

Features overview

Flexible deployment configuration

A JSON called deploy_config carries partitions schema, partitioning behavior, images schema, various deployment args. It can be passed through various places like nova VM metadata, image metadata, node metadata etc. Resulting JSON is a result of merge operation, that works basing on the priorities configureed in /etc/ironic/ironic.conf.

LVM support

Configuration JSON allows to define schemas with mixed partitions and logical volumes.

Multiple partitioning behaviors available

Verify. Reads schema from the baremetal hardware and compares with user schema.
Verify+clean. Compares baremetal schema with user schema, wipes particular filesystems basing on the user schema.
Clean. Wipes disk, deploys from scratch.

Multiple image deployment

Configuration JSON allows to define more than 1 image. The Bareon Ironic driver provides handles to switch between deployed images. This allows to perform a baremetal node upgrades with minimal downtime.

Block-level copy & file-level Image deployment

Bareon Ironic driver allows to do both: bare_swift drivers for block-level and bare_rsync drivers for file-level.

Deployment termination

The driver allows to teminate deployment in both silent (wait-callback) and active (deploying) phases.

Post-deployment hooks

Two hook mechanisms available: on_fail_script and deploy actions. The first one is a user-provided shell script which is executed inside the deploy ramdisk if deployment has failed. The latter is a JSON-based, allows to define various actions with associated resources and run them after the deployment has passed.

Building HTML docs

$ pip install sphinx $ cd bareon-ironic/doc && make html