For standalone ironic deployments, such as those deployed using bifrost, there
is typically no keystone or placement service running. Use of the ironic API is
without authentication. We use clouds.yaml in this case.
Change-Id: I61ed791d019e43f6dfc632fa185f079b385c290c
Story: 2004425
Task: 28077
Adds support for pxe_ipmitool, pxe_ipmitool_socat, agent_ipmitool and
agent_ipmitool_socat drivers with virtualbmc. Also adds entries for SNMP-based
drivers.
Change-Id: I461e74e3199e02a35ee0d3ddc1f6e49c1eda0536
You can now use either a name or a UUID for these images. Also, remove
the unnecessary setting of node states, which is now handled by the
scheduling plugin.
Instead of just an allocations file, Tenks now uses a 'state' file. This
contains the node allocations, as well as physical network mappings and
indices. Clusters can also now be re-deployed with different specs to
update the state.
Much of the logic in the existing 'deploy' playbooks could be reused for
a teardown command, so it didn't make sense to duplicate this. Instead,
rename/restructure playbooks such that they refer to an area of
responsibility, rather than an action.
Also, make some changes to allow a new 'teardown' action.
Pass any interface that was specified through to Ironic; otherwise, let
Ironic decide a default for it. Also, pass through any property
key-value pairs we get.
VM types and specifications can't really have sensible defaults since
they depend on the hypervisors' specs. Leave them empty and give format
examples in comments.
Only a single controller would have ever been required, so explicitly
referencing localhost makes more sense.
Also, remove a duplicate 'when' attribute.