[PATCH] [Kimchi] New UI for adding network bridges
by peterpnns＠gmail.com
From: peterpennings <peterpnns(a)gmail.com>
This patch adds Linux and OVS bridges. netinfo.py had to be updated to show OVS bridges in order to reflect the changes made in the UI.
peterpennings (1):
Issue #791: New UI for adding network bridges
netinfo.py | 3 +-
ui/js/src/kimchi.network.js | 2 +
ui/js/src/kimchi.network_add_main.js | 146 ++++++++++++++++++++++-------------
ui/pages/network-add.html.tmpl | 3 +-
4 files changed, 96 insertions(+), 58 deletions(-)
--
2.5.0
8 years, 10 months
[RFC][Kimchi] Guest Max memory setup and update
by Rodrigo Trujillo
Hi all,
The guest xml tag <max_memory> is necessary to allow memory hotplug.
Currently, max_memory is the lesser value among "guest memory X4",
"Host Memory" or "1TB". It is also not possible to user, to set it.
Proposal: Modify backend and frontend in order to allow users to
increase/decrease max_memory value. In other words, user will be allowed
to set the amount of memory that will be possible to hotplug.
BACKEND (a previous patch was already sent to mailing list, must sent
new version)
- Remove current settings when guest is created. Set max_memory equal
guest memory.;
- Does not allow change max_memory when guest is running;
- When hotplug, continue with slots of 1GB, but restrict 32 slots in
PowerPC;
- Update/Add tests;
- Change JSON memory field to: memory: { current: XXX, maxmemory: YYYY };
FRONTEND
- In guest edit window, modify memory input field. Change it to a
increase/decrease ( +/- ) input box;
- Create a hidden area which will hold max memory input box
(increase/decrease);
- Increments will be of 1GB;
- Create a "More Options" link besides Memory , that is going to
show/hide max memory area;
- If guest is online:
* max memory field will be disabled;
* memory will be enabled, allowing hotplug;
- When guest is offline, it is ok to change max memory, enable it;
API CHANGES:
JSON must be changed in requests and responses:
- When updating guest (PUT), memory field will become:
memory: { current: <memory new value>, maxmemory:
<maxmemory new value> }
- response (GET):
memory: { current: <memory new value>, maxmemory:
<maxmemory new value> }
It is not necessary to include maxmemory if was not changed.
Thoughts ?
Rodrigo Trujillo
8 years, 10 months
[PATCH] [WoK 0/2] Makefile changes - whitespace check and others
by dhbarboza82＠gmail.com
From: Daniel Henrique Barboza <dhbarboza82(a)gmail.com>
This patch set implements enhancements in the Makefile.am
of WoK, including whitespace checks and fixes for the
existing whitespaces.
Daniel Henrique Barboza (2):
Makefile.am targets enhancements
Whitespace fixes in existing code
Makefile.am | 26 ++++++++++++++++++--------
configure.ac | 1 +
ui/css/src/modules/_login.scss | 4 ++--
ui/css/src/modules/_modal-flat.scss | 10 +++++-----
ui/css/src/modules/_navbar-flat.scss | 6 +++---
ui/css/src/modules/_wok-confirm.scss | 4 ++--
ui/css/src/modules/_wok-grid.scss | 6 +++---
ui/css/src/modules/_wok-variables.scss | 6 +++---
ui/images/theme-default/edit-alt.svg | 4 ++--
ui/js/src/wok.grid.js | 4 ++--
ui/js/src/wok.line-chart.js | 10 +++++-----
ui/js/src/wok.list.js | 6 +++---
ui/js/src/wok.login.js | 6 +++---
ui/js/src/wok.main.js | 6 +++---
14 files changed, 55 insertions(+), 44 deletions(-)
--
2.5.0
8 years, 10 months
