Ansible roles and playbooks to enable a standalone Ironic install
a6086eb4b7
After the cut of a bifrost stable branch, it is necessary to modify the default branch used to install dependencies to stable/rocky. We also use the rocky tinyipa ramdisk and kernel image artifacts. Change-Id: I284ea5456e556ddbb7c14900b22e86313138f42e |
||
---|---|---|
bifrost | ||
doc | ||
playbooks | ||
releasenotes | ||
scripts | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
babel.cfg | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
env-vars | ||
HACKING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
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.
- The project source code repository is located at:
- Bugs can be filed in storyboard: