From 7dae88a9d538e601e4a55c48bdc6780e79feef56 Mon Sep 17 00:00:00 2001 From: amanolache Date: Tue, 13 Oct 2026 13:01:02 +0300 Subject: [PATCH 1/2] Updated documentation, every platform now lives in a specific directory to keep track more easily of md files. Created a new suse-linux-kvm-plugin.md file as a Work in progress file --- source/bare-metal/index.md | 2 +- ...cture-classic-oci-c-opc-coriolis-plugin.md | 4 +- source/index.md | 1 - ...amazon-web-services-aws-coriolis-plugin.md | 14 +- .../aws-as-a-destination-cloud.md | 5 +- .../aws-as-a-source-cloud.md | 3 +- .../coriolis-bare-metal-hub-plugin.md | 30 ++-- .../cloudstack-as-a-destination-cloud.md | 1 + .../hyper-v}/hyper-v-coriolis-plugin.md | 10 +- source/platforms/index.md | 33 ++-- ...bevirt-harvester-as-a-destination-cloud.md | 3 +- .../kubevirt-harvester-coriolis-plugin.md | 12 +- .../microcloud-lxd-as-a-destination-cloud.md | 5 +- .../microcloud-lxd-coriolis-plugin.md | 10 +- .../azure-as-a-destination-cloud.md | 5 +- .../azure-as-a-source-cloud.md | 3 +- ...rosoft-azure-azurestack-coriolis-plugin.md | 10 +- .../nutanix-as-a-source-cloud.md | 7 +- .../openstack-as-a-destination-cloud.md | 5 +- .../openstack-as-a-source-cloud.md | 11 +- .../openstack}/openstack-coriolis-plugin.md | 18 +- ...loud-infrastructure-oci-coriolis-plugin.md | 12 +- .../ovirt-as-a-destination-cloud.md} | 9 +- .../{ => ovirt}/ovirt-as-a-source-cloud.md | 5 +- .../ovirt}/ovirt-coriolis-plugin.md | 8 +- .../proxmox-as-a-destination-cloud.md | 7 +- .../proxmox}/proxmox-coriolis-plugin.md | 10 +- .../stackit-as-a-destination-cloud.md | 5 +- .../stackit-as-a-source-cloud.md | 5 +- .../stackit}/stackit-coriolis-plugin.md | 12 +- .../suse-linux-kvm/suse-linux-kvm-plugin.md | 13 ++ ...suse-linux-kvm-sap-hana-target-platform.md | 5 + .../suse-linux-kvm-target-platform.md | 7 +- .../vmware-as-a-destination-cloud.md | 7 +- .../{ => vmware}/vmware-as-a-source-cloud.md | 9 +- .../vmware}/vmware-coriolis-plugin.md | 14 +- source/plugins/index.md | 20 --- source/reference/coriolis-eula.md | 155 ------------------ source/reference/coriolis-release-notes.md | 1 + source/reference/index.md | 2 +- 40 files changed, 177 insertions(+), 321 deletions(-) rename source/{plugins => deprecated}/oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin.md (99%) rename source/{plugins => platforms/amazon-web-services-aws}/amazon-web-services-aws-coriolis-plugin.md (87%) rename source/platforms/{ => amazon-web-services-aws}/aws-as-a-destination-cloud.md (98%) rename source/platforms/{ => amazon-web-services-aws}/aws-as-a-source-cloud.md (98%) rename source/{plugins => platforms/bare-metal-hub}/coriolis-bare-metal-hub-plugin.md (82%) rename source/platforms/{ => cloudstack}/cloudstack-as-a-destination-cloud.md (99%) rename source/{plugins => platforms/hyper-v}/hyper-v-coriolis-plugin.md (98%) rename source/platforms/{ => kubevirt-harvester}/kubevirt-harvester-as-a-destination-cloud.md (99%) rename source/{plugins => platforms/kubevirt-harvester}/kubevirt-harvester-coriolis-plugin.md (91%) rename source/platforms/{ => microcloud-lxd}/microcloud-lxd-as-a-destination-cloud.md (98%) rename source/{plugins => platforms/microcloud-lxd}/microcloud-lxd-coriolis-plugin.md (93%) rename source/platforms/{ => microsoft-azure-azurestack}/azure-as-a-destination-cloud.md (98%) rename source/platforms/{ => microsoft-azure-azurestack}/azure-as-a-source-cloud.md (97%) rename source/{plugins => platforms/microsoft-azure-azurestack}/microsoft-azure-azurestack-coriolis-plugin.md (96%) rename source/platforms/{ => nutanix}/nutanix-as-a-source-cloud.md (96%) rename source/platforms/{ => openstack}/openstack-as-a-destination-cloud.md (99%) rename source/platforms/{ => openstack}/openstack-as-a-source-cloud.md (97%) rename source/{plugins => platforms/openstack}/openstack-coriolis-plugin.md (95%) rename source/{plugins => platforms/oracle-cloud-infrastructure-oci}/oracle-cloud-infrastructure-oci-coriolis-plugin.md (97%) rename source/platforms/{oracle-linux-virtualization-manager-as-a-destination-cloud.md => ovirt/ovirt-as-a-destination-cloud.md} (96%) rename source/platforms/{ => ovirt}/ovirt-as-a-source-cloud.md (96%) rename source/{plugins => platforms/ovirt}/ovirt-coriolis-plugin.md (95%) rename source/platforms/{ => proxmox}/proxmox-as-a-destination-cloud.md (97%) rename source/{plugins => platforms/proxmox}/proxmox-coriolis-plugin.md (91%) rename source/platforms/{ => stackit}/stackit-as-a-destination-cloud.md (99%) rename source/platforms/{ => stackit}/stackit-as-a-source-cloud.md (97%) rename source/{plugins => platforms/stackit}/stackit-coriolis-plugin.md (93%) create mode 100644 source/platforms/suse-linux-kvm/suse-linux-kvm-plugin.md rename source/platforms/{ => suse-linux-kvm}/suse-linux-kvm-sap-hana-target-platform.md (98%) rename source/platforms/{ => suse-linux-kvm}/suse-linux-kvm-target-platform.md (98%) rename source/platforms/{ => vmware}/vmware-as-a-destination-cloud.md (97%) rename source/platforms/{ => vmware}/vmware-as-a-source-cloud.md (96%) rename source/{plugins => platforms/vmware}/vmware-coriolis-plugin.md (92%) delete mode 100644 source/plugins/index.md delete mode 100644 source/reference/coriolis-eula.md diff --git a/source/bare-metal/index.md b/source/bare-metal/index.md index 6de60a2..a4c642a 100644 --- a/source/bare-metal/index.md +++ b/source/bare-metal/index.md @@ -1,4 +1,4 @@ -# Bare metal +# Bare Metal Migrations ```{toctree} :maxdepth: 1 diff --git a/source/plugins/oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin.md b/source/deprecated/oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin.md similarity index 99% rename from source/plugins/oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin.md rename to source/deprecated/oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin.md index a1154c1..1e38059 100644 --- a/source/plugins/oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin.md +++ b/source/deprecated/oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin.md @@ -1,9 +1,9 @@ --- -title: "Oracle Cloud Infrastructure Classic (OCI-C/OPC) Coriolis Plugin" +title: "Oracle Cloud Infrastructure Classic (OCI-C/OPC)" wp_id: 38531 --- -# Oracle Cloud Infrastructure Classic (OCI-C/OPC) Coriolis Plugin +# Oracle Cloud Infrastructure Classic (OCI-C/OPC) ```{note} This platform is no longer supported by Oracle and has been archived in Coriolis. diff --git a/source/index.md b/source/index.md index fd8cb43..bd0a6bb 100644 --- a/source/index.md +++ b/source/index.md @@ -9,7 +9,6 @@ and **cross-site disaster recovery** features (DRaaS) between a source cloud pla guides/index reference/index -plugins/index platforms/index walkthroughs/index features/index diff --git a/source/plugins/amazon-web-services-aws-coriolis-plugin.md b/source/platforms/amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin.md similarity index 87% rename from source/plugins/amazon-web-services-aws-coriolis-plugin.md rename to source/platforms/amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin.md index a5440e5..41022bf 100644 --- a/source/plugins/amazon-web-services-aws-coriolis-plugin.md +++ b/source/platforms/amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin.md @@ -1,13 +1,13 @@ --- -title: "Amazon Web Services (AWS) Coriolis Plugin" +title: "Amazon Web Services (AWS)" wp_id: 38516 --- -# Amazon Web Services (AWS) Coriolis Plugin +# Amazon Web Services (AWS) **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, Coriolis guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. -![](_static/images/AWS-source.jpg) ![](_static/images/ASW-destination.jpg) +![](../../_static/images/AWS-source.jpg) ![](../../_static/images/ASW-destination.jpg) ### Deployment requirements and supported AWS instances @@ -43,11 +43,11 @@ Each parameter represents: ### AWS as a source cloud -For more information on using AWS as a **source cloud** for Replica/MIgration, please check the **[AWS as a source cloud](../platforms/aws-as-a-source-cloud.md)** page. +For more information on using AWS as a **source cloud** for Replica/MIgration, please check the **[AWS as a source cloud](../amazon-web-services-aws/aws-as-a-source-cloud.md)** page. -### AWS as a dstination cloud +### AWS as a destination cloud -For more information on using AWS as a **destination cloud** for Replica/MIgration, please check the **[AWS as a destination cloud](../platforms/aws-as-a-destination-cloud.md)** page. +For more information on using AWS as a **destination cloud** for Replica/MIgration, please check the **[AWS as a destination cloud](../amazon-web-services-aws/aws-as-a-destination-cloud.md)** page. ### AWS platform specifics @@ -60,4 +60,4 @@ Source disk export requirements| VM disks must be EBS-backed. Disk export is don Instance identification scheme| ID or "Name" tag| How instances to migrate/replicate are identified on a source cloud handled by this plugin Network identification scheme| IDs of VPCs| How networks are identified by the plugin. Required for the **network_map** field of the **- destination-environment** Storage identification scheme| EBS volume types| How storage backends are identified by the plugin. Required for the **storage_map** field of the **- destination-environment** -For more information regarding Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. diff --git a/source/platforms/aws-as-a-destination-cloud.md b/source/platforms/amazon-web-services-aws/aws-as-a-destination-cloud.md similarity index 98% rename from source/platforms/aws-as-a-destination-cloud.md rename to source/platforms/amazon-web-services-aws/aws-as-a-destination-cloud.md index 57e9a2c..6f3c2b3 100644 --- a/source/platforms/aws-as-a-destination-cloud.md +++ b/source/platforms/amazon-web-services-aws/aws-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "AWS as a destination cloud" wp_id: 41166 +orphan: true --- # AWS as a destination cloud @@ -37,7 +38,7 @@ Below is a listing of the configuration section needed when migrating from AWS: #### Configuration options for AWS as a destination -![](_static/images/ASW-destination.jpg) +![](../../_static/images/ASW-destination.jpg) ```ini [aws_migration_provider] @@ -149,4 +150,4 @@ Each parameter represents: ### Troubleshooting -For more information regarding Coriolis Troubleshooting, check the **[Troubleshooting page](../reference/coriolis-troubleshooting.md)**. +For more information regarding Coriolis Troubleshooting, check the **[Troubleshooting page](../../reference/coriolis-troubleshooting.md)**. diff --git a/source/platforms/aws-as-a-source-cloud.md b/source/platforms/amazon-web-services-aws/aws-as-a-source-cloud.md similarity index 98% rename from source/platforms/aws-as-a-source-cloud.md rename to source/platforms/amazon-web-services-aws/aws-as-a-source-cloud.md index 3e6de92..f535b8c 100644 --- a/source/platforms/aws-as-a-source-cloud.md +++ b/source/platforms/amazon-web-services-aws/aws-as-a-source-cloud.md @@ -1,6 +1,7 @@ --- title: "AWS as a source cloud" wp_id: 41200 +orphan: true --- # AWS as a source cloud @@ -33,7 +34,7 @@ Below is a listing of the configuration section needed when migrating from AWS: #### Configuration options for AWS as a migration source -![](_static/images/AWS-source.jpg) +![](../../_static/images/AWS-source.jpg) ```ini [aws_migration_provider] diff --git a/source/plugins/coriolis-bare-metal-hub-plugin.md b/source/platforms/bare-metal-hub/coriolis-bare-metal-hub-plugin.md similarity index 82% rename from source/plugins/coriolis-bare-metal-hub-plugin.md rename to source/platforms/bare-metal-hub/coriolis-bare-metal-hub-plugin.md index 04b771c..197f2ec 100644 --- a/source/plugins/coriolis-bare-metal-hub-plugin.md +++ b/source/platforms/bare-metal-hub/coriolis-bare-metal-hub-plugin.md @@ -1,15 +1,15 @@ --- -title: "Coriolis Bare Metal Hub Plugin" +title: "Coriolis Bare Metal Hub" wp_id: 41641 --- -# Coriolis Bare Metal Hub Plugin +# Coriolis Bare Metal Hub **Coriolis** integrates the platform Plugin on the Appliance itself. Here, Coriolis will need to take advantage of Snapshot Agents deployed on the Bare Metal Server to establish communication with the Plugin. This way, Coriolis guarantees the connection to the Bare Metal server, as long as all requirements are met. **Bare Metal Hub Plugin** is one of the supported Source platforms by Coriolis, which will allow Migrating workload from bare-metal to the cloud, for what is called **Physical to Virtual (p2v)**, as Coriolis supports multiple clouds as Destination platforms. -![Coriolis P2V](_static/images/p2v-3.jpg) +![Coriolis P2V](../../_static/images/p2v-3.jpg) Coriolis P2V @@ -18,7 +18,7 @@ Source to Coriolis required ports: 1. TCP port 9999 for communication between Coriolis and the Bare Metal Server. The port can be customized. 2. TCP port 80 for the Coriolis certificate issuing process upon Snapshot Agent install on the Bare Metal Server. This is required only once - during Agent installation. -For the Coriolis appliance to the target platform port requirements, you can refer to [this page](../reference/coriolis-network-ports-requirements.md). +For the Coriolis appliance to the target platform port requirements, you can refer to [this page](../../reference/coriolis-network-ports-requirements.md). In the **Bare Metal Hub**, which is a UI section for Coriolis-metal-hub functionality, you will be able to: @@ -45,13 +45,13 @@ Incremental Replica syncs for a bare-metal server using the Coriolis Agent are c | **Release** | **Supported versions** | **Latest kernel verified** | |---|---|---| -| ![](_static/images/ubuntu.svg) **Ubuntu Server** | 16.04 - 22.04 | 5.15.0-83 | -| ![](_static/images/redhat.svg) **Red Hat Enterprise Linux** | 7.0 - 8.3 | 4.18.0-240 | -| ![](_static/images/centos.svg) **CentOS** | 7.0 - 8.3 | 4.18.0-240.22 | -| ![](_static/images/oracle.png) **Oracle Linux**
Red Hat Compatible Kernel | 7.9 - 8.3 | 4.18.0-240 | -| ![](_static/images/suse.svg) **SUSE Linux** | 12 - 15 SP4 | 5.14.21-150400.24 | -| ![](_static/images/opensuse.svg) **openSUSE Leap** | 15.4 | 5.14.21-150400.24 | -| ![](_static/images/debian.svg) **Debian** | 10 | 4.19.0-21 | +| ![](../../_static/images/ubuntu.svg) **Ubuntu Server** | 16.04 - 22.04 | 5.15.0-83 | +| ![](../../_static/images/redhat.svg) **Red Hat Enterprise Linux** | 7.0 - 8.3 | 4.18.0-240 | +| ![](../../_static/images/centos.svg) **CentOS** | 7.0 - 8.3 | 4.18.0-240.22 | +| ![](../../_static/images/oracle.png) **Oracle Linux**
Red Hat Compatible Kernel | 7.9 - 8.3 | 4.18.0-240 | +| ![](../../_static/images/suse.svg) **SUSE Linux** | 12 - 15 SP4 | 5.14.21-150400.24 | +| ![](../../_static/images/opensuse.svg) **openSUSE Leap** | 15.4 | 5.14.21-150400.24 | +| ![](../../_static/images/debian.svg) **Debian** | 10 | 4.19.0-21 | ```{note} Oracle Linux Unbreakable Kernel is not supported, **Red Hat Compatible Kernel** must be used instead. @@ -61,7 +61,7 @@ Oracle Linux Unbreakable Kernel is not supported, **Red Hat Compatible Kernel** The Coriolis Snapshot Agent for Bare Metal Servers is used for the process of Replica/MIgrate to be possible, and the agent is required to be installed on the machine for Coriolis to be able to communicate with it and fetch the machine info and clone the disks. -The installation guide can be found on the **[Snapshot Agent](../bare-metal/installing-the-snapshot-agent.md)** page. +The installation guide can be found on the **[Snapshot Agent](../../bare-metal/installing-the-snapshot-agent.md)** page. ### Add Bare Metal Server using Coriolis Dashboard @@ -69,19 +69,19 @@ As the Endpoint and the Snapshot Agent are installed, the next step is to add th * in the Dashboard, navigate from the left side menu to Bare Metal Server -![](_static/images/bm-severs.jpg) +![](../../_static/images/bm-severs.jpg) * Select 'Add a Bare Metal Server' and add the Host address and the port for the machine, and click 'Add' * the IP address of the machine * the port set upon installing the snapshot agent -![](_static/images/addbm.jpg) +![](../../_static/images/addbm.jpg) * Once the machine has been contacted, the connection will be validated and listed as **active**, meaning that the machine is ready to be used for **Replica/Migration**. * Also, Coriolis will display the hardware details of the newly added machine -![](_static/images/addedsrv1.png) +![](../../_static/images/addedsrv1.png) ### File-systems supported diff --git a/source/platforms/cloudstack-as-a-destination-cloud.md b/source/platforms/cloudstack/cloudstack-as-a-destination-cloud.md similarity index 99% rename from source/platforms/cloudstack-as-a-destination-cloud.md rename to source/platforms/cloudstack/cloudstack-as-a-destination-cloud.md index 23b1fa0..2fa06b0 100644 --- a/source/platforms/cloudstack-as-a-destination-cloud.md +++ b/source/platforms/cloudstack/cloudstack-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "CloudStack as a destination cloud" wp_id: 44185 +orphan: true --- # CloudStack as a destination cloud diff --git a/source/plugins/hyper-v-coriolis-plugin.md b/source/platforms/hyper-v/hyper-v-coriolis-plugin.md similarity index 98% rename from source/plugins/hyper-v-coriolis-plugin.md rename to source/platforms/hyper-v/hyper-v-coriolis-plugin.md index d61be10..b901382 100644 --- a/source/plugins/hyper-v-coriolis-plugin.md +++ b/source/platforms/hyper-v/hyper-v-coriolis-plugin.md @@ -1,15 +1,15 @@ --- -title: "Microsoft Hyper-V Coriolis Plugin" +title: "Microsoft Hyper-V" wp_id: 38511 --- -# Microsoft Hyper-V Coriolis Plugin +# Microsoft Hyper-V **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, Coriolis guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. This section describes the functionality available via Coriolis' Hyper-V plugin, which enables Coriolis to both migrate (CMaaS) and replicate (DRaaS) instances from Hyper-V. -![](_static/images/hyper-v-source.jpg) +![](../../_static/images/hyper-v-source.jpg) ## Hyper-V Coriolis endpoint @@ -17,7 +17,7 @@ When creating the Hyper-V endpoint in Coriolis, a local account must be used for Using a domain account for the WinRM connectivity is subject to additional configuration at the domain level to allow such access. Please refer to the Microsoft documentation for further details on how this can be achieved. -![](_static/images/hv.png) +![](../../_static/images/hv.png) ## Deployment requirements and supported Hyper-V instances @@ -188,7 +188,7 @@ For exported VMs, Coriolis will take the following OSMorphing steps as part of t * no OSMorphing steps are taken as the integration services are part of the Windows guest OS itself -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. ### RCT service installation and configuration procedure diff --git a/source/platforms/index.md b/source/platforms/index.md index 760f02a..cbc6cbb 100644 --- a/source/platforms/index.md +++ b/source/platforms/index.md @@ -4,23 +4,18 @@ :maxdepth: 1 :titlesonly: -aws-as-a-source-cloud -aws-as-a-destination-cloud -azure-as-a-source-cloud -azure-as-a-destination-cloud -vmware-as-a-source-cloud -vmware-as-a-destination-cloud -openstack-as-a-source-cloud -openstack-as-a-destination-cloud -ovirt-as-a-source-cloud -oracle-linux-virtualization-manager-as-a-destination-cloud -nutanix-as-a-source-cloud -proxmox-as-a-destination-cloud -microcloud-lxd-as-a-destination-cloud -kubevirt-harvester-as-a-destination-cloud -suse-linux-kvm-target-platform -suse-linux-kvm-sap-hana-target-platform -stackit-as-a-source-cloud -stackit-as-a-destination-cloud -cloudstack-as-a-destination-cloud + +vmware/vmware-coriolis-plugin +openstack/openstack-coriolis-plugin +kubevirt-harvester/kubevirt-harvester-coriolis-plugin +suse-linux-kvm/suse-linux-kvm-plugin +hyper-v/hyper-v-coriolis-plugin +amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin +microsoft-azure-azurestack/microsoft-azure-azurestack-coriolis-plugin +microcloud-lxd/microcloud-lxd-coriolis-plugin +proxmox/proxmox-coriolis-plugin +oracle-cloud-infrastructure-oci/oracle-cloud-infrastructure-oci-coriolis-plugin +ovirt/ovirt-coriolis-plugin +stackit/stackit-coriolis-plugin +bare-metal-hub/coriolis-bare-metal-hub-plugin ``` diff --git a/source/platforms/kubevirt-harvester-as-a-destination-cloud.md b/source/platforms/kubevirt-harvester/kubevirt-harvester-as-a-destination-cloud.md similarity index 99% rename from source/platforms/kubevirt-harvester-as-a-destination-cloud.md rename to source/platforms/kubevirt-harvester/kubevirt-harvester-as-a-destination-cloud.md index e47de37..5bb468b 100644 --- a/source/platforms/kubevirt-harvester-as-a-destination-cloud.md +++ b/source/platforms/kubevirt-harvester/kubevirt-harvester-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "KubeVirt/Harvester as a destination cloud" wp_id: 43149 +orphan: true --- # KubeVirt/Harvester as a destination cloud @@ -9,7 +10,7 @@ wp_id: 43149 Migrations to KubeVirt operate in the same way Replicas do and thus entail the same requirements and steps described below. -![](_static/images/Untitled.png) +![](../../_static/images/Untitled.png) ## Replicating (DRaaS) to Kubevirt diff --git a/source/plugins/kubevirt-harvester-coriolis-plugin.md b/source/platforms/kubevirt-harvester/kubevirt-harvester-coriolis-plugin.md similarity index 91% rename from source/plugins/kubevirt-harvester-coriolis-plugin.md rename to source/platforms/kubevirt-harvester/kubevirt-harvester-coriolis-plugin.md index baa80c2..7fbdfbd 100644 --- a/source/plugins/kubevirt-harvester-coriolis-plugin.md +++ b/source/platforms/kubevirt-harvester/kubevirt-harvester-coriolis-plugin.md @@ -1,9 +1,9 @@ --- -title: "KubeVirt and Harvester Coriolis Plugin" +title: "KubeVirt and Harvester" wp_id: 43143 --- -# KubeVirt and Harvester Coriolis Plugin +# KubeVirt and Harvester **Coriolis** provides agentless integration with supported virtualization platforms by running the platform plugin directly on the Coriolis Appliance. This architecture eliminates the need to deploy agents on source or destination platforms and simplifies connectivity and setup. @@ -11,25 +11,25 @@ Coriolis has been validated for Harvester environments from **version 1.3 throug For a VMware to SUSE Virtualization migration, here is a representation of the steps involved: -![](_static/images/vmware-to-suse-virt.png) +![](../../_static/images/vmware-to-suse-virt.png) ## KubeVirt destination cloud For detailed information regarding KubeVirt/Harvester capabilities and steps performed while using it as a destination cloud, please check the following page: -**[KubeVirt/Harvester as a destination cloud](../platforms/kubevirt-harvester-as-a-destination-cloud.md)** +**[KubeVirt/Harvester as a destination cloud](../kubevirt-harvester/kubevirt-harvester-as-a-destination-cloud.md)** ## KubeVirt Endpoint Connection Parameters To connect to Kubevirt to perform migration to it, the following connection parameters are required: -![](_static/images/Untitled-1.png) +![](../../_static/images/Untitled-1.png) A valid kubeconfig YAML needs to be passed to the Coriolis endpoint. In a traditional KubeVirt setup, the kubeconfig can be found at the **~/.kube/config** location in your environment. If using Harvester, a kubeconfig can be generated for the logged-in user by accessing the Harvester UI's Support page and clicking **Download KubeConfig**, as shown below. -![](_static/images/kubeconf.png) +![](../../_static/images/kubeconf.png) ## KubeVirt platform specifics diff --git a/source/platforms/microcloud-lxd-as-a-destination-cloud.md b/source/platforms/microcloud-lxd/microcloud-lxd-as-a-destination-cloud.md similarity index 98% rename from source/platforms/microcloud-lxd-as-a-destination-cloud.md rename to source/platforms/microcloud-lxd/microcloud-lxd-as-a-destination-cloud.md index d9782f7..bf0e892 100644 --- a/source/platforms/microcloud-lxd-as-a-destination-cloud.md +++ b/source/platforms/microcloud-lxd/microcloud-lxd-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "MicroCloud (LXD) as a Destination Cloud" wp_id: 42661 +orphan: true --- # MicroCloud (LXD) as a Destination Cloud @@ -74,7 +75,7 @@ lxc publish --alias windows-worker --reuse description="Windows Worker ## Configuration Options -![](_static/images/lxc-options.png) +![](../../_static/images/lxc-options.png) Below is a listing of the configuration section needed when migrating/replicating to MicroCloud/LXD: @@ -134,4 +135,4 @@ Depending on the OS release we are migrating, the following notable steps will b * installing the VirtIO drivers * installing cloudbase-init and enabling cloudbase-init service -For more information regarding the Coriolis Worker template, please check the [Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md) page. +For more information regarding the Coriolis Worker template, please check the [Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md) page. diff --git a/source/plugins/microcloud-lxd-coriolis-plugin.md b/source/platforms/microcloud-lxd/microcloud-lxd-coriolis-plugin.md similarity index 93% rename from source/plugins/microcloud-lxd-coriolis-plugin.md rename to source/platforms/microcloud-lxd/microcloud-lxd-coriolis-plugin.md index 87be969..f9eb8bb 100644 --- a/source/plugins/microcloud-lxd-coriolis-plugin.md +++ b/source/platforms/microcloud-lxd/microcloud-lxd-coriolis-plugin.md @@ -1,25 +1,25 @@ --- -title: "MicroCloud (LXD) Coriolis Plugin" +title: "MicroCloud (LXD)" wp_id: 42651 --- -# MicroCloud (LXD) Coriolis Plugin +# MicroCloud (LXD) **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Coriolis guarantees the connection to the supported platform set up to be used as a Destination, as long as the requirements are met. -![](_static/images/lxc-options.png) +![](../../_static/images/lxc-options.png) ## MicroCloud destination cloud For detailed information regarding MicroCloud capabilities and performed steps while using it as a destination cloud, please check the following page: -**[MicroCloud (LXD) as a Destination Cloud](../platforms/microcloud-lxd-as-a-destination-cloud.md)** +**[MicroCloud (LXD) as a Destination Cloud](../microcloud-lxd/microcloud-lxd-as-a-destination-cloud.md)** ## LXD Endpoint Connection Parameters In order to connect to LXD to perform migration to it, the following connection parameters are required: -![](_static/images/lxd02.png) +![](../../_static/images/lxd02.png) ### LXD endpoint setup diff --git a/source/platforms/azure-as-a-destination-cloud.md b/source/platforms/microsoft-azure-azurestack/azure-as-a-destination-cloud.md similarity index 98% rename from source/platforms/azure-as-a-destination-cloud.md rename to source/platforms/microsoft-azure-azurestack/azure-as-a-destination-cloud.md index 68e15ad..c8c0386 100644 --- a/source/platforms/azure-as-a-destination-cloud.md +++ b/source/platforms/microsoft-azure-azurestack/azure-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "Azure as a destination cloud" wp_id: 39531 +orphan: true --- # Azure as a destination cloud @@ -219,7 +220,7 @@ The Windows image should have the Azure provisioning agent or cloudbase-init ins The template OS version must be at least the same as the OS of the VM that needs to be Replicated or Migrated. -![](_static/images/azure-target-options.png) +![](../../_static/images/azure-target-options.png) **Option name (UI)** | **Parameter** | **Description** ---|---|--- @@ -262,4 +263,4 @@ The images do **NOT** require any special Coriolis agent running in them and can **Windows**: the Windows image should have the Azure provisioning agent OR cloudbase-init installed and configured for the first boot. Coriolis will create a unique password for each migration deployment and use it to set up WinRM access via a VM extension. -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. diff --git a/source/platforms/azure-as-a-source-cloud.md b/source/platforms/microsoft-azure-azurestack/azure-as-a-source-cloud.md similarity index 97% rename from source/platforms/azure-as-a-source-cloud.md rename to source/platforms/microsoft-azure-azurestack/azure-as-a-source-cloud.md index 53b1db8..538c624 100644 --- a/source/platforms/azure-as-a-source-cloud.md +++ b/source/platforms/microsoft-azure-azurestack/azure-as-a-source-cloud.md @@ -1,6 +1,7 @@ --- title: "Azure as a source cloud" wp_id: 39529 +orphan: true --- # Azure as a source cloud @@ -16,7 +17,7 @@ Migrations from Azure operate in the same way Replicas do and thus entail the sa * some parameters related to the ARM environment to aid in locating the VM (example: location, resource group name, etc…) * the name of the VM on Azure -Please consider reviewing the general steps recommended to be performed before creating migration for an instance from Azure [here](../guides/preparing-a-vm-for-migration-replication.md). +Please consider reviewing the general steps recommended to be performed before creating migration for an instance from Azure [here](../../guides/preparing-a-vm-for-migration-replication.md). #### Steps performed by Coriolis diff --git a/source/plugins/microsoft-azure-azurestack-coriolis-plugin.md b/source/platforms/microsoft-azure-azurestack/microsoft-azure-azurestack-coriolis-plugin.md similarity index 96% rename from source/plugins/microsoft-azure-azurestack-coriolis-plugin.md rename to source/platforms/microsoft-azure-azurestack/microsoft-azure-azurestack-coriolis-plugin.md index 019056f..b0a72b1 100644 --- a/source/plugins/microsoft-azure-azurestack-coriolis-plugin.md +++ b/source/platforms/microsoft-azure-azurestack/microsoft-azure-azurestack-coriolis-plugin.md @@ -1,14 +1,14 @@ --- -title: "Microsoft Azure/AzureStack Coriolis Plugin" +title: "Microsoft Azure/AzureStack" wp_id: 38520 --- -# Microsoft Azure/AzureStack Coriolis Plugin +# Microsoft Azure/AzureStack **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, Coriolis guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. Only**Azure Stack Hub** is supported. Other Azure Stack offerings (including Azure Stack HCI, Azure Local, or similar solutions) are not available in Coriolis. -![](_static/images/azure-target-options.png) +![](../../_static/images/azure-target-options.png) ### Deployment requirements and supported Azure API versions @@ -26,11 +26,11 @@ The Coriolis Azure plugin only supports interacting with Azure through the Resou ### Azure as a source cloud -For more information regarding **[Azure as a source cloud](../platforms/azure-as-a-source-cloud.md)**, please check the documentation page. +For more information regarding **[Azure as a source cloud](../microsoft-azure-azurestack/azure-as-a-source-cloud.md)**, please check the documentation page. ### Azure as a destination cloud -For more information regarding **[Azure as a destination cloud](../platforms/azure-as-a-destination-cloud.md)**, please check the documentation page. +For more information regarding **[Azure as a destination cloud](../microsoft-azure-azurestack/azure-as-a-destination-cloud.md)**, please check the documentation page. ### Required permissions diff --git a/source/platforms/nutanix-as-a-source-cloud.md b/source/platforms/nutanix/nutanix-as-a-source-cloud.md similarity index 96% rename from source/platforms/nutanix-as-a-source-cloud.md rename to source/platforms/nutanix/nutanix-as-a-source-cloud.md index ca5c036..f7d2b6e 100644 --- a/source/platforms/nutanix-as-a-source-cloud.md +++ b/source/platforms/nutanix/nutanix-as-a-source-cloud.md @@ -1,13 +1,14 @@ --- title: "Nutanix as a source cloud" wp_id: 44200 +orphan: true --- # Nutanix as a source cloud Coriolis integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish communication between the platform and the Coriolis components. Using this type of architecture, **Coriolis** guarantees the connection to the supported platform set up to be used as a Source, as long as the requirements are met. -![](_static/images/source_options.png) +![](../../_static/images/source_options.png) ### Deployment requirements @@ -27,7 +28,7 @@ Nutanix Prism Central| >= 7.3 Coriolis requires the following connection parameters to access Nutanix Prism Central and migrate resources: -![](_static/images/image-20260826-092533.png) +![](../../_static/images/image-20260826-092533.png) Each parameter represents: @@ -46,7 +47,7 @@ Transfer Migrations from Nutanix operate in the same way Transfer Replicas do an #### Requirements: -Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from Nutanix [_here_](../guides/preparing-a-vm-for-migration-replication.md). +Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from Nutanix [_here_](../../guides/preparing-a-vm-for-migration-replication.md). #### Steps performed by Coriolis diff --git a/source/platforms/openstack-as-a-destination-cloud.md b/source/platforms/openstack/openstack-as-a-destination-cloud.md similarity index 99% rename from source/platforms/openstack-as-a-destination-cloud.md rename to source/platforms/openstack/openstack-as-a-destination-cloud.md index 242645d..15ea200 100644 --- a/source/platforms/openstack-as-a-destination-cloud.md +++ b/source/platforms/openstack/openstack-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "OpenStack as a destination cloud" wp_id: 38996 +orphan: true --- # OpenStack as a destination cloud @@ -47,7 +48,7 @@ In case a Floating IP Pool network is not visible to be selected, it can mean th The Floating IP Pool network must also carry the "router:external" property set, on the OpenStack side. -![](_static/images/openstack-target-new-1.jpg) +![](../../_static/images/openstack-target-new-1.jpg) ### OSMorphing steps taken when migrating/replicating to OpenStack @@ -64,7 +65,7 @@ Depending on the virtualization technology used and the OS release we are migrat * installing cloudbase-init and enabling cloudbase-init service * installing the VirtIO drivers if OpenStack is KVM-based -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. ### Preserve network settings for migrated VM diff --git a/source/platforms/openstack-as-a-source-cloud.md b/source/platforms/openstack/openstack-as-a-source-cloud.md similarity index 97% rename from source/platforms/openstack-as-a-source-cloud.md rename to source/platforms/openstack/openstack-as-a-source-cloud.md index a2e2c9c..bdde8c2 100644 --- a/source/platforms/openstack-as-a-source-cloud.md +++ b/source/platforms/openstack/openstack-as-a-source-cloud.md @@ -1,6 +1,7 @@ --- title: "OpenStack as a source cloud" wp_id: 38992 +orphan: true --- # OpenStack as a source cloud @@ -18,7 +19,7 @@ In the process of replicating from an OpenStack, Coriolis will clone locally the **Input**: the ID or name (if and only if it is unique in the given tenant) of the instance to be replicated. The instance can be booted either from a Cinder volume or directly from a Glance image. ```{note} -Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from OpenStack [here](../guides/preparing-a-vm-for-migration-replication.md). +Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from OpenStack [here](../../guides/preparing-a-vm-for-migration-replication.md). ``` #### Steps performed by Coriolis @@ -45,7 +46,7 @@ In the process of replicating from an OpenStack, Coriolis will use Cinder-backup **Input**: the ID or name (if and only if it is unique in the given tenant) of the instance to be replicated. The instance must be booted from a Cinder volume to replicate through Cinder backups. ```{note} -Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from OpenStack [here](../guides/preparing-a-vm-for-migration-replication.md). +Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from OpenStack [here](../../guides/preparing-a-vm-for-migration-replication.md). ``` #### Steps performed by Coriolis @@ -70,7 +71,7 @@ In the process of replicating from an OpenStack, Coriolis will use Cinder-snapsh **Input**: the ID or name (if and only if it is unique in the given tenant) of the instance to be replicated. The instance must be booted from a Cinder volume to replicate. Coriolis cannot replicate instances booted off of Glance images. ```{note} -Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from OpenStack [here](../guides/preparing-a-vm-for-migration-replication.md). +Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from OpenStack [here](../../guides/preparing-a-vm-for-migration-replication.md). ``` #### Steps performed by Coriolis @@ -93,9 +94,9 @@ Depending on the virtualization technology used and the OS release we are migrat In Windows instances, the recommendation is to manually uninstall the VirtIO drivers or any integration tools, given that the destination cloud is different from the source one. -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. -![](_static/images/openstack-source.jpg) +![](../../_static/images/openstack-source.jpg) ### OpenStack source environment parameters diff --git a/source/plugins/openstack-coriolis-plugin.md b/source/platforms/openstack/openstack-coriolis-plugin.md similarity index 95% rename from source/plugins/openstack-coriolis-plugin.md rename to source/platforms/openstack/openstack-coriolis-plugin.md index 58465b7..ecbbe3c 100644 --- a/source/plugins/openstack-coriolis-plugin.md +++ b/source/platforms/openstack/openstack-coriolis-plugin.md @@ -1,9 +1,9 @@ --- -title: "OpenStack Coriolis Plugin" +title: "OpenStack" wp_id: 38472 --- -# OpenStack Coriolis Plugin +# OpenStack **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish communication between the platform and the Coriolis components. Using this type of architecture, Coriolis guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. @@ -11,7 +11,7 @@ This section describes the functionality available via Coriolis' OpenStack plugi For a typical VMware to OpenStack migration scenario, here is a representation of the steps involved: -![](_static/images/openstack-vmware-migration-diagram.png) +![](../../_static/images/openstack-vmware-migration-diagram.png) ### Deployment requirements and supported OpenStack versions @@ -19,7 +19,7 @@ Coriolis needs network access to the API endpoints (either **public**, **interna Coriolis can also be hosted on the OpenStack cloud, to which it will be transferring to or from. -Refer to the [Network Ports Requirements page](../reference/coriolis-network-ports-requirements.md) for the full list of OpenStack services that Coriolis must be able to connect to. +Refer to the [Network Ports Requirements page](../../reference/coriolis-network-ports-requirements.md) for the full list of OpenStack services that Coriolis must be able to connect to. #### OpenStack as a Source (Ceph-snapshot-based exports) @@ -69,9 +69,9 @@ Coriolis will by default connect to the public endpoint URL of the above OpenSta For detailed information regarding OpenStack capabilities and performed steps while using it as a source or destination cloud, please check the following pages: -[**OpenStack as a source cloud**](../platforms/openstack-as-a-source-cloud.md) +[**OpenStack as a source cloud**](../openstack/openstack-as-a-source-cloud.md) -[**OpenStack as a destination cloud**](../platforms/openstack-as-a-destination-cloud.md) +[**OpenStack as a destination cloud**](../openstack/openstack-as-a-destination-cloud.md) ### OSMorphing worker images @@ -83,7 +83,7 @@ The images do **NOT** require any special Coriolis agent running in them and can **Windows**: the Windows image should have cloudbase-init installed and configured for the first boot. Coriolis will create a unique key pair for each migration/replication and use it to decrypt the unique password generated by cloudbase-init during the worker's boot. -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. ### Installing Coriolis as part of an existing OpenStack @@ -117,7 +117,7 @@ UEFI is supported in certain situations: ### Coriolis OpenStack Ceph integration -Coriolis also offers the option of Ceph backend storage to be used with the two features of **Ceph Snapshots** and **Ceph Backups** for **Replica and Migration** tasks. For more information on this option, please go to **[Coriolis OpenStack Ceph integration](../platform-notes/openstack-ceph-integration.md)** page. +Coriolis also offers the option of Ceph backend storage to be used with the two features of **Ceph Snapshots** and **Ceph Backups** for **Replica and Migration** tasks. For more information on this option, please go to **[Coriolis OpenStack Ceph integration](../../platform-notes/openstack-ceph-integration.md)** page. ### OpenStack platform specifics @@ -206,4 +206,4 @@ Each parameter represents: ### Known issues -Please check the **[Known issues page](../platform-notes/openstack-known-issues.md)** for some known issues and their workaround. +Please check the **[Known issues page](../../platform-notes/openstack-known-issues.md)** for some known issues and their workaround. diff --git a/source/plugins/oracle-cloud-infrastructure-oci-coriolis-plugin.md b/source/platforms/oracle-cloud-infrastructure-oci/oracle-cloud-infrastructure-oci-coriolis-plugin.md similarity index 97% rename from source/plugins/oracle-cloud-infrastructure-oci-coriolis-plugin.md rename to source/platforms/oracle-cloud-infrastructure-oci/oracle-cloud-infrastructure-oci-coriolis-plugin.md index 85fd039..61f4de0 100644 --- a/source/plugins/oracle-cloud-infrastructure-oci-coriolis-plugin.md +++ b/source/platforms/oracle-cloud-infrastructure-oci/oracle-cloud-infrastructure-oci-coriolis-plugin.md @@ -1,14 +1,14 @@ --- -title: "Oracle Cloud Infrastructure (OCI) Coriolis Plugin" +title: "Oracle Cloud Infrastructure (OCI)" wp_id: 38527 --- -# Oracle Cloud Infrastructure (OCI) Coriolis Plugin +# Oracle Cloud Infrastructure (OCI) **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, Coriolis guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. This section describes the functionality available via Coriolis' OCI plugin, enabling Coriolis to migrate (CMaaS) and replicate (DRaaS) instances to OCI. -![](_static/images/image-3.png) +![](../../_static/images/image-3.png) ### Deployment requirements @@ -71,7 +71,7 @@ By default, Coriolis automatically creates and cleans up all of the temporary re In cases where resource usage limitations are not a factor, or where the time cost outweighs the resource allocation costs, Coriolis offers the ability to pre-allocate the Minion Machines on source/destination platforms into so-called “Minion Machine Pools”. -For more information, please check the **[Minion Pools page](../features/coriolis-minion-pools-operations-and-usage.md)**. +For more information, please check the **[Minion Pools page](../../features/coriolis-minion-pools-operations-and-usage.md)**. ### OSMorphing steps taken when Migrating/Replicating to OCI @@ -94,11 +94,11 @@ The following other notable steps will be performed as part of the OSMorphing pr The OSMorphing worker images (governed by the **migr_image_map** option) which are used for temporary disk copy/OSMorphing VMs on OCI bear no special requirements and any generic Oracle Linux or Windows OCI image may be used as long as they have cloud-init or Cloudbase-init installed and configured for a first run. Windows worker image must be an English edition or set to use English as the system language. -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. ### Oracle Cloud Infrastructure user/group policy requirements -Coriolis allows users to choose two compartments when migrating to OCI, for more details regarding the compartments and their requirements, follow **[Oracle Cloud Infrastructure user/group policy requirements documentation](../platform-notes/oracle-cloud-infrastructure-user-group-policy-requirements.md)**. +Coriolis allows users to choose two compartments when migrating to OCI, for more details regarding the compartments and their requirements, follow **[Oracle Cloud Infrastructure user/group policy requirements documentation](../../platform-notes/oracle-cloud-infrastructure-user-group-policy-requirements.md)**. ### Oracle Cloud Infrastructure connection parameters diff --git a/source/platforms/oracle-linux-virtualization-manager-as-a-destination-cloud.md b/source/platforms/ovirt/ovirt-as-a-destination-cloud.md similarity index 96% rename from source/platforms/oracle-linux-virtualization-manager-as-a-destination-cloud.md rename to source/platforms/ovirt/ovirt-as-a-destination-cloud.md index 9bbafea..3cc380f 100644 --- a/source/platforms/oracle-linux-virtualization-manager-as-a-destination-cloud.md +++ b/source/platforms/ovirt/ovirt-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "oVirt as a destination cloud" wp_id: 43526 +orphan: true --- # oVirt as a destination cloud @@ -43,7 +44,7 @@ The **VM templates** need to have the IDs all zeroed, like the default **oVirt** The most common way to create the image Coriolis needs is to import 'as template' one of the images found in the '**ovirt-image-repository** ', as seen below -![](_static/images/olvm-image.jpg) +![](../../_static/images/olvm-image.jpg) Once the image is imported as a template, a new VM must be created using it and verify if '**qemu-guest-agent** ' is installed: @@ -75,7 +76,7 @@ On Windows, download the VirtIO drivers using the [**official archive**](https:/ #### Post-completion -After completing the **qemu-guest-agent** install, depending on the OS type selected **Linux or Windows**, follow the [**temporary worker**](../reference/coriolis-temporary-migration-worker.md) page for the completing steps. +After completing the **qemu-guest-agent** install, depending on the OS type selected **Linux or Windows**, follow the [**temporary worker**](../../reference/coriolis-temporary-migration-worker.md) page for the completing steps. **Note:** For Windows VMs, the temporary worker image version must be at least the same as the OS of the VM that needs to be migrated. @@ -115,12 +116,12 @@ Depending on the Coriolis configuration, the disk copy worker might have to do s The images do **NOT** require any special Coriolis agent running in them and can be images already available on oVirt, granted the following requirements: - * When Migrating a Windows VM, **[the temporary worker image](../reference/coriolis-temporary-migration-worker.md)** version used for the temporary worker**must be the same** as the one for the VM replicated/migrated or **newer**. + * When Migrating a Windows VM, **[the temporary worker image](../../reference/coriolis-temporary-migration-worker.md)** version used for the temporary worker**must be the same** as the one for the VM replicated/migrated or **newer**. * image must have **VirtIO drivers** and ovirt **guest agent/qemu guest agent** For VirtIO drivers, please follow the **[official page](https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/)** for download for the community drivers, or use the Oracle VirtIO drivers. ## Configuration Options -![](_static/images/olvm-target-options.png) +![](../../_static/images/olvm-target-options.png) Below is a listing of the configuration section needed when migrating/replicating to oVirt: diff --git a/source/platforms/ovirt-as-a-source-cloud.md b/source/platforms/ovirt/ovirt-as-a-source-cloud.md similarity index 96% rename from source/platforms/ovirt-as-a-source-cloud.md rename to source/platforms/ovirt/ovirt-as-a-source-cloud.md index 7020035..c250e66 100644 --- a/source/platforms/ovirt-as-a-source-cloud.md +++ b/source/platforms/ovirt/ovirt-as-a-source-cloud.md @@ -1,6 +1,7 @@ --- title: "oVirt as a source cloud" wp_id: 43569 +orphan: true --- # oVirt as a source cloud @@ -43,7 +44,7 @@ During a Replica/Migration process from oVirt, if the option to keep the static ### oVirt source environment parameters -![](_static/images/ovirt-source-options.png) +![](../../_static/images/ovirt-source-options.png) The source environment parameters are a set of source-cloud-specific parameters that offer some extra options to the migration/replication process on a per-VM basis. @@ -67,7 +68,7 @@ The following notable steps will be performed as part of the OSMorphing process * if not needed on the destination, the following packages will be uninstalled: cloud-init, qemu-guest-agent (or its legacy counterpart, ovirt-guest-agent) -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migraiton Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migraiton Worker](../../reference/coriolis-temporary-migration-worker.md)** page. ### Configuration Options diff --git a/source/plugins/ovirt-coriolis-plugin.md b/source/platforms/ovirt/ovirt-coriolis-plugin.md similarity index 95% rename from source/plugins/ovirt-coriolis-plugin.md rename to source/platforms/ovirt/ovirt-coriolis-plugin.md index c700578..4730e0a 100644 --- a/source/plugins/ovirt-coriolis-plugin.md +++ b/source/platforms/ovirt/ovirt-coriolis-plugin.md @@ -1,9 +1,9 @@ --- -title: "oVirt Coriolis Plugin" +title: "oVirt" wp_id: 40789 --- -# oVirt Coriolis Plugin +# oVirt ```{note} Both OLVM and RHEV are considered oVirt platforms in the Coriolis documentation pages and therefore all notes about the oVirt platform will apply to both the OLVM and RHEV providers. @@ -21,11 +21,11 @@ Coriolis supports environments running the oVirt engine starting from version 4. ### oVirt as a source cloud -For more information on using oVirt as a **source cloud** for Replica/Migration, please check the **[oVirt as a source cloud](../platforms/ovirt-as-a-source-cloud.md)** page. +For more information on using oVirt as a **source cloud** for Replica/Migration, please check the **[oVirt as a source cloud](../ovirt/ovirt-as-a-source-cloud.md)** page. ### oVirt as a destination cloud -For more information on using oVirt as a **destination cloud** for Replica/Migration, please check the **[oVirt as a destination cloud](../platforms/oracle-linux-virtualization-manager-as-a-destination-cloud.md)** page. +For more information on using oVirt as a **destination cloud** for Replica/Migration, please check the **[oVirt as a destination cloud](../ovirt/ovirt-as-a-destination-cloud.md)** page. ### Deployment requirements and supported oVirt engine versions diff --git a/source/platforms/proxmox-as-a-destination-cloud.md b/source/platforms/proxmox/proxmox-as-a-destination-cloud.md similarity index 97% rename from source/platforms/proxmox-as-a-destination-cloud.md rename to source/platforms/proxmox/proxmox-as-a-destination-cloud.md index a735fc6..02d5fbe 100644 --- a/source/platforms/proxmox-as-a-destination-cloud.md +++ b/source/platforms/proxmox/proxmox-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "Proxmox as a destination cloud" wp_id: 42900 +orphan: true --- # Proxmox as a destination cloud @@ -10,11 +11,11 @@ Migrations to Proxmox VE operate in the same way Replicas do and thus entail the ### Replicating (DRaaS) to Proxmox -![](_static/images/proxmox-target.png) +![](../../_static/images/proxmox-target.png) #### Requirements: -To **Replicate** to Proxmox VE, **VM templates** for temporary Coriolis workers are required. The templates need the following platform specifics in addition to **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)**. +To **Replicate** to Proxmox VE, **VM templates** for temporary Coriolis workers are required. The templates need the following platform specifics in addition to **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)**. In the case of Replicating or Migrating to Proxmox VE, images will need to be created for both Linux and Windows machines for the worker to create temporary VMs to perform the tasks. The template OS version must be at least the same as the VM OS that needs to be migrated. @@ -67,7 +68,7 @@ systemctl status qemu-guest-agent * **Template VM config** must have an **SCSI** controller bus attached - * for more information regarding Coriolis’ Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. + * for more information regarding Coriolis’ Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. #### User Role requirements diff --git a/source/plugins/proxmox-coriolis-plugin.md b/source/platforms/proxmox/proxmox-coriolis-plugin.md similarity index 91% rename from source/plugins/proxmox-coriolis-plugin.md rename to source/platforms/proxmox/proxmox-coriolis-plugin.md index c8840b8..83b12f0 100644 --- a/source/plugins/proxmox-coriolis-plugin.md +++ b/source/platforms/proxmox/proxmox-coriolis-plugin.md @@ -1,25 +1,25 @@ --- -title: "Proxmox Coriolis Plugin" +title: "Proxmox" wp_id: 42897 --- -# Proxmox Coriolis Plugin +# Proxmox **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, Coriolis guarantees the connection to the supported platform set up to be used as Destination, as long as the requirements are met. Coriolis supports Proxmox VE environments starting from version 8.0 and is compatible with newer releases up to 9.1. From these, the EOL versions are not actively tested and may experience issues. -![](_static/images/proxmox-target.png) +![](../../_static/images/proxmox-target.png) ### Proxmox as a destination cloud -For more information on using Proxmox as a **destination cloud** for Replica/MIgration, please check the **[Proxmox as a destination cloud](../platforms/proxmox-as-a-destination-cloud.md)** page. +For more information on using Proxmox as a **destination cloud** for Replica/MIgration, please check the **[Proxmox as a destination cloud](../proxmox/proxmox-as-a-destination-cloud.md)** page. ### Proxmox connection parameters In order to connect to an Proxmox cloud to perform a migration/replica to that cloud, the following connection parameters are required: -![](_static/images/proxmox_endpoint.png) +![](../../_static/images/proxmox_endpoint.png) #### Example of connection info JSON to be passed to the Proxmox plugin diff --git a/source/platforms/stackit-as-a-destination-cloud.md b/source/platforms/stackit/stackit-as-a-destination-cloud.md similarity index 99% rename from source/platforms/stackit-as-a-destination-cloud.md rename to source/platforms/stackit/stackit-as-a-destination-cloud.md index c8df023..1c4f6b0 100644 --- a/source/platforms/stackit-as-a-destination-cloud.md +++ b/source/platforms/stackit/stackit-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- -title: "StackIt as a destination cloud" +title: "STACKIT as a destination cloud" wp_id: 44279 +orphan: true --- # StackIt as a destination cloud @@ -43,7 +44,7 @@ The worker image OS version must be the same as or newer than the migrated insta When Replicating/Migrating a **Windows VM**, both **Linux and Windows images** have to be specified, as **Disk transferring** is performed using the Linux template and **OSMorphing** is performed using the Windows template. ``` -![](_static/images/image-5.png) +![](../../_static/images/image-5.png) ### OSMorphing steps taken when migrating/replicating to Stackit diff --git a/source/platforms/stackit-as-a-source-cloud.md b/source/platforms/stackit/stackit-as-a-source-cloud.md similarity index 97% rename from source/platforms/stackit-as-a-source-cloud.md rename to source/platforms/stackit/stackit-as-a-source-cloud.md index 92e4453..b7cefef 100644 --- a/source/platforms/stackit-as-a-source-cloud.md +++ b/source/platforms/stackit/stackit-as-a-source-cloud.md @@ -1,6 +1,7 @@ --- title: "StackIt as a source cloud" wp_id: 44263 +orphan: true --- # StackIt as a source cloud @@ -18,7 +19,7 @@ In the process of replicating from Stackit, Coriolis will clone locally the volu **Input**: the ID or name of the instance to be replicated. The instance is expected to be booted from volume, an error will be raised if ephemeral root disks are used since these cannot be exported. ```{note} -Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from Stackit [here](../guides/preparing-a-vm-for-migration-replication.md). +Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from Stackit [here](../../guides/preparing-a-vm-for-migration-replication.md). ``` #### Steps performed by Coriolis @@ -30,7 +31,7 @@ Please consider reviewing the general steps recommended to be performed before c After the above steps are completed, the contents of the disks will be transferred and written to disks on the destination via the destination cloud plugin. Only the changed data will be transferred to the destination cloud. -![](_static/images/stackit-source-options.png) +![](../../_static/images/stackit-source-options.png) ### Stackit source environment parameters diff --git a/source/plugins/stackit-coriolis-plugin.md b/source/platforms/stackit/stackit-coriolis-plugin.md similarity index 93% rename from source/plugins/stackit-coriolis-plugin.md rename to source/platforms/stackit/stackit-coriolis-plugin.md index 4618fe8..138cb23 100644 --- a/source/plugins/stackit-coriolis-plugin.md +++ b/source/platforms/stackit/stackit-coriolis-plugin.md @@ -1,13 +1,13 @@ --- -title: "StackIt Coriolis Plugin" +title: "STACKIT" wp_id: 44258 --- -# StackIt Coriolis Plugin +# STACKIT **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, **Coriolis** guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. -![](_static/images/stackit-source-options.png) ![](_static/images/image-5.png) +![](../../_static/images/stackit-source-options.png) ![](../../_static/images/image-5.png) ### Deployment requirements @@ -19,17 +19,17 @@ Stackit does not allow snapshotting ephemeral root disks, as such Coriolis can o ### StackIt as a source cloud -For more information on using StackIt as a **source cloud** for Replica/Migration, please check the **[StackIt as a source cloud](../platforms/stackit-as-a-source-cloud.md)** page. +For more information on using StackIt as a **source cloud** for Replica/Migration, please check the **[StackIt as a source cloud](../stackit/stackit-as-a-source-cloud.md)** page. ### StackIt as a destination cloud -For more information on using StackIt as a **destination cloud** for Replica/Migration, please check the **[StackIt as a destination cloud](../platforms/stackit-as-a-destination-cloud.md)** page. +For more information on using StackIt as a **destination cloud** for Replica/Migration, please check the **[StackIt as a destination cloud](../stackit/stackit-as-a-destination-cloud.md)** page. ### Stackit connection parameters Coriolis requires the following connection parameters in order to acces Stackit and migrate resources: -![](_static/images/stackit-endpoint.png) +![](../../_static/images/stackit-endpoint.png) Each parameter represents: diff --git a/source/platforms/suse-linux-kvm/suse-linux-kvm-plugin.md b/source/platforms/suse-linux-kvm/suse-linux-kvm-plugin.md new file mode 100644 index 0000000..66c4302 --- /dev/null +++ b/source/platforms/suse-linux-kvm/suse-linux-kvm-plugin.md @@ -0,0 +1,13 @@ +--- +title: "SUSE Linux KVM" +--- + +# SUSE Linux KVM + +**Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, **Coriolis** guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. + +## WORK IN PROGRESS + +**[SUSE Linux (KVM) as a destination cloud](../suse-linux-kvm/suse-linux-kvm-target-platform.md)** + +**[SUSE Linux (KVM) as a destination cloud (SAP HANA SKU)](../suse-linux-kvm/suse-linux-kvm-sap-hana-target-platform.md)** \ No newline at end of file diff --git a/source/platforms/suse-linux-kvm-sap-hana-target-platform.md b/source/platforms/suse-linux-kvm/suse-linux-kvm-sap-hana-target-platform.md similarity index 98% rename from source/platforms/suse-linux-kvm-sap-hana-target-platform.md rename to source/platforms/suse-linux-kvm/suse-linux-kvm-sap-hana-target-platform.md index df4f592..10e346f 100755 --- a/source/platforms/suse-linux-kvm-sap-hana-target-platform.md +++ b/source/platforms/suse-linux-kvm/suse-linux-kvm-sap-hana-target-platform.md @@ -1,3 +1,8 @@ +--- +title: "SUSE Linux (KVM) as a destination cloud (SAP HANA SKU)" +orphan: true +--- + # SUSE Linux (KVM) as a destination cloud (SAP HANA SKU) SAP HANA workloads require a separate licensing model and endpoint, which diff --git a/source/platforms/suse-linux-kvm-target-platform.md b/source/platforms/suse-linux-kvm/suse-linux-kvm-target-platform.md similarity index 98% rename from source/platforms/suse-linux-kvm-target-platform.md rename to source/platforms/suse-linux-kvm/suse-linux-kvm-target-platform.md index f9dcd2b..309a368 100644 --- a/source/platforms/suse-linux-kvm-target-platform.md +++ b/source/platforms/suse-linux-kvm/suse-linux-kvm-target-platform.md @@ -1,6 +1,7 @@ --- title: "SUSE Linux (KVM) as a destination cloud" wp_id: 43972 +orphan: true --- # SUSE Linux (KVM) as a destination cloud @@ -33,11 +34,11 @@ If an SSH private key is provided in the connection info, it must be base64-enco base64 -w0 ``` -![](_static/images/suse-linux-endpoint.png) +![](../../_static/images/suse-linux-endpoint.png) #### Transfer executions -![](_static/images/target-options.png) +![](../../_static/images/target-options.png) #### Steps performed by Coriolis @@ -102,7 +103,7 @@ Save the configuration and start a sysprep process, then shut down the Windows V Place the resulting QCOW2 disk image in a dir-type Libvirt storage pool on the destination host. -For more information regarding the Coriolis Worker image, please check the [_Coriolis Temporary Migration Worker_](../reference/coriolis-temporary-migration-worker.md) page. +For more information regarding the Coriolis Worker image, please check the [_Coriolis Temporary Migration Worker_](../../reference/coriolis-temporary-migration-worker.md) page. ## OSMorphing steps diff --git a/source/platforms/vmware-as-a-destination-cloud.md b/source/platforms/vmware/vmware-as-a-destination-cloud.md similarity index 97% rename from source/platforms/vmware-as-a-destination-cloud.md rename to source/platforms/vmware/vmware-as-a-destination-cloud.md index 2916c74..5984f6b 100644 --- a/source/platforms/vmware-as-a-destination-cloud.md +++ b/source/platforms/vmware/vmware-as-a-destination-cloud.md @@ -1,6 +1,7 @@ --- title: "VMware as a destination cloud" wp_id: 39837 +orphan: true --- # VMware as a destination cloud @@ -32,7 +33,7 @@ The templates need the following: * **VMWare tools** need to be installed * Configuration to a **network** with a **DHCP server**, a network which Coriolis can reach * **Template VM config** must have a **SCSI** controller bus attached - * for more information regarding Coriolis' Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. + * for more information regarding Coriolis' Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. #### Replica executions @@ -62,7 +63,7 @@ In the case of Replicating or Migrating to VMWare vSphere, there will need to be The template OS version must be at least the same as the OS of the VM that needs to be Replicated or Migrated. -**![](_static/images/vmware-target.jpg)** +**![](../../_static/images/vmware-target.jpg)** ### Required permissions in vCenter @@ -132,7 +133,7 @@ In the situation of creating a **Replica Deployment** using an existing **Replic #### Windows * install the VMWare drivers - * required tools and drivers. Instructions are found on the **[OS Morphing tools and drivers](../platform-notes/vmware-tools-and-drivers-for-osmorphing.md)** page. + * required tools and drivers. Instructions are found on the **[OS Morphing tools and drivers](../../platform-notes/vmware-tools-and-drivers-for-osmorphing.md)** page. ```{note} During the OSMorphing process, Coriolis will install only the drivers from the **VMware Tools ZIP file**. For full integration of the guest instance with the VMware platform, the user should install the VMware Tools after the instance migration is complete. Refer to the following VMware KB article for more details: [How to install VMware Tools (1014294)](https://kb.vmware.com/s/article/1014294) diff --git a/source/platforms/vmware-as-a-source-cloud.md b/source/platforms/vmware/vmware-as-a-source-cloud.md similarity index 96% rename from source/platforms/vmware-as-a-source-cloud.md rename to source/platforms/vmware/vmware-as-a-source-cloud.md index 4c67adb..e53ae35 100644 --- a/source/platforms/vmware-as-a-source-cloud.md +++ b/source/platforms/vmware/vmware-as-a-source-cloud.md @@ -1,6 +1,7 @@ --- title: "VMware as a source cloud" wp_id: 39836 +orphan: true --- # VMware as a source cloud @@ -56,7 +57,7 @@ Coriolis supports two mechanisms for exporting VMware virtual disks: * **OpenVixDiskLib** — This is the **default** export mechanism. **[OpenVixDiskLib](https://github.com/cloudbase/OpenVixDiskLib)** is Coriolis's own implementation of the VixDiskLib interface and is included in the Coriolis appliance. No additional installation or configuration is required. * **VMware VDDK** — Coriolis can alternatively use VMware's official **Virtual Disk Development Kit (VDDK)**. Using VDDK requires the user to **download and install VDDK separately in the Coriolis appliance** and configure Coriolis to use it. -**Note:** Before configuring Coriolis to use VDDK, follow the **[VDDK setup guide](../platform-notes/setting-up-the-vixdisklib-library.md)** to download, install, and configure the required VDDK components in the Coriolis appliance. +**Note:** Before configuring Coriolis to use VDDK, follow the **[VDDK setup guide](../../platform-notes/setting-up-the-vixdisklib-library.md)** to download, install, and configure the required VDDK components in the Coriolis appliance. #### Additional Requirements and Considerations @@ -64,7 +65,7 @@ Coriolis supports two mechanisms for exporting VMware virtual disks: * **DC1/somevmfolder/The VM** * For VMs located directly under the datacenter, the datacenter name can be omitted: **The VM** * **ESXi host name resolution:** The Coriolis virtual appliance must be able to resolve the **FQDNs of the ESXi hosts** registered with vSphere. If DNS resolution is not available, you can manually add the required FQDN entries to the Coriolis appliance's hosts file using the Coriolis console interface. - * **Network connectivity:** Ensure that the required network connectivity between the Coriolis appliance and the VMware infrastructure is available. See the [Network Ports Requirements](../reference/coriolis-network-ports-requirements.md) page for the required ports. + * **Network connectivity:** Ensure that the required network connectivity between the Coriolis appliance and the VMware infrastructure is available. See the [Network Ports Requirements](../../reference/coriolis-network-ports-requirements.md) page for the required ports. * **Static IP preservation:** If the migration is configured to keep the static IP addresses, VMware Tools must be installed and available on the source VM. The VM must also be **powered on at least once** while Coriolis collects VM information from the source VM (which happens on any Transfer Execution or Transfer Update). If the VM is required to be powered off for transfer, users must use the **Shutdown Instance** execution option instead of manually shutting down. * **Third-party backup software:** If third-party backup software uses or locks **VSS** on Windows source VMs, consider temporarily pausing the backup software for the duration of the migration. This includes backup solutions that install an agent inside the Windows VM. @@ -72,7 +73,7 @@ Before creating and executing a Replica or Migration from vSphere, review the re ### VMWare source environment parameters -![](_static/images/image_2026-09-14_144911260.png) +![](../../_static/images/image_2026-09-14_144911260.png) ### OSMorphing steps taken when migrating/replicating from vSphere/ESXi @@ -87,7 +88,7 @@ The following notable steps will be performed as part of the OSMorphing process * uninstall the VMWare guest tools and drivers -For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../reference/coriolis-temporary-migration-worker.md)** page. +For more information regarding the Coriolis Worker template, please check the **[Coriolis Temporary Migration Worker](../../reference/coriolis-temporary-migration-worker.md)** page. ### Required permissions in vCenter diff --git a/source/plugins/vmware-coriolis-plugin.md b/source/platforms/vmware/vmware-coriolis-plugin.md similarity index 92% rename from source/plugins/vmware-coriolis-plugin.md rename to source/platforms/vmware/vmware-coriolis-plugin.md index 28b529d..10ca6db 100644 --- a/source/plugins/vmware-coriolis-plugin.md +++ b/source/platforms/vmware/vmware-coriolis-plugin.md @@ -1,9 +1,9 @@ --- -title: "VMWare Coriolis Plugin" +title: "VMWare" wp_id: 38507 --- -# VMWare Coriolis Plugin +# VMWare **Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, Coriolis guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. VMware platform is supported via Coriolis Plugins as a stand-alone ESXi (source-only) and VMware vSphere. @@ -12,7 +12,7 @@ VMware platform is supported via Coriolis Plugins as a stand-alone ESXi (source- VMware Tools should be installed and updated to the latest current version available on the source VMs. -![](_static/images/fcd.jpg) +![](../../_static/images/fcd.jpg) ### Deployment requirements and supported vSphere/ESXi versions @@ -32,7 +32,7 @@ In a vSphere environment, the Coriolis virtual appliance must be able to connect The Coriolis virtual appliance must be able to resolve the FQDNs of the ESXi hosts if they are enrolled under vSphere. ``` -Refer to the [Network Ports Requirements page](../reference/coriolis-network-ports-requirements.md) for more details. +Refer to the [Network Ports Requirements page](../../reference/coriolis-network-ports-requirements.md) for more details. ### Supported versions @@ -40,11 +40,11 @@ Coriolis supports VMware vSphere (vCenter/ESXi) environments starting from versi ### vSphere as a source cloud -For more information on using vSphere/ESXi as a **source cloud** for Replica/MIgration, please check the **[VMware as a source cloud](../platforms/vmware-as-a-source-cloud.md)** page. +For more information on using vSphere/ESXi as a **source cloud** for Replica/MIgration, please check the **[VMware as a source cloud](../vmware/vmware-as-a-source-cloud.md)** page. ### vSphere as a destination cloud -For more information on using vSphere/ESXi as a **destination cloud** for Replica/MIgration, please check the **[VMware as a destination cloud](../platforms/vmware-as-a-destination-cloud.md)** page. +For more information on using vSphere/ESXi as a **destination cloud** for Replica/MIgration, please check the **[VMware as a destination cloud](../vmware/vmware-as-a-destination-cloud.md)** page. ### vSphere/ESXi connection parameters @@ -86,4 +86,4 @@ Storage identification scheme| Names of datastore hosting the virtual disks(s)| ### VMware Coriolis plugin known issues -For further information regarding the VMware Plugin's known issues, please check the **[documentation page](../platform-notes/vmware-plugin-known-issues.md)**. +For further information regarding the VMware Plugin's known issues, please check the **[documentation page](../../platform-notes/vmware-plugin-known-issues.md)**. diff --git a/source/plugins/index.md b/source/plugins/index.md deleted file mode 100644 index d7e8d44..0000000 --- a/source/plugins/index.md +++ /dev/null @@ -1,20 +0,0 @@ -# Plugins - -```{toctree} -:maxdepth: 1 -:titlesonly: - -vmware-coriolis-plugin -openstack-coriolis-plugin -kubevirt-harvester-coriolis-plugin -hyper-v-coriolis-plugin -amazon-web-services-aws-coriolis-plugin -microsoft-azure-azurestack-coriolis-plugin -microcloud-lxd-coriolis-plugin -proxmox-coriolis-plugin -oracle-cloud-infrastructure-oci-coriolis-plugin -oracle-cloud-infrastructure-classic-oci-c-opc-coriolis-plugin -ovirt-coriolis-plugin -stackit-coriolis-plugin -coriolis-bare-metal-hub-plugin -``` diff --git a/source/reference/coriolis-eula.md b/source/reference/coriolis-eula.md deleted file mode 100644 index e657db9..0000000 --- a/source/reference/coriolis-eula.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: "Coriolis® EULA" -wp_id: 40972 ---- - -# Coriolis® EULA - -## CORIOLIS® END-USER LICENSE AGREEMENT -## (Click Through License) - -This End-User License Agreement (“EULA”) is a legal agreement between you (either an individual or a legal entity) and Cloudbase Solutions S.R.L., a Romanian LLC with legal address at Memorandului Street, no. 76-78-80, apt. 38, Timisoara, Timiș County, Romania, (“Licensor”) for the software, which may also include associated media, printed materials, and “online” or electronic documentation (collectively the “Software”). “Software” shall also include all related documentation. - -**BY CLICKING THE ACCEPT BUTTON BELOW, OR BY DOWNLOADING, INSTALLING, OR OTHERWISE USING THE SOFTWARE YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA.** IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS EULA, THEN DO NOT CLICK THE ACCEPT BUTTON, INSTALL, DOWNLOAD, OR USE THE SOFTWARE. IF YOU CLICK THE ACCEPT BUTTON OR INSTALL, DOWNLOAD OR USE THE SOFTWARE, THE TERMS AND CONDITIONS OF THIS EULA ARE FULLY ACCEPTED BY YOU. If you agree to these terms on behalf of an organization, you hereby represent to Licensor that you are authorized to accept these terms on its behalf. - -IF YOU DO NOT ACCEPT THE TERMS OF THIS EULA, CLICK THE “DECLINE” OR “CANCEL” BUTTON AND DO NOT INSTALL, DOWNLOAD OR USE THE SOFTWARE. - - 1. **GRANT OF LICENSE.** - -Licensor grants you the following rights provided that you comply with all terms and conditions of this EULA: - -(a) Grant. Licensor hereby grants you a non-exclusive, non-transferable license, without rights to sublicense, to use the object code of the Software solely for your internal business purposes, provided such purpose is in accordance with the permitted uses of the Software as set forth in this EULA and the purpose for which the Software was designed as set forth in the applicable documentation for the Software, and to the extent permitted by your payment of applicable license fees. You may use the documentation accompanying the Software in connection with permitted uses of the Software. - -(b) Installation and Use. A single license agreement covers multiple instances of the Software, with the number of permitted instances defined by the license tier. Multiple activation keys may be issued under one license. - -(c) Copies. For each machine you intend to use you will be able to download and install one copy. Upon installation, an ID will be generated. Based on the ID you will receive an activation key that will allow you to use the software for the purchased number of operations/migrations. Each licensed copy of the Software may be installed and used on the number of computers permitted by your license agreement. You may not make a copy of the Software available on a network where it could be used by multiple users at the same time. You may not make the Software available over a network where it could be downloaded by multiple users. You may make a single copy of the Software for backup purposes, provided such copy is not installed or used on any computer. At the time of registration of the Software, you may only register and put in use the most current version of the Software. - - 2. **TRIAL LICENSES.** - -(a) General. If available, the Software may be activated with no-cost evaluation Software License Key(s). - -(b) Evaluation License. If you activate the Software with an evaluation Software License Key (“Evaluation Product”) you may use the Evaluation Product for the duration (Trial Period) and the number of operations/migrations granted by the Licensor and defined by the license key, only to evaluate the suitability of the Evaluation Product for licensing on a for-fee basis. The evaluation license should not be used for production workloads or other real-life work operations. - -(c) Trial Limitations. If the Software was provided to you at no charge on a trial or evaluation basis, then the Software may be used only for the Trial Period and only for the allowed number of operations/migrations, unless you purchase a further license to the Software at the end of the Trial Period. - -(d) THE EVALUATION PRODUCT IS PROVIDED TO YOU “AS IS” WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE. LICENSOR BEARS NO LIABILITY FOR ANY DAMAGES RESULTING FROM USE (OR ATTEMPTED USE) OF THE EVALUATION PRODUCT THROUGH AND AFTER THE TRIAL PERIOD. - -(e) No Support. The licensor has no duty to provide support to you during your use of the Evaluation Product. - - 3. **RESERVATION OF RIGHTS AND OWNERSHIP.** - -The Software is licensed, and not sold, to you for use only under the terms of this EULA. The Software is protected by copyright and other intellectual property laws and treaties. Licensor or its suppliers own the title, copyright, and other intellectual property rights in the Software. Except as expressly licensed to you herein, Licensor and its suppliers’ reserve all right, title, and interest in the Software and all associated copyrights, trademarks, and other intellectual property rights therein. The EULA is limited to the intellectual property rights of the Licensor and its suppliers in the Software and does not include any rights to other intellectual property. - - 4. **LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION, AND DISASSEMBLY.** - -You may not reverse engineer, decompile, or disassemble the Software by any means whatsoever, or alter, modify, enhance, or create a derivative work of the Software. You may not remove, alter, or obscure any product identification, copyright, or other intellectual property notices in the software. - - 5. **NO RENTAL/COMMERCIAL HOSTING.** - -You may not rent, lease, lend or provide services with the Software for third parties. You may not use the Software to provide commercial services to third parties. Service providers or resellers wishing to offer the Software as part of a managed or hosted service must enter into a separate written Service Provider Agreement with the Licensor prior to any such use. - - 6. **CONSENT TO USE OF DATA.** - -Licensor processes certain technical data (such as software version, system configuration, and usage statistics) to operate, maintain, and improve the Software. All processing of personal data, where applicable, is carried out in accordance with Regulation (EU) 2016/679 (General Data Protection Regulation — GDPR) and any applicable national data protection laws, including Law No. 190/2018 of Romania. The legal basis for processing technical data is Licensor’s legitimate interest in ensuring product quality, security, and licence compliance (Article 6(1)(f) GDPR), or performance of the contract where applicable (Article 6(1)(b) GDPR). Where personal data is processed, you are entitled to exercise your rights of access, rectification, erasure, restriction of processing, data portability, and objection, as well as the right to lodge a complaint with the relevant supervisory authority (in Romania: Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal — ANSPDCP). For full information on how Licensor processes personal data, retention periods, and cross-border transfer safeguards, please refer to the Licensor’s Privacy Policy, available at the Licensor’s official website before installation of the Software. - - 7. **TRANSFER.** - -During active support periods, after the initial installation, you cannot copy/move the Software to a different Workstation Computer; such transfer may require you to contact Licensor to effectuate such transfer. If such a transfer takes place with the Licensor’s approval and support, you must completely remove the Software from the former/initial Workstation/ Computer after the transfer. NOTWITHSTANDING THE FOREGOING, YOU MAY NOT TRANSFER EVALUATION PRODUCTS OR PRE-RELEASE COPIES OF THE SOFTWARE. YOU MAY NOT SUBLICENSE, RENT OR LEASE YOUR RIGHTS IN THE SOFTWARE OR AUTHORIZE ANY PORTION OF THE SOFTWARE TO BE COPIED EXCEPT AS MAY BE EXPRESSLY PERMITTED IN THIS EULA. - - 8. **TERMINATION.** - -This EULA is granted for a fixed period and for limited usage. It will come into force on the activation date and will continue in force for the granted term or until complete usage, whichever comes first unless terminated otherwise. - -This EULA is effective until terminated. Your rights under this EULA will terminate immediately and automatically if you fail to comply with any of the terms and conditions of this EULA. Promptly upon termination, you must cease all use of the Software, destroy all copies of the Software in your possession or control, and, upon request of Licensor, certify such destruction. Licensor’s termination of this EULA will not limit any of Licensor’s other rights or remedies at law or in equity. - - 9. **ADDITIONAL SOFTWARE/SERVICES.** - -This EULA applies to updates, supplements, add-on components, or Internet-based services components, of the Software that Licensor may provide to you or make available to you after the date you obtain your initial copy of the Software unless we provide other terms along with the update, supplement, add-on component, or Internet-based services component. Licensor reserves the right to discontinue any Internet-based services provided to you or made available to you through the use of the Software. - - 10. **UPGRADES.** - -To use Software identified as an upgrade, you must first be licensed for the Software identified by Licensor as eligible for the upgrade. Except as otherwise provided in writing, after upgrading, you may no longer use the Software that formed the basis for your upgrade eligibility. - - 11. **SUPPORT AND SUBSCRIPTION SERVICES ARE NOT INCLUDED.** - -The licensor will not provide any support services under this EULA. Support services may be purchased separately pursuant to a dedicated Support Agreement, which may define service levels including, but not limited to, 8×5 and 24×7 support tiers. Unless a valid Support Agreement is in effect, you are not entitled to software upgrades, patches, or new versions of the Software. This EULA does not give you any rights to any updates or upgrades to the Software or to any extensions or enhancements to the Software developed by Licensor at any time in the future. Licensor may offer support services separately. Any supplemental software code or related materials that the Licensor provides to you as part of any support services are to be considered part of the Software and are subject to the terms and conditions of this EULA. - - 12. **EXPORT RESTRICTIONS.** - -You acknowledge that the Software is subject to various European and national and international export control regulations jurisdiction. You agree to comply with all applicable national and international (re-) export control regulations. In any event of such transfer and/or use of the software you shall comply with the (re-) export control regulations of Romania, of the European Union, and of the United States of America. - - 13. **WARRANTY OF TITLE.** - -Licensor warrants that it owns and/or has the right to license the Software. - - 14. **DISCLAIMER OF WARRANTIES.** - -The express warranty in SECTION 13 IS in lieu of all other warranties, express, implied, or statutory, regarding the SOFTWARE AND DOCUMENTATION, including any warranties of merchantability and fitness for a particular purpose. YOU acknowledge that YOU HAVE NOT relied on ANY warranties other than the express warranty SET FORTH in SECTION 13 Licensor DOES NOT WARRANT THAT THE USE OR OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE. - - 15. **INTELLECTUAL PROPERTY INFRINGEMENT CLAIMS.** - -15.1 **Indemnification Against Liability for Infringement.** Licensor shall indemnify you against all liabilities, claims and legal costs (including reasonable attorney fees) paid to or for the benefit of a third party arising from any third-party claim or suit alleging that the Software infringes: (i) any copyright; (ii) the trade secret or trademark rights of any third party; or iii) any patent or registered design right existing on the date the Software in question is delivered to you, in any jurisdiction where Licensor is authorized to conduct business. You shall promptly notify Licensor in writing of any such third-party claim. No failure to so notify Licensor shall relieve Licensor of its obligations under this Agreement except to the extent that Licensor can demonstrate damages attributable to such failure. Licensor shall be entitled to have sole control over the defense and settlement of such claim; provided that (i) you shall be entitled to participate in the defense of such claim and to employ counsel at your own expense to assist in the handling of such claim, and (ii) Licensor shall obtain the prior written approval from you before entering into any settlement of such claim or ceasing to defend against such claim if such settlement or cessation would cause injunctive or other equitable relief to be imposed against you. - -15.2**Limitations on Indemnification.** Licensor shall have no liability for, and shall not indemnify you against, any infringement claim resulting from: (i) modification of any Software; (ii) combination of any Software with hardware, software or other intellectual property provided by anyone other than Licensor; (iii) use of a superseded or altered release of some or all of the Software or any modification thereof furnished under this EULA including, but not limited to, your failure to use corrections, fixes, or enhancements made available by Licensor; or (iv) use of any Software in any manner not expressly contemplated hereunder. - -15.3**Repair or Replacement of Infringing Software.** In the event of a third-party infringement claim, Licensor shall, at its sole election and expense: (i) procure for you the right to continue to use the Software pursuant to this EULA; (ii) replace or modify the Software to make it non-infringing while still complying with the terms of this EULA; or (iii) if none of the above options is reasonably available, refund the license fees associated with the infringing portion of the Software, minus depreciation based on a three-year useful life. - -15.4**Applicability to Third Party Products.** Licensor makes no representations or warranties and provides no indemnification or replacement covenants of any kind with respect to Third Party Products. Licensor’s sole responsibility as to Third Party Products is to pass through any intellectual property warranties, indemnification, and replacement provisions that Licensor receives from the vendors or suppliers of such Third-Party Products and which Licensor is allowed to pass on. “**Third Party Product**” means application software products provided by third-party vendors, including the operating system and application software with which the Software interfaces and which provides certain functionality essential to the operation of the Software. - -15.5 **EXCEPT AS OTHERWISE PROVIDED HEREIN,** Sections 15.1 through 15.4 state Licensor’s AND ITS THIRD-PARTY SUPPLIERS’ entire liability and CLIENT’s exclusive remedy for claims of infringement of intellectual property rights. - - 16. **OPEN-SOURCE DISCLOSURE.** - -Notwithstanding the foregoing license grant, you acknowledge that certain components of the software may be covered by so-called “open source” software licenses, which means any software licenses by the Open Source Initiative or any substantially similar licenses, including without limitation any license that, as a condition of distribution of the software licensed under such license, requires that the distributor make the software available in source code format (such components, “Open Source Components”). The licensor will provide a list of Open-Source Components for a particular version of the Software upon your request, iii) any patent or registered design right existing on the date the Software in question is delivered to you, in any jurisdiction where Licensor is authorized to conduct business. To the extent required by the licenses covering Open-Source Components, the terms of such licenses will apply in lieu of the terms of this Eula. By accepting the terms of this EULA, you are accepting the terms of the open-source license agreements, that govern the use of such open-source software, including all disclaimers of warranty and limitations of liability set forth therein. - - 17. **EXCLUSION OF INCIDENTAL, CONSEQUENTIAL, AND CERTAIN OTHER DAMAGES.** - -TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL LICENSOR OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS EULA, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE), MISREPRESENTATION, STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF LICENSOR OR ANY SUPPLIER, AND EVEN IF LICENSOR OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - - 18. **LIMITATION OF LIABILITY AND REMEDIES.** - -Notwithstanding any damages that you might incur for any reason whatsoever (including, without limitation, all damages referenced herein and all direct or general damages in the contract or anything else), the entire liability of the Licensor and any of its suppliers under any provision of this EULA and your exclusive remedy hereunder (except for any remedy of repair or replacement elected by Licensor) shall be limited to actual, direct damages up to the amount actually paid by you for the Software. The foregoing limitations, exclusions, and disclaimers (including Sections 14, 15, 16, and 17) shall apply to the maximum extent permitted by applicable law, even if any remedy fails its essential purpose. - - 19. **APPLICABLE LAW.** - -This EULA will be governed by the laws of Romania. Unless expressly waived by the Licensor in writing for the particular instance or contrary to local law, the sole and exclusive jurisdiction and venue for actions related to the subject matter hereof shall be the Timișoara relevant court. Both parties consent to the jurisdiction of such courts and agree that the process may be served in the manner provided herein for giving of notices or otherwise as allowed by Romanian law. The parties agree that the UN Convention on Contracts for the International Sale of Goods shall not apply to this EULA nor to any dispute or transaction arising out of this EULA. - -Notwithstanding the foregoing, for disputes arising between Licensor and licensees domiciled or established outside Romania, the parties may by mutual written agreement submit their dispute to binding arbitration under the Rules of Arbitration of the International Chamber of Commerce (ICC) or under the UNCITRAL Arbitration Rules, with the seat of arbitration to be agreed by the parties. Nothing in this section shall prevent either party from seeking urgent injunctive or interim relief before any court of competent jurisdiction. - - 20. **FOREIGN CORRUPT PRACTICES ACT (FCPA) COMPLIANCE STATEMENT** - -The Licensor warrants that it, including its officers, directors, employees, and agents, have complied at all times, and are in compliance, with all applicable laws, including but not limited to anti-bribery measures enacted by the Romanian laws. The Licensor also agrees not to: - -**(i)** take any action that would violate the Anti-Bribery Laws; or **(ii)** pay, offer or promise to pay, or authorize the payment, directly or indirectly, of any money or anything of value to any individual for the purpose of influencing any act or decision, including forbearance from action, of the individual in connection with the activities of the Licensor under the existing written or verbal distributor agreement. - -20.1. The Licensor further warrants that it, including its officers, directors, employees, and agents, has complied at all times, and complies, with the Foreign Corrupt Practices Act of 1977 (FCPA) and other jurisdictions which may be related to the activities covered under the existing written or verbal distributor agreement. Licensor also agrees not to pay, offer or promise to pay, or authorize the payment, directly or indirectly, of any money or anything of value, to: - -**(i)** any foreign official (as such term is defined in the United States Foreign Corrupt Practices Act of 1977 (FCPA), for the purpose of influencing any official act or decision of such official or inducing him or her to use his or her influence to affect any act or decision of governmental authority; **(ii)** any foreign political party or official thereof or candidate for foreign political office for the purpose of influencing or inducing any official act or decision of such party, official, or candidate to use his, her, or its influence to affect any act or decision of a foreign governmental authority. The Licensor also agrees not to take any action that would violate any applicable anti-bribery or anti-corruption laws of Romania. - - 21. **ENTIRE AGREEMENT; SEVERABILITY.** - -This Agreement sets forth the Licensor’s entire liability and your exclusive remedy with respect to the Software and supersedes the terms of any purchase orders and any other communications or advertising with respect to the Software. You acknowledge that this Agreement is a complete statement of the agreement between you and Licensor with respect to the Software and that there are no other prior or contemporaneous understandings, promises, representations, or descriptions with respect to the Software. No amendment to or modification of this EULA will be binding unless made in writing and signed by the Licensor. No failure to exercise and no delay in exercising, on the part of either party, any right or any power hereunder shall operate as a waiver thereof, nor shall any single or partial exercise of any right or power hereunder preclude further exercise of any other right hereunder. If any provision of this EULA is held to be void, invalid, unenforceable, or illegal, the other provisions shall continue in full force and effect the invalid, unenforceable, or illegal provision shall be amended to achieve as closely as possible the effect of the original term. - - 22. **INJUNCTIVE RELIEF.** - -You agree that a breach of this EULA adversely affecting the Licensor’s proprietary rights in the Software may cause irreparable injury to the Licensor for which monetary damages would not be an adequate remedy and the Licensor shall be entitled to seek equitable relief in addition to any remedies it may have hereunder or at law. - - 23. **CONFIDENTIAL INFORMATION.** - -You acknowledge and agree that the Software and all information emanating from the Software and Licensor’s business in any form are valuable trade secrets of the Licensor and “Confidential Information.” You agree that you will not, during or after the term of this Agreement, permit the duplication, use, or disclosure of any such Confidential Information to any person (other than your employees, agents, or representatives), unless such duplication, use, or disclosure is specifically authorized by Licensor in writing prior to any disclosure. You shall use reasonable diligence and in no event less than that degree of care that you use in respect to your own confidential information of like nature, to prevent the unauthorized disclosure or reproduction of the Confidential Information. Without limiting the generality of the foregoing, to the extent that this Agreement permits the copying of Confidential Information, all such copies shall bear the same confidentiality notices, legends, and intellectual property rights designations that appear in the original versions and the party shall keep detailed records of the location of all Confidential Information. - - 24. **SURVIVAL.** - -The provisions of this Section and Sections 3, 6, 8, 14, 16, 17, 18, 20, 21, 22, 23, 25, 26, and 27 shall survive termination or expiration of this Agreement, for any reason. - - 25. **PRE-MIGRATION BACKUP OBLIGATION.** - -Before initiating any migration operation using the Software, you are solely responsible for creating a complete and verified backup of all data, applications, virtual machines, workloads, and configurations in the source environment. The Software will display a prominent notification recommending such backup prior to commencing any migration. Licensor shall not be liable for any data loss, corruption, or service disruption arising from your failure to maintain adequate backups prior to using the Software. - - 26. **FORCE MAJEURE.** - -Neither party shall be liable for any delay or failure in performing its obligations under this EULA to the extent that such delay or failure is caused by events beyond its reasonable control, including but not limited to acts of God, war, terrorism, pandemic, earthquake, fire, flood, governmental action, or failure of third-party infrastructure (force majeure events). The affected party shall promptly notify the other party of the force majeure event and use reasonable efforts to mitigate its effects. - - 27. **GOVERNING LANGUAGE.** - -This EULA is made in the English language. If this EULA is translated into any other language, the English-language version shall prevail in the event of any inconsistency or conflict between the translations, to the extent permitted by applicable law. diff --git a/source/reference/coriolis-release-notes.md b/source/reference/coriolis-release-notes.md index 35c7aa2..0c68614 100644 --- a/source/reference/coriolis-release-notes.md +++ b/source/reference/coriolis-release-notes.md @@ -1,6 +1,7 @@ --- title: "Coriolis Release Notes" wp_id: 40587 +tocdepth: 2 --- # Coriolis Release Notes diff --git a/source/reference/index.md b/source/reference/index.md index 591308f..d4d6d07 100644 --- a/source/reference/index.md +++ b/source/reference/index.md @@ -17,5 +17,5 @@ coriolis-replica-migration-cli-parameters coriolis-troubleshooting coriolis-release-notes coriolis-roadmap -coriolis-eula +Coriolis EULA ``` From 6926bbe87a8823b6921e0df325a33ffdf696c897 Mon Sep 17 00:00:00 2001 From: amanolache Date: Fri, 16 Oct 2026 15:33:42 +0300 Subject: [PATCH 2/2] Fixed wrong linked md files. --- ...iolis-minion-pools-operations-and-usage.md | 2 +- .../coriolis-shared-disks-migrations.md | 2 +- source/guides/coriolis-getting-started.md | 36 ++++++------- .../platform-notes/openstack-known-issues.md | 2 +- ...amazon-web-services-aws-coriolis-plugin.md | 4 +- .../cloudstack/cloudstack-coriolis-plugin.md | 11 ++++ source/platforms/index.md | 2 + .../nutanix/nutanix-coriolis-plugin.md | 11 ++++ .../stackit/stackit-as-a-destination-cloud.md | 54 +++++++++---------- .../stackit/stackit-as-a-source-cloud.md | 32 +++++------ .../stackit/stackit-coriolis-plugin.md | 44 +++++++-------- .../vmware/vmware-coriolis-plugin.md | 4 +- source/reference/coriolis-release-notes.md | 2 +- ...tep-guide-vmware-to-openstack-migration.md | 4 +- 14 files changed, 117 insertions(+), 93 deletions(-) create mode 100644 source/platforms/cloudstack/cloudstack-coriolis-plugin.md create mode 100644 source/platforms/nutanix/nutanix-coriolis-plugin.md diff --git a/source/features/coriolis-minion-pools-operations-and-usage.md b/source/features/coriolis-minion-pools-operations-and-usage.md index b878af0..0d5118b 100644 --- a/source/features/coriolis-minion-pools-operations-and-usage.md +++ b/source/features/coriolis-minion-pools-operations-and-usage.md @@ -95,6 +95,6 @@ The parameters for Source Options are the following: * If set to **Ceph Backups**: Coriolis will create a Cinder backup and will connect to the source Ceph via RADOS and retrieve chunks of disks. * if set to **Ceph snapshots**: Coriolis will create a Cinder snapshot for the disks and fetch the diff chunks from the source Ceph. -The steps that follow the ones mentioned above are identical to **[OpenStack Replica/Migration](../platforms/openstack-as-a-destination-cloud.md)**. +The steps that follow the ones mentioned above are identical to **[OpenStack Replica/Migration](../platforms/openstack/openstack-as-a-destination-cloud.md)**. Coriolis Minion Pools can also be fully managed using CLI. For more information, please check **[Coriolis CLI](../reference/coriolis-cli.md)** page. diff --git a/source/features/coriolis-shared-disks-migrations.md b/source/features/coriolis-shared-disks-migrations.md index 45b3501..842289f 100644 --- a/source/features/coriolis-shared-disks-migrations.md +++ b/source/features/coriolis-shared-disks-migrations.md @@ -9,7 +9,7 @@ Some workloads attach the same disk to multiple virtual machines at the same tim Coriolis supports migrating these workloads as a single clustered transfer. Coriolis identifies each shared disk once, transfers its data once, and then attaches the migrated disk to every destination instance that requires it. -This section describes destination-side behavior and the end-to-end requirements for migrating shared disks. For source-side export behavior affecting disks that cannot use Changed Block Tracking (CBT), including shared disks and disks configured in VMware Independent mode, see [**Disks that do not support CBT**](../platforms/vmware-as-a-source-cloud.md#disks-that-do-not-support-cbt). +This section describes destination-side behavior and the end-to-end requirements for migrating shared disks. For source-side export behavior affecting disks that cannot use Changed Block Tracking (CBT), including shared disks and disks configured in VMware Independent mode, see [**Disks that do not support CBT**](../platforms/vmware/vmware-as-a-source-cloud.md#disks-that-do-not-support-cbt). ```{note} All source VMs that share a disk must be powered off during Transfer Execution. diff --git a/source/guides/coriolis-getting-started.md b/source/guides/coriolis-getting-started.md index 5ad87eb..4ceb9c6 100644 --- a/source/guides/coriolis-getting-started.md +++ b/source/guides/coriolis-getting-started.md @@ -179,28 +179,28 @@ For more information regarding each supported platform, please check the corresp
diff --git a/source/platform-notes/openstack-known-issues.md b/source/platform-notes/openstack-known-issues.md index f9dfcb4..f1ba9dc 100644 --- a/source/platform-notes/openstack-known-issues.md +++ b/source/platform-notes/openstack-known-issues.md @@ -41,4 +41,4 @@ To have it fixed, use config drive to send metadata to the temporary disk copy/O The parameter for the above example is **migr_worker_use_config_drive**, and it is part of the OpenStack destination environment parameters. -Please refer to the JSON file example mentioned under Openstack destination environment parameters on **[OpenStack main documentation page.](../platforms/openstack-as-a-destination-cloud.md)** +Please refer to the JSON file example mentioned under Openstack destination environment parameters on **[OpenStack main documentation page.](../platforms/openstack/openstack-as-a-destination-cloud.md)** diff --git a/source/platforms/amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin.md b/source/platforms/amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin.md index 41022bf..f688db1 100644 --- a/source/platforms/amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin.md +++ b/source/platforms/amazon-web-services-aws/amazon-web-services-aws-coriolis-plugin.md @@ -43,11 +43,11 @@ Each parameter represents: ### AWS as a source cloud -For more information on using AWS as a **source cloud** for Replica/MIgration, please check the **[AWS as a source cloud](../amazon-web-services-aws/aws-as-a-source-cloud.md)** page. +For more information on using AWS as a **source cloud** for Replica/Migration, please check the **[AWS as a source cloud](../amazon-web-services-aws/aws-as-a-source-cloud.md)** page. ### AWS as a destination cloud -For more information on using AWS as a **destination cloud** for Replica/MIgration, please check the **[AWS as a destination cloud](../amazon-web-services-aws/aws-as-a-destination-cloud.md)** page. +For more information on using AWS as a **destination cloud** for Replica/Migration, please check the **[AWS as a destination cloud](../amazon-web-services-aws/aws-as-a-destination-cloud.md)** page. ### AWS platform specifics diff --git a/source/platforms/cloudstack/cloudstack-coriolis-plugin.md b/source/platforms/cloudstack/cloudstack-coriolis-plugin.md new file mode 100644 index 0000000..44871db --- /dev/null +++ b/source/platforms/cloudstack/cloudstack-coriolis-plugin.md @@ -0,0 +1,11 @@ +--- +title: "CloudStack" +--- + +# CloudStack + +**Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, **Coriolis** guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. + +## WORK IN PROGRESS + +**[CloudStack as a destination cloud](../cloudstack/cloudstack-as-a-destination-cloud.md)** \ No newline at end of file diff --git a/source/platforms/index.md b/source/platforms/index.md index cbc6cbb..5b199ca 100644 --- a/source/platforms/index.md +++ b/source/platforms/index.md @@ -17,5 +17,7 @@ proxmox/proxmox-coriolis-plugin oracle-cloud-infrastructure-oci/oracle-cloud-infrastructure-oci-coriolis-plugin ovirt/ovirt-coriolis-plugin stackit/stackit-coriolis-plugin +nutanix/nutanix-coriolis-plugin +cloudstack/cloudstack-coriolis-plugin bare-metal-hub/coriolis-bare-metal-hub-plugin ``` diff --git a/source/platforms/nutanix/nutanix-coriolis-plugin.md b/source/platforms/nutanix/nutanix-coriolis-plugin.md new file mode 100644 index 0000000..4384975 --- /dev/null +++ b/source/platforms/nutanix/nutanix-coriolis-plugin.md @@ -0,0 +1,11 @@ +--- +title: "Nutanix" +--- + +# Nutanix + +**Coriolis** integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture, **Coriolis** guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met. + +## WORK IN PROGRESS + +**[Nutanix as a source cloud](../nutanix/nutanix-as-a-source-cloud.md)** \ No newline at end of file diff --git a/source/platforms/stackit/stackit-as-a-destination-cloud.md b/source/platforms/stackit/stackit-as-a-destination-cloud.md index 1c4f6b0..c2e6fbd 100644 --- a/source/platforms/stackit/stackit-as-a-destination-cloud.md +++ b/source/platforms/stackit/stackit-as-a-destination-cloud.md @@ -4,39 +4,39 @@ wp_id: 44279 orphan: true --- -# StackIt as a destination cloud +# STACKIT as a destination cloud -### Migrating (CMaaS) to Stackit +### Migrating (CMaaS) to STACKIT -Transfer Migrations to Stackit operate in the same way Transfer Replicas do and thus entail the same requirements and steps described below. +Transfer Migrations to STACKIT operate in the same way Transfer Replicas do and thus entail the same requirements and steps described below. -### Replicating (DRaaS) to Stackit +### Replicating (DRaaS) to STACKIT #### Replica executions: #### Steps performed by Coriolis - 1. if this is the first replica execution for the VM, create empty Stackit volumes on the destination side, each matching the specifications of a disk the VM had on the source. If this is a later replica execution, the previously created Stackit volumes are used + 1. if this is the first replica execution for the VM, create empty STACKIT volumes on the destination side, each matching the specifications of a disk the VM had on the source. If this is a later replica execution, the previously created STACKIT volumes are used 2. if this is the first replica execution of the VM, create a new live snapshot of the disks of the VM on the source cloud (handled by whatever source cloud plugin we are using). If this is a later replica execution, create a new live snapshot based on the one from the last successful replica execution - 3. create a temporary Linux worker VM (the “disk copy worker”) on the destination side and attach the Stackit volumes from Step 1 to it + 3. create a temporary Linux worker VM (the “disk copy worker”) on the destination side and attach the STACKIT volumes from Step 1 to it 4. read the contents of the snapshot created at step 2 via the source platform’s snapshot/backup APIs (handled by whatever source cloud plugin we are using), transferring the written chunks to the temporary VM created in step 3, which then writes the chunks at the appropriate index/offset of the disks created at step 1 - 5. once the contents of all the disks have been synced to the Stackit volumes created in Step 1, detach the Stackit volumes and delete the disk copy worker created in Step 3 + 5. once the contents of all the disks have been synced to the STACKIT volumes created in Step 1, detach the STACKIT volumes and delete the disk copy worker created in Step 3 #### Replica deployments: #### Steps performed by Coriolis - 1. create snapshots of the replicated Stackit volumes on the destination side to be able to roll back any changes. By default, new volumes are created from these snapshots, leaving the original replica volumes intact for future replica executions - 2. depending on the OS of the VM whose replica is being deployed, boot a temporary worker VM (“the OSMorphing worker”) with the same OS type on the destination cloud, and attach the Stackit volumes from step 1 to it - 3. perform the “OSMorphing process”, where Coriolis commands the OSMorphing worker created in step 2 to scan all attached disks for the OS installation of the VM we are migrating, mount, and perform the steps needed to prepare the installation for the Stackit platform (ex: uninstalling the VMWare guest tools and installing VirtIO drivers as well as the Stackit agent) - 4. detach the Stackit volumes created at step 1 from the OSMorphing worker created at step 2 and delete the temporary worker VM - 5. create and boot the migrated VM on the destination cloud with the specifications of the original VM on the source cloud (which have been noted during the particular replica execution we are deploying), creating and attaching any necessary NICs and Stackit volumes. + 1. create snapshots of the replicated STACKIT volumes on the destination side to be able to roll back any changes. By default, new volumes are created from these snapshots, leaving the original replica volumes intact for future replica executions + 2. depending on the OS of the VM whose replica is being deployed, boot a temporary worker VM (“the OSMorphing worker”) with the same OS type on the destination cloud, and attach the STACKIT volumes from step 1 to it + 3. perform the “OSMorphing process”, where Coriolis commands the OSMorphing worker created in step 2 to scan all attached disks for the OS installation of the VM we are migrating, mount, and perform the steps needed to prepare the installation for the STACKIT platform (ex: uninstalling the VMWare guest tools and installing VirtIO drivers as well as the STACKIT agent) + 4. detach the STACKIT volumes created at step 1 from the OSMorphing worker created at step 2 and delete the temporary worker VM + 5. create and boot the migrated VM on the destination cloud with the specifications of the original VM on the source cloud (which have been noted during the particular replica execution we are deploying), creating and attaching any necessary NICs and STACKIT volumes. ### Configuration Options -#### Advanced Target options for Stackit target destination +#### Advanced Target options for STACKIT target destination -When migrating or replicating instances to Stackit, the user must specify which images to use for Linux and Windows temporary migration workers. We recommend using the public Stackit images. +When migrating or replicating instances to STACKIT, the user must specify which images to use for Linux and Windows temporary migration workers. We recommend using the public STACKIT images. The worker image OS version must be the same as or newer than the migrated instance. @@ -46,7 +46,7 @@ When Replicating/Migrating a **Windows VM**, both **Linux and Windows images** h ![](../../_static/images/image-5.png) -### OSMorphing steps taken when migrating/replicating to Stackit +### OSMorphing steps taken when migrating/replicating to STACKIT The following notable steps will be performed as part of the OSMorphing process: @@ -60,29 +60,29 @@ The following notable steps will be performed as part of the OSMorphing process: * installing cloudbase-init and enabling cloudbase-init service * installing the VirtIO drivers -In addition to that, the Stackit agent will be installed. +In addition to that, the STACKIT agent will be installed. ### Network configuration for the migrated VMs -When migrating instances to Stackit, users can specify which network to use for each individual NIC. The following parameters can be used to further customise the VM network configuration. +When migrating instances to STACKIT, users can specify which network to use for each individual NIC. The following parameters can be used to further customise the VM network configuration. #### Preserve fixed IPs -If enabled, the Stackit NIC will use the same fixed (private) IP as the source NICs. An error will be raised if the source IP address is not in the range of the specified Stackit network. +If enabled, the STACKIT NIC will use the same fixed (private) IP as the source NICs. An error will be raised if the source IP address is not in the range of the specified STACKIT network. -If disabled, Stackit will pick a random address from the given network. +If disabled, STACKIT will pick a random address from the given network. -Note that Stackit does not currently support IPv6 networks, as such any IPv6 addresses will be dropped. +Note that STACKIT does not currently support IPv6 networks, as such any IPv6 addresses will be dropped. #### Use public IP -If enabled, the first NIC will receive a public IP selected by Stackit. +If enabled, the first NIC will receive a public IP selected by STACKIT. #### Set DHCP This setting determines how the guest network interfaces will be configured during OS morphing. -It’s enabled by default and as a result Coriolis will configure each interface to use DHCP. Since all Stackit networks provide DHCP, we recommend leaving this setting on. This also ensures that the correct MTU and routes will be applied. +It’s enabled by default and as a result Coriolis will configure each interface to use DHCP. Since all STACKIT networks provide DHCP, we recommend leaving this setting on. This also ensures that the correct MTU and routes will be applied. If disabled, Coriolis expects the guest to have static network configuration. Depending on the guest operating system, the following steps will be taken: @@ -96,15 +96,15 @@ If disabled, Coriolis expects the guest to have static network configuration. De * define static network configuration through a script that will be invoked by cloudbase-init during the first replica boot -#### Configuration options for Stackit as a destination +#### Configuration options for STACKIT as a destination -Below is a listing of the configuration section needed when migrating/replicating to Stackit: +Below is a listing of the configuration section needed when migrating/replicating to STACKIT: -### Stackit destination environment parameters +### STACKIT destination environment parameters The destination environment parameters are a set of destination-cloud-specific parameters that offer additional options to the migration/replication process on a per-VM basis. -Below is a listing of the destination environment parameters the Stackit plugin supports when migrating/replicating a VM to Stackit: +Below is a listing of the destination environment parameters the STACKIT plugin supports when migrating/replicating a VM to STACKIT: ```ini [stackit_migration_provider] @@ -325,7 +325,7 @@ Each parameter represents: * **network_map** (string–string mapping, required) — mapping between source network identifiers and names or IDs of existing networks on destination STACKIT. For each NIC of the source server, Coriolis creates a NIC on the mapped destination network. * **storage_mappings** (object) — how to map each source disk or storage backend to a STACKIT volume performance class. The mapping is expected to contain one or more of the following keys: **default**, **backend_mappings**, and **disk_mappings**. If omitted or empty, STACKIT picks the default performance class. Unmapped disks can also fall back to the plugin’s **default_volume_performance_class** config option. * **machine_type** (string) — name of an existing STACKIT machine type for the migrated server. If omitted, Coriolis picks the smallest type that satisfies the source CPU/RAM. Windows guests need an explicit Windows-compatible type. - * **project** (string) — ID of the Stackit project in which to create the migrated resources (VM, volumes, NICs). If unset, the project of the service account from the Coriolis endpoint is used. This option applies to the created migration minions as well. + * **project** (string) — ID of the STACKIT project in which to create the migrated resources (VM, volumes, NICs). If unset, the project of the service account from the Coriolis endpoint is used. This option applies to the created migration minions as well. * **keypair_name** (string) — name of a keypair available to the Coriolis endpoint user, injected into the migrated server via metadata. Has no effect if **retain_user_credentials** is true (cloud-init will not add that key). * **delete_disks_on_server_termination** (boolean, default **false**) — whether the boot volume is deleted when the migrated server is terminated. Applies only to the boot volume. * **security_groups** (list of strings) — names or IDs of existing security groups in the same project as the Coriolis endpoint, applied to the migrated server. Joined with the plugin’s **default_security_groups** config option. diff --git a/source/platforms/stackit/stackit-as-a-source-cloud.md b/source/platforms/stackit/stackit-as-a-source-cloud.md index b7cefef..db330ea 100644 --- a/source/platforms/stackit/stackit-as-a-source-cloud.md +++ b/source/platforms/stackit/stackit-as-a-source-cloud.md @@ -1,43 +1,43 @@ --- -title: "StackIt as a source cloud" +title: "STACKIT as a source cloud" wp_id: 44263 orphan: true --- -# StackIt as a source cloud +# STACKIT as a source cloud -### Migrating (CMaaS) from Stackit +### Migrating (CMaaS) from STACKIT -Transfer Migrations from Stackit operate in the same way Transfer Replicas do and thus entail the same requirements and steps described below. +Transfer Migrations from STACKIT operate in the same way Transfer Replicas do and thus entail the same requirements and steps described below. -### Replicating (DRaaS) from Stackit using Coriolis-based exports: +### Replicating (DRaaS) from STACKIT using Coriolis-based exports: #### Requirements: -In the process of replicating from Stackit, Coriolis will clone locally the volumes of the source VM and boot a temporary worker VM on the source Stackit side to perform the actual disk exports. +In the process of replicating from STACKIT, Coriolis will clone locally the volumes of the source VM and boot a temporary worker VM on the source STACKIT side to perform the actual disk exports. **Input**: the ID or name of the instance to be replicated. The instance is expected to be booted from volume, an error will be raised if ephemeral root disks are used since these cannot be exported. ```{note} -Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from Stackit [here](../../guides/preparing-a-vm-for-migration-replication.md). +Please consider reviewing the general steps recommended to be performed before creating and executing a replica of an instance from STACKIT [here](../../guides/preparing-a-vm-for-migration-replication.md). ``` #### Steps performed by Coriolis - 1. read the configuration of the instance on the source Stackit (e.g. machine type information, disks, NICs) + 1. read the configuration of the instance on the source STACKIT (e.g. machine type information, disks, NICs) 2. snapshot and clone the attached volumes - 3. create a temporary worker VM (the “disk export worker”) on the source Stackit and attach the volumes from step 2 + 3. create a temporary worker VM (the “disk export worker”) on the source STACKIT and attach the volumes from step 2 4. the **temporary disk export worker VM** will then determine the differences and export the contents of the attached volumes After the above steps are completed, the contents of the disks will be transferred and written to disks on the destination via the destination cloud plugin. Only the changed data will be transferred to the destination cloud. ![](../../_static/images/stackit-source-options.png) -### Stackit source environment parameters +### STACKIT source environment parameters The source environment parameters are a set of source-cloud-specific parameters that offer some extra options to the migration/replication process on a per-VM basis. -Below is a listing of the source environment parameters the Stackit plugin supports when migrating/replicating a VM from Stackit: +Below is a listing of the source environment parameters the STACKIT plugin supports when migrating/replicating a VM from STACKIT: ```json { @@ -55,20 +55,20 @@ Below is a listing of the source environment parameters the Stackit plugin suppo Each parameter represents: - * **guest_os_type_override** (string: **linux** or **windows**) — overrides the OS type Coriolis reads from source image or boot-volume metadata. Use this when Stackit metadata is missing or wrong; it affects listing, export info, and which destination OSMorphing tools/worker image are used. + * **guest_os_type_override** (string: **linux** or **windows**) — overrides the OS type Coriolis reads from source image or boot-volume metadata. Use this when STACKIT metadata is missing or wrong; it affects listing, export info, and which destination OSMorphing tools/worker image are used. * **guest_firmware_type_override** (string: **BIOS** or **EFI**) — overrides the firmware type Coriolis reads from source image or volume metadata (**uefi**). Use this when that metadata is missing or wrong; the destination uses it when creating the migrated server (including volume image config). - * **export_image** (string) — name or ID of a pre-existing Ubuntu image on the source Stackit side for the temporary disk-export worker. The image must be visible to the Coriolis endpoint project and have cloud-init installed and configured for first boot. Disk export always uses a Linux worker, including for Windows guests. + * **export_image** (string) — name or ID of a pre-existing Ubuntu image on the source STACKIT side for the temporary disk-export worker. The image must be visible to the Coriolis endpoint project and have cloud-init installed and configured for first boot. Disk export always uses a Linux worker, including for Windows guests. * **export_network** (string, required) — name or ID of an existing network for the temporary export worker NIC. If **export_worker_use_public_ip** is false, Coriolis must be able to route to this network. * **export_machine_type** (string, required) — machine type for the temporary disk-export worker. Must be compatible with **export_image**. * **export_worker_use_public_ip** (boolean, default **true**) — allocate a public IP for the temporary disk-export worker. If false, Coriolis must reach the worker on **export_network**. * **export_worker_volume_size** (integer, min 1) — size in GB of the volume used to boot the temporary export worker. If omitted, Coriolis uses the image minimum size or the selected **export_machine_type**. * **export_worker_volume_performance_class** (string) — volume performance class for the temporary export worker’s boot volume. - * **project** (string) — ID of the Stackit project from which to export VMs. If unset, the project of the service account from the Coriolis endpoint is used. Export workers and source minion pools must use the same project. + * **project** (string) — ID of the STACKIT project from which to export VMs. If unset, the project of the service account from the Coriolis endpoint is used. Export workers and source minion pools must use the same project. ```{note} -The **project** option can only be populated and used if the endpoint service account has StackIt Organization level permissions to access all the projects in it. +The **project** option can only be populated and used if the endpoint service account has STACKIT Organization level permissions to access all the projects in it. ``` -The export worker is always created in the same availability zone as the source server. Created source minion pools must also be configured to use the same availabilizy zone as the migrated VMs. Servers booted from an ephemeral root disk (not from volume) cannot be exported, because Stackit does not expose those disk contents. +The export worker is always created in the same availability zone as the source server. Created source minion pools must also be configured to use the same availabilizy zone as the migrated VMs. Servers booted from an ephemeral root disk (not from volume) cannot be exported, because STACKIT does not expose those disk contents. These source options can also be set in the **[stackit_migration_provider]** config section and overridden per migration/replica in the source environment. diff --git a/source/platforms/stackit/stackit-coriolis-plugin.md b/source/platforms/stackit/stackit-coriolis-plugin.md index 138cb23..6b84cf2 100644 --- a/source/platforms/stackit/stackit-coriolis-plugin.md +++ b/source/platforms/stackit/stackit-coriolis-plugin.md @@ -11,32 +11,32 @@ wp_id: 44258 ### Deployment requirements -The Coriolis appliance(s) need network access to the Stackit APIs, as well as to the public IPs of the temporary VMs Coriolis will be creating during the migration process. +The Coriolis appliance(s) need network access to the STACKIT APIs, as well as to the public IPs of the temporary VMs Coriolis will be creating during the migration process. ### Supported instances -Stackit does not allow snapshotting ephemeral root disks, as such Coriolis can only migrate Stackit instances that were booted from volume. +STACKIT does not allow snapshotting ephemeral root disks, as such Coriolis can only migrate STACKIT instances that were booted from volume. -### StackIt as a source cloud +### STACKIT as a source cloud -For more information on using StackIt as a **source cloud** for Replica/Migration, please check the **[StackIt as a source cloud](../stackit/stackit-as-a-source-cloud.md)** page. +For more information on using STACKIT as a **source cloud** for Replica/Migration, please check the **[STACKIT as a source cloud](../stackit/stackit-as-a-source-cloud.md)** page. -### StackIt as a destination cloud +### STACKIT as a destination cloud -For more information on using StackIt as a **destination cloud** for Replica/Migration, please check the **[StackIt as a destination cloud](../stackit/stackit-as-a-destination-cloud.md)** page. +For more information on using STACKIT as a **destination cloud** for Replica/Migration, please check the **[STACKIT as a destination cloud](../stackit/stackit-as-a-destination-cloud.md)** page. -### Stackit connection parameters +### STACKIT connection parameters -Coriolis requires the following connection parameters in order to acces Stackit and migrate resources: +Coriolis requires the following connection parameters in order to acces STACKIT and migrate resources: ![](../../_static/images/stackit-endpoint.png) Each parameter represents: * name - an arbitrary user defined name for this endpoint - * organization ID - the Stackit organization ID - * project ID - the Stackit project ID - * region name - the name of the Stackit region + * organization ID - the STACKIT organization ID + * project ID - the STACKIT project ID + * region name - the name of the STACKIT region * service account key - base64 encoded service account key JSON form: @@ -52,34 +52,34 @@ JSON form: Make sure that the specified service account has enough privileges to access, create and modify IAAS resources. For example, consider using the “Editor” role. -### Stackit platform specifics +### STACKIT platform specifics Supported Actions: | Migration (CMaaS) Source/Destination – Replica (DRaaS) Source/Destination| Comments ---|---|--- -Plugin identifier| **stackit**| Identifies the plugin. Used for the **–provider** CLI parameter -Credentials needed| Stackit organization, project, region and service account key.| The service account key is expected to be base64 encoded. -Deployment requirements| Coriolis worker component(s) need network access to the Stackit API endpoint.| Coriolis deployment and environment connectivity requirements +Plugin identifier| **STACKIT**| Identifies the plugin. Used for the **–provider** CLI parameter +Credentials needed| STACKIT organization, project, region and service account key.| The service account key is expected to be base64 encoded. +Deployment requirements| Coriolis worker component(s) need network access to the STACKIT API endpoint.| Coriolis deployment and environment connectivity requirements Source disk export requirements| The VMs must be booted from volume and not use ephemeral root disks.| Requirements to use the replica export features. Instance identification scheme| By name or ID.| How instances to migrate/replicate are identified on a source cloud handled by this plugin Network identification scheme| By name or ID.| How the plugin identifies networks. Required for the **network_map** field of the **–destination-environment** -Storage identification scheme| By the name or ID of the Stackit storage performance class.| How the plugin identifies storage backends. Required for the **storage_map** field of the **–destination-environment** +Storage identification scheme| By the name or ID of the STACKIT storage performance class.| How the plugin identifies storage backends. Required for the **storage_map** field of the **–destination-environment** -### Stackit Coriolis plugin known issues and limitations +### STACKIT Coriolis plugin known issues and limitations #### Automatic machine type selection for Windows instances -The Stackit plugin cannot reliably select the machine type automatically when migrating Windows instances. Stackit requires a Windows compatible machine type as documented here: +The STACKIT plugin cannot reliably select the machine type automatically when migrating Windows instances. STACKIT requires a Windows compatible machine type as documented here: -Stackit machine types returned by the API do not currently contain any Windows related labels or description keywords, as such the user must manually select one of the machine types documented as Windows compatible. +STACKIT machine types returned by the API do not currently contain any Windows related labels or description keywords, as such the user must manually select one of the machine types documented as Windows compatible. #### vTPM -Stackit does not support vTPM devices, as such we cannot migrate VMs that use guest side encryption (e.g. BitLocker, LUKS). This may also affect other Windows hardening features that require a vTPM device. +STACKIT does not support vTPM devices, as such we cannot migrate VMs that use guest side encryption (e.g. BitLocker, LUKS). This may also affect other Windows hardening features that require a vTPM device. #### Migrating instances that have ephemeral root disks -Stackit instances that were not booted from volume and have ephemeral root disks cannot be migrated. +STACKIT instances that were not booted from volume and have ephemeral root disks cannot be migrated. #### IPv6 -Stackit does not support IPv6 networks, as such any IPv6 addresses will be dropped. +STACKIT does not support IPv6 networks, as such any IPv6 addresses will be dropped. diff --git a/source/platforms/vmware/vmware-coriolis-plugin.md b/source/platforms/vmware/vmware-coriolis-plugin.md index 10ca6db..f67c7ee 100644 --- a/source/platforms/vmware/vmware-coriolis-plugin.md +++ b/source/platforms/vmware/vmware-coriolis-plugin.md @@ -40,11 +40,11 @@ Coriolis supports VMware vSphere (vCenter/ESXi) environments starting from versi ### vSphere as a source cloud -For more information on using vSphere/ESXi as a **source cloud** for Replica/MIgration, please check the **[VMware as a source cloud](../vmware/vmware-as-a-source-cloud.md)** page. +For more information on using vSphere/ESXi as a **source cloud** for Replica/Migration, please check the **[VMware as a source cloud](../vmware/vmware-as-a-source-cloud.md)** page. ### vSphere as a destination cloud -For more information on using vSphere/ESXi as a **destination cloud** for Replica/MIgration, please check the **[VMware as a destination cloud](../vmware/vmware-as-a-destination-cloud.md)** page. +For more information on using vSphere/ESXi as a **destination cloud** for Replica/Migration, please check the **[VMware as a destination cloud](../vmware/vmware-as-a-destination-cloud.md)** page. ### vSphere/ESXi connection parameters diff --git a/source/reference/coriolis-release-notes.md b/source/reference/coriolis-release-notes.md index 0c68614..35b6d6f 100644 --- a/source/reference/coriolis-release-notes.md +++ b/source/reference/coriolis-release-notes.md @@ -652,7 +652,7 @@ This is a minor release to address several bugs and to bring several improvement * Introducing **Coriolis Bare Metal Agent** - migrating p2v * This can also be used for v2v where platform access is limited * Linux Agent only is currently available - * More details can be found at [Coriolis Bare Metal Hub Plugin - Cloudbase Solutions](../plugins/coriolis-bare-metal-hub-plugin.md) + * More details can be found at [Coriolis Bare Metal Hub Plugin - Cloudbase Solutions](../platforms/bare-metal-hub/coriolis-bare-metal-hub-plugin.md) * Introducing support for **OLVM - Oracle Linux Virtualization Manager** - as a destination platform * This is backed by oVirt and KVM nodes * **RedHat Virtualization (RHV/RHEV)** is also supported as a destination platform diff --git a/source/walkthroughs/step-by-step-guide-vmware-to-openstack-migration.md b/source/walkthroughs/step-by-step-guide-vmware-to-openstack-migration.md index 32091e7..2d5cc97 100644 --- a/source/walkthroughs/step-by-step-guide-vmware-to-openstack-migration.md +++ b/source/walkthroughs/step-by-step-guide-vmware-to-openstack-migration.md @@ -172,7 +172,7 @@ For VMware as a source platform, the options are represented by: * vixDiskLib compatibility mode - it is set to 8.0 by default, and it is backwards compatible in the case that your VMware runs on older versions * Use VM Hostname as Instance Name - if enabled, Coriolis will use the hostname of the machine to identify it more easily -All the platform specifics are available on **[VMware as a source page](../platforms/vmware-as-a-source-cloud.md)**. +All the platform specifics are available on **[VMware as a source page](../platforms/vmware/vmware-as-a-source-cloud.md)**. ![](_static/images/mgr4.png) @@ -186,7 +186,7 @@ Once the source details are set, the next step will provide the target platform Once the target platform is selected, target options must be allocated to the VM/VMs to be migrated. -All the options are found on the[ **OpenStack as a destination page**](../platforms/openstack-as-a-destination-cloud.md). +All the options are found on the[ **OpenStack as a destination page**](../platforms/openstack/openstack-as-a-destination-cloud.md). ![](_static/images/mgr7.png)