6de3cfdc08
VMOTION-ABORT is sent by the source host. It does not require any specific response or action, but we currently fail to recognize it, which causes the _source_ vSPC connection to be terminated, and that seems undesirable as the source should be fine -- it is the _destination_ which has failed and is expected to disconnect. This change handles it with a debug log message, but the side effect of handling it is that the connection is no longer terminated. Also fix the direction indicator for the debug message for VMOTION-PEER-OK. Change-Id: Id09ed363d6713c023323235a60d4c678c65079f1
vmware-vspc
Virtual Serial Port Concentrator for use in the vSphere environment. It collects serial console logs from VMs which have configured virtual serial port pointing to it.
Usage with OpenStack
Copy vspc.conf.sample as vspc.conf and edit
as appropriate:
[DEFAULT]
debug = True
host = 0.0.0.0
port = 13370
cert = cert.pem
key = key.pem
uri = vmware-vspc
serial_log_dir = /opt/vmware/vspcThen start with:
$ vmware-vspc --config-file vspc.confIn nova.conf add the following properties:
[vmware]
serial_port_service_uri = vmware-vspc
serial_port_proxy_uri = telnets://<vspc_host>:13370#thumbprint=<vspc_thumbprint>where vspc_host is the host where VSPC runs and
vspc_thumbprint is the SHA1 thumbprint of the configured
certificate.
Usage with Devstack
There is a devstack plugin, so simply add this to your
local.conf:
[[local|localrc]]
enable_plugin vmware-vspc https://github.com/openstack/vmware-vspc