virtualbmc/requirements.txt

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.

pbr!=2.1.0,>=2.0.0 # Apache-2.0
six>=1.10.0 # MIT
libvirt-python!=4.1.0,>=3.7.0 # LGPLv2+
pyghmi>=1.0.22 # Apache-2.0
cliff!=2.9.0,>=2.8.0 # Apache-2.0
pyzmq>=14.3.1  # LGPL+BSD
Restructure the repository according to OpenStack This patch is restructuring the VirtualBMC repository according to the OpenStack template for projects (Cookiecutter). This patch also removes the dependency on the python-daemon library since it is not present in the OpenStack global-requirements, now a new class called "detach_process" has been added to the virtualbmc/utils.py module that will take care of detaching the process context from its parent and session. Change-Id: Id4ae1db5b73a18abc54276fe1dfbf3ceff7adc06 2016-05-05 16:30:17 +01:00			`# The order of packages is significant, because pip processes them in the order`
			`# of appearance. Changing the order has an impact on the overall integration`
			`# process, which may cause wedges in the gate later.`

Updated from global requirements Change-Id: I5e1eddb79afbd81b72696d0991357a4549db551d 2017-05-02 21:23:24 +00:00			`pbr!=2.1.0,>=2.0.0 # Apache-2.0`
Updated from global requirements Change-Id: I085ae8262a4e135d7498db427237b4b0e89928ce 2017-11-16 11:30:56 +00:00			`six>=1.10.0 # MIT`
Bump lower libvirt-python to 3.7 Otherwise it mismatches the libvirt binary on bionic and fails to build. Change-Id: Ic7821d2e9ac764c980db1a2708ee3441855f3830 2019-03-21 11:07:26 +01:00			`libvirt-python!=4.1.0,>=3.7.0 # LGPLv2+`
Updated from global requirements Change-Id: I66a97610051faa090ba099674a5511bed5b9df3a 2017-07-19 18:29:43 +00:00			`pyghmi>=1.0.22 # Apache-2.0`
Updated from global requirements Change-Id: I29a5071b68643914b8e4b1988700e6ec772195a6 2018-03-16 03:55:01 +00:00			`cliff!=2.9.0,>=2.8.0 # Apache-2.0`
multiprocess server, ZMQ-based management cli tool Original design of the VirtualBMC tool was that user manages config files for individual VirtualBMC (via a cli tool), then requests the tool to start the instances representing individual VirtualBMC instances (via the cli tool). Then the instances become independent processes. The only way to know their whereabouts is through the pidfiles they maintain. There were certain practical inconveniences with the original design, namely: * Cumbersome to start/stop/monitor free-standing vBMC instances processes * No two-way communication between the parent process and the VirtualBMC instances what makes child state check or modification unnecessary difficult This commit turns server part of the tool into a single process spawning multiple children processes and herding them via ZMQ client/server. The parent process runs server part of the control interface, maintains persistent VirtualBMC instances configuration and ensures all its children are alive and kicking. Each VirtualBMC instance is still a separate parent fork. If child dies, parent respawns it right away. If parent is about to die, it tries its best to kill all the prospective orphans. This new implementation tries to stay compatible with the original one in part of `vbmc` tool CLI interface and behaviour. Whenever it can't connect to the `vbmcd` it tries to fork and spawn the daemon behind the scenes. While the threading design for this tool might look better, the underlying pyghmi library is apparently rather complicated to use its concurrency capabilities reliably. The other minor consideration is that running multiple processes leverages CPU-based concurrency. Other changes: * The `start` command now accepts more than one domains to be started Change-Id: Ie10f4598c7039a7afa9b45d01df3b3c3db252c1d Story: 1751570 Task: 12057 2017-07-28 12:00:56 +02:00			`pyzmq>=14.3.1 # LGPL+BSD`