►
From YouTube: Application Modernization and Migration with Konveyor Ramón Román Nissen (Red Hat) OSCG 2022 Spain
Description
Application Modernization and Migration with Konveyor
Speaker: Ramón Román Nissen (Red Hat)
OpenShift Commons Gathering Kubecon EU
May 17, 2022 Live from Kubecon EU in Valencia, Spain
Full Agenda here: https://commons.openshift.org/gatherings/OpenShift_Commons_Gathering_at_Kubecon_Europe_2022.html
Learn more at: https://commons.openshift.org
A
Okay,
so
welcome
to
this
talk
about
the
conveyor
community.
First
of
all,
allow
me
to
introduce
myself.
My
name
is
ramon
roman
nissan,
I'm
the
product
manager
for
the
migration
toolkit
for
applications
in
in
red
hat
and
probably
in
relationship
to
this
talk.
The
most
interesting
thing
about
myself
is
that
I
was
in
red
hat
consulting
for
five
years,
leading
larger
scale
migration
projects.
A
So
that's
why
I
guess
they
chose
me
for
this
pm
thingy
that
I've
I've
been
doing
for
the
past
year.
So
without
further
ado.
Let's
start
talking
about
conveyor
and
sorry
for
that,
but
I
think
the
first
thing
we
should
be
doing
is
getting
a
little
bit
of
context
of
why
we
started
this
community
and
this
will
be
a
series
of
figures
and
statistics
and
everything,
so
this
might
be
a
little
bit
of
a
snoozefest
for
the
most
technical
part
of
the
asean
audience.
Sorry
for
that
I'll
try
to
be
as
quick
as
possible.
A
A
On
the
other
hand,
this
gardner
latest
garner
forecast
by
2022,
more
than
75
percent
of
global
organizations,
will
be
running
container
containers
in
in
production.
So
if
we
get
the
two
of
them,
then
we
can
conclude
that
kubernetes
is
becoming
the
default
platform
for
application
deployment,
and
it
is
also
the
target
for
most
of
modernization
projects
out
there.
A
I
won't
go
through
the
whole
stuff
that
we
have
on
screen.
Just
to
sum
things
up.
There
is
a
30
billion
business
out
there
by
2026
related
to
application
modernization.
So
that's
that's
a
huge
number
out
there,
especially
for
vendors
and
gsis,
but
there
seems
to
be
a
a
problem
going
back
to
the
gardner
forecast.
A
This
is
a
completely
open
community
that
we
have
created
to
help
organizations
embrace
adopt
and
leverage
kubernetes,
and
we
have
a
two-pronged
approach
to
this
help
to
this
kind
of
ease
of
use
of
of
kubernetes.
On
one
hand,
we
have
a
lot
of
things
related
to
knowledge
sharing,
so
we
are
a
full-blown
community.
We
arrange
and
schedule
meetups
on
a
regular
basis.
A
We
are
really
focused
on
this
thing
being
an
open
community
in
which
everyone
is
welcome,
and
the
proof
of
that
is
that
we
have
submitted
the
khmer
community
as
a
sandbox
project
for
the
cncf,
we're
currently
working
on
getting
this
thing
on
board
on
the
cncf
going
back
to
the
tools.
Of
course,
this
is
an
open
community.
A
Next
thing
I
want
to
share
related
to
this
knowledge,
sharing
that
we
are
doing
in
the
community.
We
just
released
the
state
of
application,
modernization
report
for
2022.
We
run
a
survey
across
seven
600
organizations
and
companies
out
there
to
understand
the
latest
trends
on
application,
modernization
and
migration.
It's
pretty
interesting,
it's
completely
fresh
and
it
has
been
published
in
our
new
and
revamped
conveyor.io
website.
So
I
invite
you
to
to
just
take
a
look
at
it
and
let's
get
back
to
the
different
projects
that
we
have
within
the
conveyor
community.
A
So
what
we're
trying
to
do
with
our
projects
is
to
address
three
of
the
six
r's,
that
of
the
six
hours
framework
that
amazon
popularized
back
in
the
day.
So
we
tried
to
provide
help
to
achieve
three,
the
first
three
of
these
hours,
the
things
that
we
understand
the
these
are
in
our
own
way.
So,
for
example,
we
can
see
the
rehosting
as
moving
applications
towards
kubernetes
without
performing
any
change
on
the
application
itself.
A
A
And
finally,
we
consider
refactoring
as
adapting
your
application,
the
source
code
of
your
application
to
run
on
kubernetes,
coming
from
more
traditional
platforms
like
application,
servers
or
servlet
containers
to
have
the
application
running
on
kubernetes,
and
for
that
we
have
the
the
tackle
project
to
measure
the
whole
software
delivery
performance.
We
also
have
the
polaris
project
that
will
help
you
measure
or
track
the
different
dora,
metrics
or
devops
metrics
associated
with,
as
I
said,
the
software
delivery
performance
so
yeah
since
I'm
the
the
pm
from
from
migration
toolkit
for
applications.
A
At
the
same
time,
I
will
read
it:
we
want
tackle
to
become
the
ultimate
open
source
toolkit
to
help
organizations
safely
migrate
and
modernize,
their
application
portfolio
to
leverage
kubernetes
providing
differential
value
on
each
stage
of
the
adoption
process,
and
I
want
to
stress
the
word
safely
because,
as
you
might
know,
for
the
refactoring
scenario,
there
is
no
magic
there.
In
there
there
is
no
pixie
dust.
There
is
no
magic
button
that
you
press
and
all
the
source
code
just
runs
on
the
target
platform.
A
Our
idea
is
to
provide
two
differentiated
things
on
one
hand,
provide
as
much
insight
as
possible
for
adoption
leads
for
architects,
leading
this
migration
and
modernization
process
to
have
or
to
make
informed
decisions.
So
a
lot
of
insight
provided
by
the
tool
about
the
application
portfolio
and,
on
the
other
hand,
for
the
developers
for
the
ones
that
are
actually
performing
the
changes
on
the
source
code
and
adapting
it
to
the
target
platform
we're
trying
to
provide
as
much
guidance
as
possible
and,
of
course,
some
degree
of
of
automation
when
possible.
A
So,
as
I
said,
two
pronged
approach,
two
two
key
pilots
inside
for
the
adoption
leads
guidance
and
automation
for
the
developers
performing
the
changes.
The
idea
behind
that
approach
is
fairly
fairly
easy.
We
are
focusing
on
reducing
the
risk
to
make
the
migration
process
measurable
and
predictable.
A
A
We
are
releasing
tackle
2,
the
next
generation
of
the
tackle
tooling,
which
will
become
the
upstream
project
for
the
migration
toolkit
for
application,
the
next
generation
of
the
tool-
and
it
has
a
lot
of
exciting
things-
it
enhances-
enhances
what
we
probably
previously
had
on
on
tackle
one.
So,
let's
talk
about
the
different
components
that
we
haven't
tackle.
A
First
of
all,
of
course,
an
operator
to
make
things
as
easy
as
possible,
so
there
is
no
need
to
fiddle
around
with
the
charts
and
everything
everything
gets
automatically
deployed
and
managed
with
an
operator
that
is
available
for
all
kubernetes
distributions
out
there.
The
only
requirement
is
to
install
the
operator,
lifecycle
management
manager.
Sorry,
on
upstream
distributions,
if
you're
using
openshift,
that
comes
out
of
the
box
and
should
be
available
from
from
day
one.
A
The
usage
is
fairly
easy.
It
provides
a
tackle
crd
everything
gets
installed
and
configured
for
you,
but
you
still
have
some
granularity
to
adjust
the
installation
to
the
kind
of
cluster
that
that
of
kubernetes
clusters
that
you
have,
and
for
the
moment
we
have
capability
level
two
for
the
operator,
but
we're
looking
to
enhance
the
the
life
cycle
and
and
make
it
even
even
better
and
more
automated.
A
So
that's
it
yeah
cool.
I
can
install
tackle
automatically
or
auto
magically.
But
what
can
this
thing
do?
First
thing,
probably
key
or
or
the
driver
for
the
user
experience
in
tackle
would
be
the
application
portfolio
inventory,
sorry,
which
is
used
to
maintain
an
application
portfolio
of
an
organization.
A
So
the
whole
idea
behind
the
inventory
is
to
allow
organizations
to
have
a
holistic
view
of
their
whole
application
portfolio
and
once
they
have
this
view
being
able
to
classify
applications
in
application
types
using
an
extensible
tagging
model
that
allows
them
to
classify
their
applications
in
as
many
dimensions
as
they
might
want.
So
the
idea
is
to
is,
for
an
applica,
an
organization
to
be
able
to
classify
their
applications
in
application
types
and
with
that
then
being
able
to
come
up
with
suitable
migration
strategies
for
each
one
of
these
application
types.
A
A
We
can
retrieve
source
code
and
binaries
from
different
maven
or
git
repositories,
even
subversion
for
the
most
legacy
organizations
out
there.
And
of
course,
if
we're
dealing
with
with
source
code
repositories,
we
need
to
deal
with
credentials
as
well.
So
we
have
implemented
a
credentials
managers
management
system
that
allows
you
to
have
a
decoupled
usage
of
credentials,
so
architects
can
consume
credentials
without
necessarily
knowing
the
contents
of
such
credentials.
A
Next
thing
will
be
application
assessment,
so
three
pilots
on
on
tackle
application,
portfolio,
management,
assessment
and
analysis
assessment
will
be
next
and
by
assessing
we,
we
understand
a
questionnaire-driven
assessment
for
con
containerization
suitability.
So
the
idea
of
the
tool
is
that
it
presents
you
with
a
questionnaire
with
different
answers
and
out
of
this
answer,
the
tool
is
able
to
identify
risks
that
might
prevent
you
from
running
the
application
on
containers
as
as
it
currently
is.
So
it's
pretty
useful
to
get
an
overview
of
your
application
or
application
types
and
start
understand
it.
A
What
would
be
the
risk
or
the
problems
that
you
might
have
when
trying
to
onboard
these
applications
or
migrate?
These
applications
towards
kubernetes
next
step
to
get
more
into
into
the
detail
would
be
application
analysis.
So,
once
you
have
assessed
your
application
portfolio,
you
are
able
to
get
down
to
the
detail
of
each
one
application
and
run
static
analysis
on
your
application
source
code
on
binaries
and
try
to
detect
anti
patterns
in
your
in
your
source
code
that
might
be
preventing
you
for
for
from
running
your
your
application
in
in
containers.
A
So
right
now,
the
analysis
bit
is
only
compatible
with
java
applications.
Sorry
for
that,
but
we're
working
on
expanding
it.
This
thing
has
been
around
for
for
quite
some
years,
the
analysis
mode
and
we
have
done
what
we
have
done
is
integrated
into
the
whole
tackle
user
experience
and,
of
course
it
supports
a
numerous
migration
paths
and
creates
a
rich
set
of
reports.
We
will
see
some
examples
now
and
yeah.
A
Let's
see,
for
example,
issue
identification,
cool
things
that
it
detects
where
the
problems
are
happening
straight
into
your
source
code
and
points
out
to
the
exact
line
that
might
be
a
problem
for
you
to
run
the
application
on
the
target
platform.
It
also
provides
hints
it
provides
story
points
for
you
to
be
able
to
measure
the
cost
of
migrating.
Your
your
your
application.
A
This
is
one
of
the
key
things
about
the
analysis:
module,
there's,
also
a
technology
identification
system
that
allows
you
to
get
a
deeper
understanding
of
the
technology
stack
of
the
analyze
applications
that
might
seem
trivial.
But
when
you
are
a
large
organization,
you
probably
don't
have
all
the
details
about
each
one
of
the
of
your
of
the
applications
that
you
have
in
your
portfolio.
A
So
this
is
very
helpful
to
get
meaningful
and
and
real
information
about
the
technologies
that
are
involved
in
each
one
of
your
your
applications
and
there's
yet
another
thing
which
is
for
me:
it's
key.
It's
the
dependencies
identification
and
the
coolest
thing
about
this
thing
is
that
it
is
able
to,
by
hash,
identify
each
one
of
the
different
dependencies
that
your
application
might
be
using.
Even
if
you
are
using
a
legacy
application.
A
Let's
say
you
live
in
the
past
century
and
you're,
not
using
maven
or
gradle,
or
anything
and
you're,
just
you're
just
shopping
in
your
your
jars
into
the
main
war
or
er
file.
This
thing
is
able
to
identify
these
jars
and
point
you
to
the
maven
coordinates
into
the
maven
central
repository,
so
that's
great
for
the
process
of
mobilization
of
these
legacy
applications,
which
will
definitely
be
a
requirement
from
for
bringing
these
applications
into
into
the
cloud.
A
There
are
many
migration
paths
supported
by
the
tool
out
of
the
box.
This
thing
was
developed
back
in
the
day
for
the
migrations
between
application
servers,
but
we
have
expanded
the
rule
sets
that
the
the
tool
ships
with
so
we
support
things
like,
of
course,
cloud
native
or
or
cloud
readiness.
Sorry,
we
are
opening
for
other
run
times.
There
is
a
certain
vendor
that
I
cannot
rebuild
just
yet
that
is
willing
to
contribute
more
rules
for
other
container
platforms
and
and
and
cloud
platforms
as
well.
A
So
we
expect
to
expand
these
rule
sets
as
as
times
as
time
moves
on,
but
you
might
be
wondering
yeah,
that's
cool,
but
what,
if
I'm
using
a
corporate
framework
custom
framework
or
this
technology
hasn't
been
just
tackled
just
yet?
What
can
I
do?
Well,
this
thing
comes
out
of
the
box
with
a
custom
rose
development
model.
This
thing
is
fully
documented,
so
it's
fairly
easy
using
an
xml
syntax
to
create
your
own
rules.
This
is
very
powerful.
A
Cool
thing
about
the
tackle
project
is
that
this
being
a
huge
collaborative
effort
between
red
hat
and
ibm,
at
least
for
the
moment,
but
there
seems
to
be
other
other
vendors
and
gsis
that
want
to
get
involved
in
the
tackle
project
as
well.
We
have
several
initiatives
for
the
moment.
Key
contributors
are
red,
hat
and
ibm.
A
Research,
for
example,
tackle
have
the
main
user
experience
and
the
application
portfolio
has
been
contributed
by
red
hat,
also
pathfinder,
which
is
the
the
project
powering
the
assessment
module
of
tackle,
also
windup,
which
is
the
project
behind
the
analysis
module
of
windup.
But
there
are
other
upcoming
initiatives,
really
exciting
stuff
being
contributed
by
ibm
research.
So,
for
example,
we
have
the
containerization
assessment,
which
is
able
to
identify
which
will
be
the
most
suitable
runtime
image
for
an
application
based
on
a
natural
language,
description
of
the
of
the
application.
A
So
it
uses
ai
and
machine
learning
to
try
to
match
your
description.
The
description
of
your
application
with
a
suitable
container
image,
which
would
be
very,
very,
very,
very
useful
when
we
are
dealing
with
a
large
portfolio
with
loose
descriptions
of
the
technologies
involved
which,
with
each
one
of
the
applications,
we
also
have
the
automated
configuration
discovery
project
which
is
able
to
understand
the
configuration
files
of
a
given
runtime,
translate
it
into
a
canonical
model
and
then
output.
Any
configuration
file
on
any
model
available
available,
so
translate
it
into
human.
A
That
would
mean
that,
for
example,
if
you
have
a
spring
boot
application
and
you
want
to
migrate
toward
quarkus,
it
will
be
able
to
understand
spring
boot
configuration
files
and
render
them
into
quarkus
configuration
files.
They
they
want
to
enhance
this
thing
with
ai,
so
it
will
be
able
to
look
for
hard-coded
value
configuration
values
into
into
your
source
code
and
extract
them
into
configuration
files
as
well.
A
There's
also
the
data
intensive
validity
advisor
or
diva
like
we
like
to
call
it,
which
is
a
transaction
analyzer.
Basically,
it
detects
these
distributed
transactions
in
your
source
code
and
is
able
to
tell
you
which
are
the
different
participants
of
these
transactions
and
everything.
So
it
basically
analyze
the
the
storage
layer
of
your
applications
and
gives
you
insights
on
the
different
actors,
data
stores
that
might
be
involved,
which
is
especially
useful
when
you're
trying
to
your
to
split
your
monolithic
application
into
into
microservices.
A
And
finally,
we
have
test
driven
modernization,
which
is
one
of
the
most
exciting
things
in
there.
The
idea
behind
that
is
to
create
some
sort
of
safety
net,
so
basically
that
the
main
problem
that
you
have
when
you're
trying
to
migrate
is
to
ensure
that
the
application
behaves
the
same
on
the
target
platform.
So
this
thing
using
automatically
generated
unit
test,
will
be
able
to
create
a
functional
profile
of
your
application
that
can
can
then
be
used
when
the
application
has
been
to
migrated
to
ensure
that
the
application
behaves
the
same.
A
A
There
are
instructions
in
there
to
to
install
the
the
tool
and
we
expect
to
have
it
available
in
operator
hub
by
the
end
of
the
day
today
or
maybe
tomorrow.
But
if
that's
not
enough,
we
will
be
demoing
the
whole
thing
by
tomorrow
on
the
red
hat
booth,
there
is
a
demo
theater
in
there.
I
will
be
running
a
demo
of
tackle
2
at
yeah
for
for
quarter
past
four,
I
don't
have.
I
don't
think
we
have
time
for
questions,
but
I'll
be
around
I'll,
be
around
the
red
hat
booth.