this changes the ha status view and ha resources view, so that they take
an rstore and use that instead of a new one
we do this, so that we can display the status and the resources grid
with one api call
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Add the new stopped state to the ResourceEdit panel.
Rename enabled state to started as done in ha-manager.
As 'enabled' is now the wrong label use the more correct label
'Request state', for both the resource edit window and the grid
column.
Do this by replacing the checkbox with a KVCombogrid.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
As we cannot migrate to the source node do not show it in the
migration window's node selector.
Fixes#1049 partly
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
when forwarding an API request to the responsible node,
only accept the certificate that this node should have
according to the contents of the cluster file system.
to limit performance issues, cache certificate fingerprint
on first request for each node, and only regenerate cache
(at most once per minute) if the actual encountered
fingerprint does not match or every 30 minutes (to clear out
old entries).
to save the columns/layouts in the browsers local storage
also change width to string (or else jslint complains)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
since we now have the client settings, we do not need this anymore
also rename the stateid to 'grid-resource'
(we want to establish a convention to differentiate between saved local
storage items)
the whole saveCurrentState logic was not really necessary, so we can drop this too
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
since we get the string "0" from the backend if the line is in the
groups.cfg, we have to set the field to type boolean, or the string will
always be interpreted as true
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
insideUpdate protects for a endless loop which gets caused if the sm
selection change callback updates vmidField which then triggers the
vmidField change callback which updates the selection model again,
and the circle starts again.
As this construct is rather confusing when looking first at the code
replace it with a temporary suspend of the change event during the
vmidField update.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This patch adds curves to use with TLS_ECDHE_* ciphers
They will automatically be used be the proxy as they are
in the HIGH ciphersuite.
This patch uses the prime256v1 curve, which should be supported
by most clients. openssl 1.0.1 only supports a single curve.
This also forces the use of new DHE and ECDHE keys on every
handshake. This does not seem to have an impact on performance.
Signed-Off-By: Jos Ewert flami@flami.net
this adds a subclass of Ext.form.field.Number with the settings for
Integers (allowDecimals: false and allowExponential: false and default
step size 1)
and use it where we only accept integers
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this patch moves the onlineHelp ids into the javascript classes, instead
of defining them where we use the classes
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
also the correct value for haGroupSelector is [] not '',
with this, the reset button works correctly
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
The 'max_reloacte' and 'max_restart' properties can be set via CLI
and API for about a year, expose them to the user alsow via web
interface
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
values['delete'] is always empty here, plus the code was buggy for
the case that it wasn't:
values['delete'] = values['delete'] ? ',group' : 'group';
^^^
always overwrites values['delete'], even if not empty
So just drop it here.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
