since the value at the top is now directly a string,
we need the jslint confusion at the number and not for the
string at the bottom anymore
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we expect a gettext on a single line and to not contain any
variable/logic, so we remove the long text from it altogether (since we
do not want to translate that at the moment), and we rearrange the code
so that gettext only contains strings
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
This allows to display a 'CT', a 'VM', or a 'CT/VM' label
to be displayed, depending on the context.
Currently when restoring a CT backup or creating a CT via the
wizard, we are asked to enter a *VM* ID, which is confusing.
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>
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>
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>
Disabling a HA resource/service means that this
ressource will always be turned off.
However some users though this disabling HA management
for this VM, see
http://pve.proxmox.com/pipermail/pve-user/2016-October/011024.html
so we had a hint after clicking on the 'disable' checkbox, that
the checkbox is meant for shutdown
