tenks/ansible/roles/virtualbmc-domain
Mark Goddard 7ad354c2af Use node state rather than 'cmd'
There are two cases when we may want to delete things:

1. if a desired node configuration or spec changes, we delete existing node
   resources.
2. if we use the teardown.yml playbook, cmd == teardown, delete
   everything, including global state.

In both cases, Tenks state (state.yml), all nodes to be deleted are given a
'state' of absent'. We should therefore use this rather than the 'cmd' variable
which only works in the latter case.

Change-Id: Icc033340c7fd882e61d90e3d086f7ba4a5b673bf
Story: 2004907
Task: 29257
2019-01-31 14:59:47 +00:00
..
2019-01-31 14:59:47 +00:00

Virtual BMC Domain

This role configures a Libvirt domain in Virtual BMC. If vbmc_state is present, it will ensure the domain is added and started; if vbmc_state is absent, it will ensure the domain is stopped and deleted.

Requirements

  • Virtual BMC installed in a virtualenv
  • Virtual BMC daemon running

Role Variables

  • vbmc_domain: The name of the Libvirt domain to be added to Virtual BMC.
  • vbmc_virtualenv_path: The path to the virtualenv in which Virtual BMC is installed.
  • vbmc_ipmi_address: The address on which Virtual BMC will listen for IPMI traffic.
  • vbmc_ipmi_port: The port on which Virtual BMC will listen for IPMI traffic.
  • vbmc_ipmi_username: The IPMI username that Virtual BMC will use.
  • vbmc_ipmi_password: The IPMI password that Virtual BMC will use.
  • vbmc_log_directory: The directory in which to store Virtual BMC logs. If not overridden from None, output will not be logged to a file.
  • vbmc_state: Whether the domain should be present or absent in Virtual BMC. Defaults to present.