mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
77 lines
4.4 KiB
Plaintext
77 lines
4.4 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="advanced-migration-options-3-4"]
|
|
= Advanced migration options
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: advanced-migration-options-3-4
|
|
:advanced-migration-options-3-4:
|
|
|
|
toc::[]
|
|
|
|
You can automate your migrations and modify the `MigPlan` and `MigrationController` custom resources in order to perform large-scale migrations and to improve performance.
|
|
|
|
include::modules/migration-terminology.adoc[leveloffset=+1]
|
|
|
|
include::modules/migration-migrating-on-prem-to-cloud.adoc[leveloffset=+1]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
* For information about creating a MigCluster CR manifest for each remote cluster, see xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#migration-migrating-applications-api_advanced-migration-options-3-4[Migrating an application by using the {mtc-short} API].
|
|
* For information about adding a cluster using the web console, see xref:../migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc#migrating-applications-mtc-web-console_migrating-applications-3-4[Migrating your applications by using the {mtc-short} web console]
|
|
|
|
[id="migrating-applications-cli_{context}"]
|
|
== Migrating applications by using the command line
|
|
|
|
You can migrate applications with the {mtc-short} API by using the command-line interface (CLI) in order to automate the migration.
|
|
|
|
include::modules/migration-prerequisites.adoc[leveloffset=+2]
|
|
include::modules/migration-creating-registry-route-for-dim.adoc[leveloffset=+2]
|
|
include::modules/migration-about-configuring-proxies.adoc[leveloffset=+2]
|
|
include::modules/migration-configuring-proxies.adoc[leveloffset=+3]
|
|
include::modules/migration-migrating-applications-api.adoc[leveloffset=+2]
|
|
include::modules/migration-state-migration-cli.adoc[leveloffset=+2]
|
|
|
|
[role="_additional-resources"]
|
|
[id="additional-resources-for-state-migration_{context}"]
|
|
|
|
=== Additional resources
|
|
|
|
* See xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#migration-excluding-pvcs_advanced-migration-options-3-4[Excluding PVCs from migration] to select PVCs for state migration.
|
|
* See xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#migration-mapping-pvcs_advanced-migration-options-3-4[Mapping PVCs] to migrate source PV data to provisioned PVCs on the destination cluster.
|
|
* See xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#migration-kubernetes-objects_advanced-migration-options-3-4[Migrating Kubernetes objects] to migrate the Kubernetes objects that constitute an application's state.
|
|
|
|
include::modules/migration-hooks.adoc[leveloffset=+1]
|
|
include::modules/migration-writing-ansible-playbook-hook.adoc[leveloffset=+2]
|
|
|
|
[id="migration-plan-options_{context}"]
|
|
== Migration plan options
|
|
|
|
You can exclude, edit, and map components in the `MigPlan` custom resource (CR).
|
|
|
|
include::modules/migration-excluding-resources.adoc[leveloffset=+2]
|
|
include::modules/migration-mapping-destination-namespaces-in-the-migplan-cr.adoc[leveloffset=+2]
|
|
include::modules/migration-excluding-pvcs.adoc[leveloffset=+2]
|
|
include::modules/migration-mapping-pvcs.adoc[leveloffset=+2]
|
|
include::modules/migration-editing-pvs-in-migplan.adoc[leveloffset=+2]
|
|
|
|
[role="_additional-resources"]
|
|
[id="additional-resources-for-editing-pv-attributes_{context}"]
|
|
|
|
==== Additional resources
|
|
|
|
* For details about the `move` and `copy` actions, see xref:../migrating_from_ocp_3_to_4/about-mtc-3-4.adoc#migration-mtc-workflow_about-mtc-3-4[MTC workflow].
|
|
* For details about the `skip` action, see xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#migration-excluding-pvcs_advanced-migration-options-3-4[Excluding PVCs from migration].
|
|
* For details about the file system and snapshot copy methods, see xref:../migrating_from_ocp_3_to_4/about-mtc-3-4.adoc#migration-understanding-data-copy-methods_about-mtc-3-4[About data copy methods].
|
|
|
|
include::modules/migration-kubernetes-objects.adoc[leveloffset=+2]
|
|
|
|
[id="migration-controller-options_{context}"]
|
|
== Migration controller options
|
|
|
|
You can edit migration plan limits, enable persistent volume resizing, or enable cached Kubernetes clients in the `MigrationController` custom resource (CR) for large migrations and improved performance.
|
|
|
|
include::modules/migration-changing-migration-plan-limits.adoc[leveloffset=+2]
|
|
include::modules/migration-enabling-pv-resizing-dvm.adoc[leveloffset=+2]
|
|
include::modules/migration-enabling-cached-kubernetes-clients.adoc[leveloffset=+2]
|
|
|
|
:advanced-migration-options-3-4!:
|