►
From YouTube: Reza Shafii - State of the Union, OpenShift Roadmap and Vision - OCG Buenos Aires 2018
Description
Reza Shafii (Red Hat) State of the Union, OpenShift Roadmap and Vision - OCG Buenos Aires 2018
A
B
B
So
today,
I
wanted
to
you
know,
obviously
talk
about
the
openshift
roadmap
and
authorship
vision.
But
before
doing
that,
I
wanted
to
maybe
talk
about
a
more
fundamental
question,
which
is
you
know?
Why
does
it
matter?
Why
does
OpenShift
matter
and
what
we
all
do
every
day,
what
we
all
love
to
do
every
day
into
to
talk
about
that
question,
I'm
gonna,
go
way
back,
I'm
gonna
go
to
2003
we're
in
the
Harvard
Business
Review.
There
was
an
article
that
came
out.
That
said
it
doesn't
matter,
and
but
it
doesn't
matter
you
know.
B
B
B
Just
like
it
was
software,
so
so
Nicholas
Carr
was
probably
wrong,
but
wait
a
minute
that
last
example
I
used.
Maybe
he's
actually
right,
because
the
way
that
I
received
all
of
the
computing
resources
when
I
used
AWS
that
has
somewhat
commoditized
computing
services,
I
can
go
to
a
couple
of
cloud
providers.
I
can
use
their
services
on
a
consumption
based
spaces,
and
so
therefore,
wouldn't
that
say
that
computing
has
become
commoditized.
B
I
just
want
networking
that
is
on
its
way
to
commoditizing
over
time,
and
the
cloud
providers
are
definitely
on
their
way
to
doing
that,
and
that's
great,
but
that
doesn't
mean
that
innovation
is
stopping
on
the
layers
above
and
that
dad
I
see
as
a
whole
and
technology
as
a
whole
is
not
a
source
of
innovation,
because
if
you
go
just
one
layer
above
what
we
commonly
call
middleware,
innovation
is
still
staggering.
You
get
things
like
Kafka,
you
get
things
like
Vitesse.
B
There
is
huge
amounts
of
innovation
that
one
can
achieve
by
using
new
middleware
services
that
are
just
appearing
on
a
technological
scene
in
order
to
write
applications
which
is
the
next
day
or
above
that,
and
applications,
of
course,
are
the
things
that
give
us
the
most
innovations
by
being
able
to
more
quickly
build
the
right
applications
and
improve
the
right
applications.
Our
businesses
are
going
to
be
more
successful
and
that
source
of
IT
innovation
is
likely
not
going
to
stop
for
a
long
long
time.
B
Uber
is
an
application
at
the
end
of
the
story
and
who
cares
what
it's
running
in
the
bottom
layer,
but
the
fact
that
is
using
a
really
high
speed,
high
scale,
chewing
service
or
publish/subscribe
service
does
matter
to
Ober.
But
the
fact
what
kind
of
hardware
is
using,
probably
doesn't
matter
that
much
it's
interesting,
because
I
think
Nicholas
car
and
I'm
not
picking
on
Nicholas
car
too
much
here,
and
it
was
actually
wrong
on
the
electrical
aspect
of
this
as
well.
B
B
B
These
are
devices
back
in
the
1900s
that
started
using
electricity
and
you'll
notice,
something
peculiar
about
them,
so
you've
got
a
toaster.
On
the
left
hand,
you've
got
at
the
top
left
a
device
to
heat
food
and
bottom
left.
It's
it's
a
hair
straightener,
and
so
you
can
see
that
all
of
them
use
a
light
bulb
socket
and
that's
because
electricity
was
first
introduced
for
lightning
and
then
people
started
actually
building
other
devices
to
actually
tap
into
the
electricity,
and
they
said
okay
I'm
just
going
to
use
the
the
lightbulb.
B
When
you
use
a
service
like
lambda,
when
you
use
a
service
like
Athena
or
Kinesis,
you
are
tightly
coupled
to
AWS
infrastructure
and
what
that
means
is
is
if
the
equivalent
of
the
toaster
was
built.
That
way,
I
was
told.
Last
night,
that
here
in
Buenos,
Aires,
there's
two
electricity
provider
and
this
Sharan
data,
nor
that
would
mean
that
whenever
you
move
to
a
place,
that's
editor
and
your
toaster
was
built
with
Edden
or
you
could
not
move
your
toaster.
You
got
to
buy
a
new
toaster.
You
want
to
go
to
Uruguay.
B
Sorry,
you
got
to
buy
a
new
toaster
or
that
would
not
be
a
world
I
would
like,
and
you
definitely
don't
want
your
applications
to
be
that
way.
So
so
that
is
a
big
part
of
why
I
think
openshift
matters,
because
openshift
brings
that
neutrality,
layer
that
portability
layer
to
the
underlying
cloud
infrastructures.
B
It
allows
you
to
take
the
advantage
of
the
flexibility
and
ease
of
what
infrastructure-as-a-service
has
effectively
become
yet
be
able
to
build
applications
that
are
decoupled
from
that,
while
taking
advantage
of
the
flexibility
and
simplicity
I
want
to
talk
about
how
openshift
achieves
that
there
is
at
least
three
pieces
to
the
puzzle.
The
first
is
kubernetes.
B
The
second
is
automated
operations,
and
the
third
is
bringing
automated
operations
to
the
diverse
set
of
services
that
are
out
there
and
not
just
one
cloud
provider
services,
and
so
let's
talk
about
each
of
these.
Let's
start
with
kubernetes
do
Bernese
was
introduced
a
while
ago,
2015
I
believe
it's
the
anniversary
of
kubernetes
and
stuff
a
couple
of
weeks
ago.
So
you
see
a
lot
of
blogs
out
there
and
he's
Google
obviously
introduced
kubernetes.
B
B
There
was
two
companies
that
work
closely
with
Google
to
do
that:
Red,
Hat
and
core
OS,
and
they
happen
to
be
the
same
company
now
now
for
a
while
there.
If
you
were
following
this
scene,
it
was
unclear
what
orchestration
technology.
So
everyone
agreed
that
containers
are
the
future,
but
it
was
unclear
what
orchestration
technology
is
going
to
win.
B
What
it
does
is
that
it
abstracts
away
the
compute
infrastructure
from
the
overlying
applications
that
are
running
on
it.
So
you
can
say:
I've
got
I'm,
just
gonna
keep
adding
compute
on
one
side
to
serve
my
compute
needs,
but
at
the
top
you
just
add
applications,
and
you
tell
cuba
name
is
what
the
compute
needs
are
and
then
each
starts
playing
that
perfect
tetris
game
in
order
to
make
sure
that
the
right
applications
have
the
right
resources.
So
you
don't
have
to
schedule
all
of
that.
B
So
that's
one
piece
of
the
puzzle:
let's
talk
about
the
other
two
pieces,
the
puzzle,
which
was
automated
operations
and
bringing
the
simplicity
of
the
cloud
to
the
services
that
are
above
the
kubernetes
there,
those
two
pieces
of
the
puzzle,
a
big
part
of
how
Red
Hat
is
solving.
That
problem
is
through
the
acquisition
of
core
OS
and
the
integration
of
cores
technology
into
OpenShift
and
the
future
of
open
shifts.
B
B
One
was
called
core
OS
container,
a
Lynx
which
is
container
optimized
operating
system
with
over-the-air
updates.
Gonna
talk
more
about
that
polarized
tectonic,
which
was
the
competitor
to
OpenShift
kubernetes
distribution.
It
also
came
with
automated
operations
and
over-the-air
updates.
What
I
mean
by
that
by
the
way
is
that
it
brings
the
simplicity
of
the
cloud,
no
matter
where
you're
running
it.
B
So
if
you
run
tectonics
on
AWS
or
on
your
premises
on
OpenStack
or
on
Google,
it
doesn't
matter,
but
you
will
continue
to
get
updates
that
will
pop
up
just
like
your
iPhone
and
say
an
update
from
version
1.7
to
1.8
of
cuber
Nettie's
is
available.
Do
you
want
to
apply
that
you
press
a
button
and
within
10
minutes
all
of
your
nodes
are
updated.
The
cluster
automatically
backs
itself
up.
The
HCD
state
is
backed
up
so
that,
if
something
goes
wrong,
you
can
always
restore
it
automatically.
B
These
are
the
capabilities
we
typically
associate
with
the
cloud,
but
we
want
to
really
have
anywhere
and
we
just
want
to
not
worry
about
it
and
that's
what
tectonic
brought
to
the
picture
and
finally,
core
OS
quai,
which
was
the
image
registry
that
allow
the
allowed
one
to
actually
store
all
of
the
images
and
track
their
changes
and
point
all
the
applications
container
to
so.
I
talked
about
that
right.
B
So
the
big
part
of
what
Kuro
has
brought
to
the
picture
is
NATO
operations,
automation
of
data
operations,
installation
upgrade,
backup
failure,
recovery
and
so
on,
so
that
you
don't
have
to
worry
about
it,
no
matter
where
you
are,
but
that
it
brought
that
to
the
picture
at
the
operating
system
and
kubernetes
layer.
But
a
good
question
that
you
might
ask
is
what
about
everything
else:
I
use
on
top
of
it.
I
have
Postgres
database,
my
sequel
database
of
Kafka
running
on
there
I
have
elasticsearch
running
under
Redis.
In-Memory
data
grid
fuse
whatnot.
B
They
all
need
to
act
like
the
simplicity
of
the
cloud
for
me
to
be
incented,
to
use
those
services
versus
the
cloud
provider,
services
that
have
the
the
issue,
with
the
light
bulb
going
all
the
way
down
to
the
provider,
and
so
with
that
we
introduced
at
cube
con
Copenhagen
about
three
months
ago.
Something
called
the
operator
framework.
It's
an
open
source
project.
B
And
if
you
go
to
the
operated
frameworks,
awesome
operator
repo,
you
will
see
a
list
of
55
existing
operators
that
have
already
been
written
that
have
that.
There's
things
like
Redis:
in
there
there
is
WebLogic
one
there
Kafka
one.
There
is
many
many
types
of
operators
by
variety
of
vendors.
Some
of
them
are
competitors
to
us,
but
that's
exactly
what
we
wanted.
Our
goal
is
to
create
a
diverse
set
of
services
by
all
the
vendors
out
there,
so
that
one
cloud
provider
cannot
held
us
hostage
to
their
services
alone,
and
that
is
succeeding.
B
What
does
this
mean
for
OpenShift,
so
we're
taking
all
that
technology
and
bringing
it
into
the
overshift
and
exposing
it
as
first-class
citizen,
so
going
forward
open
ship
is
going
to
have
an
operator
console
as
well,
so
not
only
there
will
be
a
console
for
the
consumers
of
the
cluster
that
want
to
deploy
their
applications.
You'll
have
a
console
that
gives
you
a
much
more
system
at
mid,
centric
view
of
the
cluster
that
will
show
you
updates
that
are
coming
up,
so
you
can
apply.
B
The
updates
I'll,
give
you
monitoring
and
metering
information
which
I'll
talk
more
about
as
well
in
the
coming
slides.
I
want
to
just
go
back
now
to
the
operating
system.
I
mentioned
that
container
Linux
was
one
of
the
technologies
that
we
acquired
from
core
OS
atomic
and
container
Linux
are
being
merged
into
a
new
operating
system.
That's
called
Red
Hat
core
OS
and
the
Red
Hat
chorus
operating
system
will
have
all
the
qualities
of
the
container
Linux
operating
system.
So
it
will.
B
It
is
going
to
be
container
optimized,
meaning
just
enough
operating
system
with
a
small
surface
area
for
attacks.
It
will
also
have
over-the-air
updates.
That
means
that
you
are
going
to
be
able
to
receive
updates
that
can
be
dynamically
applied
to
all
of
your
operating
system
layers
running
with
container
linux.
We
have
today
over
200,000
nodes
that
are
registered
to
receive
automated
updates.
That
means
every
two
weeks
when
we
push
an
update,
200,000
nerds
get
updated
automatically,
and
this
is
what's
coming
up
to
Red
Hat
core
OS.
B
So
that
means
that
the
installation
and
upgrade
experience
of
OpenShift
is
going
to
change.
Fundamentally,
we
are
going
to
a
world
now
where
the
first
layer
will
be
Red,
Hat,
core
OS,
and
on
top
of
that
cuber
Nettie's,
with
fully
automated
operations,
so
we'll
go
to
from
this
world
where
you
have
to
do
a
lot
more
management
of
the
infrastructure
to
a
world
where
the
whole
infrastructure
is
automated
operations
with
automated
backups
and
automated
tuning
and
automated
upgrades
and
so
on.
B
But
as
an
operator,
you
still
want
to
see.
What's
going
on
so
you're
still
going
to
be
able
to
see.
Ok,
these
upgrades
are
coming
in.
I
want
to
do
a
dry
run.
Let's
see,
what's
going
to
happen.
Ok,
the
dry
on
is
looking
good.
First
I'm
going
to
apply
to
my
pre-production
environment
that
works
now,
I'm
going
to
apply
to
my
production
environments
that
work.
If
it
didn't
work,
you
can
roll
it
back.
These
are
the
things
you
want
to
be
able
to
do
as
an
operator.
B
You
want
the
system
to
automate
it,
but
you
still
want
to
have
control
part
of
having
control
is
going
to
be
monitoring
and
we
are
bringing
in
Prometheus
we're
one
of
the
main
contributors
to
Prometheus,
which
is
becoming
a
really
important
project
for
monitoring
purposes
out
there.
So
we're
building
in
Prometheus
into
openshift,
with
out-of-the-box
dashboards,
both
embedded
within
the
operator
console,
but
also
with
technology
called
grow
fauna
that
allows
you
to
view
and
slash
and
dash
the
data
in
very
powerful
ways
baked
into
our
console
now.
B
B
You
will
notice
that
you
know
one
one
experience
and
I'm
sure
those
of
you
who
are
using
it
that
way.
It's
an
aggregating
technology,
all
the
different
stakeholders
that
had
different
applications
running
on
their
own
infrastructure
are
now
going
to
be
deploying
the
applications
on
kubernetes,
which
is
abstracting
away
the
infrastructure
layer,
so
guess
who's
paying
the
bill
for
the
infrastructure.
Now
it's
not
going
to
be
the
application
owners
anymore.
B
It's
going
to
be
the
kubernetes
provider,
and
if
you
are
that
the
people
who
are
bringing
in
cuber
Nerys,
you
have
to
worry
about
paying
the
bill
for
the
infrastructure,
the
application
owners
don't
anymore.
That's
good,
but
you're
gonna
have
to
explain
to
your
CIO
why
this
bill
is
so
big
and
so
operator
metering
allows
you
to
explain
that.
Sometimes
we
call
this,
you
know
metering
and
chargebacks.
B
Sometimes
we
call
it
metering
and
Shane
back
and
that's
because
what
it
allows
you
to
do
is
to
show
that
the
division,
this
application
is
using
this
much
of
the
AWS
bill.
This
other
application
is
using
this
much
of
the
CPU
and
this
much
of
the
memory,
and
it
comes
down
to
this
much
dollars
an
important
part
of
running
openshift
at
scale.
B
Okay,
a
couple
of
hands
so
helm
is
a
technology
used
to
describe
application
in
the
Kuban
Eddy's
world
and
we
are
betting
quite
a
bit
on
helm.
So
going
forward,
we
are
going
to
double
down
on
quai
the
image
registry
support
for
helm,
and
what
that's
going
to
be
allowing
us
to
do
is
to
basically
treat
your
own
applications
if
you
have
mobile
apps
that
need
to
run
on
cue.
B
Burnett
is,
if
you
have
any
enterprise
offspring,
what
you
represent
them
by
helm,
charts
that
describes
what
you
know,
what
kubernetes
constructs
they
need
to
map
to
you
and
then
in
Quay,
we'll
be
able
to
represent
those
as
applications,
even
though
they
span.
Multiple
image
and
multiple
kubernetes
manifests
and
then
be
able
to
tie
that
to
a
helm
operator
which
comes
out
of
the
box
with
OpenShift
and
which
allows
us
to
actually
then
have
the
full
CI
CD
pipeline
automated
for
you.
So
as
a
user,
you
just
submit
your
code
to
github.
B
B
Okay.
That
brings
me
to
my
second
last
slide:
we're
going
to
exciting
places
with
open
shift
for
which
is
going
to
be
our
next
big
release.
I
know,
openshift
310
was
just
released,
311
is
coming
up
and
it's
going
to
have
elements
of
what
you
just
saw,
such
as
metering
and
chargeback
and
monitoring
built
in,
but
it
won't
have
the
automated
operations
capabilities
with
automated,
with
openshift
4
we're
going
to
have
the
automated
operation
capabilities,
the
monitoring
capabilities
we
just
talked
about.
B
We
are
going
to
have
the
an
extended
catalog
of
applications
that
our
vendor
backed
that
have
automated
operations
with
them
certified
our
openshift
and
we're
going
to
have
the
developer
experience
capable
teachers
talked
about
in
terms
of
integration
with
helm
charts.
So
this
is
the
big
release
for
us
very
exciting
release
that
is
coming
up
currently
planned
for
January
type
timeframe,
but
we
really
believe
this
is
the
game
changer
and
the
reason
why
this
matters
the
reason
why
this
man
is
because
openshift
is
picking
up
steam.