Mark Goddard 507228a228 Support storage of introspection data in Nginx
As an operator I want to be able to persist raw and processed
introspection data so that I am able to view it at a later date.

As an operator I want to be able to persist raw and processed
introspection data so that I am able to reprocess the data after the
initial inspection process has completed.

In the absence of swift, we can use the bifrost nginx web server -
masquerading as an object store - to store raw and processed
introspection data for nodes.

This allows introspection data to be retrieved and reprocessed after the
initial inspection has completed. This can be useful when the processing
pipeline or introspection rules are changed.

Change-Id: Ia2bd16080594e854054f380d4f7670eaea98e82b
Closes-Bug: #1685879
2018-02-27 14:56:43 +00:00
2018-02-13 12:35:41 +00:00
2018-02-13 09:44:31 +00:00
2017-08-03 10:07:01 +08:00
2015-05-25 13:52:46 +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.

Description
Ansible roles and playbooks to enable a standalone Ironic install
Readme 27 MiB
Languages
Python 55.3%
Jinja 27.1%
Shell 17.6%