Hello, We're trying to create a multisite architecture where any VM could be relocated to the secondary site whenever the primary site fails (primary/backup for disaster recovery purposes). We don't require live migration, and we are okay with shutting down machines in order to relocate them.
We are using Cloudstack 4.15 on Ubuntu Focal. In our current setup, each datacenter has a Cloudstack management node, as well as a few hypervisors running KVM and a Cloudstack agent. We're using Ceph as our primary storage, and NFS as our secondary storage on each site. To ensure metadata resiliency, we've replicated the MySQL database across both sites, much like described following this guide: https://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.11/choosing_deployment_architecture.html#multi-site-deployment We tried setting up multiple zones, one for each datacenter, each one having its own primary storage, but we are faced with the issue where we are not able to migrate VMs across zones (only Pod/Cluster/Host level is available). We tried this method using the GUI as well as via the Cloudmonkey CLI. Are we using the right level of abstraction for our case? If so, how can we migrate a VM (compute + storage) from one zone to another? If not, what is the right level to use that allows us to use two separate primary storage endpoints and ensures that only the primary site gets used for compute resource allocation in normal conditions? Also, we would like to know whether there is some place where we could find documentation for the best practices and guidelines when addressing these more complex use cases. Kind regards, Vladimir DOMBROVSKI -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email. *AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.