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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The type parameter is not needed anymore because the service type
can be extracted by only using the unique vmid.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
As the size parameter is now deprecated and was replaced with the
new rootfs parameter, use that one when creating an container.
So we don't get an 'parameter verification failed' error.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
The original fix using a config Object was a bit overkill, this works well too , requires less code in the child classes, and is more consistent with rest of the code we have.
It is currently unclear howto restrict storages for container usage.
The 'rootdir' property does not work anymore, because we can now create
containers on normal VM image files.
Ext.applyIf(me, {
title: gettext('Search')
});
in initComponent() is not safe anymore with ExtJS5.
Since the 'title' property is existing at that stage (even if with a null or undefined value), Ext.applyIf will not update it.
ExtJS refuses with version to have an id set to an empty string, hence we can't
use our "key" property as a custom idProperty (an empty string for key is ok for us, and is used to set back a PVE property to its default value)
We always access the KeyValues entities via their Key property, so this change should be safe.
Since ExtJS5, when doing such a declaration,
Ext.applyIf(me, {
items: {
xtype: 'pveKVComboBox',
comboItems: data,
}
});
the comboItems property is passed in the parent class as a config object,
instead of being directly available via this.comboItems
Since using a config object is the recommended way of passing parameters
int the ExtJS class model, adapt the parent class to use the new paradigm.
It seems that in ExtJS5 the prototype of the Window component already sets
some default values to me.buttons and me.layout, hence calling applyIf
on these properties will silently fail.
me.layout is already set to 'auto' by the framework, we don't need to set
that anymore.
Added a column in the datacenter backup job overview to see if a job
is enabled or not. Added checkbox to the input panel, which enables
or disables a job.
This closes bug/feature request 492.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
getRoot() semantics changed with ExtJS5.
To avoid further annoyances when ExtJS6 is around the corner, replace the call
to this private method, set rootProperty in the ObjectStore call,
and use the value of rootProperty to filter out the content of the server
answer.
This patch does the following:
* remove the EXT5DEBUG header we added previously
* build the items[] array as a one-dimensional array, as PVE.panel.Config
with ExtJS5 is not able to find the elements otherwise
* rename the problematic panel tabs with TODO suffix, to be dealed later on
