►
From YouTube: ROSA: Who Does What? | Amazon Web Services
Description
Ryan Niksch (AWS) and Charlotte Fung (Red Hat) take a look at Red Hat OpenShift Service on AWS (ROSA), diving into what customers are responsible for and which functions are now provided by Red Hat.
Learn more at: https://go.aws/3VqBY23
Subscribe:
More AWS videos - http://bit.ly/2O3zS75
More AWS events videos - http://bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers — including the fastest-growing startups, largest enterprises, and leading government agencies — are using AWS to lower costs, become more agile, and innovate faster.
#redhat #openshift #redhatopenshiftserviceonaws #rosa #AWS #AmazonWebServices #CloudComputing
A
B
A
Always
a
pleasure
Charlotte
I've
been
working
with
openshift
customers,
more
notably
the
red
hat
openshift
service
on
AWS,
so
the
managed
version
of
openshift
and
a
common
question
I
get
from
my
customers
is
yes,
it's
a
managed
service.
What
does
that
actually
mean?
What
do
I
as
a
customer
focus
on?
What
does
red
hat
do
for
me,
what
are
the
things
that
infrastructure
teams,
administrators
operators
not
have
to
worry
about,
and,
secondly,
when
they
need
to
reach
out
to
support?
A
B
Thank
you
so
much
Ryan
for
that
question,
which
is
really
an
important
one,
because
going
from
like
a
serve
managed
because
that's
what
usually
happens,
customers
goes
from.
They
go
from
a
self-managed
to
a
managed
service
and
it
causes
that
confusion
and
they're
not
sure
what
am
I
supposed
to
do
now.
What
is
my
responsibility
or
what
is
Red,
Hats
and
aws's
responsibility
so
on
the
spot
here,
I
have
like
two
blocks
of
responsibility
to
spread
it
out.
Everything
to
my
left
is
what
the
customer
should
worry
about.
Okay,.
A
And
I'm,
assuming
then,
this
side
of
the
fence
is
what
is
being
provided
by
the
managed
service
by
most
likely
read
out.
Sre.
Is
that
that's
correct?
Let's
spend
some
time
and
talk
about
the
customer
side
of
things
here.
I
noticed
that
you've
specified
the
application
life
cycle
so
that
that's
the
customer's
applications,
the
development
of
those
applications.
Maintenance
of
those
applications
do
the
management
teams
on
the
red
hat
side,
so
the
sres
have
access
to
customers,
applications
access
to
customers,
data.
A
So
very
clear:
separation
from
a
open
shift
projects
and
namespaces
perspective-
everything
that
is
the
customers
is
ring,
fenced
from
the
actual
cluster
I
suppose,
to
some
degree,
what
red
hat
is
doing
in
managing
Red,
Hats
mandates
or
interest
isn't
around
the
applications?
It's
really
to
make
sure
that
open
shift
as
a
platform
is
always
there
and
working
as
expected
that
way.
Red
Hat
focuses
on
this.
The
customer
can
focus
on
what's
important
to
them
and
their
business,
which
is
their
application
workloads.
You
notice
user
management
at
the
top.
What
do
you
mean
by
that?
A
B
For
user
management,
what
we
do
at
like
the
platform
itself
it
comes
with
and
with
an
art,
Server,
Like,
An
authentication
operator,
and
then
you
can
it
downloads
the
server
and
what
the
customer
is
responsible
for
is
making
sure
they
Grant
access
to
their
users
to
your
projects.
It's
like.
All
of
that
is
the
customer's
responsibility.
Okay,.
A
With
now
there's
two
parts
to
that,
you
know
we're
not
going
to
deploy
an
openshift
cluster.
One
of
the
things
I
commonly
do
is
I,
go
and
configure
an
identity
provider
yeah,
whether
that's
Microsoft
active
directory
or
whether
that's
an
oid,
City
type
solution
I,
as
the
customer
then
have
to
add
users
to
their
and
Define
what
those
users
have
access
to.
So
again,
everything
within
the
customer's
side,
in
terms
of
who
has
access
to
what
element
of
my
business,
is
up
to
me.
The
customer
not
up
to
red
hat.
A
A
B
All
right,
so
our
SRE
team
is
actually
the
team
behind
the
managed
service
they're,
the
group
that
makes
this
a
truly
managed
service
because
they
take
away
they
take
of
the
like
heavy
lifting.
They
do
all
the
heavy
lifting
for
you
in
the
background,
so
you
don't
have
to
worry
about
your
platform
availability
and
all
of
that
and
so
for
cluster
creation.
A
I
was
gonna,
say
you
don't
create
a
cluster
I
do
I'm
the
one
that
talks
in
my
keyboard,
Rose
so
cluster.
Now
what
you
mean
is
there's
a
very,
very
simple,
intuitive
step
for
the
customer
to
create
the
cluster,
exactly
the
automation,
a
lot
of
the
stuff
that
is
prescriptive.
It's
a
much
simpler
journey
to
what
it
was
in,
say,
openshift,
three
and
and
the
success
or
failure
of
that
cluster
creation
really
is
within
in
Red
Data
I
Define,
which
AWS
region
I'm
deploying
into
whether
it's
a
multi-az
cluster.
A
What
openshift
version
I
think,
there's
probably
about
nine
or
ten
parameters
that
eyes
are
customer
decide
and
then
the
rest
is
real.
Automation
in
the
background
and
the
SRE
team
is,
is
monitoring
that
in
the
back
end
to
make
sure
that
that
goes
ahead.
Cluster
management.
There
is
a
bit
of
an
overlap
here,
because
there
are
things
the
customer
can
do
on
the
cluster,
but
I
think
for
the
most
part.
What
we're
talking
about
here
is
the
health
of
the
cluster
yeah.
B
A
There's
two
very
interesting
things
there.
The
first
is
from
a
an
updates
perspective:
I
can
choose
whether
it's
automatic
or
not,
and
if
it's
automatic,
I
Define
a
schedule
that
works
for
my
business.
That's
right!
If
it's
not
automatic,
it's
a
bit
more
of
a
manual
request
process.
I
I
want
to
update
now
when
I
send
a
request
in
and
then
the
SRE
teams
do
the
update,
that's
correct
and
that
update
takes
place
without
impacting
my
applications.
A
The
openshift
environment
is
resilient
in
its
design,
so
I
can
update
one
node,
while
the
other
two
nodes
are
still
servicing
my
applications
and
will
cycle
through
them
from
a
break
fix
perspective
and
from
a
scaling
perspective.
You've
got
monitoring
that
the
sres
are
doing
so
they
don't
monitor
the
applications
themselves,
they're
monitoring
the
cluster
and
they're
looking
at
what
is
the
consumption
on
the
worker
nodes,
the
consumption
on
the
control
plane,
and
if
an
action
is
needed,
they
will
either
scale
those
some
control
plane
perspective.
A
What
I
typically
see
is
they
will
scale
the
ec2
instance
Types
on
AWS,
so
they'll
scale,
vertically,
not
horizontally.
How
is
that
communicated
to
a
customer?
Is
is
that
a
reach
out
to
customer
and
tell
you
there's
a
need
for
scaling?
Can
we
scale
or
do
they
just
scale
it
and
then
notify
you
that
that
action
is
taken?
Are.
B
A
That's
that's
a
bit
of
a
recommendation
process
as
well,
because
I
would
typically
add
in
a
a
machine,
Auto
scaler
and
Define
a
minimum
and
the
maximum,
and
and
that's
really
the
machine.
Auto
scalar
scaling
the
infrastructure
and
then
the
kubernetes
layer
of
openshift
managing
the
workloads
across
that
monitoring
and
logging.
There's.
A
There's
monitoring
and
logging
that's
important
to
customers,
there's
also
monitoring
logging
of
the
cluster
itself
and
and
that's
Telemetry
to
redheads
and
network
configuration
is
a
bit
of
an
interesting
one
because,
as
a
customer,
when
I
deploy
open
shift,
I
am
going
to
define
the
AWS
VPC
that
it
deploys
into
I'm
going
to
get
options
such
as
like
the
machine,
cider
and
things
and
how
much?
What
is
the
network
configuration
that
that
red
hat
is
managing.
B
So
the
network
configuration
that
we
manage.
We
manage
like
the
default
load
balancers
that
come
with
your
cluster.
We
also
manage
if
you
go
with
the
installer
provided
installer
provision
the
like,
if
you
go
with
that
default
installation
I
should
say
that
we
will
provide
like
the
VPC,
for
you
we'll
provide
the
subnetting.
We'll
also
make
sure
we
provide
the
service
networking
the
router
layer
that
takes
care
of
all
of
the
routing.
A
So
you're
talking
a
bit
about
the
provisioning
process
here
when
I,
when
I
provision
a
roaster
cluster
I,
don't
have
to
build
out
the
entire
network
environment
I
can
take
advantage
of
the
installer
to
create
that.
For
me,
that's
right,
but
I
do
still
have
the
choice
to
deploy
it
into
an
existing
VPC.
A
B
Thank
you
for
that,
so
for
management.
Sre
team
will
take
care
of
all
of
that
when
it
comes
to
support.
Customers
have
the
option,
because
this
is
generally
supported
by
red
hat
and
by
AWS.
So
it
doesn't
matter
who
you
contact.
When
you
have
an
issue
with
your
cluster
or
the
infrastructure
on
which
your
cluster
is
running,
you
can
either
contact
AWS
support
or
you
can
contact
Red
Hat
support
and
the
whatever
issue
you're
having
with
the
platform
will
be
so.
A
This
is
real
customer
choice
if
I
have
a
a
good
working
relationship
with,
say,
AWS,
absolutely
I
can
open
up
sport
case
with
AWS,
so
they'll
provide
tier
one
support
I'm
assuming,
if
need
be,
they
can
escalate
to
red
hat
for
something
that
is
really
openshift
specific
and
the
inverse
is
also
true.
That's.
B
A
B
Doesn't
matter
where
you
put
the
support
in
no
bouncing
off
each
other
different
support
teams?
If
it's
some
thing,
that's
related
to
the
platform
itself,
it
will
be
sent
to
Red
Hat
support
if
it's
related
to
like
the
infrastructure
like
the
cloud
infrastructure,
it
will
be
sent
to
AWS
like
AWS
support
will
handle
that
for
you,
whichever
team
is
best
fit
it
to
help
with
the
problem
will
handle
it
and
you
won't
notice
any
any
delay,
because
we
all
do
that
in
the
background
for
you
and.
A
A
I
think
there
are
situations
when
it
becomes
very
open
shift
specific.
So
if
the
customer
has
questions
around,
how
do
I
do
something
in
openshift
itself,
such
as
take
advantage
of
you
know
a
an
abstraction
provided
by
openshift,
something
that's
not
related
to
AWS
in
in
any
way
to
me,
it
does
make
sense
to
open
that
support
case
directly
to
to
Red
Hat
you're.
A
Is
with
the
SRE
team
being
on
the
red
hat
side?
If
I
know
that
there's
something
where
I
want
the
SRE
team
to
potentially
make
a
change
so
like
a
deliberate
scaling
action
I'm
assuming
it
makes
a
little
bit
more
sense
to
again
open
up
a
support
case
with
the
red
hat
side
to
get
to
the
SRE
team
quicker.
B
Think
we've
touched
on
everything
and
and
what
I
just
want
our
customers
to
take
home?
If
there's
anything
that
you
should
take
home
from
all
of
this
is
everything
that
pertains
your
application
to
your
users.
You
will
be
you're
like
100
responsible
for
them,
and
everything
that
pertains
to
the
platform
and
support,
AWS
and
red
card
will
provide
us.
A
To
the
developer,
my
application
owners
they're
still
doing
exactly
what
they
were
they're
still
getting
all
the
benefits
from
openshift.
This
change
over
here
really
impacts
infrastructure
teams,
operators,
administrators
the
developers
will
see
no
different
same
interfaces,
same
CLI,
tooling,
same
pipeline
process,
same
benefits,
life
carries
on
this
is
really
a
business,
streamlining
and
Agility
for
the
day
two
operational
aspects,
so
you're
really
getting
the
benefits
of
both
things
here,
Charlotte,
as
always
fantastic
having
you
here.
Thank
you
for
joining
me.