►
From YouTube: OCB AMA: Introducing the Migration Toolkit for Virtualization (MTV) - Miguel Perez Colino (Red Hat)
Description
Join this briefing and learn how to Migrate virtual machines to OpenShift Virtualization using Red Hat’s new Migration Toolkit for Virtualization (MTV) which is now available as a tech preview. MTV allows customers to migrate virtual machines at scale from VMware vSphere to OpenShift Virtualization in a few simple steps. The tooling provides source and destination credentials, maps infrastructures, and will even detect potential compatibility issues allowing customers to perform rapid and comprehensive migrations while minimizing time to value with Kubernetes-orchestrated OpenShift virtualization.
A
A
B
Sure
sure
well,
my
name
is
miguel
perez
colino,
I'm
I'm
a
product
manager,
I'm
the
product
manager
for
migration,
tokyo
for
virtualization
and
I'm
in
the
my
modernization,
migration
team
in
red
hat
and
well
I'm
taking
care
of
this
tool
that
has
reached
beta
stage
just
last
week
and
I
was
like
okay,
I
have
to
go
to
official
commons
to
show
it.
So
we
are
gone.
B
Okay,
so
first
things
first
open
shift,
containers
and
vm,
so
the
migration
took
it
for
virtualization
is
intended
to
move
virtual
machines
from
initially
from
vmware
to
openshift,
and
then
the
future
will
add
more
sources
and
will
keep
the
same
target
and
the
target
is
open
ship
virtualization.
So
what
is
this
about?
You
know.
So
this
is
saying
you
know:
containers
are
not
virtual
machines
and
another
saying
that
goes.
Containers
are
linux.
Linux
is
containers,
so
the
containers
is
a
way
to
isolate
process.
B
But
the
thing
is
that
you
know
in
in
linux
virtual
machine,
it's
also
a
process,
and
we
could
encapsulate
that
process
and-
and
the
thing
is
that
the
operating
system-
linux,
has
the
kernel
virtual
machine,
which
is
like
an
engine
to
be
able
to
run
virtual
machines,
which
is
used
like
in
almost
every
public
cloud
for
for
virtualization
purposes,
and
the
thing
is
like
well.
This
is
very
performant.
B
Try
to
think
what
one
percent
increase
in
performance
would
be
into
a
public
cloud.
So
try
to
understand
that
I
mean
this
is
like
a
super
super
good
engine
for
virtual
machines
and
it's
included
in
linux.
It's
included
in
enterprise,
linux
and
core
os
that
they
use
with
same
kernel
with
same
kvm.
So
we
could
leverage
that
and
all
the
experience
we
have
in
in
rehabilitation
and
openstack
to
be
able
to
build
virtual
machine
capability
on
on
openshift.
So
this
is
how
we
get
to
openshift
visualization
what
is
happening
virtualization
well.
B
You
know
like
this
declarative
way
of
deploying
infrastructure,
all
the
operational
benefits
with
prometheus
to
gather,
metrics
and
all
those
better
fields
that
you
know,
unlove
from
openshift,
plus
the
the
interfaces
to
network
and
storage.
That
operation
has
been
developed
for
so
long.
So
that's
good.
But
what
is
what
is
this?
For
you
know
it's
all
about
modernization
and
migration.
You
know
customers
and
users
worldwide
and
developers.
B
They
all
want
to
to
become
more
modern
because
it
brings
a
lot
of
benefits.
So
when,
when
development
teams
start
using
containers,
they
become
more
agile
faster,
they
have
a
lower
time
to
market.
They
release
more
frequently
in
case
there's,
an
incidence
their
time
to
restore
is
reduced.
There
are
these
metrics
that
we
all
know
that
getting
proof
when
you
start
working
in
a
in
a
cloud-native
way.
B
B
Modernize
them,
so
it's
a
lower
friction
way
to
bring
those
vms
into
a
container-like
world
and
have
one
converged
infrastructure
for
those
critical
workloads
that
you're
going
to
manage
and
then
be
able
to
do
all
that
low
modernization
process
step
by
step
during
during
the
time.
So
what
are
we
thinking?
B
What
if
we
could
automatically
convert
vmware
images
to
kvm
images
on
openshift?
Well,
that
would
lower
the
cost
of
migrating
the
workloads?
Okay.
So
that's
a
direct
benefit
of
this.
So
what
would
this
look
like?
So
let's
say
we
have
this
weblogics
with
apache
front-ends
and
a
database
running
on
vmware.
We
could
move
them
to
virtual
machines
and
then
modernize,
for
example
the
apaches.
They
are
pretty
easy
and
then
put
those
apaches
in
containers
or
even
change
it
for
nginx
and
then
be
able
to
okay,
all
those
contents
make
them
drive
them
to
containers.
B
Then
we
could
move
to,
for
example,
take
some
applications
from
weblogic
to
jboss
or
keep
them
in
web
logic
on
containers.
That's
something
you
could
also
do
on
openshift
running
weblogic
in
containers
same
as
websphere
jboss,
but
in
this
case,
let's,
let's,
let's
think,
okay,
we're
going
to
move
this
application
to
jboss,
let's
modernize,
the
application,
let's
make
it
leaner
and
more
standards
oriented,
so
you
can
run
on
jboss.
B
B
How
do
we
approach
this?
Well,
you
have
the
workloads
and
there
are
some
strategic
workflows
and
some
not
a
strategic
workloads
that
you
could
analyze
with
assess
with
pathfinder
and
analyze
with
migration
toolkit
for
applications
and
well,
what
can
you
do?
You
could
replat
from
them
as
vms.
You
know,
so
you
just
move
them
whenever
they
are
vms
as
vms.
Whenever
containers
as
containers,
you
could
refactor
them
and
repackage
them
as
containers.
So
you
do
the
modern
nicely
application.
B
You
could
repurchase
if
it's
a
third-party
application
and
then
put
them
in
openshift
projects.
So
you
test
them
in
openshift,
oh
they're,
good
they're,
not
good,
we
fix!
Then
we
test
it
they're
good,
once
they're
good
you
deploy
to
production
and
openshift
and
then
you're
modernizing
what
if
we
want
to
further
enhance?
Well,
we
could
go
to
the
refractive
loop
again
and
improve
improve
improve.
So
this
is,
for
example,
a
pattern
that
we
have
seen
with
large
monolids,
that
you
split
them
and
you
modernize
them,
organize
them
modernize
them,
and
then
modernization
is
complete.
B
What
do
you
do
with
the
non-strategic
workloads?
Well,
retire.
Re-Host
retain
so
some
of
them.
You
could
retire
them
some
of
them.
You
could
re-host
them
some
of
them.
You
could
retain
the
the
retire
has
like
a
second
fold
like,
for
example,
if
you're
running
your
own
email
process,
probably
you
want
to
move
it
as
software
as
a
service,
so
there
are
several
options
for
the
non-strategic
workloads
that
are
could
be
provided
as
a
service
that
you
could
consider
working
on.
So
we
are
working
mostly
on
every
platform.
B
Refactor
and
reports
focused
on
the
platform
and
refactor
for
migration.
Token
for
virtualization
is
fully
re-platformed
to
move
vms
from
vmware
to
opencv
virtualization.
What
are
the
benefits
and
the
operating
costs?
Well,
you
see
there
are
more
operating
costs
in
every
host
of
retained
because
you
have
to
keep
your
current
infrastructure.
B
If
you
retire,
it's
pretty
easy,
but
you
lose
some
services
and
then,
when
you
do
re-platform,
there's
more
business
benefit
and
when
you
do
refactors,
there
are
even
more
business
benefits
that
you
could
obtain
by
doing
this
this
one.
So
what
do
we
do
in
in
my
team?
Well,
we
have
tools
for
these
cases.
B
In
re
house
we
have
a
tool
called
mtc
magazine,
okay
for
containers
that
the
upstream
project
is
called
crane,
then
for
the
re-platform
we
could
move
containers
using
move
to
cube
that
will
bring
the
the
containers
running
on
cloud
foundry
to
to
openshift
and
forklift,
which
is
the
upstream
for
the
migration
toolkit
for
vitalization
to
move
vms
into
into
openshift
virtualization
as
vms,
and
then
the
refactor.
You
have
the
pathfinder
and
wind
up
projects
that
will
result
into
the
migration
token
for
applications.
B
These
are
the
migration
toolkits
and
then
you
will
be
able
to
analyze
and
assess
the
applications
to
be
able
to
first
with
the
assessment
be
able
to
choose
which
applications
to
work
first
and
then,
with
the
analysis
to
be
able
to
to
start
transforming
them
to
put
them
in
in
containers
about
the
tool.
Any
questions
so
far
is
there
anything
on
top.
B
Okay,
I
keep
going
so
what
I
said.
We
have
these
projects
in
the
upstream
there's.
This
substrate
is
conveyor.io
project.
I
really
suggest
you
to
visit
it.
If
you
go
to
github.com
conveyor,
you
will
find
all
the
projects
that
we
put
in
there.
Some
of
them
were
still
not
migrated.
This
is
like
pretty
fresh,
pretty
new,
so
we
suggested
to
go
there
they're,
like
mailing
lists.
B
There
are
forums
and
we
we
even
have
some
meetups
to
show
like
the
interlinks
and
all
the
technical
stuff
on
the
projects
and
be
able
to
to
help
everybody
to
join
and
be
able
to
contribute.
So
you
see
this
project
crane,
forklift
and
tackle
crane.
Then
we
have
the
downstream,
which
is
the
tool
that
we
provide
the
migration
okay
for
containers
to
migrate
from
openshift
three
to
four
and
also
from
four
to
four.
B
B
Where
are
we
now
well,
the
beta
is
out.
So
it's
very
easy
for
you.
If
you
are
an
openshift
to
be
able
to
install
it-
and
I
will
demo
it
in
in
some
minutes
about
the
architecture,
everything
openshift
everything
container
native
everything
in
in
containers.
So
we
are
using
all
the
natives
that
we
can.
You
see
that
we
have
a
source
which,
in
this
case
is
vmware
vsphere
and
during
this
year
we'll
be
adding
rehabilitation
and
openstack
as
sources,
but
just
in
case
you
want
to
move
vms
from
the
resources
to
openshift
virtualization.
B
We
have
an
inventory
service
that
is
going
to
gather
all
the
information
from
vmware
via
sphere
and
we
have
a
validation
server
that
is
going
to
check
okay.
How
is
this
vm
configured
and
it's
going
to
do
to
run
checks
there,
and
if
something
is
not
right,
it
will
raise
it
and
we'll
say
hey.
I
found
this.
That
could
be
an
inconvenience
to
migrate
this
vm
into
opposite
virtualization,
so
you
do
not
start
a
migration
that
could
fail.
B
Okay,
so
maybe
you
need
to
check
things
like
raw
device
mappings
that
are
attached
to
the
vm
and
that
you
want
to
keep
as
well
as
mappings
or
that
two
vms
are
sharing
the
disk
and
you
don't
want
to
end
up
with
two
vms
with
two
disks,
but
to
begin
with
one
single
disk
that
is
attached
to
both
of
them.
These
kind
of
things
are
the
ones
that
are
checked
before,
so
the
migration
is
run
as
smoothly
as
possible.
B
B
Of
course,
built
with
pattern,
five
four:
I
love
the
pattern
flight
project
it
makes
project,
it
makes
our
interfaces
look
so
nicely,
and
the
thing
is
that
we
try
to
make
it
as
simple
and
nice
as
possible
to
be
able
to
be
used
even
if
it's
powerful
try
to
make
it
really
simple
and
nice
to
to
use
and
what
do
we
have
in
there?
We
have
mappings
to
be
able
to
map
resources
from
source
to
target.
B
We
have
migration
plans
to
be
able
to
say,
okay,
which
vms
are
going
to
be
migrated
in
the
same
batch,
and
then
we
have
the
migration
run
to
execute
the
migration
and
then,
of
course,
there's
the
controller
and
then
there's
a
capability
to
import
vms
in
opencv
utilization
that
will
leverage
to
be
able
to
to
move
it
and
then,
of
course,
the
import
operator
that
is
handled
by
it.
So
this
is
the
architecture.
B
If
you
want
to
have
another
session
with
more
technical
details,
we
can
invite
my
friend
fabiendo
pong,
and
we
could
have
another
session
to
talk
about
the
internals
else.
Okay,
provide
this
first
thing:
we
need
to
connect
source
and
target.
So
we
have
a
provider
that
is
the
sources
right
now
vmware
v
sphere,
and
we
have
the
target
that
is
open
ship
virtualization.
B
So
you
have
to
connect
the
tool
to
the
provider
which
would
be
vmware
vsphere,
provide
the
credentials
and
also
to
the
target
when
you
deploy
migration
token
for
virtualization
the
openshift
instance
in
which
you
deploy
it,
it
gets
configured
automatically
as
a
target,
so
very
easy.
If
you
want
to
do
a
simple
migration,
it's
going
to
be
very
straightforward
for
you,
so
we
use
the
sources
the
destination,
so
we
have
okay.
This
is
from
where
to
where
so
and
now
how?
How
do
we
change?
What
is
already
there?
B
So
normally
what
you
have
in
the
source
is
a
set
of
configured
networks
they
normally
attach
to
the
to
vlans,
depending
on
how
you
configure
it.
But
it's
pretty
common
that
you
have
a
certain
set
of
vlans
that
you
attach
to
your
virtualization
network,
that
one
of
them
is,
for
example,
to
access
the
storage.
Another
one
is
for
administration,
another
one
is
internal.
Another
one
is
the
dmc
to
be
able
to
publish
services
outside
of
of
your
environment.
So
these
are
the
network
mappings.
B
The
network
configuration
that
you
have
in
your
source
and
you
have
to
create
the
mappings.
Now
you
have
to
do
it.
So
what
you
do
is
that
you
deploy
your
new
environment,
your
openshift
environment,
and
you
configure
these
networks
in
openshift.
So
do
once
you
have
configured
the
networks.
If
you
could
extend
the
vlans,
it
will
be
a
lot
easier.
B
Then
it's
very
simple:
you
just
take
one
vm
from
source
to
target
and
it
will
be
connected
to
the
exactly
the
same
network.
It
was
in
the
source.
If
not,
of
course,
you
can
always
change
the
addressing,
but
I
mean
if
you
can
extend
the
the
networking
configuration
will
be
the
easiest
way
to
do
it.
So
with
this
we
can
map
the
networks
in
the
source
to
the
networks
in
the
target
and
be
able
to
make
them
equivalent.
B
So
this
is
a
very
simple
way
not
to
have
to
be
changing
everything.
Every
time
you
move
a
vm
is
intended
for
mass
migration
with
the
storage.
We
do
something
very
similar.
You
have
your
storage
configuration
with
your
data
stores
in
your
vmware
environment
and
you
have
your
storage
configuration
with
your
storage
classes
in
in
openshift.
B
So
it's
very
important
to
select
the
storage
in
the
source
similar
to
the
storage
in
the
target,
so
the
storage
itself,
sometimes
you're
using,
I
don't
know,
nfs
iscsi,
sometimes
even
fiber,
channel,
depending
on
the
I
o
that
you're
going
to
require
and
then
in
the
target.
You
have
something
like
ceph.
For
example,
we
have
another
iscsi
provider
or
an
nfs
provider
that
you
have
configured
as
a
as
a
storage
class,
but
you
can
allocate
persistent
volumes
automatically.
B
So
you
map
a
to
b.
This
data
store
is
going
to
be
mapped
to
this
storage
class
in
the
target.
So
whenever
you
start
migrating,
a
disk
is
going
to
be
created
in
the
target,
which
is
due
to
the
mapping
equivalent
to
the
source.
This
way
we
map
source
and
target,
and
we
make
it
very
easy
to
perform
a
mass
migration.
B
Okay,
I
keep
going.
Please
interrupt
me
if
there's
any
question
coming
in
in
the
chat
or
if
you
want
to
to
ask
anything
so
next
step.
So
we
have
the
maps,
we
create
the
migration
plan.
This
is
where
we
select
the
vms.
Of
course,
we
have
all
the
ways
to
filter
the
vms,
to
to
make
it
easy
to
to
select
the
vms
that
we
want
in
many
many
customers
that
I've
visited
and
met
and
work
with
they
have
like
their
own.
B
Their
name
in
the
structure,
so
filtering
by
vm
name
is
usually
very,
very
common,
very
easy,
but
if
you
want
to
choose
also
the
data
center
or
filter
by
cluster,
it's
very
easy
to
filter
the
vms
and
get
a
set
of
vms
that
you
want
to
migrate
together.
So
let's
say
that
you
filter
it,
you
get
like
20
25
vms
to
be
migrated,
you
select
them
and
then
you
assign
the
network
mapping.
Of
course,
it
will
check
that
the
the
network
in
the
vm
selected
is
in
the
network
mappings,
and
it
will
not.
B
B
So
you
could
automate
all
the
process
before
the
migration
and
then
after
the
migration
re-engage
with
monitoring
reattach
the
vm
to
to
the
load
balancer
or
perform
any
changes
that
you
would
like
to
to
do.
Do
it.
So
this
way
we
ensure
that
all
the
tasks
that
you
want
to
do
during
the
migration
could
be
done.
It's
not
going
to
be
ready
for
the
tutorial,
but
it's
going
to
come
in
the
next
versions
and
then,
of
course,
we'll
be
able
to
monitor
the
migration
fraud.
B
Progress
cancel
who
doesn't
like
a
progress
bar
right,
so
we
are
we
already.
We
already
included
a
progress
via
a
way
to
monitor
how
things
are
going
and
then
a
bit
more
about
world
and
where
we
stand.
As
I
said,
we
released
last
week,
the
beta
with
the
capabilities
to
do
mass
migration,
and
we
are
preparing
in
may
to
launch
the
ga
with
warm
migration.
B
So
we
are
looking
forward
helping
our
our
friends.
Our
success
means
out
there
when
they're
doing
their
migrations,
so
they
could
make
the
most
of
their
migration
windows.
Also,
the
pre-migration
checks
to
be
able
to
check
the
vms
before
doing
migrations
to
detect
potential
compatibility
issues
before
migrating.
B
What
else
well
any,
if
you
have
any
other
questions,
comments
contributions,
any
suggestion
anything
you
want
to
tell
us,
I
mean
we
have
this
email
migrate
at
redhat.com.
Please
use
it.
Please
send
us
your
your
questions.
Please
send
us
your
suggestions
and
if
you
have
any
doubt
of
course
share
it
with
us
and
let
us
know
because
I
mean
the
whole
team
is
here
listening
to
to
help
you.
So
we
have
this
email
for
you
to
to
be
able
to
contact
us,
and
that
would
be
it.
I
mean
I'm
willing
to
show
it
to
you.
A
B
B
So
what
we
do
is
that
we
connect
just
like
any
other
backup
software
using
vmware
certified
mechanism
to
do
babacab,
which
is
using
bddk,
and
we
are
using
this
bddk
to
extract
the
data
and
the
current
supported
bddk.
It's
only
supported
for
6.5.
However,
we
know
that
this
is
backwards
compatible
and
that
and
that
you
could
use
it
to
to
to
access
any
other
previous
version
of
of
vmware.
B
B
B
B
B
Are
you
able
to
share
stories
between
the
target
vms
running
on
key
first
okay?
So
this
is
more
an
opposite
virtualization
question,
so
I
I'm
not
completely
up
to
date
on
the
status
of
shared
storage
of
office
virtualization.
So
I
don't
want
to
say
something
that
is
wrong,
but
I
mean
you
could
check
in
the
in
the
documentation
of
operative
virtualization
the
official
documentation
and
it
will
stay
there.
So.
A
A
B
So
we
built
a
provider
for
vmware
to
be
able
to
import
for
from
vmware,
and
we
are
working
in
building
another
provider
for
rehabilitation
and
by
the
end
of
the
year.
We
can.
We
want
to
work
on
another,
adding
another
provider.
But
of
course,
if
somebody
wants
to
try
to
build
his
or
her
own
provider
for
azure,
amazon
or
whatever,
and
they
want
to
share
it
in
the
community.
A
Nice,
thank
you,
two
more
questions
and
then
we'll
get
to
your
demo
and
then
even
more
questions
after
that,
all
right
vm.
What
about
vmware
tools
after
migration?
With
all
the
recommendations?
Do
you
recommend
cleanup
of
vms
prior
to
migration
like
cleaning
up
your
temp
files,
downloads,
old
programs,
etc?.
B
This
tool
was
created
to
extract
vms
from
from
vmware
and
put
them
into
qmo
or,
for
example,
over
a
hundred
plus
linux
or
any
other
qm
supported
environment.
So
it
could
be
used
to
import
into
ref.
It
could
be
used
to
import
into
openstack
and
we
are
leveraging
it
to
import
into
opposite
virtualization.
B
So
one
of
the
things
that
v2v
does
is
that
it
streams
the
disk
and
while
streaming
the
disk,
it
removes
all
the
vmware
drivers
and
tools
so
whenever
it
reads
and
adds
the
drivers
necessary
for
the
target
like
the
rear,
tire
drivers.
So
whenever
the
the
vm
arrives
at
the
target,
it
will
be
booted
and
it
will
be
put
correctly
because
it
has
the
right
drivers.
B
B
The
benefit
is
that
you
can
plan
this.
You
can
plan
it
with
the
list
of
of
vms
the
other
benefits
that
would
you
go
into
whenever
it
goes.
Ga
you're
going
to
be
able
to
check
that
the
vm
is
doesn't
have
anything
that
will
make
it
they
will
render
it
as
unbootable
or
unable
to
to
be
migrated
before
to
migrate.
B
So
we're
going
to
check
that
and
then
the
third
benefit
that
we're
we
are
working
on
delivering
for
ga
in
may
is
that
you
will
be
able
to
do
a
pre-copy
before
doing
the
migration.
So
whenever
you
do
the
migration,
you
only
have
to
copy
the
delta
and
reduce
the
amount
of
time
necessary
to
do
that
that
migration.
B
Cool
so
openshift
openshift
virtualization
right,
so
you
have
your
openshift
instance
and
it's
opposite
utilization
is
supported
on
bare
metal
nodes.
You
will
need
some
bare
metal
nodes
to
have
it
supported,
although
you
could
enable
nested
virtualization,
like
I
do
here,
so
things
are
going
to
go
a
bit
slowly
because
we
we're
going
to
be
using
nested
virtualization,
but
I
expect
this
to
to
work
properly.
So
this
is
our
lab
environment.
This
is
openshift
4.7,
as
you
can
see
here.
This
is
the
support
version.
B
I
can
go
to
the
installed
operators
and
choose
and
choose
all
projects,
and
I
will
see
that
I
have
openshift
virtualization
operator
installed
and
configured.
So
you
have
this
opposite.
Virtualization
version.
260
is
the
one
we
are
testing
on.
So
if
you
want
to
run
on
a
tested
environment,
then
you
should
run
a
migration
to
create
for
virtualization
on
top
of
opposition
260..
B
So
what
do
you
need
to
do?
You
can
install
migration
token
for
virtualization
the
operator
and
then
you
will
be
able
to
use
it.
So
how
do
you
use
it?
Well,
I
just
can
go
this
when
you
start
it.
You
get
like
a
project
created,
openshift
does
rh
mtb
and
if
you
go
to
networking
for
this
project
and
you
check
on
routes,
there's
a
published
road,
which
is
the
interface
to
the
migration
token
for
virtualization,
which
I
haven't
opened
here
yeah,
so
I
let
it
load.
This
is
the
interface
okay.
B
A
B
B
B
So
I
log
in
here
it's
logging
in
okay,
I'm
I'm
in
spain
and
the
cluster
is
in
boston,
expect
some
delays
while
running
this
demo,
but
I
mean
I've
run
it
a
couple
of
times
and
it
worked
well.
So
I
can
get
started.
I
see
the
providers.
This
is
the
provider
where
the
the
the
operator
was
installed
and
instantiated
and
it
has
found
seven
storage
classes
and
is
completely
ready.
So
I
could
add
the
provider
now
and
I
could
select
vmware
and
just
provide
a
name
to
it
vcenter
and
then
provide
a
host
name.
B
I
type
the
password,
then
the
fingerprint
this
is
to
ensure
that
we're
connecting
to
the
right
vmware
provider
and
we're
not
connecting
to
something
else.
So
once
we
do
that,
it's
going
to
connect
to
vmware,
I
could
go
to
provide
this
vmware.
It's
going
to
check
if
everything's,
okay,
it's
gathering
the
data.
You
see
two
clusters
here:
two
hosts
56
pm,
13
networks,
four
data
stores
and
now
it's
ready.
So
we
have
the
provider
ready,
the
target
provider,
sorry,
the
source
provider.
We
have
the
target
provider,
obviously
virtualization,
both
of
them
ready.
B
So
now
we
could
create
the
mappings.
I
could
go
and
create
network
mapping.
So
I
create
the
mapping
and
I
name
it-
you
know
name
it
mapping
network,
because
I'm
very
original.
So
I
choose
mapping
network,
I
choose
the
provider,
the
source
and
the
target,
and
I
have
to
choose
the
network
equivalences.
B
B
B
Storage
mapping,
select
the
provider
b
center
select
the
target
host
and
then
I
know
that
my
vm
is
running
on
the
nfs
data
store,
but
I
mean
I
could
map
the
other
ones
and
I
want
to
use
the
storage
clusters
of
rbd
because
I'm
using
openshift
container
storage
here
so
it's
properly
distributed,
it's
software
defined
and
it
works
really
well,
so
I
could
create
this
map
and
I
have
the
two
maps
ready
now.
Let's
migrate,
I
go
to
migration
plans,
I
create
a
migration
plan
and
I
give
it
a
name.
B
B
Okay,
and
if
you
click
here
it
will
create
for
me
this
namespace,
okay,
good.
Next,
then
I'm
going
to
filter
the
vms,
I'm
going
to
choose
this
cluster,
which
my
vms
are
running
and
then
I'm
going
to
click
next
and
then
it's
getting
all
the
list
of
vms.
So
there's
a
lot
of
people
working
here,
I'm
going
to
filter
the
vms
by
my
name
and
there
we
have.
We
have
this
relate
vm.
That
is
running
that
I'm
going
to
migrate.
I
chose
a
small
vm
to
make
this
migration
quick,
so
we
could
see
it
happening.
B
So
I
select
this
vm
I
could
select
like
20
vms.
If
I
wanted
to
no
problem
with
that
or
30
or
100,
and
then
I
choose
the
network
mapping
select
this
one.
Next,
I
choose
the
storage
mapping.
You
see,
I
could
create
a
new
storage
mapping
in
case.
I
was
missing
it
here
next
and
then
I
review
the
result.
These
are
the
results
I'm
going
to
make
with
only
one
vm.
B
B
B
This
is
the
progress
bar
of
the
number
of
the
vms
migrated.
So
in
this
case
it's
only
one.
So
it's
going
to
go
from
these
two
to
green
and
but
we
could
check
here
if
we
go
to
the
details
that
right
now
is
in
the
transparent
disk
face
and
it's
copying
the
first
gigabyte
of
data
out
of
nine.
So
it's
going
to
be
copying
and
streaming
the
data
and
then
it
will
convert
the
image
to
keep
vert
doing
all
these
transformations
about
the
drivers
that
I
mentioned
and
cleaning
up
the
tools.
B
So
when,
when
completed,
it
will
be
totally
done,
so
this
is
not
running,
I
could
go
to
openshift.
I
could
go
to
overview
projects
and
then
select
the
project
that
I
just
typed
mtv
migrate,
and
this
is
the
project
that
has
been
created
for
me.
Wasn't
here
before
I
can
click
on
details,
workloads
and
then
a
vm
will
be
created
here
in
the
workloads
and
I
will
be
able
to
check
on
it.
B
B
It's
like
super
super
simple.
I
mean
we
have
our
friends
in
user
experience
and
design
are
working
with
us
and
are
making
things
like
super
easy
super
easy
to
understand
and
very
well
located,
and
then
the
engineering
team
is
focusing
on
making
this
as
robust
as
possible.
So
we
end
up
with
these
tools,
as
you
see
like
very
simple
and
I'm
very
reliable,
so.
B
B
B
So
these
are
the
two
tools
that
we
have
available
so
in
case
you
want
to
re-platform
and
bring
virtual
machines
to
kubernetes.
You
could
use
mtv
and
let's
say:
okay,
I'm
moving
20
vms
with
jboss
enterprise,
application
platform
to
containers,
and
I
want
to
turn
those
applications
into
into
something
apply
a
stronger
pattern
and
be
able
to
turn
it
into
microservices
or
I
haven't
running
in
in
webaspire
or
tomcat,
and
I
want
to
put
them
in
containers.
So
there
are
a
set
of
paths
that
mta
covers.
B
The
migration
took
it
for
applications
and
what
mta
is
going
to
do
is
analyze
the
application
of
the
application
level.
But
what
you
can
do
is
that
you
take
the
vm
as
it
is
in
vmware
and
bring
it
to
openshift,
and
then
you
already
have
other
developers
working
in
openshift
with
an
environment
built
for
developers
that
developers
enjoy
and
understand.
You
can
manage
it
in
in
a
way
which
you
could
manage
all
your
environment
for
cloud
native
applications,
but
with
virtual
machines
to
make
the
transition
even
smoother.
B
So
once
the
vms,
with
your
weblogic,
let's
say
they
are
running
on
your
opencv
virtualization.
You
will
be
able
to
take
those
applications
and
analyze
them,
and
the
thing
is
that
what
mta
does
is
pretty
simple.
You
know,
and
I
can
run
it
for
you.
I
have
it
here,
so
you
just
have
to
give
it
an
application.
It
will
analyze
it
and
will
tell
you
what
do
you
need
to
change
in
the
application
to
do
that
migration.
B
So
for
that
I
mean
you
could
go
to
red.xt,
slash,
mta
and
download
it.
This
is
version
5.1.
So
far,
so
you
just
download
the
zip
file
and
zip.
It
run
the
script
that
suggested
and
then
you
will
be
able
to
run
the
migration
token
for
applications,
analyze
your
applications
and
then
this
is
what
you
will
see
and
you're
getting
two
demos
at
the
price
of
one.
So
this
is
an
application
that
I
analyzed
that
is
completely
ready
to
run
on
java,
cip,
whereas
this
other
one
has
some
web
logic,
proprietary
artifacts.
B
That
need
to
be
changed.
I
could
dig
down
into
this
application,
check
the
issues
and
be
able
to
check
look
I'm
using
the
weblogic
property
logger
and
you
need
to
change
it.
So
these
are
the
two
parts
that
you
could
follow
and
normally
you
follow
first
migrating.
The
vms
then
migrating
the
applications,
although
sometimes
it
makes
more
sense
to
do
the
application
migration
directly
depending
on
the
status.
B
A
B
How
do
they
want
to
do
this
this
modernization
and
how
to
get
to
this
journey,
to
the
open,
hybrid
cloud
to
to
have
a
better,
to
provide
a
better
service
for
their
own
clients
and
to
be
able
sometimes
to
expand
their
addressable
market
and
be
able
to
grow
faster,
so
yeah?
If
we
could
help
our
customers
in
that
way,
they
were
always
willing
to
do
it.
A
A
B
Yeah,
the
the
v-volts
so
far
what
we
have
tested
if
they
behave
they're
like
some
corner
cases
there
in
which
we
we
we
find
some
issues
when
obtaining
the
data
from
the
vivos,
but
is
is
very
unlikely
to
happen.
You
know
because
again,
the
way
we
are
extracting
the
data
from
the
vm
is
the
same
way.
A
backup
solution
would
do
and
vmware
wants
their
backup
vendors
to
work
well
with
their
v-bulbs.
B
A
B
B
So
this
is
the
direction
we
are
heading.
Of
course,
as
I
said,
we
are
choosing
the
safest
path,
so
right
now
this
beta.
What
it
does
is
that
it
powers
down
the
vm
and
then
it
starts
copying
the
data
with
the
vm
power
down.
So
the
vm
is
in
a
consistent
state
and
then
it
powers
up
the
vm
in
the
target,
but
it
doesn't
remove
the
vm
industry.
A
B
This
is,
this
is
something
you
got
me,
I'm
I'm
not
completely
sure
the
previous
behaviors
that
we
collapsed
the
snapshots,
so
we
didn't
have
any
issue
with
the
snapshots
I
mean
vmware
is
telling
all
the
customers
look,
don't
use
the
snapshots
for
backup.
So
if
you
have
a
snapshot,
they
should
be
able
to
be
collapsed.
B
C
Yeah,
just
just
a
quick
note
on
that,
we
are
not.
We
are
not
deleting
snapshots,
so
actually
it
was
in
ims,
ims101
and
start
in
ims.
1.2
we
validated
that
it
works
without
removing
snapshots
at
all.
So
we
kept
on
that
line
and
the
snapshots
are
not
a
problem
from
the
vmware
point
of
view.
If
the
vm
is
down
we're,
actually
it's
going
to
use
the
current
state
of
the
vm
as
a
base
to
do
the
transfer.
C
C
For
one
migration
we
are
creating
snapshots
or
change
block
tracking,
but
normally
they
shouldn't
affect
normal
snapshots.
It's
something
that
we
need
to
verify
in
with
real
virtual
machines
that
we
kind
of
try
to
break
and
see
and
see
how
it
happens,
but
that's
something
in
our
test
plan
for
the
one
migration.
B
B
A
C
A
A
C
Well,
it's
still
alive,
but
sleeping
so
we
should
just
shut
the
vm
down,
but
the
vm
is
not
removed
as
we
as
miguel
explained,
we
keep
it
as
a
as
a
backup
plan.
So
if
anything
is
wrong
on
the
destination,
you
can
still
roll
back.
Your
vm
is
there
and
it's
an
easy
rollback
and
really
fast.
That's
why
we
keep
it.
We
keep
them.
C
No
major
issues-
one
thing
we've
noticed
is
that
we've
seen
sometimes
windows
machine
not
really
appreciating
to
be
migrated,
but
usually
it
well
trying
the
same
vm
from
a
different
view.
Center
worked
like
it's.
We
we
considered
more
than
being
an
environment
issue
in
the
in
the
test
labs
we
have,
rather
than
a
vm
or
conversion
issue
on
third
v2e
from
a
network
convention.
Point
of
view.
Of
course,
the
faster
the
network
is
better
to
reduce
the
downtime.
Mainly
it's
really
a
question
of
downtime.
C
We
are
doing
a
test
in
psi
and
it's
not
super
fast
environment,
because
we
are
sharing
the
network
with
many
other
projects,
so
sometimes
it's
quite
slow
and
well.
The
migration
goes
to
the
end.
It
works.
It's
just
that
you
have
to
be
patient,
so
yeah.
We
really
advise
to
have
a
network
benchmark
before
you
start
doing
mass
migration
to
have
a
clear
assessment
of
what
the
platform
can
support.
C
You
also
don't
want
to
crash
the
network
and
have
an
impact
on
running
vms
or
on
backups,
because
they
are
likely
to
use
the
same
the
same
via
the
same
storage
back
end
too.
So
if
you,
if
we
have
two
two
processes,
reading
the
same
disk
at
the
same
time,
going
to
like
probably
slow
down
the
backup,
which
is
not
a
good
idea,
if
you
want
to
keep
your
if
you
need
to
roll
back.
A
A
B
It
will
be
we're
working
on
it,
so
let's
say
that
for
third
quarter
of
this
year
we,
if
everything
goes
beautiful
and
wonderful,
we'll
be
able
to
have
ref
as
a
source
and
then
by
the
end
of
the
year,
we
want
to
have
openstack.
So
it's
in
the
plan,
it's
we're
already,
considering
it.
Other
providers
like
hyper-v
or
nutanix
are
not
in
in
the
plan
right
now.
However,
if
somebody
wants
to
contribute
that
we
are
more
than
willing
to
listen
to
them
and
to
help
them
ramp
up
to
be
able
to
build
it.
A
B
We
just
we
just
updated
recently,
so
you
can
have
all
the
information
here.
All
the
projects,
re-host
containers
with
hospital
machinery,
platform
measure,
software
delivery,
performance,
refactor
applications
to
kubernetes
and
meetups
that
we
do
also
that,
with
with
content
on
on
on
real
world
example,
in
many
cases
in
which
well,
we
invite
people
that
to
the
community
that
are
especially
in
the
field
working
with
with
customers
that
could
provide
hints
and
feedback
on
how
to
to
perform
a
good
migration
and
what
to
avoid
and
what
to.
What
are
the
good.