Ansible roles and playbooks to enable a standalone Ironic install
d81c122b85
Recently released ironic-inspector-client v3.0.0 no longer has a meaningful default for 'inspector_url' argument - its default is None and in this case endpoint resolution from keystone catalog is attempted. This means that in bifrost we should now set explicit endpoint for inspector in ironic's config file for noauth case. Change-Id: I9948a3edc8e297059005bdb4065796c30003ee63 |
||
---|---|---|
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.