You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
||5 months ago|
|bifrost||7 months ago|
|doc||6 months ago|
|playbooks||5 months ago|
|releasenotes||6 months ago|
|scripts||5 months ago|
|tools||1 year ago|
|zuul.d||5 months ago|
|.ansible-lint||2 years ago|
|.gitignore||1 year ago|
|.gitreview||4 years ago|
|.mailmap||3 years ago|
|.stestr.conf||3 years ago|
|CONTRIBUTING.rst||2 years ago|
|HACKING.rst||6 years ago|
|LICENSE||8 years ago|
|README.rst||2 years ago|
|ansible-collections-requirements.yml||9 months ago|
|bifrost-cli||2 years ago|
|bindep.txt||5 months ago|
|requirements.txt||5 months ago|
|setup.cfg||10 months ago|
|setup.py||3 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||9 months ago|
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 infrastucture, 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.
- Bifrost's documentation can be found at:
- Release notes are at:
- The project source code repository is located at:
- Bugs can be filed in storyboard: