Current Series Release Notes

3.2.0

Upgrade Notes

  • Support for Python 3.8 has been removed. Now the minimum python version supported is 3.9 .

3.0.0

Upgrade Notes

  • Virtualbmc does not support Python 3.6 and 3.7 anymore, please use version 3.8 or higher.

Security Issues

  • Secure information in the Libvirt domain XML document is now preserved. For more information, please see story 2010382.

Bug Fixes

  • Fixes an issue where secure fields were accidentally lost in the Libvirt domain XML document.

2.0.0

New Features

  • Added error status to vbmc list and vbmc start commands output. If the instance is failing to start, such instance will be shown as error rather than being down.

Upgrade Notes

  • Python 2.7 support has been dropped. Last release of virtualbmc to support Python 2.7 is OpenStack Train. The minimum version of Python now supported by virtualbmc is Python 3.6.

  • Removes the backward compatibility feature of vbmc to automatically start up vbmcd daemon process if it is not running. From now on, vbmcd should be started by systemd or some other mechanism.

Bug Fixes

  • Properly closes standard I/O streams to prevent shell-piped processes from hanging infinitely on a dead pipe.

1.6.0

New Features

  • Adds the ability to override default configuration file location by exporting the $VIRTUALBMC_CONFIG variable, pointing to the desired config file, into vbmcd and vbmc processes environment.

1.5.0

Bug Fixes

  • Ignores instance “start” command if instance appears to be running. This helps preserving backward-compatible behaviour, as previous implementation has required the user to explicitly “start” enabled instances. With current virtualbmc, only the master process needs to be started.

1.4.0

New Features

  • Changes the design of the VirtualBMC tool. Instead of forking the vbmc command-line tool to become a daemon and serve a single libvirt domain, the vbmcd master process and vbmc command-line client have been introduced. These client-server tools communicate over the ZeroMQ queue. The vbmcd process is responsible for herding its children, each child still serves a single libvirt domain.

  • The vbmc start command now supports multiple domains.

Upgrade Notes

  • It is advised to invoke vbmcd master process on system boot, perhaps by a systemd unit file.

Deprecation Notes

  • Deprecates automatically starting up the vbmcd daemon process if it is not running. This backward-compatibility feature will be removed in the OpenStack Stein release.

Security Issues

  • Hardens PID file creation to prevent the symlink attack.