Mark Goddard cf8ac8216c Enabled hardware type 'ucs' does not exist
During classic driver deprecation [1], the ucs hardware type was added
to the list of default enabled hardware types. This hardware type does
not exist - the Cisco UCS hardware types are cisco-ucs-managed and
cisco-ucs-standalone. This causes conductor to fail to start.

This was not caught during testing as only the ipmi ironic hardware type
is configured when testing. Now that VBMC is in use, it is no
longer necessary to use a different set of drivers for testing.

This change enables the cisco-ucs-managed hardware type by default, and
uses the default set of drivers and hardware types for testing. It also
adds configuration options for setting the enabled boot, power and
management interfaces, with default values including interfaces required
by the ilo and ucs hardware types.

[1]
46453661ba

Change-Id: Icfa89a2555966c6fbfd06186fdd17d852bc5ae7a
Closes-Bug: #1752975
2018-03-03 21:46:34 +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.4%
Jinja 27%
Shell 17.6%