Ansible roles and playbooks to enable a standalone Ironic install
660038ac57
This version introduced the network_data.json file, and is supported by cloud-init 0.7.9. Cloud-init 0.7.9 will always prefer a versioned metadata to 'latest', which in this case forces the use of the 2012-08-10 Folsom version, which does not provide network_data.json. Change-Id: I3a604c170e124de3bbbe95f002d14439c138ca3e Closes-Bug: #1742957 |
||
---|---|---|
bifrost | ||
doc/source | ||
playbooks | ||
releasenotes | ||
scripts | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
babel.cfg | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
env-vars | ||
HACKING.rst | ||
LICENSE | ||
MISSION.rst | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Bifrost
Bifrost (pronounced bye-frost) is a set of Ansible playbooks that automates the task of deploying a base image onto a set of known hardware using ironic. It provides modular utility for one-off operating system deployment with as few operational requirements as reasonably possible.
Team and repository tags:
Use Cases
- Installation of ironic in standalone/noauth mode without other OpenStack components.
- Deployment of an operating system to a known pool of hardware as a batch operation.
- Testing and development of ironic in a standalone use case.
Documentation
Bifrost's documentation can be found at the OpenStack documentation site.