OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 day ago|
|bareon_ironic||1 year ago|
|doc/source||2 years ago|
|etc/ironic||2 years ago|
|patches||2 years ago|
|.gitignore||2 years ago|
|.gitreview||1 day ago|
|.testr.conf||2 years ago|
|LICENSE||3 years ago|
|README.rst||3 years ago|
|requirements.txt||2 years ago|
|setup.cfg||2 years ago|
|setup.py||3 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||1 year ago|
bareon_ironic package adds support for Bareon to OpenStack Ironic. Ironic1 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 Bareon2 as deploy agent. Current implementation requires and tested with Ironic/Nova Stable Kilo release.
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
Configuration JSON allows to define schemas with mixed partitions and logical volumes.
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.
Bareon Ironic driver allows to do both: bare_swift drivers for block-level and bare_rsync drivers for file-level.
The driver allows to teminate deployment in both silent (wait-callback) and active (deploying) phases.
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.
$ pip install sphinx $ cd bareon-ironic/doc && make html