Go to file
Mark Goddard a6086eb4b7 Use the stable/rocky branch for dependencies
After the cut of a bifrost stable branch, it is necessary to modify the
default branch used to install dependencies to stable/rocky. We also
use the rocky tinyipa ramdisk and kernel image artifacts.

Change-Id: I284ea5456e556ddbb7c14900b22e86313138f42e
2018-11-19 13:07:46 +00:00
2018-07-10 16:33:42 +00:00
2018-07-18 15:52:15 +07:00
2017-08-03 10:07:01 +08:00
2018-08-10 21:40:04 +00:00
2015-04-16 15:58:23 -04:00
2017-08-11 11:34:49 +02:00
2017-03-02 23:53:04 +00:00

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:

image

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:

https://git.openstack.org/cgit/openstack/bifrost/

Bugs can be filed in storyboard:

https://storyboard.openstack.org/#!/project/941

Release notes

https://docs.openstack.org/releasenotes/bifrost/

Description
Ansible roles and playbooks to enable a standalone Ironic install
Readme 30 MiB
Languages
Python 58%
Jinja 23.7%
Shell 18.3%