v2 changes:

GUI option for CT protection added

so that we can change times in future

this is important to avoid that all PVE nodes start the update procedure at the same time

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>

This allows the Backup to work with ExtJS5

Signed-off-by: Alexandre Derumier <aderumier@odiso.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>

Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

this is necessary because we use image files for both.

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.

We already did this for ExtJS4, just copying from there

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.