Dear Teams,
I have Dell EMC ScaleIO (renamed to VxFlexOS) license.
ScaleIO has 3 components:
SDS: server storage provider. This component could be installed on
Proxmox ok.
MDM: distributed storage metadata management. This is installed on a VM
for HA & live-migration requirement.
SDC: storage
On Fri, Sep 21, 2018 at 03:21:50PM +0200, Dietmar Maurer wrote:
> > I know you just do this to not duplicate the blockdevice path assembly,
> > but it feels a bit weird to directly have an map with $nomap method call
> > in unmap, maybe pull the common parts out in its own ($private) helper sub?
>
and check correctly that the storage exists only when the user
want to create a storage
this is useful if you want to create the same storage on
multiple nodes
Signed-off-by: Dominik Csapak
---
PVE/API2/Disks/Directory.pm | 9 +
PVE/API2/Disks/LVM.pm | 3 +--
On 9/19/18 11:35 AM, Dominik Csapak wrote:
> explain how to use it, what it is and a link to further documentation
>
> Signed-off-by: Dominik Csapak
> ---
> qm.adoc | 31 +++
> 1 file changed, 31 insertions(+)
>
> diff --git a/qm.adoc b/qm.adoc
> index
> I know you just do this to not duplicate the blockdevice path assembly,
> but it feels a bit weird to directly have an map with $nomap method call
> in unmap, maybe pull the common parts out in its own ($private) helper sub?
I though somebody will suggest a better name for that parameter so
On 9/21/18 2:37 PM, Thomas Lamprecht wrote:
> [...]
>
> Single thing which was not working was the a full clone of a linked clone,
> i.e., convert a CT to a template, create a linked clone with said template
> as base (works) and then clone the linked clone (full clone), which seems
> to work
On 9/21/18 7:58 AM, Dietmar Maurer wrote:
> This allows to request a mapped device/path explicitly,
> regardles of the storage option, eg. krbd option in the RBDplugin.
I like this approach more, less intrusive and more explicit.
I tested a bit around, i.e., create CT, snapshot it, clone from
