IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
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>
this patch fixes that moving your mouse over the top help button or the
settings button, does not change your mouse cursor like on every other
link/button/etc
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this patch adds a custom progressbar widget which changes color,
depending on the value, and adds cpu/memory usage and uptime as columns
to the nodeview
altough those columns are missing in the model/api call, this works , because we
inject the data in our data collectin loop and having the fields not in
the model, causes the store not to overwrite them
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds the panels to the cluster dashboard
to get the values, we add a listener to the PVE.data.ResourceStore
and iterate over all elements, collecting the data
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this patch changes a few things:
* instead of having the nodeview in full size, it is just a panel in
the summary, similar to node/qemu/lxc summary
* creates the store in the summary component, and not in the nodeview,
because we need it later
* makes most of the config options of the nodeview declarative, gets
rid of the initcomponent
* changes the 'online' yes/no to a check/x
* makes the panel resizable with tools
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds a guests panel which will show the running/stopped/etc. guests
in the cluster dashboard
to update this, we have to call updateValues with the data
we do this, because in the component above, we will collect the data
after a load event of the PVE.data.Resources store, to avoid going
through this (sometimes large) list more than once
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds a dc health panel which will be used in the cluster dashboard
it shows the overall cluster status (or simply ok if no cluster defined)
with a symbol and text
then it shows the number of online and offline nodes
optionally it shows then the overall ceph health
of the connected node
if the api call for ceph fails 3 times, we stop it
the ceph status is hidden by default
for updating the cluster and node status, we have to call
updateStatus as a callback from a store which
loads the /api2/json/cluster/status call
we do not have our own store for this, because we will be using the store
which handles this in the component above
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds a gaugeWidget panel, which will be used for the
cluster dashboard
it shows a title, a gauge (a half circle) with the percentage
in the center
over 59% the color is yellow,
over 89% the color is red
also you can add a text to the bottom
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
instead of having a menu with one entry, directly open the my settings
window. also change the icon from a down caret to a gear, to make it
more visible
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds a menu right to the username with an entry 'my settings',
this opens a window with (for now) browser specific settings
and a place to reset them
the plan would be to add password change, 2fa setup etc here
one remark: the reset layout button reloads the window,
to really apply the reset
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this patch adds a checkbox to the login window,
which uses the localstorage to save the username
if one is saved, set the textfield and move focus
to the password field
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
with this patch, vms in an ha error state get an icon (reusing the node
offline icon) to indicate the error
in the resource grid, we also add the icon, and have an additional
column where we can display the ha state
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds a hastate field to all vms/ct which have ha enabled
we will use this for showing the error state in the tree (in the webgui)
and for the cluster dashboard (to count the error state guests)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the error messages for several input fields (e.g. snapshot name)
did not correctly reflect the regex which was checked
this patch adds additional information about the required format
Signed-off-by: Dominik Csapak <d.csapak@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
when we get a max value of 0
(for example when a storage is not active)
the render function would show:
'NaN% (0B of 0B)'
because of a division by 0
this patch simply returns 'N/A' because
a max value of 0 should never be valid
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
