2d286dd7da
Early on in bifrost, we used a static template for a short time. As time evolved, so did the template, and we were able to rely upon the conductor placing the boot.ipxe file upon startup. Ironic since performed the copy upon driver init as opposed to once a deployment has been requested. As it is no longer needed, we shouldn't put an invalid ipxe boot configuration in place. Removing legacy copy. Change-Id: I7f2fc2afca6c8ee0f18efe8aa461bf906794e049 |
||
---|---|---|
bifrost | ||
doc | ||
playbooks | ||
releasenotes | ||
scripts | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MISSION.rst | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
env-vars | ||
lower-constraints.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.
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: