On Wed, Mar 17, 2021 at 12:01 AM Daniel Gurgel < [email protected]> wrote:
> Nir, thank you for your help and practical examples. I'll try to simulate. > > In fact, most companies that actually have different offices do not share > the same SAN/Storage structure , there are physical limitations and network > details and time that make procedures impossible - As I said, storages that > work differently, are also a limiting factor. > > Export Domain, we can count today, but in six months, we don't know if > it'll still be there. > Even if export domains will still be there, you'd probably want to switch to an alternative that is better tested these days and that would comply with recent/future changes. Let me be more concrete here - we're adding TPM [1] + have already added NVRAM and there's no plan to preserve them when exporting and importing from an export domain. Nir touched the trade-off between the alternatives that were described and I'll add to that: 1. Detach+attach date domain is indeed nice in the sense that you don't copy data but if you intend to use it as an alternative to export domains, be aware that you have to have all the disks of the VM/template on the storage domain(s) you detach and when detaching a storage domain, the entities (VMs/templates) are "unregistered" (i.e., removed) from the original data center. 2. Export/Import OVAs is the closest replacement for export domains - if you want the ability to export a VM/template from one data center and import it elsewhere while ensuring the VM/template includes all its resources (disks, TPM, NVRAM, etc) at the target data center and without affecting the original data center, that's the mechanism I'd go with. We made significant fixes for that recently so I'd suggest updating to 4.4.4. [1] https://www.ovirt.org/develop/release-management/features/virt/tpm-device.html > > Most hypervisors support Live Migrate/Off line migrate between "data > centers". It would be great to have this feature up to oVirt 4.5.x > _______________________________________________ > Devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/WYRHNO2V6RF4FSIDJCLCR2DMVAI4LLJR/ >
_______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/CCQ7GGQV5D2O7XWNAJ77DH6FRRF3NU56/
