►
Description
Introducing the Red Hat APAC Hybrid Cloud Kopi Hour!
That’s right, we’re kicking off live streaming in APAC and it all starts with a nice strong cup of Kopi!
Join us for our first “beta” session at a time that suits you! For the first session we’ll be joined by a panel of regional experts for an engaging discussion about all things APAC and Hybrid Cloud!
A
A
Hello,
everyone
and
Welcome
to
our
very
first
APAC
streaming
show
I
am
so
excited
to
be
coming
to
you
live
from
Sydney
Australia.
My
name
is
August
simonelli
and
I'm.
A
technical
marketing
manager
here
at
red
hat
and
I
am
introducing
you
to
the
very
first
beta
Edition
of
the
APAC
hybrid
Cloud
copy
hour.
So
two
things
about
that
title
right:
we've
got
a
couple
of
things
in
there
that
are
interesting.
One
is
that
it's
beta,
so
why
do
I
call
it
beta?
A
Well,
it's
an
evolving
concept,
and
this
is
our
very
first
show,
so
we're
just
kicking
the
tires
at
the
moment.
What
we
hope
to
do
as
we
go
forward,
is
highlight
the
voices
and
languages
from
around
our
region.
We
want
to
share
the
wisdom
and
knowledge
of
APAC
Red
Hat
directly
with
you,
and
hopefully
one
day
have.
Maybe
you
on
our
show,
it's
going
to
be
a
lot
of
fun
and
I'm
really
looking
forward
to
it,
but
I'm
calling
it
beta
so
that
we
can
blame
any
mistakes
on
that
right.
It
was
beta.
A
A
It's
really
really
popular
there
and
if
you've
been
there,
you've
probably
had
it.
You've
probably
seen
it
it's
kind
of
part
of
the
culture
of
Singapore.
It
comes
in
all
these
different
types
and
I
know.
People
here
will
know
that
it
has
different
names
and
and
everything
the
one
I
love
is
Kopi
and
it's
got
the
the
sweet,
condensed
milk,
it's
super
delicious
and
it's
it's!
It's
super
nice.
So
that's
what
we've
come
up
with
we're
going
to
call
it
the
APAC
hybrid
Cloud
copy
hour.
So
what
are
we
going
to
do?
A
That's
enough
about
caffeinated
beverages,
let's
get
to
these
nice
folks
who
are
sitting
here
next
to
me?
Well,
they're,
not
next
to
me,
but
who
are
virtually
next
to
me.
This
is
our
panel,
for
the
first
show
I
want
to
introduce
you
to
them
and
then
we'll
kick
off
with
our
first
question.
So
the
first
person
we'll
meet
is
Steve,
Ellis
and
Steve
is
a
principal
architect
out
of
New
Zealand
Steve.
Why
don't
you
go
ahead
and
say
a
few
things.
B
A
big
part
of
my
background's
been
helping
customers
as
they
grow
things
at
scale,
but
often
delivering
Solutions,
leveraging
open
source
technology,
and
it's
something
I
continue
to
do
today
at
red
hat,
and
it's
really
interesting,
seeing
the
rapid
rate
of
innovation,
we
can
now
deliver
using
a
combination
of
you
know.
On-Premise
platforms
and
the
environments
provided
Us
by
those
hyperscalers.
B
A
C
Thanks
August
I
see
we
have
a
great
hybrid
theme
going
on
in
the
panel
a
couple
of
people
working
from
home,
some
of
us
in
office
so
really
glad
to
be
here
for
everyone.
My
name
is
Dave
shanba
principal
architect
with
the
customer
success
organization
in
the
Australia
New
Zealand
region
been
with
red
hat
for
just
around
six
years
now,
and
these
days
I
focus
my
efforts
in
working
with
our
Telco
customers,
make
the
most
out
of
their
investments
in
open
source
and
really
glad
to
be
here.
A
Thanks
Steph
yeah,
Dev
and
I
have
been
working
together
for
a
while
we've
been
in
Consulting
teams
together
right
down
there.
Actually,
you
know
working
on
Solutions
directly
for
customers,
so
we're
getting
a
lot
of
variety
here
on
on
the
panel
and
it's
really
great
to
see
next
up
is
Mohan.
Sita
mohand
is
a
GTM
specialist.
Now
Mohan
you're
in
Singapore,
so
you've
probably
had
Kopi
this
morning
am
I
right
or
is
it
not
your
thing.
D
Absolutely
I
had
a
wonderful
copy
in
the
morning,
so
it's
me
in
the
local
slang.
It's
called
copy
or
you're
100
true,
so
though
we
call
it
coffee
from
outside
people,
but
local
people
pretty
much.
There
are
some
Hawker
centers
here.
If
you
go
here,
everybody
call
Copy
Copy
copywoo.
They
see
things
like
that.
It's
very
common
in
Singapore
get
to
hear
that
title
and
history
about
copy.
D
So
our
portfolio
in
this
segment
is
growing,
so
we
already
have
three
scale:
API
Gateway,
then
Kafka
or
queer
registry
and
our
data
open
data
science
open
Hub
right.
So
these
are
the
portfolio
right
now.
Red
hat
is
apparently
offering.
So
we
are
help
our
customers
and
on
adapting
this
red
hat
cloud
services
and
day-to-day
life.
A
Problem
I
mean
and
as
Steve
was
saying
like
just
you
naming
off
all
those
bits
and
pieces
is
pretty
impressive,
like
suddenly
there's
this
portfolio,
that
is,
is
just
massive
and
covering
all
levels,
and
so
that
brings
us
more
to
the
topic
at
hand.
I'd
love
to
discuss
more
about
caffeinated
beverages.
You
know
it's
getting
into
the
afternoon
here.
I'm
I'm
already
looking
for
my
next
one,
but.
B
A
Are
but
we're
not
going
to
do
that,
I
mean
that
could
be
a
good
session,
but
what
we're
going
to
talk
about
today
is
specifically
what
does
hybrid
Cloud
actually
mean
to
our
APAC
customers,
so
I
think
we're
trying
to
think
about
how
it's
tackled
in
APAC
and
maybe
how
it
differs
from
other
regions.
So,
for
instance,
do
our
customers
in
Apex
start
in
the
data
center
and
move
to
adopting
public
cloud,
or
is
it
happening
the
other
way?
What's
driving
those
choices?
A
B
Yeah,
so
just
to
kind
of
kick
off
some
of
the
themes
here
with
the
like
I've
dealt
with
in
my
role,
many
different
types
of
organizations
from
fsis
through
telcos,
through
government
departments
and
large-scale
Enterprises,
and
they
all
think
they're
unique.
But
many
of
them
are
approaching
Cloud
the
same
way:
they've
dabbled
they
try
something
out
and
then
maybe
the
organization
thinks
they're
going
to
go
all
in,
but
seldom
are
they
all
in
on
just
one
Cloud
platform.
B
They
don't
even
think
that
they're
hybrid,
without
realizing
that
they're
adopting
a
hybrid
Journey
because
say
they
decide
to
use
Amazon's
platform
to
initially
spin
up
some
some
public
cloud
services.
They
want
to
front-end
their
web
applications
and
do
some
caching,
maybe
they'll,
start
to
bring
on
someone
like
Cloud
for
Flair
to
protect
their
customer
facing
platforms
and
do
some
like
this
distributed.
B
So
when
we
talk
about
hybrid,
we
need
to
think
about
more
than
just
the
Enterprise
applications
we
normally
would
focus
on
was
red
hat
it's
a
much
broader
conversation,
so
those
organizations
already
have
contracts
with
multiple
providers,
they'll
be
consuming,
SAS
they'll
be
consuming,
compute
they'll
be
consuming.
You
know.
Caching,
services
and
Outsourcing
other
capabilities,
and
so
hybrid
actually
has
a
much
broader
construct
than
we
initially
think
about
interesting.
A
B
Same
thing
used
to
happen
in
traditional
I.T.
You
know
many
of
us
have
been
in
that
traditional
I.T
environment,
where
you
often
have
organizations
with
two
completely
separate
Windows
teams:
multiple
Unix
management
teams,
even
within
an
on-premise
footprint,
the
running
joke
for
many
years
was
many
organizations.
First
foray
into
Cloud
was
through
the
marketing
department,
who
would
slap
down
their
credit
card
and
go
and
buy
some
some
environments
and
spin
up
some
new
service
to
promote
something
for
their
business,
and
you
know
various
forms
of
backdoor
I.T.
A
I
remember:
when
I
worked
for
a
very
large
Masthead
in
in
Australia
we
had.
We
found
that
certain
Dev
teams
were
actually
using
SAS
components
inside
our
home
page
and
we
didn't
know
they
were
there
and
so
in
a
way
we
were
going
hybrid
and
it
actually
caused
trouble.
Because,
often,
if
that
broke,
we
didn't
know,
and
that
can
be
a
challenge.
So
I.
A
Imagine
Dev
that
when
you're,
when
you're
at
on-site
of
the
customer
and
you're
seeing
this
hybrid
mix,
there
must
be
a
level
of
like
embracing,
but
also
like
Steve's
talking
about
some
some
frustration
around
how
to
keep
a
balance
and
and
and
make
all
those
pieces
work.
Do
you
see
that
on
the
ground
as
you're
in
these
companies,
yeah.
C
I
think
an
interesting
point
Steve
made
as
well.
Some
organizations
do
think
they
are
one
way
or
the
other,
but
they
are
kind
of
adopting
the
Hybrid
Club.
Some
of
the
customers
that
I
work
with
telcos
and
exercise
are
heavily
invested
in
the
data
center,
so
they
have
their
own
private
clouds,
but
at
the
same
time
they
are
using
things
like
slack.
For
example,
for
you
know,
collaboration
they're
thinking,
atlassian
products,
so
it
really
is
hybrid.
C
A
D
Basically,
I
would
like
to
stock
I
mean
start
with
benefit
of
our
custom
audience.
What
actually
hybrid
cloud
is
right,
so
a
hybrid
Cloud
environment.
What
we
are
talking
about
today
is
basically
consist
consistent
platform
across
bare
metal,
virtual
and
private
and
public
Cloud
environments
right.
So
potentially,
what
we
are
gaining
here
is
speed,
performance,
agility
and
portability.
These
are
the
key
things
we
gaining
using
this
strategy.
D
So
many
customers
use
this
strategy
for
few
reasons
right
so
I
I
just
want
to
before
going
to
reasons,
I'll
call
out
two
approaches
here:
the
customers
basically
want
the
dev
environment,
testing
environment
in
the
on-prem
and,
however,
and
their
production
environment
is
on
the
in
the
public.
Cloud
are
hyperscalers
and
the
second
type
of
is
the
other
way
around
right.
So
basically
they
want
their
Dev
environment
and
they
are
testing
environment
in
the
cloud.
However,
the
production
into
their
data
center.
D
So
let's
dig
into
these
two
customers
why
they
are
following
these
two
different
approaches
right,
so
basically,
the
type
1
customers
where
they're
starting
their
Dev
and
sat,
is
still
using
on
the
on-prem
or
data
center
they're,
huge
capex
right.
So
overnight
they
don't
just
they
just
don't
want
to
throw
or
throw
away
this
capex
Capital
expense
just
move
on
to
everything
onto
their
hyperscalous
right.
So
that's
the
one
strategy
there,
so
they
have
huge
investment
and
they
want
to
just
make
use
of
their
investment
and
still
run
their
applications.
B
D
Yeah,
that's
a
this.
Is
the
one
type
of
customers
right
they
precisely.
They
have
high
investment.
They
just
want
to
get
the
ROI
before
this
capping
up
this
entire
thing
and
move
to
Cloud
right.
So
that's
a
good
strategy
and
the
second
one
they
want
to
gain
the
they
don't
want
to
manage
the
environment
they
want
to
their.
Their
team
want
to
invest
more
time
on
the
Innovation
rather
than
just
managing
the
environments
and
their
application
life
cycles
right.
So
that's
another.
D
The
cloud
ecosystem
today
is
giving
too
much
of
innovation
too
much
of
Cloud
native
applications
available.
You
can
just
plug
and
play
any
of
your
development
in
the
The
Innovation
happening
in
the
cloud
environment.
You
can't
do
that
in
the
same
way
in
the
in
the
on-prem
right.
So
that's
another
kind
of
a
customers.
They
want
to,
you
know,
start
their
journey
in
in
Cloud.
D
B
Mohan
for
those
sort
of
customers
which
ones
tend
to
have
the
data
gravity
issue,
that's
something
that
come.
We
we
talk
about
a
lot
in
this
region.
You
know
Geographic
issues,
government
issues
around
where
we
place
data.
We
know
about
gdpr
in
Europe,
but
we've
got
similar
constraints
here
in
Asia,
we're
quite
a
quite
a
diverse
environment,
lots
of
different
countries
with
different
Geographic
restrictions,
who's.
Looking
at
data
Gravity,
the
most.
D
So
the
government
entities
are
I
mean
public
sector
is
what
I
could
say
that
they
are
actually
much
worried
about
their
compliance
and
data
security.
So
that's
another
reason
most
of
this
public
sector.
They
still
run
their
production
into
their
data
centers
and
they
are
working
with
the
Devon
testing
environment
in
the
public
hyperscalers.
When
it
comes
to
the
compliance
and
there's
a
stringent
security
requirements,
they
can't
you
know,
go
away
public
cloud
and
run
their
applications,
that's
where
they
they
run
their
applications
in
the
data
center.
A
And
so
for
all
of
you
speaking
about
you
know
these
decisions
being
made,
is
it
being
is
it
is
it
coming
from?
You
know,
geographical
stuff,
who
is
kind
of
leading
and
steering
where
these
places
are,
are
where
we're
choosing
to
lead
to
to
run
apps
right.
How
is
chain
who's?
Who
are
the
leaders
in
APAC,
right
who's,
steering
the
ship
and
making
those
decisions
and
and
who
follows
I,
know
in
India
the
banks
can
be
very
strong
force
and
and
the
leading
decision
who
do
we
look
to
in
aipac?
A
B
B
A
C
A
So
are
the
bigger
companies
and
bigger
customers
being
pulled
in
by
smaller,
consulting
firms
who
come
in
are
working
with
them
and
suggesting
these
things,
rather
than
than
trying
to
do
them
on
premises
or
is
there
that
drive
inside
the
company,
because
the
large
Telco
or
whatever
sees
what's
happening,
and
it
happily
wants
to
move
on
or
is
it
being?
Are
they
being
kind
of
pulled
into
that
by.
B
My
comment
earlier:
the
marketing
department
slaps
down
the
credit
card.
An
organization
needs
to
do
something
really
quickly.
It's
often
outsourced
to
a
third
party.
That's
how
often
some
of
these
things
get
kick-started
and
there's
often
very
little
governance
applied.
As
these
organizations
are
maturing
they're,
bringing
in
governance
they're,
bringing
in
some
central
control
and
coming
back
to
mohan's
Common.
B
We,
if
an
organization
is
sensible,
it
doesn't
want
to
repeat
of
the
Unix
Wars
or
the
Java
Wars
I
mean
that's
been
a
ridiculous
amount
of
time,
helping
people
Port
things
between
web
sphere
and
weblogic
and
JBoss,
and
you
try
moving
things
between
you
know,
eks
and
AKs.
If
you've
built,
you
know
strong
Integrations
into
Amazon
or
aws's
platform,
it's
really
really
difficult
to
move
things
around.
A
So
I
was
going
to
say
so
talk
to
me
guys
a
little
bit
about
that
consistency
that
you
to
make
hybrid
Cloud
not
feel
hybrid
right
when
we
talk
about
everything's
different,
that's
great,
that's
hybrid
Cloud,
but
that's
like
dysfunctional,
hybrid
Cloud.
So
with
openshift
right
we
can
see
the
same
thing
in
multiple
places
on
premises.
A
You
know
self-managed
or
even
the
managed
service
offerings.
We
have
you're
getting
the
same
thing
so
that
that
consistency
is
is
there
and
the
ability
to
move
applications
is
much
simpler.
How
is
that
Landing
in
APAC
are
customers
seeing
that
you're
alluding
to
it
Steve?
But
you
know
Mohan
say
a
bit
more
about
how
that
how
powerful
that
is
to
be
able
to
do
that,
and
if
that
message
is
landing
and
people
are
starting
to
adopt
like
going
all
the
way
from
an
open
shift
on
premises
into
a
managed
offering
of
the
same
thing.
A
C
Think
customers
get
it.
I
was
just
talking
to
a
customer
this
morning
and
he
said
they
are
quite
intentional
in
their
strategy
in
terms
of
where
they
are
spending
their
efforts
and
their
dollars.
So
they
understand
they
want
to
have
a
hybrid
approach.
However,
they
are
keen
on
getting
both
of
that
together
really
well,
so
the
struggle
they
have
is,
how
do
they
manage
their
internal
processes
so
that
both
can
come
together
and
coexist?
So
that's
that's
what
their
effort
has
been.
They
have
intentional.
B
B
You
know
I
used
to
regularly
see
organizations
where
the
development
team
worked
are
using
something
like
JBoss,
but
then
they
went
to
production
on
websphere
or
weblogic,
and
then
they
could
never
reproduce
their
bugs.
They
can
never
reproduce
their
issues.
The
environments
weren't
effectively
the
same
with
both
Rel
and
with
openshift.
We
kind
of
normalize
that
environment,
and
it
does
mean
coming
back
to
mohan's
comment
earlier.
B
The
organization
that
still
wants
to
keep
production
on
premises
but
wants
to
Leverage
The
elasticity
of
public
Cloud
for
Devon
test
can
do
that,
whilst
providing
a
normalized
environment.
They
know
that
the
workload
the
deploying
exactly
the
same
workload
exactly
the
same
way
in
Dev
and
test
as
they're,
deploying
when
they
run
it
in
production
and
that
then
drives
agility.
It
drives
a
much
more
rapid
development
and
release
cycle.
It
drives
a
level
of
consistency
that
organizations
need
for
the
change
that
they're
having
to
adopt
today.
D
D
Yeah
I
just
want
to
add
few
things
and
when
it
comes
to
manage
Cloud,
I
guess
your
previous
question.
So
basically,
the
customers
are
very
keen
to
move,
manage
clouds,
a
couple
of
reasons
right,
so
they
they
it's
been
several
years
now
the
customers
are
managing
their
on-prem
self-hosted.
Thank
you,
application
platforms,
or
maybe
in
Cloud
self-hosted
again
in
the
cloud
they're
hosting
their
application
platform
right
so
experienced
many
years.
D
The
few
challenges
I
would
like
to
call
out
here
life
cycle
management
when
it
comes
to
version
upgrades
or
patching
it.
So,
for
example,
openshift
three
to
four
some
of
the
customers
literally
struggled
we
they
took.
You
know
exceptional
time
to
move
from
three
to
four
version
upgrades
and
when
it
comes
to
some
key
vulnerabilities
and
CV
is
available,
the
customer
taking
own
sweet
time
to
upgrade
because
the
applications
team
is
not
supporting
them
to
allow
this
upgrade
right.
D
So
giving
XYZ
reasons
and
security,
container
security
Registries
and
day
two
operations
I
mean
the
list
goes
on
right.
So
this
is
something
like
a
last
thing:
I
just
want
to
color
this
one
consistent
user
experience.
When
it
comes
to
hybrid
Cloud.
We
need
a
consistent
user
experience,
irrespective
is
on-prem
or
hyperscalers
wherever
you
do.
Your
applications
are
running
the
the
consistent
user
experience
very
key,
a
key
factor
when
it
comes
to
right,
so
I
don't
want
to
see
one
way
of
of
deploying
things
in
day.
D
One
I
don't
want
to
see
different
way
of
deploying
things
in
when
it
comes
to
the
private
or
public
Cloud.
So
these
are
the
some
of
the
challenges
I
mean
it's
been,
customers
are
experiencing
and
they
they're
very
sure
that
when
it
comes
to
application
platform,
it
has
to
be
managed.
That's
where
we
are
driving
this.
We
call
it
Rosa,
red
hat
openshift
and
AWS
and
ero
Azure
Red
Hat
open
shift.
These
are
the
two
things
we
offering
in
a
public
scale,
hyperscalers
right
now
and
IBM
and
Google
Cloud.
D
Also
we
have
same
same
offerings
in
different
type
of
scalars
right,
so
why
they
choose
these
hyperscalers
than
self-managing.
These
are
the
key
challenges,
the
the
customer
experience
and
they
don't
want
to
just
the
entire
resource.
Don't
don't
want
to
manage
this
trunky
application
platforms,
rather
just
they
want
to
go
as
a
pay-as-you-go
model
like
the
and
every
Enterprise
today,
they're
doing
Cloud
adoption
alongside
Cloud
adoption.
They
are
exploring
this
managing
Red,
Hat
managed
Cloud
offerings
the
main
reason,
whatever
I
call
it
just
now.
D
A
So
when
the
customer
does
managed,
because
they're
trying
to
avoid
some
of
the
heavy
maintenance
of
looking
after
those
environments,
do
we
sometimes
find
that
they
don't
want
to
actually
run
those
things
on
premises
at
all
and
if
they
do
yeah,
how
do
they?
How
do
they
make
that
transition
because
they
do
have
to
look
at
those
on-premises
Solutions?
So
that
kind
of
goes
to
that
original
question?
Are
they
going?
Are
they
starting
on
premises
and
going?
A
This
is
hard,
and
this
is
so
much
easier
when
they
go
to
manage,
but
then
does
that
cause
some
kind
of
problem
for
the
on-premises
solutions
and
how
you
know.
How
can
we
help
them
and
you
know,
keep
those
going
as
well,
because
there
will
be
some
things
where
they
have
to
keep
it
on
premises
right
for
whatever
the.
D
Reason
I
take
this
question.
Yeah
so
basically
see
it's
continuation
to
what
I
explained
my
first
term.
So
basically,
some
customers
want
the
full
control
of
their
environment
and
that's
where
they
want
their
City
environments.
Kind
of
you
know,
testing
environments,
they
want
full
control
and
they
they
want
to
administrate
everything
and
they
want
to
give
that
luxury
to
the
developer
team
teams
and
their
internal
teams
to
deploy,
manage
everything
and
other
factors
like
the
capex
right.
So
these
are
the
few
things
they
consider.
D
On-Prem
I
know
it's
a
bit
challenging
that
the
environments
managing
and
you're
pushing
your
code
to
higher
environments
in
a
hyperscalers.
That's
something
you
when
it
goes
to
hyperscale
everything.
It's
taken
away.
All
the
all
issues
button
whatever
customer
facing
in
the
down
and
the
lower
environments,
is
in
a
way
handled
very
easily
by
crowd-powered
us
and
a
joint
supports
in
some
cases.
D
Giant
supports
like
red
hat
and
hyperscale
is
together
supporting
their
environments
right
so,
and
on
top
of
that
we
have
SRE
teams
so
who
monitor,
monitors
24x7
across
the
globe
and
enter
the
Clusters
and
their
version
upgrades
patching.
Everything
is
taken
care
by
our
SRE
team
right.
So
these
are
the
you
know,
some
of
the
things
I
I
would
like
to
call
out
so
yeah.
It's
a
combination
of
mix
of
self
managing
in
the
lower
environment
and
when
it
comes
to
higher
environment,
select
production
or
preferred
you're
pushing
everything
in
the
cloud.
D
So
you
have
some
responsibilities,
it's
a
mixed
responsibilities
in
the
lower
environments
and
when
it
goes
to
Cloud
it's
a
different
responsibilities.
There,
it's
actually
a
kind
of
a
term.
It
actually
brings
a
lot
of
advantages.
You
have
a
lot
of
flexibility
in
lower
environments
and
you're
gaining
the
capex.
Whatever
you
did
past
few
years,
investment
you're
trying
to
get
the
alloy
out
of
it
right.
So
that's
a
key
factor
there
and
other
way
rounds.
Also
customer
exploring
because
of
a
lot
of
compliances
issues,
the
other
one
we
discussed
some
of
the
customer.
D
B
Yeah
I
know
one
customer
where
they
they've
got
a
mix
of
openshift
footprints,
on-premise
public
cloud
and
managed,
and
one
reason
why
they're
running
several
services
in
one
of
the
hyperscalers
was
it
circumvented
some
of
their
certification
for
security,
because
they're
the
the
provided
environment
was
pre-secured.
It
was
already
signed
off.
They
didn't
need
to
be
worried
about
some
of
the
regulatory
requirements
for
a
particular
service,
so
they
were
mixing
and
matching
simply
for
regulatory
issues,
but
I
think
from
one
one
area
that
I
think
really
can
really
help.
B
Drive
a
customer's
Journey,
really
accelerated,
is
looking
towards
the
managed
Services
platform
for
new
projects,
particularly
organizations
that
haven't
invested
already
in
operational
skills
around
kubernetes,
because
just
a
developer,
throwing
a
workload
at
kubernetes
is
relatively
simple:
operationally
scaling,
kubernetes
and
dealing
with
logging
and
Reporting
and
monitoring,
and
everything
else
is
a
as
a
is
a
skill.
It's
a
big
investment,
so
Outsourcing
that
to
someone
operating
as
a
managed
service
lowers
your
barrier
to
entry.
You
can
start
adopting
This
Cloud
native
platform
sooner
rather
than
later.
B
So
actually,
you
adopting
managed
Services
as
soon
as
possible,
using
it
for
that
initial
project.
Using
a
few
development
teams
means
that
you
can
reduce
your
barrier
to
entry
and
you've
got
an
elastic
investment
rather
than
a
sunk
cost
yeah,
and
then,
if
later
on,
you
do
need
to
bring
some
of
those
things
back
on
premises
because
you're
going
live
and
data
gravity
is
some
other
reason.
A
And
I
think
you
made
an
interesting
point
when
you
call
that
the
regulatory
thing
one
of
the
questions
I
had
is
is
how
is
that
shift
to
manage
services
affecting
an
organization's
security
landscape?
Because
the
first
thing
is:
oh
I'm
handing
everything
over
what
am
I
going
to
do?
That's
not
safe,
but
there's
many
ways
that
it's
actually
an
advantage.
You
know
not
only
for
the
regulatory
stuff,
but
with
tools
like
ACS
with
red
hat
ACS
you
you're
actually
able
to
manage.
You
know
these
different
things.
A
B
The
security
team
has
always
been
an
interesting
part
of
the
puzzle.
Capabilities
when
we
look
back
at
Rel
with
things
like
insides
is
a
really
important
tool
to
drive
introspection
into
your
environment.
I
I
talk
about
it
in
terms
of
proactive
operations.
I
get
many
security
teams
react
negatively,
because
we're
providing
too
much
data
to
Red,
Hat
and
all
we're
doing
is
trying
to.
You
know,
help
their
data
experience
when
they
start
moving
to
public
Cloud,
often
they've.
B
It's
that
balance
between
your
contract
with
the
provider
and
what
the
provider
States
is
their
security
landscape
and
then
how
your
own
teams
look
at
hardening
that
footprint
and
and
again
one
great
thing
about
our
platforms.
Is
we
build
our
security
inherently
from
the
start?
So
you
know,
openshift
kubernetes
platform
runs
on
top
of
red
Enterprise
Linux
Granite
Pros
Linux
has
very
high
security
standards
as
part
of
just
running
kubernetes.
B
They
are
hardened
to
a
different
layer
level.
You
know
at
the
end
of
the
day,
when
you
run
in
the
public
cloud
in
theory,
someone
else
could
have
access
to
your
data
in
practice.
We
hope
that
they
don't
it's
a
risk
that
you're
always
taking.
If
you're
Ultra
paranoid
about
it,
then
just
run
everything
on
premises.
A
Right
but
and
as
you
said,
what
I
think
so
cool
is
you're
getting
that
same
Arcos,
you
know
Red
Hat,
core
OS
bass
across
wherever
you
are
so
you're
eliminating
an
unknown
there.
You
know
when
you
use
maybe
another
another
kubernetes
distribution
and
you're
having
to
patch
those
those
nose
and
look
after
them.
It
can
be
very
risky
and
I.
Imagine
in
aipac
it's
it's
very
helpful
to
just
know
that
you're
getting
that
secure
base
all
the
time.
Well,.
A
B
Cycle
of
your
kubernetes
environment
is
critical.
Yeah
kubernetes
is
an
ever-changing
ecosystem
where
it
releases.
You
know
three
times
a
year
so,
depending
on
the
workloads,
you're
deploying
you
need
to
have
consistency,
but
you
also
need
to
maintain
currency,
but
you
need
to
maintain
the
right
kind
of
security,
landscape
and
that's
challenging,
because
when
a
customer
deploys
a
workload,
it
isn't
just
the
OS
and
the
kubernetes
layer
and
wherever
else
is
offered
by
openshift,
it's
every
open
source
library
and
toolkit
that
they're
importing
into
the
workloads
they're
running.
That's
the
big
game.
B
D
Thing
so
when
it
comes
to
manage
Cloud
right,
so
the
industry
standard
compliance,
for
example,
pcie
or
HIPAA
all
these
are,
we
are
collaborating
with
the
hyperscalers
and
we
are
actually
certifying
all
this.
You
know
compliances
so
many
of
this,
the
including
public
sector
and
the
finance
customers
who
have
this
constraints.
D
So
in
a
way
we
are
guaranteeing.
What
are
you
following
the
complaints
in
your
on-prem?
We
are
pretty
much
guaranteeing
same
thing
in
the
hyperscalous
as
well,
so
they
are
convinced
and
I
can
name
it.
Hundreds
of
customers
are
moving
from
on-prem
to
our
manage
cloud
services
in
the
in
the
current
ERA,
where
they
are
all
companies.
They
are
all
big
Banks
and
big
public
sectors,
telcos
and
Commercial,
like
all
in
Airways
logistics
company,
every
every
segment,
you
name
it
all
of
them.
D
Are
you
know
taking
this
journey
so
in
a
way
everybody
is
accepting
and
they
are
comparing
with
what
they're
having
today
in
the
on-prem,
what
kind
of
compliance
they
are
following,
whether
it's
there
in
the
hyperscalers.
If,
yes,
then
Nothing
is
Stopping
Ram
right,
so
they
are
just
making
the
cloud
adoption
as
part
of
their
go
to
strategy.
So
we
are
there
right
here.
A
So
as
they
make
this
adoption
and
change
I
want
to
talk
a
little
bit
about
and
is
something
we've
talked
about
off.
You
know
Affairs
application
and
platform
modernization
so
that
move
of
now
that
you
are
actually
getting
into
a
hybrid
Cloud
doing
things
a
little
differently
and
my
personal
and
I
know
Steve
and
I
always
share
conversations
about
openshift
virtualization
and
the
ability
to
move
VMS
into
openshift
and
drive
them
in
a
cloud-native
way.
A
C
I'll
go
first,
so
I
think
from
that
perspective,
VMS
are
quite
the
standard.
They'll
still
coexist.
However,
a
lot
of
organizations
when
they
kind
of
do
in
integration
they've
realized
that
the
move
from
vnf
to
CNF
there
are
Parts,
where
you
know
you
could
kind
of
have
VMS
and
containers
coexist
and
that's
kind
of
been
the
shift,
but
again,
at
least
in
the
ANZ
world,
where
I
see
VMS
will
still
be
there
for
the
next
five
years
or
so
easily
again
and.
A
Have
with
vendors
I
know
when
we
were
you
and
I
used
to
work
on
openstack
together,
and
it
was
a
fight
to
get
them
on
to
get
Hardware
components
moved
into
virtual
machines.
How
is
that
progress
going
to
now
modernize
into
containerized?
You've
said
they'll
be
around
for
a
while,
but
are
you
seeing
vendors
willing
to
embrace
even
VMS
in
openshift
in
kubernetes,
or
is
that
still
a
bit
a
bit
of
a
stretch
and
they're
still
not
getting
it
yet.
C
I
think
the
industry
is
kind
of
changing
in
a
bit
where
the
the
move
is
towards
containerization.
However,
there
are
a
lot
of
pieces
that
will
still
exist
in
the
VMware,
so
they're
kind
of
you
know
trying
to
bring
everything
into
harmony
where
some
some
workloads
have
been
containerized,
but
some
will
kind
of
you
know
will
be
there
on
the
virtualized
environments,
a
lot
of
the
Greenfield
deployment
that
we
see
are
moving
towards
CNF,
so
a
containerized
world.
But
again
you
know
there
are
certain
things
you
know
when
it
comes
to
integration.
C
D
I
I
go
next,
so
I
have
few
statistics
here.
This
is
my
favorite
topic.
Actually,
yes,
oh
yes,
so
we
use
this
one
of
the
anchor
use
case.
We
call
it
application,
modernization
and
migration
strategy.
Anchoring
use
case
for
especially
in
the
Epic
region,
rose
on
their
Ward
options,
especially
cloud
services,
adaption
right.
So,
according
to
some
statistics,
IDT
2021
reports,
65
percent
of
Legacy
applications
have
been
modernized
to
some
degree
in
2021
right
so
which
is
expected
to
grow
73
percent
in
cy23.
D
So
you
see
that
65
percent
of
Legacy
applications
have
already
been
some
degree.
You
know
they
touched
some
portions,
maybe
just
plain
as
Dev
explained,
maybe
just
lift
and
shift
running
still
VM.
Some
degree
of
modernization
are
maybe
just
infused
in
some
kind
of
a
devops
or
cacd
pipelines
are
maybe
bit
of
containerization
or
maybe
monolithic
to
microservice.
I,
don't
know
this,
but
the
according
to
the
port.
It's
already
like
65
percent
of
already
people.
You
know
the
customers
are
touching
their
Legacy
applications
and
Gartner
report.
D
Gartner
estimates
that
in
the
new
digital
workloads
will
grow
from
from
30
percent,
which
is
actually
2021
to
over
95
percent
by
2025,
so
from
30
percent
to
95
percent
in
2020.
That's
the
you
know.
Huge
shift
is
going
to
happen
in
the
modernization
area,
modernization
migration
area,
so
we
want
to
literally
you
know,
utilize
this
anchor
use
case
and
drive
this
Cloud
adoption
and
especially
when
it
comes
to
manage
Cloud
right,
manage
Cloud
right.
So
we
are
helping
customers
using
this
anchor
use
case,
especially
modernizing
their
applications
are.
D
The
customers
are
just
already
modernized.
Maybe
the
custom
workloads
are
running
openshift,
on-prem
or
openshift
3.x,
we're
just
doing
lift
and
shift
to
the
public
cloud
or
private
Cloud.
Using
this
anchor
use
case,
or
maybe
in
the
other
way
like
the
customers
are
two
Legacy
applications
and
they
want
to
do
go
like
face
face
manner,
maybe
targeting
some,
let's
say,
EAP
workloads
which
is
running
on
VMS
and
moving
to
openshift
on
AWS
and
fully
containerized
right.
D
So
they
are
so
we
use
this
literally
this
four
or
six
factors,
the
first
two
hours,
I
I,
don't
call
it
at
the
other.
Force,
like
we've
rehost,
re-platform
repurchase,
all
these
four
Gartner
things
right.
So
we
use
those
for
four
hours
strategy
in
this
our
anchor
use
case
and
looking
the
customer,
where
he's
today
and
where
he,
what
is
his
goal
for
next
couple
of
years,
and
we
do
this
assessment,
basically
platform
maturity
assessment
based
on
the
customer
needs.
D
B
I
think
also,
when
we
take
that
out
to
the
kind
of
partner
on
isv
ecosystem.
We
see
some
similar
themes
here.
You
know
the
there's
plenty
of
organizations
who
still
run
what's
called
cots.
You
know
Common
off-the-shelf
applications,
so
many
of
those
originally
were
designed
to
run
on
Virtual
machines
or
physical
machines,
big
fat
systems
and
many
of
those
are
being
refactored
in
one
of
two
ways:
they're,
either
moving
over
to
a
container
type
platform.
B
Think
the
other
interesting
shift
is
the
number
now
that
are
locking
it
moving
to
SAS
style
models,
so
we're
seeing
an
increased
number
of
business
offerings
go
off
that
way.
So
in
some
companies
they
may
find
that
Core
Business
applications
now
are
they
consuming
as
a
sales,
offering
they're
no
longer
running
themselves,
they're
consuming
them.
The
aren't
just
simply
managed
Services,
it's
a
true
SAS
offering.
B
So
then,
as
a
organization
where's
the
value,
what
are
you
delivering
for
your
customer?
So
the
important
thing
is:
how
do
you
build
or
maybe
their
apis?
How
do
you
build
on
the
capabilities
of
the
SAS
services
to
deliver
value
to
your
customers,
and
your
customers
may
be
your
employees?
It
may
be
some
some
staff
management
system.
It
may
be
some
customer
facing
platform.
It
may
be,
as
we've
seen
with
the
digital
platform
Innovation
the
last
few
years,
the
need
to
be
able
to
deliver
on
mobile,
not
just
on
web.
B
How
are
you
fronting
that
well
you're
going
to
deliver
that
in
microservices
you're,
going
to
deliver
that
in
containers
you're
going
to
deliver
that
using
potentially
languages,
you've
never
used
before
as
an
organization
who's
been
wedded
to.net
and
to
to
Java,
and
you
can
innovate
all
of
that
on
a
platform
like
kubernetes
or
like
openshift,
you
can
do
it
at
scale.
You
have
that
and
with
we
have
seen,
organizations
where
they
need
to
sometimes
run
components
of
that
as
close
as
possible
to
the
SAS
service.
B
So
if
your
sales
provider
happens
to
be
operating
in
the
Singapore
region,
then
you
want
to
run
may
be
part
of
your
API
part
of
your
core
in
that
Singapore
region.
But
maybe
your
customers
are
running
in
Japan,
so
you
maybe
run
your
front
end
in
Japan.
So
then
we
start
dealing
with
the
geographic
needs
of
your
customer
base.
Not
just
is
this
on
premise
or
is
it
in
the
public
cloud
and
that
Geographic
need
and
the
fact
you
can
now
adopt
resources
from
multiple
Cloud
providers
to
meet
that
I?
A
And
yeah,
no,
that
makes
sense
and
when
you've
got
all
these
different
sources,
I
mean
how
do
tools
like
Red
Hat
ACM
come
into
play.
Do
we
see
a
strong
uptake
in
the
region
for
using
tool?
Like
you
know,
single
pane
of
glass
management?
You
can
pull
and
manage
service
offerings.
You
know
you
can
pull
in
your
Rosa
and
your
arrow.
You
know
talk
a
bit
about
that.
You
know
where
is
ACM
playing
in
this
kind
of
hybrid
Cloud
wrangling
in
the
region.
D
Yeah
I
can
go
fast,
so
I
see
a
lot
of
ignition
in
ACM,
especially
when,
with
this
hybrid
Cloud
strategy,
customers
are
running
an
on-prem
and
hyperscalers
and
knowing
the
fact
that
the
single
pane
of
glass,
so
you
can
manage
these
classes
from
anywhere
right
so
and
that's
a
video
of
the
cscm.
So
customers
are
understanding
the
advantage
of
ACM
and
underneath
adding
odf
like
open
data,
Foundation
kind
of
a
when
the
customers,
where
the
customers
have
Dr
strategies
and
even
the
stateful
workloads
like
live
synchronization
or
a
synchronization.
D
This
is
typical
requirements
when
it
when
we
are
talking
to
customers
right
so
so
it
can
be
easily
fulfilled,
and
your
cluster
also
can
be
brought
up
just
like
this
in
single
clicks
from
esm
dashboards.
So
these
are
the
some
of
the
driving
factors
when
it
comes
to
why
the
customers
are
choosing
ACM
and
even
security.
It's
had
on.
C
To
that
I
think
customers
are
definitely
seeing
a
lot
of
value
in
ACM,
a
customer
and
one
of
our
customers
came
to
us
asking.
We
have
all
these
virtualized
clusters,
we
have
these
bare
Metals.
We
have
some
presence
in
the
cloud
and
we
want
to
deploy
our
container
native
Cloud
native
applications
in
various
clouds
to
address
different
use
cases.
How
do
we
do
that?
I?
C
B
The
policy
piece,
I
think,
is
really
really
important.
You
can
Define
your
corporate
policies,
you
can
Define
Regional
policies,
but
I
think
what
we're
going
to
see
in
the
next
18
months
from
ACM
in
terms
of
its
how
it's
a
game
changer
is
the
fact
that
we
don't
just
scale
up.
We
scale
down
and
taking
acm's
management
out
to
Edge
devices.
So
that
way
we
can
work
with
manufacturing.
We
can
work
with
customers
in
the
Telco
ecosystem,
even
in
the
retail
type
ecosystem,
even
in
the
FSI
space.
B
Ultimately
many
you
know,
Banks
and
other
institutions
are
kind
of
retailers.
They
have.
Retail
points
of
presence
are
being
able
to
deliver
consistent
workloads
in
the
same
secure
manner,
on
very
small
lightweight
Edge
devices
at
scale,
in
the
same
way
that
you're
managing
large
Footprints,
be
they
core
banking
or
your
Telco
core,
your
5G
core
or
your
core.
You
know
government
Department
type
services,
and
you
can
do
all
of
that.
B
Not
quite
through
single
paneer
glass
I
mean
the
single
paneer
glass
thing
became
a
bit
of
a
running
joke
in
the
in
the
operation
side
of
the
tech
industry
for
many
years.
But
it's
your
it's
it's
your
kind
of
it's
the
point
where
you
bring
everything
together.
It's
your
jumping
off
point:
it's
your
control
point,
you
kind
of
command
a
control
center,
and
then,
on
top
of
that,
you
can
then
continue
to
do
things
in
a
cloud
native
manner.
You
leverage
your
favorite
tools
for
doing
monitoring,
reporting,
logging
and
extending
the
environment
output.
A
I
think
that's
so
important.
The
consistency
we've
been
talking
about
that.
If
the
complexity
of
the
hybrid
Cloud
environment
is
just
amazing
10
years
ago,
it
was
complex,
but
it
wasn't
like
this
openshift
levels
that
out
a
bit,
but
then
you
bring
in
at
something
like
ACM
and
I.
Think
it's
just
the
best
entry
point
for
things,
because
you
can
connect
so
much
to
it.
You
can
take
old
clusters
and
get
them
wrangled
in
you
can
add.
You
can
deploy
new
clusters
with
it.
You
can
any
any
compliant.
Kubernetes
can
be
brought.
B
In
we're
doing
a
demo
with
the
Apex
Summit
connect
events
at
the
moment,
using
the
power
of
ACM
we're
showing
a
true
hybrid
Cloud
footprint,
with
a
mix
of
Arrow
Rosa
bare
metal,
virtual
Footprints
and
we're
showing
the
fact
we
can
see
all
of
them
through
that
ACM
based
footprint,
and
we
now
have
convenience.
We
have
choice
and
even
an
organization
is
deciding
to
go
down
a
single
path.
B
We've
just
published
on
our
main
Channel,
an
update
from
Vodafone
New
Zealand,
talking
about
their
recent
Journey
with
red
hat,
using
our
integration
tools
using
openshift
and
the
fact
they've
adopted.
Aro
has
already
red
hat.
Openshift
is
a
primary
platform,
but
one
reason
why
they
went
down
that
route
wasn't
just
because
of
it
being
a
managed
service.
It
was
because
they
could
be
Cloud
neutral,
whilst
they're
adopting
a
large
part
of
this
on
Aro.
Today
it
doesn't
mean
that
their
future
is
100.
A
Yeah
and
yes,
I
was
just
looking.
I
was
trying
to
find
the
summit
connect
URL
to
share
with
everyone,
but
there's
a
bunch
of
those
events
coming
up.
I,
don't
know
if
you
wanted
to
to
speak
a
little
bit
just
as
we
as
we
finish
up
here.
You
know
the
way
that
red
hat
is
is
sharing
an
APAC.
We've
got
events
everywhere
going
on
and
it's
something
to
work
it's
worth
reaching
out
and
finding
out
more
about
things.
A
B
It
yeah
I
think
when
we,
when
we
push
this
out,
maybe
we'll
drop
the
link
to
the
Vodafone
session
in
the
chat
in
the
notes,
but
yeah
reach
out
to
your
local
Red.
Hat
teams
find
out
when
we've
got
events
and
we
run
an
awful
lot
of
meetups
around
our
technology
base.
We've
got
a
bunch
of
ansible
events
happening
right
now
in
the
US
that
you
can
stream
live
yeah
and
that's
another
big
Le,
a
part
of
our
story
for
all
the
things
on
the
periphery
of
your
environment.
B
A
And
I
I
think
we
could
have
a
whole
conversation
about
how
ansible
fits
into
the
hybrid
Cloud.
Maybe
that's
the
next
the
next
show,
but
we
are
coming
to
the
end
of
time.
So
I
guess
to
wrap
up
I
mean
we're
discussing
what
hybrid
Cloud
means
for
APAC
customers
to
me
it
sounds
very
much
like
it's
a
pretty
consistent
message
across
the
world,
and
this
is
this
is
happening
everywhere.
B
B
This
is
why
hybrid
resonates,
I,
think
even
better
here
in
emea
than
it
maybe
does
in
North
America
organizes
North
America
can
go
100
Cloud
because
they
know
everything's
running
in
North
America.
Here
you
can't
go
100
clouds,
you
can't
be
sure
everything's
running
in
your
country,
in
your
jurisdiction
within
the
the
controls
you
need
to
apply.
So
a
hybrid
model
makes
a
lot
of
sense.
C
D
Got
your
statistics
out
there
I
totally
agree
with
the
student.
What
he
explained
just
to
summarize
hybrid
is
something
like
a
very
good
strategy.
You
need
not
to
follow
every
each
and
every
customer,
but
the
customer
have
some
preferences
on
the
use
their
already
invested
data
centers
and
make
use
of
the
Innovation
going
in
the
required
agiles.
D
They
need
rocket
speed,
so
they
make
use
of
you
know
hyperscalers
to
reach
that
Speed
and
Agility,
and
stability
and
use
your
the
local
DC
environments
to
still
continue
your
expenditure,
reduce
the
cost
and
again
the
capex
right.
So
this
is
two
things:
I
want
to
call
out
and
hybrid
Cloud.
When
you
talk
about
hybrid
Cloud,
the
openshift
kind
of
a
platform
environment
is
become
de
facto,
because
you
need
a
consistent
experience.
You
we
are
playing
with
multiple
environments
and
multiple
hyperscalers,
so
you
need
consistent
experience.
That's
something!
D
Only
the
open
shift
kind
of
platform
can
bring
that
consistent
user
experience.
So
don't
forget
that
the
hybrid
cloud
is
a
similar
bullet,
but
the
app
platform
plays
a
very
key
role.
So
it's
like
a
a
win-win
for
both,
like
you
have
to
have
a
hybrid
Cloud
strategy.
You
have
to
have
the
right
platform
application
platform.
Generally.
Your
strategy,
can,
you
know,
get
the
super
fun.
C
A
D
A
Really
cool
things
that
make
hybrid
cloud
and
I
think
we
could
go
another
hour
and
so
I
I
think
it's
really
kind
of
exciting
that
you
know
so
as
if
you
re
Red
Hat,
just
it's
just
in
our
blood
to
do
it.
This
way
as
you
can,
as
you
can
see
that
so
I
think
you
know
reach
out
to
a
local
Red
Hatter.
We
have
people
all
over
the
region
and
they'll
have
this
same
conversation
with
you
and
I.
Think
that's
what's
I!
A
Think
that's
the
coolest
part
is
it's
it's
really
about
making
hybrid
Cloud
work
for
for
a
customer
for
a
solution
whatever
it
is,
making
those
products
just
be
things
that
solve
a
problem
and
I.
Think
that's
the
coolest
part
about
what
you
know:
red
hat
and
hybrid
Cloud-
that
we
do
that
with
it.
So
so
yeah
go
on
more.
D
A
So
I
want
to
just
quickly
reflect
on
that
yeah.
So,
like
I
said,
this
was
our
very
first
session
of
doing
this.
This
is
part
of
the
red
hat
streaming
initiative.
So
it's
something
that
we
expect
to
do
a
lot
more
of
we're.
Looking
for,
you
know,
give
us
your
comments
and
your
feedback
and
and
keep
an
eye
on
that
streaming
calendar
because
we'll
be
we
will
be
here
with
more
events.
We've
got
some
great
things
planned
and
yeah.
B
A
Nicely
said,
I
think
it's
a
great
end.
All
right
folks,
I
think
we'll
go
ahead
and
wrap
that
up.
Look
at
the
streaming
calendar
for
our
next
exciting
episode
and
we'll
share
this
on
social
media
and
make
sure
you
I'm
supposed
to
say
make
sure
you,
like
And,
subscribe
to
the
to
the
YouTube
channel
and
I
look
forward
to
joining
you
again
in
the
future.
Bye.