Bifrost presently only supports ipmi and ssh based drivers

[Julia Kreger]

Presently Bifrost requires explicit logic to support drivers utilizing technologies other than ipmi and ssh for control of machines. This is an artifact of the initial proof of concept, and requires additional abstraction and changes to support other technologies such as AMT.

[Julia Kreger (juliaashleykreger)]

I'm presently working on a new inventory data source that does not utilize the original CSV file format, which should also allow for easy extension. This will also require revamping and streamlining the playbook role code, but ultimately that will be a natural progression.

[Julia Kreger (juliaashleykreger)]

I have proposed some changes which should make supporting drivers aside ipmi and ssh easier.

Example inventory data source:
https://review.openstack.org/#/c/184084/

Example enrollment:
https://review.openstack.org/#/c/188176/

Changes along these lines would allow for the roles to be generic with minimal or no logic for the differing deployment types, which ultimately means the bulk of the work becomes the requirements for the conductor.

[Julia Kreger (juliaashleykreger)]

pxe_amt support: https://review.openstack.org/#/c/191109/
agent_ilo support: https://review.openstack.org/#/c/191218/

[Julia Kreger (juliaashleykreger)]

agent_ucs: https://review.openstack.org/191219

All proposed driver additions have landed in bifrost's configuration template. Marking committed.