Re: [ceph-users] features required for live migration

Thanks a lot for all your comments, If you don't see any problem... I will enable the following features that might fit my requirements: Layering Striping Exclusive locking Object map Fast-diff Thanks a lot Óscar Segarra 2017-11-14 16:56 GMT+01:00 Jason Dillaman : >

Re: [ceph-users] features required for live migration

>From the documentation [1]: shareable If present, this indicates the device is expected to be shared between domains (assuming the hypervisor and OS support this), which means that caching should be deactivated for that device. Basically, it's the use-case for putting a clustered file system

Re: [ceph-users] features required for live migration

>From the documentation [1]: shareable If present, this indicates the device is expected to be shared between domains (assuming the hypervisor and OS support this), which means that caching should be deactivated for that device. Basically, it's the use-case for putting a clustered file system

Re: [ceph-users] features required for live migration

Hi Jason, The big use-case for sharing a block device is if you set up a clustered file system on top of it, and I'd argue that you'd probably be better off using CephFS. --> Nice to know! Thanks a lot for your clarifications, in this case I referenced the shareable flag that one can see in the

Re: [ceph-users] features required for live migration

On Tue, Nov 14, 2017 at 10:25 AM, Oscar Segarra wrote: > In my environment, I have a Centos7 updated todate therefore, all > features might work as expected to do... > > Regarding the other question, do you suggest making the virtual disk > "shareable" in rbd?

Re: [ceph-users] features required for live migration

In my environment, I have a Centos7 updated todate therefore, all features might work as expected to do... Regarding the other question, do you suggest making the virtual disk "shareable" in rbd? Thanks a lot 2017-11-14 15:58 GMT+01:00 Jason Dillaman : > Concur --

Re: [ceph-users] features required for live migration

Concur -- there aren't any RBD image features that should prevent live migration when using a compatible version of librbd. If, however, you had two hosts where librbd versions were out-of-sync and they didn't support the same features, you could hit an issue if a VM with fancy new features was

Re: [ceph-users] features required for live migration

Hi Oscar, exclusive-locking should not interfere with live-migration. I have a small virtualization cluster backed by ceph/rbd and I can migrate all the VMs which RBD image have exclusive-lock enabled without any issue. Em 11/14/2017 9:47 AM, Oscar Segarra escreveu: Hi Konstantin, Thanks a

Re: [ceph-users] features required for live migration

Hi, I include Jason Dillaman, the creator of this post http://tracker.ceph.com/issues/15000 in this thread Thanks a lot 2017-11-14 12:47 GMT+01:00 Oscar Segarra : > Hi Konstantin, > > Thanks a lot for your advice... > > I'm specially interested in feature "Exclusive

Re: [ceph-users] features required for live migration

Hi Konstantin, Thanks a lot for your advice... I'm specially interested in feature "Exclusive locking". Enabling this feature can affect live/offline migration? In this scenario (online/offline migration) I don't know if two hosts (source and destination) need access to the same rbd image at

Re: [ceph-users] features required for live migration

On 11/14/2017 06:19 PM, Oscar Segarra wrote: What I'm trying to do is reading documentation in order to understand how features work and what are they for. http://tracker.ceph.com/issues/15000 I would also be happy to read what features have negative sides. The problem is that

Re: [ceph-users] features required for live migration

Hi Konstantin, What I'm trying to do is reading documentation in order to understand how features work and what are they for. http://tracker.ceph.com/issues/15000 The problem is that documentation is not detailed enough. The proof-test method you suggest I think is not a good procedure because

Re: [ceph-users] features required for live migration

I misunderstand you. If you at the testing/deploy stage - why you can't test what features you need and what supported by your librbd? On 11/14/2017 05:39 PM, Oscar Segarra wrote: In this moment, I'm deploying and therefore I can upgrade every component... I have recently executed "yum

Re: [ceph-users] features required for live migration

For understanding: live migration is just the same run like clean run from powered off state, exception only the copying memory from one host to another, i.e. if your VM start from powered off state, than live migration should works without any issues. Also, client must be compatible with the

Re: [ceph-users] features required for live migration

Hi, Yes, but looks lots of features like snapshot, fast-diff require some other features... If I enable exclusive-locking or journaling, live migration will be possible too? Is it recommended to set KVM disk "shareable" depending on the activated features? Thanks a lot! 2017-11-14 4:52

Re: [ceph-users] features required for live migration

I'd like to use the live migration feature of KVM. In this scenario, what features may be enabled in the rbd base image? and in my EV (snapshot clone)? You can use live migration without features. For KVM I can recommend minimal "rbd default features = 3" (layering, striping).

Re: [ceph-users] features required for live migration

Hi, Anybody has experience with live migration features? Thanks a lot in advance. Óscar Segarra El 7 nov. 2017 14:02, "Oscar Segarra" escribió: > Hi, > > In my environment I'm working with a 3 node ceph cluster based on Centos 7 > and KVM. My VM is a clone of a

[ceph-users] features required for live migration

Hi, In my environment I'm working with a 3 node ceph cluster based on Centos 7 and KVM. My VM is a clone of a protected snapshot as is suggested in the following document: http://docs.ceph.com/docs/luminous/rbd/rbd-snapshot/#getting-started-with-layering I'd like to use the live migration