Hi,
the first things are working. But i've problems to mark the owner disk
as shared. This is needed so that i can block deletion on owner vm as
long as the disk is shared.
So right now i have:
VM: 123
scsi4: cephkvmpool1:vm-123-disk-4,cache=none,size=32G
Attach the disk to another VM:
~#
Hi Dietmar,
sorry to ask this again - but i still don't know what you like and you
dislike.
to be clear. I'll add shared_virtioX, shared_ideX, shared_sataX, ... or
should skip this and use normal virtioX, ideX, sataX property and just
work with the owner != vmid flag?
Greets, Stefan
sorry to ask this again - but i still don't know what you like and you
dislike.
sorry - I am working on other things right now.
to be clear. I'll add shared_virtioX, shared_ideX, shared_sataX, ...
or should skip this and use normal virtioX, ideX, sataX property and
just work with the
Hi,
thanks. I think I need to mark a disk as shared - so that i can block
deletion whioe shared.
Does the API allow to modify a VM config running on host B from host A?
Greets,
Stefan
Am 18.12.2012 17:56, schrieb Dietmar Maurer:
sorry to ask this again - but i still don't know what you
thanks. I think I need to mark a disk as shared - so that i can block deletion
whioe shared.
Again, it is marked shared if the 'owner == 0' (that is the idea).
Does the API allow to modify a VM config running on host B from host A?
No, that would we dangerous because it does not lock the VM
Hi Dietmar,
sorry for the late reply.
Am 17.12.2012 07:49, schrieb Dietmar Maurer:
But shared disk are really usefull, I regulary use them for web cluster or
databases clusters.
Can you provide some details? What database or what web server is able to
use such shared disk?
The webserver or
Can you provide some details? What database or what web server is able
to use such shared disk?
webserver : all webservers (apache,nginx,...) under linux with a shared
filesystem (ocfs2,gfs,...).
Seem we talk about different things!
Stefan want to pass a file on GFS into several VMs.
Hi Dietmar,
Am 17.12.2012 10:48, schrieb Dietmar Maurer:
Can you provide some details? What database or what web server is able
to use such shared disk?
webserver : all webservers (apache,nginx,...) under linux with a shared
filesystem (ocfs2,gfs,...).
Seem we talk about different things!
) which can manage the disk sharing.
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com, Stefan Priebe s.pri...@profihost.ag
Envoyé: Lundi 17 Décembre 2012 10:48:27
Objet: RE: [pve-devel] introduce linked disks
webserver : all webservers (apache,nginx,...) under linux with a
shared filesystem (ocfs2,gfs,...).
Seem we talk about different things!
Stefan want to pass a file on GFS into several VMs.
IMHO, this is a safe way to destroy all data?
What do i want? I want to share a disk between
Hi Dietmar,
Am 17.12.2012 11:01, schrieb Dietmar Maurer:
Please can you describe exactly what you want to do? Form what I see you
want to run GFS on the host and pass file on GFS into the VM?
No.
Or do you run GFS inside the guest?
Yes! I'm using ocfs2 but that doesn't matter. The host isn't
Or do you run GFS inside the guest?
Yes! I'm using ocfs2 but that doesn't matter. The host isn't touched by this.
I'm using a cluster fs INSIDE guests.
So X guests can share the same disk and data.
That makes more sense now ;-)
___
pve-devel
Hi,
Am 17.12.2012 11:06, schrieb Dietmar Maurer:
Or do you run GFS inside the guest?
Yes! I'm using ocfs2 but that doesn't matter. The host isn't touched by this.
I'm using a cluster fs INSIDE guests.
So X guests can share the same disk and data.
That makes more sense now ;-)
Sorry for
store1:/0/vm-0-disk-1.raw
(owner is VM 0). But I am not sure if that is a good idea.
The idea is to have entries like this one:
shared_scsi1:vm-117-disk-5
shared_virtio2:vm-117-disk-9
We don't need the path as the PVE code always rely on the vm-(\d+)
number. So my idea was to do
Hi,
Am 17.12.2012 11:08, schrieb Dietmar Maurer:
store1:/0/vm-0-disk-1.raw
(owner is VM 0). But I am not sure if that is a good idea.
The idea is to have entries like this one:
shared_scsi1:vm-117-disk-5
shared_virtio2:vm-117-disk-9
We don't need the path as the PVE code always rely on the
Am 17.12.2012 11:08, schrieb Dietmar Maurer:
store1:/0/vm-0-disk-1.raw
(owner is VM 0). But I am not sure if that is a good idea.
The idea is to have entries like this one:
shared_scsi1:vm-117-disk-5
shared_virtio2:vm-117-disk-9
We don't need the path as the PVE code always rely
Hi Dietmar,
Am 17.12.2012 11:20, schrieb Dietmar Maurer:
Am 17.12.2012 11:08, schrieb Dietmar Maurer:
store1:/0/vm-0-disk-1.raw
(owner is VM 0). But I am not sure if that is a good idea.
The idea is to have entries like this one:
shared_scsi1:vm-117-disk-5
shared_virtio2:vm-117-disk-9
We
(owner is VM 0). But I am not sure if that is a good idea.
I didn't have thinked about it.
I think that the master need also too know where the disk is shared.
Because if we do a snapshot rollback for example, on the master, we need
to stop all vms where the disk is shared...
So do we need
So your idea is to prefix the controller (scsi, ide, virtio) on ALL guests.
No.
And the owner is just detected by the ID? (vm-$ID-disk-$I)
We already have an 'owner' for each volume (that is already implemented).
If (owner == 0) === shared disk
___
I like examples to be sure we're talking about the same thing. So you mean
like this:
VM 123
scsi1: ...,vm-123-disk5,...
owner = 1
no, owner = 123
VM 124
shared_scsi6: ...,vm-123-disk5,...
owner = 0
owner = 123
VM 125
shared_scsi7: ...,vm-123-disk5,...
owner = 0
owner =
We already have an 'owner' for each volume (that is already implemented).
Ah OK sorry didn't know that. How is that detected?
I like examples to be sure we're talking about the same thing. So you mean
like this:
VM 123
scsi1: ...,vm-123-disk5,...
owner = 1
The 'owner' is not a
Hi,
Am 17.12.2012 11:45, schrieb Dietmar Maurer:
I like examples to be sure we're talking about the same thing. So you mean
like this:
VM 123
scsi1: ...,vm-123-disk5,...
owner = 1
no, owner = 123
OK another question. Do we pass all params like cache I/O limits... to
shared guests? Or should
OK another question. Do we pass all params like cache I/O limits... to
shared guests? Or should this be configurable in shared guests too? I
would like too keep it as simple as possible and would pass these settings
from master
guest to the shared guests.
With my suggestion, there is
diet...@proxmox.com, Stefan Priebe - Profihost AG
s.pri...@profihost.ag
Cc: pve-devel@pve.proxmox.com
Envoyé: Lundi 17 Décembre 2012 11:59:10
Objet: Re: [pve-devel] introduce linked disks
OK another question. Do we pass all params like cache I/O limits... to
shared guests? Or should
Am 17.12.2012 11:58, schrieb Dietmar Maurer:
OK another question. Do we pass all params like cache I/O limits... to shared
guests? Or should this be configurable in shared guests too? I would like too
keep it as simple as possible and would pass these settings from master
guest to the shared
Hi,
Am 17.12.2012 12:04, schrieb Alexandre DERUMIER:
But I guess we should force cache=none for shared disk anyways?
Not sure about it, but I use directsync. (I'll retest it, but I think that
cache=none (writeback in guest), doesn't allow ocfs2 to start)
Mhm i would say cache doesn't matter.
Owner is always the VM which created the disk. So resizing deleting is only
working in that VM. Same for backup snapshot...
Stefan
Am 16.12.2012 um 08:50 schrieb Dietmar Maurer diet...@proxmox.com:
you mean by editing the qemu/VMID.conf file?
That's correct but i would like todo this
- Profihost AG s.pri...@profihost.ag
À: Dietmar Maurer diet...@proxmox.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Dimanche 16 Décembre 2012 09:21:25
Objet: Re: [pve-devel] introduce linked disks
Owner is always the VM which created the disk. So resizing deleting is only
working in that VM. Same
on storage)
Same as above.
Greets,
Stefan
- Mail original -
De: Stefan Priebe - Profihost AG s.pri...@profihost.ag
À: Dietmar Maurer diet...@proxmox.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Dimanche 16 Décembre 2012 09:21:25
Objet: Re: [pve-devel] introduce linked disks
Owner
some things to check I have in my mind:
resize:
if you resize on a vm, the second vm will not see the new size without reboot
I think (no way to advertise it)
snapshot rollback:
Doesn't will break thing if you rollback on a vm, with the second vm running.
(maybe the second vm will
snapshot rollback:
Doesn't will break thing if you rollback on a vm, with the second vm
running. (maybe the second vm will crash or hang ?)
This is only possible if alle VMs are offline.
disk restore : can we restore a disk, if it's running on another vm ?
(maybe they are some locks
idea how to implemented shared disks?
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Stefan Priebe s.pri...@profihost.ag, Alexandre DERUMIER
aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Dimanche 16 Décembre 2012 16:02:30
Objet: RE: [pve-devel] introduce
: pve-devel@pve.proxmox.com, Stefan Priebe s.pri...@profihost.ag
Envoyé: Lundi 17 Décembre 2012 07:49:08
Objet: RE: [pve-devel] introduce linked disks
And I still not know why I need that at all?
My point was just that we some some protections if shared disks are used.
Sure.
But shared
Hello,
i would like to add support for linked disks. These are disks owned by a
VM but available in other VMs too. For example for GFS, OCFS2, ...
Is there a general interest in it?
Dietmar what would be the right way?
1.) introduce a command in qm cmd?
2.) introcude API2
3.) introduce Web
implementing backend (qemuserver,pve-storage,..).
then finally implemented gui.
- Mail original -
De: Stefan Priebe s.pri...@profihost.ag
À: pve-devel@pve.proxmox.com
Envoyé: Samedi 15 Décembre 2012 14:38:31
Objet: [pve-devel] introduce linked disks
Hello,
i would like to add
i would like to add support for linked disks. These are disks owned by a VM
but available in other VMs too. For example for GFS, OCFS2, ...
Is there a general interest in it?
Dietmar what would be the right way?
1.) introduce a command in qm cmd?
2.) introcude API2
3.) introduce Web
you mean by editing the qemu/VMID.conf file?
That's correct but i would like todo this through the Web GUI.
So how do you plan to solve the ownership problem?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
37 matches
Mail list logo
