[PATCH v3 0/2] UI - Column Resizing Function Broken in Host Tab
by Hongliang Wang
1) Fixed column resizing bug.
2) Added repository grid column CSS width values.
v2 -> v3:
2) Corrected indent
(Aline's comment)
v1 -> v2:
2a) Added license header back
(Aline's comment)
Hongliang Wang (2):
Issue#364: UI - Column Resizing Function Broken in Host Tab
Host Tab: Add Widths for Repository Grid Columns
ui/css/theme-default/host.css | 12 +
ui/js/src/kimchi.grid.js | 606 +++++++++++++++++++++++-------------------
2 files changed, 346 insertions(+), 272 deletions(-)
--
1.8.1.4
10 years, 11 months
[PATCH v5 0/4] Github #329: Kimchi must not run as root
by Daniel Barboza
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
New in v5:
- fixes to VNC connection
- fixes to unit tests
- obscuring kimchid port by making it localhost only
- launhing nginx proxy in unit tests
New in v4:
- added a new module with all nginx-related methods
- added DEBIAN entries
- other fixes proposed by Aline
After reading the comments from Zhou Zheng Sheng, I simplified
the work I did in version 2 to run only one cherrypy process
instead of two processes, one for frontend and another for the
backend. Nginx is still being used as a reverse proxy to allow
kimchid to run as root, but not being exposed to the outside.
As Zhou mentioned, it is to little avail to run frontend and
backend separately if the exposed port is running by the
reverse proxy anyway. He mentioned the RPC approach as a best
long-term approach, which I agree. We can solve this issue right
now and the work in a more suitable solution, such as RPC, and
then ditch nginx.
Daniel Henrique Barboza (4):
Github #329: Proxy module and template file
Github #329: Kimchid, config.py.in and server.py changes
Github #329: changes in mockmodel, model/config and tests
Github #329: .gitignore, spec, control.in and readme
.gitignore | 1 +
contrib/DEBIAN/control.in | 3 +-
contrib/kimchi.spec.fedora.in | 2 +
contrib/kimchi.spec.suse.in | 2 +
docs/README.md | 4 +-
src/Makefile.am | 3 +-
src/kimchi/config.py.in | 6 ++-
src/kimchi/mockmodel.py | 2 +-
src/kimchi/model/config.py | 2 +-
src/kimchi/proxy.py | 88 +++++++++++++++++++++++++++++++++++++++++++
src/kimchi/server.py | 15 +++++++-
src/kimchid.in | 50 ++++++++++++++++++------
src/nginx.conf.in | 55 +++++++++++++++++++++++++++
tests/test_rest.py | 8 ++--
tests/utils.py | 16 ++++++--
15 files changed, 229 insertions(+), 28 deletions(-)
create mode 100644 src/kimchi/proxy.py
create mode 100644 src/nginx.conf.in
--
1.8.3.1
10 years, 11 months
libvirt reports "Broken pipe"
by Sheldon
anyone encounter this problem?
$ sudo PYTHONPATH=src ./src/kimchid --host "0.0.0.0" --port 8000
Loading YumUpdate features.
Loaded plugins: langpacks, refresh-packagekit
[16/Apr/2014:13:47:33] ENGINE Bus STARTING
[16/Apr/2014:13:47:33] ENGINE Started monitor thread 'Autoreloader'.
[16/Apr/2014:13:47:33] ENGINE Started monitor thread '_TimeoutMonitor'.
[16/Apr/2014:13:47:33] ENGINE Serving on 0.0.0.0:8001
[16/Apr/2014:13:47:33] ENGINE Serving on 0.0.0.0:8000
*** Running feature tests ***
127.0.0.1 - - [16/Apr/2014:13:47:34] "HEAD /images/icon-fedora.png
HTTP/1.1" 200 4449 "" ""
127.0.0.1 - - [16/Apr/2014:13:47:34] "GET /images/icon-fedora.png
HTTP/1.1" 206 4449 "" ""
127.0.0.1 - - [16/Apr/2014:13:47:34] "HEAD /images/icon-fedora.png
HTTP/1.1" 200 4449 "" ""
WebSocket server settings:
- Listen on :64667
- Flash security policy server
- No SSL/TLS support (no cert file)
- proxying from :64667 to targets in /var/lib/kimchi/vnc-tokens
*** Feature tests completed ***
[16/Apr/2014:13:47:40] ENGINE Bus STARTED
libvirt: XML-RPC error : Cannot write data: Broken pipe
Connection to libvirt broken. Recycling. ecode: 38 edom: 7
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/site-packages/cherrypy/process/plugins.py",
line 475, in run
self.function(*self.args, **self.kwargs)
File "/home/shhfeng/work/workdir/kimchi/src/kimchi/model/vms.py", line
66, in _update_guests_stats
vm_list = self.get_list()
File "/home/shhfeng/work/workdir/kimchi/src/kimchi/model/vms.py", line
221, in get_list
return self.get_vms(self.conn)
File "/home/shhfeng/work/workdir/kimchi/src/kimchi/model/vms.py", line
226, in get_vms
names = [dom.name().decode('utf-8') for dom in conn.listAllDomains(0)]
File
"/home/shhfeng/work/workdir/kimchi/src/kimchi/model/libvirtconnection.py",
line 62, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4038, in
listAllDomains
raise libvirtError("virConnectListAllDomains() failed", conn=self)
libvirtError: Cannot write data: Broken pipe
--
Thanks and best regards!
Sheldon Feng(冯少合)<shaohef(a)linux.vnet.ibm.com>
IBM Linux Technology Center
10 years, 11 months
[PATCH v2 0/2] UI - Column Resizing Function Broken in Host Tab
by Hongliang Wang
1) Fixed column resizing bug.
2) Added repository grid column CSS width values.
v1 -> v2:
2a) Added license header back
(Aline's comment)
Hongliang Wang (2):
Issue#364: UI - Column Resizing Function Broken in Host Tab
Host Tab: Add Widths for Repository Grid Columns
ui/css/theme-default/host.css | 12 +
ui/js/src/kimchi.grid.js | 860 ++++++++++++++++++++++--------------------
2 files changed, 473 insertions(+), 399 deletions(-)
--
1.8.1.4
10 years, 11 months
[PATCH v4 0/3] Github #329: Kimchi must not run as root
by Daniel Barboza
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
Changes from last version:
- added a new module with all nginx-related methods
- added DEBIAN entries
- other fixes proposed by Aline
After reading the comments from Zhou Zheng Sheng, I simplified
the work I did in version 2 to run only one cherrypy process
instead of two processes, one for frontend and another for the
backend. Nginx is still being used as a reverse proxy to allow
kimchid to run as root, but not being exposed to the outside.
As Zhou mentioned, it is to little avail to run frontend and
backend separately if the exposed port is running by the
reverse proxy anyway. He mentioned the RPC approach as a best
long-term approach, which I agree. We can solve this issue right
now and the work in a more suitable solution, such as RPC, and
then ditch nginx.
Daniel Henrique Barboza (3):
Github #329: Proxy module and template file
Github #329: Kimchid, config.py.in and server.py changes
Github #329: .gitignore, spec, control.in and readme
.gitignore | 1 +
contrib/DEBIAN/control.in | 3 +-
contrib/kimchi.spec.fedora.in | 2 ++
contrib/kimchi.spec.suse.in | 2 ++
docs/README.md | 4 +--
src/Makefile.am | 3 +-
src/kimchi/config.py.in | 6 ++--
src/kimchi/proxy.py | 80 +++++++++++++++++++++++++++++++++++++++++++
src/kimchi/server.py | 4 +++
src/kimchid.in | 51 +++++++++++++++++++++------
src/nginx.conf.in | 55 +++++++++++++++++++++++++++++
11 files changed, 195 insertions(+), 16 deletions(-)
create mode 100644 src/kimchi/proxy.py
create mode 100644 src/nginx.conf.in
--
1.8.3.1
10 years, 11 months
[PATCH V3 0/3] VM Edit CPU/Memory
by Rodrigo Trujillo
V3:
- Fix PEP8 issues
V2:
- Rebased with latest Kimchi master
V1:
- This patch set implements backend side of feature "Edit VM CPU/Memory".
You can use curl to test:
curl -X PUT -u <USER> -H 'Content-type: application/json'
-H 'Accept: application/json' http://localhost:8000/vms/<VM_NAME>
-d '{ "cpus": <NUM>, "memory": <NUM>}'
Rodrigo Trujillo (3):
VM Edit CPU/Memory: (Backend) Changes API.md, API.json and i18n.py
VM Edit CPU/Memory: (Backend) Changes VM control and model
VM Edit CPU/Memory: (Backend) Changes mockmodel and tests
docs/API.md | 3 +++
src/kimchi/API.json | 12 ++++++++++++
src/kimchi/control/vms.py | 4 ++--
src/kimchi/i18n.py | 3 ++-
src/kimchi/mockmodel.py | 30 +++++++++++++++++-------------
src/kimchi/model/vms.py | 43 +++++++++++++++++++++++++++----------------
tests/test_mockmodel.py | 5 +++--
tests/test_model.py | 24 +++++++++++++++++++-----
tests/test_rest.py | 32 +++++++++++++++++++++++++++++---
9 files changed, 114 insertions(+), 42 deletions(-)
--
1.8.5.3
10 years, 11 months
[PATCH V4 0/2] config version API support
by shaohef＠linux.vnet.ibm.com
From: ShaoHe Feng <shaohef(a)linux.vnet.ibm.com>
V3 -> V4:
don't differ if the package is installed or not.
V2 -> V3:
add a variable in config.py.in to tell kimchi run in package directory.
V1 -> V2:
use rpm and dpkg to probe that kimchi run in package directory.
ShaoHe Feng (2):
config version API support: add a method to get kimchi version
config version API support in backend.
docs/API.md | 1 +
src/kimchi/Makefile.am | 4 +++-
src/kimchi/config.py.in | 6 ++++++
src/kimchi/mockmodel.py | 3 ++-
src/kimchi/model/config.py | 5 +++--
5 files changed, 15 insertions(+), 4 deletions(-)
--
1.8.5.3
10 years, 11 months
[PATCH v3 0/3] Github #329: Kimchi must not run as root
by Daniel Barboza
From: Daniel Henrique Barboza <danielhb(a)linux.vnet.ibm.com>
After reading the comments from Zhou Zheng Sheng, I simplified
the work I did in version 2 to run only one cherrypy process
instead of two processes, one for frontend and another for the
backend. Nginx is still being used as a reverse proxy to allow
kimchid to run as root, but not being exposed to the outside.
As Zhou mentioned, it is to little avail to run frontend and
backend separately if the exposed port is running by the
reverse proxy anyway. He mentioned the RPC approach as a best
long-term approach, which I agree. We can solve this issue right
now and the work in a more suitable solution, such as RPC, and
then ditch nginx.
Daniel Henrique Barboza (3):
Github #329: kimchid script changes
Github #329: nginx proxy template
Github #329: .gitignore, spec and readme changes
.gitignore | 1 +
contrib/kimchi.spec.fedora.in | 2 +
contrib/kimchi.spec.suse.in | 2 +
docs/README.md | 4 +-
src/kimchid.in | 111 ++++++++++++++++++++++++++++++++++++++----
src/nginx.conf.in | 55 +++++++++++++++++++++
6 files changed, 164 insertions(+), 11 deletions(-)
create mode 100644 src/nginx.conf.in
--
1.8.3.1
10 years, 11 months
[PATCH V3 0/3] config version API support
by shaohef＠linux.vnet.ibm.com
From: ShaoHe Feng <shaohef(a)linux.vnet.ibm.com>
V2 -> V3
add a variable in config.py.in to tell kimchi run in package directory.
V1 -> V2:
use rpm and dpkg to probe that kimchi run in package directory.
ShaoHe Feng (3):
add a method to tell the kimchi is in package directory
config version API support: add a method to get kimchi version
config version API support in backend.
Makefile.am | 3 ++-
docs/API.md | 1 +
src/kimchi/Makefile.am | 11 ++++++++++-
src/kimchi/config.py.in | 10 ++++++++++
src/kimchi/mockmodel.py | 3 ++-
src/kimchi/model/config.py | 5 +++--
6 files changed, 28 insertions(+), 5 deletions(-)
--
1.8.5.3
10 years, 11 months
