OK.
I created an issue about this feature.
https://gitlab.com/libvirt/libvirt/-/issues/37
Guy
Le 22/06/2020 à 13:06, Michal Privoznik a écrit :
> On 6/19/20 8:24 AM, Guy Godfroy wrote:
>> Hello,
>>
>> Is there any news about this feature ?
>
> Unfortunately no news. Sorry.
>
> Michal
On 6/19/20 8:24 AM, Guy Godfroy wrote:
Hello,
Is there any news about this feature ?
Unfortunately no news. Sorry.
Michal
Hello,
Is there any news about this feature ?
Guy Godfroy
Le 27/01/2020 à 15:06, Guy Godfroy a écrit :
Cool :)
Don't worry I'm not on a rush: I guess the feature will not be part of
Debian before next major release anyway.
Le ven., janv. 24, 2020 at 17:24, Michal Privoznik
a écrit :
On 1
Hello,
Any news on that feature?
Le 27/01/2020 à 15:06, Guy Godfroy a écrit :
Cool :)
Don't worry I'm not on a rush: I guess the feature will not be part of
Debian before next major release anyway.
Le ven., janv. 24, 2020 at 17:24, Michal Privoznik
a écrit :
On 1/24/20 4:34 PM, Guy Godfro
Cool :)
Don't worry I'm not on a rush: I guess the feature will not be part of
Debian before next major release anyway.
Le ven., janv. 24, 2020 at 17:24, Michal Privoznik
a écrit :
On 1/24/20 4:34 PM, Guy Godfroy wrote:
I don't really understand what new hook this would be.
Libvirt's migr
On 1/24/20 4:34 PM, Guy Godfroy wrote:
I don't really understand what new hook this would be.
Libvirt's migration happens in phases [1]. The last one is 'Confirm'
where either the domain is either killed (because it's running on the
destination successfully), or resumed (because there was an
I don't really understand what new hook this would be.
Le 24/01/2020 à 14:05, Michal Privoznik a écrit :
On 1/23/20 1:43 PM, Guy Godfroy wrote:
So, how likely is it possible to get this feature (two new events for
the qemu hook)?
I've started writing it, but then I realized we might need thi
On 1/23/20 1:43 PM, Guy Godfroy wrote:
So, how likely is it possible to get this feature (two new events for
the qemu hook)?
I've started writing it, but then I realized we might need third hook -
in confirm phase - which would be run on the source when quemu switches
control over to the dest
So, how likely is it possible to get this feature (two new events for
the qemu hook)?
Le 22/01/2020 à 10:56, Guy Godfroy a écrit :
That's right, I need also that second hook event.
For your information, for now I manage locks manually or via Ansible.
To make hook manage locks, I still need to
That's right, I need also that second hook event.
For your information, for now I manage locks manually or via Ansible. To make
hook manage locks, I still need to find out a secure way to run LVM commands
from a non-root account, but this is another problem.
Le 22 janvier 2020 10:24:53 GMT+01:0
On 1/22/20 9:23 AM, Guy Godfroy wrote:
I could launch `lvchange -asy` on the source host manually, but the aim
of hooks is to automatically execute such commands and avoid human errors.
Agreed. However, you would need two hooks actually. One that is called
on the source when the migration is s
I could launch `lvchange -asy` on the source host manually, but the aim of
hooks is to automatically execute such commands and avoid human errors.
Le 22 janvier 2020 09:18:54 GMT+01:00, Michal Privoznik a
écrit :
>On 1/21/20 9:10 AM, Guy Godfroy wrote:
>> Hello, this is my first time posting on
On 1/21/20 9:10 AM, Guy Godfroy wrote:
Hello, this is my first time posting on this mailing list.
I wanted to suggest a addition to the qemu hook. I will explain it
through my own use case.
I use a shared LVM storage as a volume pool between my nodes. I use
lvmlockd in sanlock mode to protec
Hello, this is my first time posting on this mailing list.
I wanted to suggest a addition to the qemu hook. I will explain it
through my own use case.
I use a shared LVM storage as a volume pool between my nodes. I use
lvmlockd in sanlock mode to protect both LVM metadata corruption and
conc
14 matches
Mail list logo
