- 06 Sep, 2015 2 commits
-
-
Dietmar Maurer authored
so that we can change times in future
-
Wolfgang Link authored
this is important to avoid that all PVE nodes start the update procedure at the same time
-
- 05 Sep, 2015 1 commit
-
-
Dietmar Maurer authored
-
- 04 Sep, 2015 8 commits
-
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
- 03 Sep, 2015 2 commits
-
-
Thomas Lamprecht authored
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>
-
Emmanuel Kasper authored
This allows the Backup to work with ExtJS5
-
- 02 Sep, 2015 1 commit
-
-
Dietmar Maurer authored
-
- 31 Aug, 2015 3 commits
-
-
Dietmar Maurer authored
-
Alexandre Derumier authored
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
-
Thomas Lamprecht authored
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>
-
- 29 Aug, 2015 2 commits
-
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
- 28 Aug, 2015 3 commits
-
-
Dietmar Maurer authored
-
Alexandre Derumier authored
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
-
Alexandre Derumier authored
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
-
- 26 Aug, 2015 3 commits
-
-
Wolfgang Link authored
this is necessary because we use image files for both.
-
Emmanuel Kasper authored
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.
-
Emmanuel Kasper authored
We already did this for ExtJS4, just copying from there
-
- 25 Aug, 2015 2 commits
-
-
Wolfgang Link authored
-
Dietmar Maurer authored
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.
-
- 24 Aug, 2015 1 commit
-
-
Dietmar Maurer authored
-
- 20 Aug, 2015 2 commits
-
-
Dietmar Maurer authored
-
Dietmar Maurer authored
-
- 18 Aug, 2015 6 commits
-
-
Dietmar Maurer authored
-
Emmanuel Kasper authored
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.
-
Emmanuel Kasper authored
-
Emmanuel Kasper authored
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.
-
Emmanuel Kasper authored
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.
-
Dietmar Maurer authored
-
- 17 Aug, 2015 3 commits
-
-
Dietmar Maurer authored
-
Wolfgang Link authored
-
Wolfgang Link authored
in the pvesm and pvesh we are giving the correct size of the used space from a disk. this change make the output of Gui and CLI consistent.
-
- 12 Aug, 2015 1 commit
-
-
Wolfgang Bumiller authored
Fixes #681
-