cd74a120ce
Previously NAT was required since bridges can't have addresses, and the instackenv.json template was expecting an address on the external bridge to populate pm_addr. If the external network is designated as a bridge, another network must be set to NAT in order for the virthost to be able to access the undercloud, since otherwise there's no address given to the VM. If no such network is defined, the default libvirt network (virbr0) is used. In addition, the requirement to have networks named 'external' and 'overcloud' has been removed. The first bridge network specified in the network list will be used as a pxe network regardless of name. Change-Id: I77f2df7862a71d9a62e4382138bc5287d0687569 |
||
---|---|---|
.. | ||
meta | ||
setup | ||
tasks | ||
teardown | ||
vars | ||
README.md |
Configure libvirt environment
The environment/setup
role will:
- Install libvirt and any dependencies
- Configure and load the
kvm
module (and arch-specifickvm_intel
orkvm_amd
module) - Configure the libvirt networks defined in the
networks
variable - Whitelist the libvirt network bridges in
/etc/qemu/bridge.conf
(or equivalent file)
The environment/teardown
role will:
- Remove whitelist entries from
/etc/qemu/bridge.conf
- Destroy and undefine the libvirt networks
The cleanup
role will not remote packages or attempt to undo the
KVM configuration, because these things may have been configured
prior to running the script and we do not want to break an existing
environment.