-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path02_migrate_vms.html
606 lines (556 loc) · 23.5 KB
/
02_migrate_vms.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="favicon-16x16.png">
<link rel="manifest" href="site.webmanifest">
<link rel="mask-icon" href="safari-pinned-tab.svg" color="#5bbad5">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="theme-color" content="#ffffff">
<script src="jquery/jquery.min.js"></script>
<script src="popper/popper.min.js"></script>
<script src="bootstrap/js/bootstrap.min.js"></script>
<script src="requirejs/require.js"></script>
<script>var workshop_base_url = "/workshop";</script>
<link rel="stylesheet" href="asciidoctor/css/asciidoctor.css">
<link rel="stylesheet" href="bootstrap/css/bootstrap.min.css">
<link rel="stylesheet" href="fontawesome/css/all.min.css">
<link rel="stylesheet" href="css/workshop.css">
<link rel="stylesheet" href="css/workshop-asciidoc.css">
</head>
</body>
<!-- Header -->
<header class="header">
<div class="container-fluid">
<div class="row">
<div class="col-sm-6">
<a href="index.html" class="logo">Red Hat OpenShift Virtualization Roadshow</a>
</div>
</div>
</div>
</header>
<!-- Main -->
<div class="container-fluid">
<div class="row">
<div class="col-sm-3 d-sm-block d-none">
<!-- Table of Contents -->
<ul class="menu">
<li class="category">
<ul class="modules">
<h5 class="category-title">Workshop Modules</h5>
<li class="page"><a href="index.html">Welcome</a></li>
<li class="page active"><a href="02_migrate_vms.html">Migrating Virtual Machines</a></li>
<li class="page"><a href="03_ocpv_basics.html">OpenShift Virtualization Basics</a></li>
<li class="page"><a href="04_thanks.html">Thank you and next steps</a></li>
<li class="page"><a href="05_ocpv_customization.html">Optional: Customize Virtual Machines</a></li>
<li class="page"><a href="06_windows_vm.html">Optional: Windows Virtual Machines</a></li>
<li class="page"><a href="07_bare_metal.html">Optional: Bare Metal OpenShift Overview</a></li>
<li class="page"><a href="08_network_management.html">Optional: Network Management</a></li>
<li class="page"><a href="09_storage_management.html">Optional: Storage Management</a></li>
<li class="page"><a href="10_backup_restore.html">Optional: Backup and Restore</a></li>
<li class="page"><a href="11_metallb.html">Optional: Exposing apps using MetalLB</a></li>
<li class="page"><a href="12_service_route.html">Optional: Exposing apps using a Route</a></li>
</ul>
</li>
</ul>
</div>
<div class="col-sm-9">
<section class="page-content">
<!-- Top Navigation -->
<div class="btn-group btn-group-xs float-right">
<button type="button" onclick="location.href='/workshop/01_welcome';" class="btn btn-xs btn-transparent" aria-label="Prev">
<span class="fas fa-arrow-left" aria-hidden="true"></span>
</button>
<button type="button" onclick="location.href='/workshop/';" class="btn btn-xs btn-transparent" aria-label="Home">
<span class="fas fa-home" aria-hidden="true"></span>
</button>
<button type="button" onclick="location.href='/workshop/03_ocpv_basics';" class="btn btn-xs btn-transparent" aria-label="Next">
<span class="fas fa-arrow-right" aria-hidden="true"></span>
</button>
</div>
<!-- Title -->
<h1 class="title">Migrating Virtual Machines</h1>
<!-- Content -->
<div id="toc" class="toc">
<div id="toctitle">Table of Contents</div>
<ul class="sectlevel1">
<li><a href="02_migrate_vms.html#_introduction">Introduction</a></li>
<li><a href="02_migrate_vms.html#_prerequisites_for_the_vmware_provider">Prerequisites for the VMware Provider</a></li>
<li><a href="02_migrate_vms.html#_migrating_virtual_machines_from_vmware">Migrating Virtual Machines from VMware</a>
<ul class="sectlevel2">
<li><a href="02_migrate_vms.html#_review_the_vmware_environment">Review the VMware environment</a></li>
<li><a href="02_migrate_vms.html#_review_the_vmware_provider_to_the_migration_toolkit">Review the VMware provider to the migration toolkit</a></li>
<li><a href="02_migrate_vms.html#_create_storage_and_network_mappings">Create storage and network mappings</a></li>
<li><a href="02_migrate_vms.html#_create_a_migration_plan">Create a Migration Plan</a></li>
<li><a href="02_migrate_vms.html#_review_and_configure_migrated_virtual_machines">Review and configure migrated Virtual Machines</a></li>
</ul>
</li>
<li><a href="02_migrate_vms.html#_summary">Summary</a></li>
</ul>
</div>
<div class="sect1">
<h2 id="_introduction">Introduction</h2>
<div class="sectionbody">
<div class="paragraph">
<p>This lab uses the <a href="https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/">Migration Toolkit for Virtualization</a> (MTV) to import a virtual machine from VMware vSphere to OpenShift. The migration toolkit supports two "modes" of import:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Cold migration turns off the source virtual machine before starting the migration. This is the default migration type.</p>
</li>
<li>
<p>Warm migration copies data while the source virtual machine continues to run. Once the bulk of data has been migrated, the VM is shutdown and the final data is copied to the destination. The new VM can then be started, resulting in a much shorter period of downtime for the VM-hosted application.</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>The migration toolkit has already been deployed to your cluster using the Operator. Documentation for how to install and configure the Operator can be found <a href="https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/">here</a>.</p>
</div>
<div class="paragraph">
<p>If you would like to learn more about how to configure the Migration Toolkit for Virtualization, please see <a href="https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.4/html/installing_and_using_the_migration_toolkit_for_virtualization/prerequisites#rhv-prerequisites_mtv">here</a> for documentation with Red Hat Virtualization or <a href="https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.4/html/installing_and_using_the_migration_toolkit_for_virtualization/prerequisites#vmware-prerequisites_mtv">here</a> for VMware vSphere.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_prerequisites_for_the_vmware_provider">Prerequisites for the VMware Provider</h2>
<div class="sectionbody">
<div class="paragraph">
<p>The following prerequisites apply to all migrations:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>ISO/CD-ROM disks must be unmounted.</p>
</li>
<li>
<p>Each NIC must contain one IPv4 and/or one IPv6 address.</p>
</li>
<li>
<p>The VM operating system must be certified and supported for use as a <a href="https://access.redhat.com/articles/973163#ocpvirt">guest operating system with OpenShift Virtualization</a>.</p>
</li>
<li>
<p>VM names must contain only lowercase letters (a-z), numbers (0-9), or hyphens (-), up to a maximum of 253 characters. The first and last characters must be alphanumeric. The name must not contain uppercase letters, spaces, periods (.), or special characters.</p>
</li>
<li>
<p>VM names must not duplicate the name of an existing VM in the OpenShift Virtualization environment.</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>The <strong>Migration Toolkit for Virtualization</strong> will automatically assign a new name to a VM that does not comply with the rules. If this happens, MTV will automatically generate a new VM name to allow the migration to proceed smoothly.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_migrating_virtual_machines_from_vmware">Migrating Virtual Machines from VMware</h2>
<div class="sectionbody">
<div class="paragraph">
<p>A three-tier application has been deployed on VMware for you to migrate to OpenShift.</p>
</div>
<div class="paragraph">
<p>The application consists of the following four virtual machines:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>One HAproxy system that redirects traffic to the web servers</p>
</li>
<li>
<p>Two Microsoft Windows servers with IIS hosting a PHP application connecting to the database</p>
</li>
<li>
<p>One Linux system running a MariaDB database</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>The application is accessible from the following link: <a href="http://webapp.vc.opentlc.com/" class="bare">http://webapp.vc.opentlc.com/</a></p>
</div>
<div class="paragraph">
<p>You will migrate three of the four virtual machines using cold migration - you will not need to migrate the HAproxy (load balancer) VM because OpenShift handles network traffic and load balancing natively for VMs connected to the SDN using a <code>Service</code>.</p>
</div>
<div class="sect2">
<h3 id="_review_the_vmware_environment">Review the VMware environment</h3>
<div class="paragraph">
<p>To help understand the process of mapping resources, such as datastores and port groups, from vSphere into OpenShift’s equivalents, network attachment definitions and storage classes, let’s begin by reviewing the source environment for the migrations.</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Navigate to vCenter via <a href="https://portal.vc.opentlc.com/ui/app/folder;nav=v/urn:vmomi:Folder:group-d1:ee1bef3e-6179-4c1f-9d2a-004c7b0df4e5/vms/vms" target="_blank" rel="noopener">https://portal.vc.opentlc.com</a></p>
</li>
</ol>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Login with the user <code>[email protected]</code> and the password <code>tlEOnKhrgRF9</code></p>
</li>
<li>
<p>By default you’ll see the VMs and Folders view, where you can see the four VMs representing the application.</p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/100_vSphere_VM_List.png" alt="100 vSphere VM List">
</div>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
The VMs with the suffix <code>_running</code> are the active ones. As for the migration have to be stopped, a clone of the VMs were created for the migration. Those VMs are the ones without that suffix.
</td>
</tr>
</table>
</div>
</li>
<li>
<p>Change to the networks view (or click <a href="https://portal.vc.opentlc.com/ui/app/dvportgroup;nav=n/urn:vmomi:DistributedVirtualPortgroup:dvportgroup-1916:ee1bef3e-6179-4c1f-9d2a-004c7b0df4e5/ports" target="_blank" rel="noopener"> this link</a>), then expand the tree to view the port group used by the virtual machines. Note that the name is <code>segment-migrating-to-ocpvirt</code>.</p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/101_vSphere_Network.png" alt="101 vSphere Network">
</div>
</div>
</li>
<li>
<p>Finally, review the datastore by browsing to the datastores view (or using <a href="https://portal.vc.opentlc.com/ui/app/datastore;nav=s/urn:vmomi:Datastore:datastore-48:ee1bef3e-6179-4c1f-9d2a-004c7b0df4e5/vms/vms" target="_blank" rel="noopener">this link</a>). Expand the tree to see the name of the datastore, <code>WorkloadDatastore</code>, and optionally browse to the <strong>VMs</strong> sub-tab to view the capacity used by each virtual machine.</p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/102_vSphere_Datastore.png" alt="102 vSphere Datastore">
</div>
</div>
</li>
</ol>
</div>
</div>
<div class="sect2">
<h3 id="_review_the_vmware_provider_to_the_migration_toolkit">Review the VMware provider to the migration toolkit</h3>
<div class="paragraph">
<p>The <strong>Migration Toolkit for Virtualization</strong> (<strong>MTV</strong>) uses the VMware Virtual Disk Development Kit (<strong>VDDK</strong>) SDK to transfer virtual disks from VMware vSphere. This VDDK has already been set up for you in this environment.</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Navigate in the left menu to <strong>Migration</strong> → <strong>Providers for virtualization</strong></p>
</li>
<li>
<p>Select project <code>openshift-mtv</code></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/91_MTV_Providers.png" alt="91 MTV Providers">
</div>
</div>
<div class="admonitionblock tip">
<table>
<tr>
<td class="icon">
<div class="title">Tip</div>
</td>
<td class="content">
MTV 2.4 and later are project/namespace aware and do not require administrator privileges. You can delegate VM imports to application teams and VM users so that they can self-serve and migrate at their own pace!
</td>
</tr>
</table>
</div>
</li>
<li>
<p>By default, there is a provider called <code>host</code> which represents the <strong>OpenShift Virtualization</strong> as a target platform</p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/92_MTV_Provider_list.png" alt="92 MTV Provider list">
</div>
</div>
</li>
<li>
<p>The lab is already configured with the VMWare provider named <code>vmware</code>.</p>
</li>
</ol>
</div>
</div>
<div class="sect2">
<h3 id="_create_storage_and_network_mappings">Create storage and network mappings</h3>
<div class="paragraph">
<p>Storage and networking are managed differently in VMware vSphere and Red Hat OpenShift. Therefore it is necessary to maps from the source datastores and networks in VMware vSphere to the equivalent in OpenShift so that the migration toolkit understands how to connect and place virtual machines after importing.</p>
</div>
<div class="paragraph">
<p>These only need to be configured once and are then reused in subsequent VM Migration Plans.</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Navigate in the left menu to <strong>Migration</strong> → <strong>NetworkMaps for virtualization</strong> and press <strong>Create NetworkMap</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/96_MTV_NetworkMaps.png" alt="96 MTV NetworkMaps">
</div>
</div>
</li>
<li>
<p>Fill in the following information in the appeared dialog. Press <strong>Create</strong>.</p>
<div class="olist loweralpha">
<ol class="loweralpha" type="a">
<li>
<p><strong>Name</strong>: <code>mapping-segment</code></p>
</li>
<li>
<p><strong>Source provider</strong>: <code>vmware</code></p>
</li>
<li>
<p><strong>Target provider</strong>: <code>host</code></p>
</li>
<li>
<p><strong>Source networks</strong>: <code>segment-migrating-to-ocpvirt</code></p>
</li>
<li>
<p><strong>Target network</strong>: <code>Pod network (default)</code></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/97_Add_VMWARE_Mapping_Network.png" alt="97 Add VMWARE Mapping Network">
</div>
</div>
</li>
</ol>
</div>
</li>
<li>
<p>Ensure the created mapping has the <strong>Status</strong> <code>Ready</code></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/98_List_VMWARE_Mapping_Network.png" alt="98 List VMWARE Mapping Network">
</div>
</div>
</li>
<li>
<p>Navigate in the left menu to <strong>Migration</strong> → <strong>StorageMaps for virtualization</strong> and press <strong>Create StorageMap</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/99_MTV_StorageMaps.png" alt="99 MTV StorageMaps">
</div>
</div>
</li>
<li>
<p>Fill in the following information. Press <strong>Create</strong>.</p>
<div class="olist loweralpha">
<ol class="loweralpha" type="a">
<li>
<p><strong>Name</strong>: <code>mapping-datastore</code></p>
</li>
<li>
<p><strong>Source provider</strong>: <code>vmware</code></p>
</li>
<li>
<p><strong>Target provider</strong>: <code>host</code></p>
</li>
<li>
<p><strong>Source storage</strong>: <code>WorkloadDatastore</code></p>
</li>
<li>
<p><strong>Target storage classs</strong>: <code>ocs-storagecluster-ceph-rbd (default)</code></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/100_Add_VMWARE_Mapping_Storage.png" alt="100 Add VMWARE Mapping Storage">
</div>
</div>
</li>
</ol>
</div>
</li>
<li>
<p>Ensure the created mapping has the <strong>Status</strong> <code>Ready</code></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/101_List_VMWARE_Mapping_Storage.png" alt="101 List VMWARE Mapping Storage">
</div>
</div>
</li>
</ol>
</div>
</div>
<div class="sect2">
<h3 id="_create_a_migration_plan">Create a Migration Plan</h3>
<div class="paragraph">
<p>Now that you have the virtualization provider and the two mappings (network & storage) you can create a Migration Plan - this plan selects which VMs to migrate from VMware vSphere to Red Hat OpenShift Virtualization and how to execute the migration (cold/warm, network mapping, storage mapping, pre-/post-hooks, etc.).</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
Depending on order of you doing the modules, you might be missing required <code>vmexamples</code> namespace here. If you haven’t done yet, do chapter <strong>OpenShift Virtualization Basics</strong> → <strong>Create a new Project</strong>)
</td>
</tr>
</table>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Navigate in the left menu to <strong>Migration</strong> → <strong>Plans for virtualization</strong> and press <strong>Create plan</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/102_Create_VMWARE_Plan.png" alt="102 Create VMWARE Plan">
</div>
</div>
</li>
<li>
<p>On the wizard fill the following information on the <strong>General settings</strong> step. Press <strong>Next</strong> when done.</p>
<div class="olist loweralpha">
<ol class="loweralpha" type="a">
<li>
<p><strong>Plan name</strong>: <code>move-webapp-vmware</code></p>
</li>
<li>
<p><strong>Source provider</strong>: <code>vmware</code></p>
</li>
<li>
<p><strong>Target provider</strong>: <code>host</code></p>
</li>
<li>
<p><strong>Target namespace</strong>: <code>vmexamples</code></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/52_General_VMWARE_Plan.png" alt="52 General VMWARE Plan">
</div>
</div>
</li>
</ol>
</div>
</li>
<li>
<p>On the next step, select <code>All datacenters</code> and press <strong>Next</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/53_VM_Filter_VMWARE_Plan.png" alt="53 VM Filter VMWARE Plan">
</div>
</div>
</li>
<li>
<p>On the next step select the three VMs: database, winweb01 and winweb02. Press <strong>Next</strong>:</p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/54_VM_Select_VMWARE_Plan.png" alt="54 VM Select VMWARE Plan">
</div>
</div>
</li>
<li>
<p>On the <strong>Network mapping</strong> step select <code>mapping-segment</code> and press <strong>Next</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/55_Network_VMWARE_Plan.png" alt="55 Network VMWARE Plan">
</div>
</div>
</li>
<li>
<p>On the <strong>Storage mapping</strong> step select <code>mapping-datastore</code> and press <strong>Next</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/56_Storage_VMWARE_Plan.png" alt="56 Storage VMWARE Plan">
</div>
</div>
</li>
<li>
<p>Press <strong>Next</strong> on the steps <strong>Type</strong> and <strong>Hooks</strong></p>
</li>
<li>
<p>Review the configuration specified and press <strong>Finish</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/57_Finish_VMWARE_Plan.png" alt="57 Finish VMWARE Plan">
</div>
</div>
</li>
<li>
<p>Ensure the status of the plan is <strong>Ready</strong></p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/58_Ready_VMWARE_Plan.png" alt="58 Ready VMWARE Plan">
</div>
</div>
</li>
<li>
<p>Press <strong>Start</strong> to begin the migration of the three VMs</p>
</li>
<li>
<p>After around 10 minutes the migration is completed</p>
<div class="imageblock">
<div class="content">
<img src="images/MTV/59_Completed_VMWARE_Plan.png" alt="59 Completed VMWARE Plan">
</div>
</div>
<div class="admonitionblock important">
<table>
<tr>
<td class="icon">
<div class="title">Important</div>
</td>
<td class="content">
<div class="paragraph">
<p>Having many participants performing the same task in parallel can cause this task to perform slower than in a real environment. Please be patient.</p>
</div>
</td>
</tr>
</table>
</div>
</li>
</ol>
</div>
</div>
<div class="sect2">
<h3 id="_review_and_configure_migrated_virtual_machines">Review and configure migrated Virtual Machines</h3>
<div class="paragraph">
<p>Your VMs have now been migrated and can be started on OpenShift Virtualization. You could connect to the VM consoles and interact with them as you would in VMware vCenter.</p>
</div>
<div class="paragraph">
<p>If you want to learn more about how to use OpenShift and Kubernetes features with the application hosted in the imported virtual machines, complete the optional module "Exposing apps using a Route".</p>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_summary">Summary</h2>
<div class="sectionbody">
<div class="paragraph">
<p>In addition to the Migration Toolkit for Virtualization, there are three other migration toolkits. The combination of these can be used to move many workloads into and within OpenShift clusters depending on your organization’s needs.</p>
</div>
<div class="ulist">
<ul>
<li>
<p><a href="https://developers.redhat.com/products/mtr/overview">Migration Toolkit for Runtimes</a> - Assist and accelerate Java application modernization and migration.</p>
</li>
<li>
<p><a href="https://access.redhat.com/documentation/en-us/migration_toolkit_for_applications/">Migration Toolkit for Applications</a> - Accelerate large-scale application modernization efforts to containers and Kubernetes.</p>
</li>
<li>
<p><a href="https://docs.openshift.com/container-platform/4.12/migration_toolkit_for_containers/about-mtc.html">Migration Toolkit for Containers</a> - Migrate stateful application workloads between OpenShift clusters.</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>For more information about these, please reach out to your Red Hat account team.</p>
</div>
</div>
</div>
<!-- Bottom Navigation -->
<div class="page-meta clearfix">
<input type="button" class="btn btn-lg btn-primary float-right" onclick="location.href='/workshop/03_ocpv_basics';" value="Continue" />
</div>
</section>
</div>
</div>
</div>
<!-- Footer -->
<footer class="footer">
</footer>
<!-- Javascript-->
<script src="js/workshop.js"></script>
<script src="js/workshop-asciidoc.js"></script>
</body>
</html>