On Wed, May 10, 2023 at 01:48:11PM +0200, Fabian Grünbichler wrote:
> On May 10, 2023 10:18 am, Dominik Csapak wrote:
> > @@ -124,6 +130,24 @@ sub updateSchema {
> >
> > next if defined($filter_type) && !defined($copts->{$p});
> >
> > + if ($propertyList->{$p}->{type} eq 'array') {
> > +
On May 10, 2023 10:18 am, Dominik Csapak wrote:
> enables section configs in the style of:
>
>
> type: id
> property value
> property value2
> property value3
>
>
> can be combined with property strings
>
> the provided createSchema just uses the name of the property but th
Am 10.05.23 um 11:57 schrieb Aaron Lauterer:
>
>
> On 5/9/23 16:43, Fiona Ebner wrote:
>> Am 09.05.23 um 14:55 schrieb Aaron Lauterer:
>>>
>>> * Don't scan all storages and only look at disk images that are
>>> referenced in the config. With this, we should have removed most
>>> situations where
On 5/9/23 16:43, Fiona Ebner wrote:
Am 09.05.23 um 14:55 schrieb Aaron Lauterer:
* Don't scan all storages and only look at disk images that are
referenced in the config. With this, we should have removed most
situations where aliases would happen, and a migration is less likely to
fail, bec
--- Begin Message ---
what about adding zfs datasets as a general type of storage?
currently, you need to create a dataset manually and add that as type
"dir" to proxmox, to be able to use file backed instead of zvol backed VMs
that feels ugly.
Am 10.05.23 um 02:08 schrieb Konstantin Filippov:
--- Begin Message ---
Signed-off-by: Konstantin Filippov
---
src/PVE/LXC.pm| 4
src/PVE/LXC/Config.pm | 3 ++-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
index d138161..30cf48d 100644
--- a/src/PVE/LXC.pm
+++ b/src/PVE/LXC.pm
@@ -183
--- Begin Message ---
As we know, ProxMox have only three possible "categories" of mount points:
ProxMox storage provider supplied, block device and bind mount. I've prepared a
little patch for pve-container package which adds a fourth "category" named
"zfs" - so with this patch it's possible to
enables section configs in the style of:
type: id
property value
property value2
property value3
can be combined with property strings
the provided createSchema just uses the name of the property but the
schema of the inner item
the api call is supposed to check if the ove
