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
The values of 'sequence' and 'secret' are arbitrary byte strings which might
contain IAC (0xff) or SE (0xf0) in any position. Lack of escaping during
transmission might cause receiver confusion and potentially vMotion failures.
This change adds escaping of these 'sequence' and 'secret' values before
transmission. They are already being unescaped correctly during receipt; Only
the transmit side needs to be fixed.
Change-Id: I82384424d684b931805ca921d0597ad7642f66ac
The Nova patch which adds 'serial_log_dir' is still under review but we
want to set it in the devstack plugin. This will enable dowstream
developers to run tempest tests for the console output feature.
Change-Id: I4e70ebe517a28a7e6a1d4e782d21b495fb484523
The VM uuid is sent with some extra characters like dash and spaces.
Strip those characters so log file names will have well defined format.
Change-Id: Ia41b6276851b363cd3b0aaa87d220c4e4425f8e9
This will fix the release job which executes:
$ tox -evenv python setup.py sdist
and currently fails: http://goo.gl/VIC4T8
Change-Id: Ie8f4aabc76c8037ace32b29ae08afe75711e3f7f
Darius Davis