applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
It is now possible to select a firewall rule on the GUI
and copy it as template for the new rule.
---
www/manager6/grid/FirewallRules.js | 35 ++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/www/manager6/grid/FirewallRules.js
b/www/manager6/grid/F
---
Note: this is of course up for discussion, especially the part
about text styles. I'd like to collect additional input and
feedback before finalizing this, and then do a cleanup over
the existing docs - at least for section headers and text styles.
README.adoc | 165 ++
Hi,
Thanks for your response.
I was looking for a way to increase number of nodes for proxmox ve (A qemu-kvm
virtulization platform which use a lot corosync of all services)
I wasn't aware of pacemaker-remote, I'll try to have a look at it.
I'll try to keep you in touch with our progress on im
I would not change the order when displaying the list. Just select
the default ...
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
This allows the setting of node priorities in HA groups.
Use a grid panel like in the dc.BackupEdit window with an widget
column which adds a number field per row to set and edit the nodes
priority.
Also fixes the bug where the priorities of an existing group (e.g.
set through the CLI) where dele
Add the getNodes function to the periodically asynchronous updated
PVEResource store. This allows a component to get the node data
directly, without making an API call and waiting that it's finished,
the data is also up to date.
A usage example would be:
var data = PVE.data.ResourceStore.getNodes
