Why not use qcow2 format over generic NFS? It will give you shapshot-rollback
features and I don't think that with much worse speed than these features on
ZFS level.
But on my experience, NFS storage for VMs is bad idea: it causes huge latencies
under
load, leading to chashes. If you want ZFS-ba
Don't get me wrong. Of course NFS works fine, but it is a "stupid" file
storage. It would be great to have snapshot/rollback features from the
Proxmox PE gui. The ZFS commands should be executed transparently on the
storage, so that you can have a "virtual" ZFS that can be used in a cluster.
I rea
On Mon, 25 Jul 2016 17:52:58 +0200
Andreas Steinel wrote:
> Hi there,
>
> are there any plans to support ZFS filesystems exported by NFS to be
> managed by Proxmox? I'd be very great to have ZFS-backed storage similar to
> ZFS-over-iSCSI but with file storage instead of block storage.
>
> Is th
Hi,
How is this different from a normal NFS share that Proxmox already
supports using? [1]
ZFS processing would happen on your shared storage NAS server where you
are exporting the NFS share from. All Proxmox sees is an NFS share
located on another machine, and remains ignorant to the specif
Hi there,
are there any plans to support ZFS filesystems exported by NFS to be
managed by Proxmox? I'd be very great to have ZFS-backed storage similar to
ZFS-over-iSCSI but with file storage instead of block storage.
Is this even a wanted feature?
Best,
Andreas
_
The password will be read from /etc/pve/priv/ldap/$realm.pw
---
In contrast to the patches floating around on the forum and bugtracker
this will read the password from /etc/pve/priv/ldap/ which I think
makes more sense for sensitive data.
PVE/Auth/LDAP.pm | 23 +--
1 file chan
---
Note: requires "make download" when applying
...470-KEYS-potential-uninitialized-variable.patch | 94
...synchronization-between-chunk-map_extend_.patch | 162 -
...synchronization-between-synchronous-map-e.patch | 113 --
Makefile
applied
On Mon, Jul 04, 2016 at 03:36:16PM +0200, Dominik Csapak wrote:
> since we allow to create a container without hostname
> (we are using localhost by default then) and hostname
> is marked optional in the JSONSchema of the config
> we should be able to delete the hostname
>
> Signed-off-by
