The alias stayed the same (store.diff) so we need to change direct
usage of 'PVE.data.DiffStore' only.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
some function are now in Proxmox.Utils instead, so we have to use that
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
most 'Remove' buttons we have used the same code pattern over and over,
with the StdRemoveButton we have a component which does all of this for
us
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
because we will use that in the widget toolkit
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
we gave erroneous entries in grids the class .x-form-invalid-field
but since we changed to the "crisp" theme, this class did not have any
highlighting
so instead we use our own "pve-invalid-row" class
and give it a light red background
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
On the old HA status we saw where a service was located currently,
this information was lost when we merged the resource and the status
tab.
Add this information again.
Signed-off-by: Thomas Lamprecht <t.lamprecht@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.
rename Request State to State, and add the request_state and crm_state
as hidden columns (so that the user can display them if they want)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
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>
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>
Tabpanel reload -> send 'show' event -> reload child panel store
do not work with ExtJS6
but
Tabpanel reload -> reload child panel -> child send 'show' event ->
reload a grid store in the panel still works
so we don't blindly replace the 'show' events everywhere but only
when the event was expected by a direct child of a tabpanel
