[PATCH v3] [Kimchi] Remove websocket initialization from Kimchi
by dhbarboza82@gmail.com
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
v3:
- changed tearDown() to tearDownModule() in test_mockmodel.py
v2:
- removed websockify references from docs and build files.
*** ATTENTION: REQUIRES '[WoK] Asynchronous UI notification implementation' PATCH ***
Daniel Henrique Barboza (1):
Use Websocket facilities from WoK
contrib/DEBIAN/control.in | 1 -
contrib/kimchi.spec.fedora.in | 1 -
contrib/kimchi.spec.suse.in | 1 -
docs/fedora-deps.md | 2 +-
docs/opensuse-deps.md | 3 +-
docs/ubuntu-deps.md | 2 +-
model/vms.py | 2 +-
root.py | 4 +-
tests/test_mockmodel.py | 2 +-
websocket.py | 121 ------------------------------------------
10 files changed, 6 insertions(+), 133 deletions(-)
delete mode 100644 websocket.py
--
2.9.3
7 years, 9 months
[PATCH] [Kimchi 0/8] Run test_model with regular user
by Lucio Correia
Lucio Correia (8):
Do not hardcode default directories
Always use /var/tmp to store test files
Mock default storage pools and networks for testing
Use "qemu:///session" as test_model libvirt uri
Remove 'run as root' requirement from some tests
Skip tests that need to run as root
Make test_use_test_host architecture independent
Mock user probe functions
model/storagepools.py | 5 +-
osinfo.py | 12 +-
tests/test_model.py | 407 +++++++++++++++++++++++++++++++++++++-------------
3 files changed, 321 insertions(+), 103 deletions(-)
--
2.7.4
7 years, 9 months
[PATCH v4] [WoK] Asynchronous UI notification implementation
by dhbarboza82@gmail.com
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
v4:
- server_loop with the socket listen was daemonized
v3:
- changed listener registration to be message specific instead of generic.
v2:
- Simplified UI code. Using now an array instead of a hashmap
to prevent the need of inserting a listener identifier;
- Changed the push server initialization. Moved it to server.py
to avoid execution in the unit tests, but allow execution in the test
mode. Do the same treatment with the ws_proxy initialization;
- Socket file was moved to /run/user/<user_id>/woknotifications
- Inserted notifications in base model level. Put code in base WoK classes
to allow notifications for every model event without the need of adding
it manually;
- Standardization of messages sent. Messages are being sent in the pattern
METHOD:plugin/entity/action;
- Minor code fixes (imports, remove kimchi references);
- Added websockify as a WoK runtime dependency.
See patch commit message for more information.
Daniel Henrique Barboza (1):
Asynchronous UI notification implementation
contrib/DEBIAN/control.in | 1 +
contrib/wok.spec.fedora.in | 1 +
contrib/wok.spec.suse.in | 1 +
docs/fedora-deps.md | 2 +-
docs/opensuse-deps.md | 3 +-
docs/ubuntu-deps.md | 3 +-
src/wok/config.py.in | 8 ++
src/wok/control/base.py | 16 ++--
src/wok/model/notifications.py | 2 +-
src/wok/pushserver.py | 164 +++++++++++++++++++++++++++++++++++++++++
src/wok/reqlogger.py | 11 ++-
src/wok/root.py | 3 +
src/wok/server.py | 13 +++-
src/wok/websocket.py | 123 +++++++++++++++++++++++++++++++
ui/js/src/wok.main.js | 54 ++++++++++++++
ui/js/wok.user-log.js | 4 +
16 files changed, 395 insertions(+), 14 deletions(-)
create mode 100644 src/wok/pushserver.py
create mode 100644 src/wok/websocket.py
--
2.9.3
7 years, 9 months
[PATCH] [Kimchi] Use Websocket facilities from WoK
by dhbarboza82@gmail.com
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
*** ATTENTION: REQUIRES '[WoK] Asynchronous UI notification implementation' PATCH ***
Daniel Henrique Barboza (1):
Use Websocket facilities from WoK
model/vms.py | 2 +-
root.py | 4 +-
websocket.py | 121 -----------------------------------------------------------
3 files changed, 2 insertions(+), 125 deletions(-)
delete mode 100644 websocket.py
--
2.9.3
7 years, 9 months
[PATCH v2] [Kimchi] Remove websocket initialization from Kimchi
by dhbarboza82@gmail.com
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
v2:
- removed websockify references from docs and build files.
*** ATTENTION: REQUIRES '[WoK] Asynchronous UI notification implementation' PATCH ***
Daniel Henrique Barboza (1):
Use Websocket facilities from WoK
contrib/DEBIAN/control.in | 1 -
contrib/kimchi.spec.fedora.in | 1 -
contrib/kimchi.spec.suse.in | 1 -
docs/fedora-deps.md | 2 +-
docs/opensuse-deps.md | 3 +-
docs/ubuntu-deps.md | 2 +-
model/vms.py | 2 +-
root.py | 4 +-
websocket.py | 121 ------------------------------------------
9 files changed, 5 insertions(+), 132 deletions(-)
delete mode 100644 websocket.py
--
2.9.3
7 years, 9 months
[PATCH v3] [WoK] Asynchronous UI notification implementation
by dhbarboza82@gmail.com
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
v3:
- changed listener registration to be message specific instead of generic.
v2:
- Simplified UI code. Using now an array instead of a hashmap
to prevent the need of inserting a listener identifier;
- Changed the push server initialization. Moved it to server.py
to avoid execution in the unit tests, but allow execution in the test
mode. Do the same treatment with the ws_proxy initialization;
- Socket file was moved to /run/user/<user_id>/woknotifications
- Inserted notifications in base model level. Put code in base WoK classes
to allow notifications for every model event without the need of adding
it manually;
- Standardization of messages sent. Messages are being sent in the pattern
METHOD:plugin/entity/action;
- Minor code fixes (imports, remove kimchi references);
- Added websockify as a WoK runtime dependency.
See patch commit message for more information.
Daniel Henrique Barboza (1):
Asynchronous UI notification implementation
contrib/DEBIAN/control.in | 1 +
contrib/wok.spec.fedora.in | 1 +
contrib/wok.spec.suse.in | 1 +
docs/fedora-deps.md | 2 +-
docs/opensuse-deps.md | 3 +-
docs/ubuntu-deps.md | 3 +-
src/wok/config.py.in | 8 ++
src/wok/control/base.py | 16 ++--
src/wok/model/notifications.py | 2 +-
src/wok/pushserver.py | 163 +++++++++++++++++++++++++++++++++++++++++
src/wok/reqlogger.py | 11 ++-
src/wok/root.py | 3 +
src/wok/server.py | 13 +++-
src/wok/websocket.py | 123 +++++++++++++++++++++++++++++++
ui/js/src/wok.main.js | 54 ++++++++++++++
ui/js/wok.user-log.js | 4 +
16 files changed, 394 insertions(+), 14 deletions(-)
create mode 100644 src/wok/pushserver.py
create mode 100644 src/wok/websocket.py
--
2.9.3
7 years, 9 months
[PATCH v2] [WoK] Asynchronous UI notification implementation
by dhbarboza82@gmail.com
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
v2:
- Simplified UI code. Using now an array instead of a hashmap
to prevent the need of inserting a listener identifier;
- Changed the push server initialization. Moved it to server.py
to avoid execution in the unit tests, but allow execution in the test
mode. Do the same treatment with the ws_proxy initialization;
- Socket file was moved to /run/user/<user_id>/woknotifications
- Inserted notifications in base model level. Put code in base WoK classes
to allow notifications for every model event without the need of adding
it manually;
- Standardization of messages sent. Messages are being sent in the pattern
METHOD:plugin/entity/action;
- Minor code fixes (imports, remove kimchi references);
- Added websockify as a WoK runtime dependency.
See patch commit message for more information.
Daniel Henrique Barboza (1):
Asynchronous UI notification implementation
contrib/DEBIAN/control.in | 1 +
contrib/wok.spec.fedora.in | 1 +
contrib/wok.spec.suse.in | 1 +
docs/fedora-deps.md | 2 +-
docs/opensuse-deps.md | 3 +-
docs/ubuntu-deps.md | 3 +-
src/wok/config.py.in | 8 ++
src/wok/control/base.py | 16 ++--
src/wok/model/notifications.py | 2 +-
src/wok/pushserver.py | 163 +++++++++++++++++++++++++++++++++++++++++
src/wok/reqlogger.py | 11 ++-
src/wok/root.py | 3 +
src/wok/server.py | 13 +++-
src/wok/websocket.py | 123 +++++++++++++++++++++++++++++++
ui/js/src/wok.main.js | 43 +++++++++++
ui/js/wok.user-log.js | 12 +++
16 files changed, 391 insertions(+), 14 deletions(-)
create mode 100644 src/wok/pushserver.py
create mode 100644 src/wok/websocket.py
--
2.9.3
7 years, 9 months
[PATCH v3] [Kimchi 0/4] Bug fix #1091: Allow to set disk performance options per guest and template
by Ramon Medeiros
Changes:
v3:
Add docs
v2:
Use REST API for tests
General fixes
Ramon Medeiros (4):
Read io and cache option from disks
Allow disks to update cache and io flags
Bug fix #1091: Allow to set disk performance options per guest and
template
Add tests to verify if cache and io of a disk can be changed
API.json | 11 ++++++++++-
docs/API.md | 4 ++++
i18n.py | 1 -
model/vmstorages.py | 55 +++++++++++++++++++++++++++++++++++------------------
tests/test_rest.py | 28 +++++++++++++++++++++++++++
xmlutils/disk.py | 23 ++++++++++++++++++++--
6 files changed, 99 insertions(+), 23 deletions(-)
--
2.9.3
7 years, 9 months
[PATCH] [Kimchi 0/3] Bug fix #1091: Allow to set disk performance options per guest and template
by Ramon Medeiros
Changes:
v2:
Use REST API for tests
General fixes
Ramon Medeiros (3):
Allow disks to update cache and io flags
Bug fix #1091: Allow to set disk performance options per guest and
template
Add tests to verify if cache and io of a disk can be changed
API.json | 11 ++++++++++-
docs/API.md | 3 +++
i18n.py | 1 -
model/vmstorages.py | 55 +++++++++++++++++++++++++++++++++++------------------
tests/test_rest.py | 28 +++++++++++++++++++++++++++
xmlutils/disk.py | 12 +++++++++++-
6 files changed, 88 insertions(+), 22 deletions(-)
--
2.9.3
7 years, 9 months