VirtualBMC Setup on the KVM Host
Install the python2-virtualbmc on the hypervisor (KVM Host)
NOTE: Please note these commands are to be run on the KVM Host
yum list installed | grep -i virtual
python2-virtualbmc.noarch 1.0.0-0.20170619104029.38502c1.el7.centos
python2-virtualbmc-tests.noarch 1.0.0-0.20170619104029.38502c1.el7.centos
Please note that the python2-virtualbmc comes from the RDO Tripleo Repos. I had installed these repos as well as activated the pike tripleo-repos using
Install the RDO Tripleo
yum -y install https://trunk.rdoproject.org/centos7/current/python2-tripleo-repos-0.0.1-0.20180319163358.8961edc.el7.centos.noarch.rpm
Enable the TripleO repositories
tripleo-repos enable -n pike current ceph
--
Create the VirtualBMC
Clean if there are any previous Virtual BMCs for the overcloud VirtualMachines.
for U in {1..9}
do
vbmc stop overcloud-node$U
vbmc delete overcloud-node$U
done
Create the VirtualBMC instances for the Virtual Machines
The username and the passwords given here will have the authorization to use the VirtualBMC on the KVM Host
for U in {1..9}
do
vbmc add overcloud-node$U --port 623$U --username stack --password 'XXXXXXXXX'
done
Start the VirtualBMC instances on the KVM host
for vbmc in overcloud-node{1..9}
do
vbmc start $vbmc
vbmc list
done
--
Enable the VirtualBMC ports in the firewall of the KVM host to allow connections from the undercloud to the VirtualBMC ports
The KVM host may have firewalld running. If so add the above UDP ports in the firewalld allow list and reload the firewalld configuration after the ports are added permanently
for port in {1..9}
do
firewall-cmd --permanent --add-port=623$U/udp
firewall-cmd --reload
done
Confirm that the VirtualBMCs are up and that the UDP ports are up on the KVM Host.
vbmc list
vbmc list
+-----------------+---------+---------+------+
| Domain name | Status | Address | Port |
+-----------------+---------+---------+------+
| overcloud-node1 | running | :: | 6231 |
| overcloud-node2 | running | :: | 6232 |
| overcloud-node3 | running | :: | 6233 |
| overcloud-node4 | running | :: | 6234 |
| overcloud-node5 | running | :: | 6235 |
| overcloud-node6 | running | :: | 6236 |
| overcloud-node7 | running | :: | 6237 |
| overcloud-node8 | running | :: | 6238 |
| overcloud-node9 | running | :: | 6239 |
+-----------------+---------+---------+------+
As soon as the VirtualBMC is up, the above UDP ports start listening on the KVM Hypervisor. The same can be checked using
netstat -ul | grep 623
(on the KVM Host)
netstat -ul |grep 623
udp6 0 0 [::]:6231 [::]:*
udp6 0 0 [::]:6232 [::]:*
udp6 0 0 [::]:6233 [::]:*
udp6 0 0 [::]:6234 [::]:*
udp6 0 0 [::]:6235 [::]:*
udp6 0 0 [::]:6236 [::]:*
udp6 0 0 [::]:6237 [::]:*
udp6 0 0 [::]:6238 [::]:*
udp6 0 0 [::]:6239 [::]:*
--
Test if the virtual BMC works
from the tripleo undercloud server issue the commands to test if the user can reset the virtual machine on the hypervisor
ipmitool -I lanplus -U stack -P XXXXXXXXX -H 172.16.0.1 -p 6231 power on
Please note that the IP address 172.16.0.1 is the 'nat' Virtual network's bridge 'virbrX' IP on the KVM Host
No comments:
Post a Comment