6210189b04
When using pre-deployed servers, you may want all of the networking setup of OVB but don't actually need to control the instances via IPMI. While this could already be done, it left a useless BMC instance lying around. This change allows the BMC to be disabled completely to clean up such environments. Change-Id: Icd6936977684d178277ebb721a7fbb3ffad51d9a
14 lines
700 B
YAML
14 lines
700 B
YAML
# *******************************************************************
|
|
# This file was created automatically by the sample environment
|
|
# generator. Developers should use `tox -e genconfig` to update it.
|
|
# Users are recommended to make changes to a copy of the file instead
|
|
# of the original, if any customizations are needed.
|
|
# *******************************************************************
|
|
# title: Disable BMC
|
|
# description: |
|
|
# Deploy a stack without a BMC. This will obviously make it impossible to
|
|
# control the instances via IPMI. It will also prevent use of
|
|
# ovb-build-nodes-json because there will be no BMC addresses.
|
|
resource_registry:
|
|
OS::OVB::BMC: ../templates/bmc-none.yaml
|