e0a5a7216d There's very little difference in the package lists. I'm just guessing there, but I believe g++ and xml2/xslt devel packages are for working with libvirt, and the python3-selinux either comes pre-installed or is installed at some earlier point by other playbooks. Change-Id: I5865c65cae695491524a8828c8abb48393a197a0 |
|
|
---|---|---|
bifrost |
|
|
doc |
|
|
playbooks |
|
|
releasenotes |
|
|
scripts |
|
|
tools |
|
|
zuul.d |
|
|
.ansible-lint |
|
|
.gitignore |
|
|
.gitreview |
|
|
.mailmap |
|
|
.stestr.conf |
|
|
CONTRIBUTING.rst |
|
|
HACKING.rst |
|
|
LICENSE |
|
|
README.rst |
|
|
ansible-collections-requirements.yml |
|
|
bifrost-cli |
|
|
bindep.txt |
|
|
requirements.txt |
|
|
setup.cfg |
|
|
setup.py |
|
|
test-requirements.txt |
|
|
tox.ini |
|
README.rst
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.
The mission of bifrost is to provide an easy path to deploy ironic in a stand-alone fashion, in order to help facilitate the deployment of infrastructure, while also being a configurable project that can consume other OpenStack components to allow users to easily customize the environment to fit their needs, and drive forward the stand-alone perspective.
Use cases include:
- 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 the standalone mode.
Useful Links
- Bifrost's documentation can be found at:
- Release notes are at:
- The project source code repository is located at:
- Bugs can be filed in launchpad: