core-admin/qubes/tests
Marek Marczykowski-Górecki 52c3753d61
storage: support asynchronous storage pool implementations
Allow specific pool implementation to provide asynchronous
implementation. vm.storage.* methods will detect if given implementation
is synchronous or asynchronous and will act accordingly.
Then it's up to pool implementation how asynchronous should be achieved.
Do not force it using threads (`run_in_executor()`). But pool
implementation is free to use threads, if consider it safe in a
particular case.

This commit does not touch any pool implementation - all of them are
still synchronous.

QubesOS/qubes-issues#2256
2017-05-12 17:04:18 +02:00
..
integ Remove WrongAssignment exception 2017-04-15 23:49:39 +02:00
tools tests: tools.qubesd 2017-05-12 14:25:29 +02:00
vm Fix tests broken by the new assignment api 2017-04-15 23:48:59 +02:00
__init__.py tests: tools.qubesd 2017-05-12 14:25:29 +02:00
app.py qubes/events: they accept only keyword arguments 2017-02-21 14:46:42 +01:00
devices.py Make pylint ♥ 2017-04-15 23:50:11 +02:00
events.py events: add support for per-instance handlers 2017-05-12 14:25:32 +02:00
extra.py qubes: port core to python3 2017-01-20 16:42:51 +01:00
firewall.py qubes: port core to python3 2017-01-20 16:42:51 +01:00
init.py qubes/events: they accept only keyword arguments 2017-02-21 14:46:42 +01:00
mgmt.py mgmt: add mgmt.label.Index method 2017-05-12 14:25:29 +02:00
run.py qubes: port core to python3 2017-01-20 16:42:51 +01:00
storage_file.py storage: support asynchronous storage pool implementations 2017-05-12 17:04:18 +02:00
storage_lvm.py qubes: port core to python3 2017-01-20 16:42:51 +01:00
storage.py qubes: port core to python3 2017-01-20 16:42:51 +01:00
tarwriter.py qubes: port core to python3 2017-01-20 16:42:51 +01:00