Ansible roles and playbooks to enable a standalone Ironic install
4c588187e3
flake8 new release 3.8.0 added new checks and gate pep8 job start failing. hacking 3.0.1 fix the pinning of flake8 to avoid bringing in a new version with new checks. Though it is fixed in latest hacking but 2.0 and 3.0 has cap for flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also break the pep8 job if new check are added. To avoid similar gate break in future, we need to bump the hacking min version. - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html Change-Id: I214fef0669c63ce3476fe872ab2a91b55120cccf |
||
---|---|---|
bifrost | ||
doc | ||
playbooks | ||
releasenotes | ||
scripts | ||
tools | ||
zuul.d | ||
.ansible-lint | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
ansible-collections-requirements.yml | ||
bifrost-cli | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
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: