►
From YouTube: Opening Keynotes with Chris Wright & Reza Shafii at OpenShift Commons Gathering Seattle 2018
Description
Opening Keynotes with Chris Wright & Reza Shafii at OpenShift Commons Gathering Seattle 2018 https://commons.openshift.org/gatherings/Seattle_2018.html
A
B
B
Just
wanted
to
talk
a
little
bit
about
why.
Why
does
it
matter
right
at
least
a
perspective
on?
Why
what
we're
all
doing
with
OpenShift
matters
and
to
talk
about
that
I'm?
Going
to
start
and
by
the
way,
we're
going
to
see
a
lot
of
tweets
here,
because
a
couple
of
announcements
coming
up
as
we're
speaking
all
right.
It's
kind
of
interesting
to
see
it
on
the
side.
B
That's
okay!
Well,
we'll
live
with
education.
It's
gotta
be
good
updates
for
everyone
all
right.
So
so
why
does
it
matter
and
I'm
going
to
go
back
15
years
to
an
article
that
that
basically
said
it
doesn't
matter
right
and
I?
Remember
being
a
young
consultant
at
the
time
this
article
actually
had
quite
a
bit
of
you,
know
momentum
and
traction
in
industry
at
the
time,
and
people
were
talking
about
how
our
industry
is
is
about
to
go.
B
You
know
where
I
was
actually
worried
about
my
career,
as
people
were
talking
about
this,
and
you
know
that
the
argument
that
Nicholas
Carr
was
making
was
that
I
T,
like
electricity
and
like
railroads
in
their
time,
is
going
to
become
commoditized
and
organizations
are
not
going
to
need.
Ite
are
not
going
to
need
to
innovate
in
IT
in
order
to
be
successful,
it's
just
the
commodity
that
you
just
use,
and
so
let
me
just
get
a
quick
poll
from
the
audience
here
who
thinks
15
years
later
now,
who
thinks
that
Nicholas
Carr
was
right.
B
B
My
phone
to
you
know
access
an
array
of
videos
and
entertainment
from
from
United
and
again
that
has
completely
changed
the
way
that
entertainment
was
being
delivered
in
airplanes
and
by
the
way
I
was
playing
around
with
openshift
for
and
doing
so,
I
was
just
accessing
resources
at
the
infrastructure
level
on
Amazon
AWS.
So
on
that
last
one
I
would
like
to
say:
I
was
accessing
those
computer
resources
like
a
commodity.
B
I
was
getting
it
like
a
utility,
and
so
even
though,
in
the
first
three
scenarios,
I
would
say,
nicholas
carr
wasn't
right
in
the
last
one.
He
was
probably
right
so
what's
happening
here.
I
think
it
depends
how
you
look
at
it
if
you
look
at
it
from
the
different
layers
from
a
computing
infrastructure
to
use
the
words
from
the
article
getting
towards
boring
necessity
to
operations.
Computing
infrastructure
is
slowly
getting
there.
B
But
if
you
go
one
layer
up
the
services
that
we
use
to
build
applications
today,
I
think
you
can
see
that
innovation
is
still
very
much
alive.
You
look
you
know.
I
was
just
coming
up
this
stairs
here,
Technologies
like
Vitesse,
right
technologies
like
@cd,
which,
by
the
way
you're
going
to
hear
more
about
tomorrow
at
the
keynote
not
to
spoil
anything
in
technologies
like
Coke,
Russia
being,
and
the
list
goes
on
on
on
and
on
the
innovation
at
the
computing
services.
B
Layer
has
not
stopped,
and
if
you
go
one
level
higher
than
that
applications,
the
applications
that
we're
all
building
in
our
organizations
that
you're
building
to
get
your
business
to
to
be
more
successful
or
innovation.
As
definitely
not
stopped
at
that
level
and
I
would
venture
to
say
that
the
same
is
true
for
the
electricity
example
that
was
used
in
the
IT
doesn't
matter
article?
Yes,
it's
true
that
the
electrical
infrastructure
level
is
getting
to
be
a
boring.
It
probably
has
been
for
a
long
time
a
boring
necessity
to
operations.
B
But
then
people
notice
is
just
electricity
and
I
can
just
plug
any
appliance
into
it,
and
so
they
started
creating
devices
or
applications
that
plugged
into
the
electrical
service
using
that
plug
and
in
some
ways
that
was
a
blessing
in
disguise
because
it
provided
decoupling
from
the
electrical
infrastructure
provider.
So
it
didn't
matter
whether
it
was
Tesla
or
Edison
or
whoever
else
who
was
coming
up
with
the
electrical
infrastructure.
B
That
is
not
the
way
we're
going
with
the
application
and
software
world
and
IT
world,
in
fact,
as
we're
tying
ourselves
to
the
services
to
the
computing
services
provided
by
the
cloud
providers,
whether
it's
at
the
server
as
functions
level,
whether
is
at
the
queuing
level,
they
are
deeply
integrated
with
the
underlying
infrastructure
and
that's
those
are.
Those
are
ties
that
are
hard
to
break.
It's
like
saying
your
toaster
works
with
the
washing
State,
University
or
electricity
here.
But
sorry,
if
you
go
to
San
Francisco,
you
can't
move
that
toaster.
B
You
got
to
buy
a
new
toaster,
and
so
this
is
why
I
think
OpenShift
matters.
If
you
look
at
the
things
we're
working
on
it's
all
about
getting
to
a
point
where
you
don't
have
to
trade
off
between
that
flexibility
and
the
simplicity
of
the
cloud
and
the
diverse
ecosystem
of
services
that
are
out
there,
the
open
community
that's
out
there
so
that
they
all
operate
like
a
cloud
so
that
your
applications
can
be
truly
portable
and
move
anywhere,
and
that's
that's
really
it.
And
so
what
are
we
doing?
You
know
big
themes.
A
So
what
I
want
to
talk
to
you
about
is
some
of
the
things
that
we're
doing
in
terms
of
collaboration
across
communities
a
little
bit
of
like
technology
sace,
like
sneak
previews
of
where
we're
going
and
really
think
about
what
are
we
building
together?
So
my
perspective
is
a
hybrid
cloud.
Isn't
is
an
opportunity
to
really
create
total
independence
for
your
applications
from
from
the
underlying
infrastructure?
A
And
this
is
something
that,
if
you
think
about
Linux
and
what
Linux
did
this
is
something
that
we've
been
doing
as
an
industry
for
quite
a
long
period
of
time,
so
Linux
created
the
opportunity
to
run
applications
and
a
consistent,
runtime
environment
independent
of
the
underlying
hardware.
A
hybrid
cloud
gives
us
that
same
capability
using
kubernetes
to
do
distributed
computing
and
allowing
us
to
place
those
applications
on
public
clouds
or
within
your
own
datacenter,
private
cloud
or
or
even
virtualized
or
bare
metal
deployment.
So
that's
a
lot
of
you
know.
A
That's
really
I
think
what
we're
building
I
think.
That's
the
the
most
exciting
part
to
me.
If
you
think
about
what
is
a
cloud,
I
would
describe
a
cloud
as
two
key
things.
One
is
basically
ease
of
operations.
You
you've
essentially
outsourced
your
operations
is,
somebody
else
run
the
infrastructure
for
me.
I'm
just
gonna
consume
it
through
api's.
That
creates
a
lot
of
benefits.
It's
really
efficient
way
from
from
a
consumer
perspective,
to
use
the
infrastructure.
A
Another
key
piece
to
a
cloud
is
what
I
would
describe
as
differing
levels
of
abstraction
or
ways
to
engage
with
the
cloud
or
services
that
you
consume
from
the
cloud.
So
a
cloud
isn't
just
easy
to
use,
but
it's
a
breadth
of
services
and
what
I'm
really
excited
about
with
the
hybrid
cloud?
Is
we
have
this
opportunity
to
create
an
ecosystem
of
services
that
run
on
top
of
a
consistent?
You
know
call
it
a
fabric
or
whatever
you
want,
whatever
sort
of
buzzword.
A
A
We
haven't
done
as
much
work
as
a
community
focused
on
on
bare
metal
and
one
of
the
things
that
I
find
interesting
is
over
the
last
roughly
year
or
so
in
talking
to
customers
and
users.
There's
this
increased
interest
in
running
kubernetes
directly
on
bare
metal,
so
you
could
argue:
we've
spent
a
whole
long
period
of
time
trying
to
convince
ourselves
that
Hardware
just
doesn't
matter.
It's
irrelevant.
It's
kind
of
this
homogeneous
commodity.
You
just
use
compute
and
what
I?
A
A
A
Another
piece
that
I
think
is
interesting
here
is
we
have
an
opportunity
to
think
of
application
deployment,
as
managed
by
say
a
single
cluster
manager
and
scheduler.
So
we've
been
working
on
this
project
called
Cubert
for
quite
some
time,
and
when
you
combine
something
like
bare
metal,
provisioning
and
Cubert,
you
get
an
environment
where
you
have
containers
and
VMs
as
peers
and
first-class
citizens
that
sit
right
side
by
side
with
one
another.
So
the
applications
that
we've
spent
the
last
decade
building
and
virtual
machines,
we
don't
have
to
just
abandon.
A
A
You
know
independent
of
the
the
you
know,
virtualization
technology,
so
kind
of
a
next-generation
way
to
look
at
infrastructure
in
it
for
applications
and
I.
Think
I
already
mentioned
the
the
performance
sensitive
pieces,
but
a
great
example.
There
is
the
use
of
GPUs
and
FPGAs
for
machine
learning
workloads.
So
there's
the
machine
learning
cig
here,
an
open
chef,
Commons
and
one
of
the
things
that
we're
hearing
a
lot
from
users
of
kubernetes
is
it's
a
maybe
to
put
it
simply,
I
think
we
would
probably
all
agree.
A
Kubernetes
is
one
kubernetes
is
the
de
facto
standard
for
how
we
do
cluster
management
and
scheduling
of
applications
across
linux
clusters.
What
that
means
is
the
entire
industry
is
collaborating
and
focused
on
a
common
platform
and
as
an
example,
bringing
data
centric
machine
learning
workloads
to
the
same
platform
is
something
that
we're
seeing
a
lot
of
interest
in,
and
so
things
like
performance,
sensitive
applications
where
we
want
direct
access
to
a
GPU
to
accelerate
the
machine
learning
environment
is
something
that
we
see.
B
A
We
they're
just
there's
been
some
scale
labs
and
a
lot
of
blog
posts
on
how
many
hundreds
or
thousands
of
nodes
we
can
scale
to,
and
that's
important
and
it's
interesting,
and
we
also
have
to
consider
what
is
the
kind
of
impact
of
a
large-scale
cluster.
Well,
you
know,
there's
there
are
some
fundamental
scaling
challenges.
A
When
we
have
multiple
clusters,
we
create
a
new
set
of
challenges
for
ourselves.
So
this
is
an
area
that
has
been
underway
in
the
kubernetes
community
for
quite
some
time,
and
we
are
slowly
bringing
this
technology
into
openshift
and
creating
a
Federation
capability
that
will
really
allow
us
to
take
advantage
of
deploying
clusters
where
they
should
go
and
then
deploying
applications
to
the
correct
cluster.
A
Over
time
and
again,
we
can't
trivialize
what
it
means
to
replicate
the
data
across
all
the
clusters
where
applications
may
need
to
land,
or
what
does
networking
look
like
in
a
context
where
you
need
to
direct
to
the
right
cluster?
You
want
to
feel
like
it's
a
seamless
interconnection
across
all
of
the
clusters.
Now
these
are
not
native
functionalities
in
kubernetes
today.
This
is
how
we
can
advance
the
state-of-the-art
already
in
openshift
311.
A
A
How
can
we
ease
deployment
and
have
this
the
system
take
over
and
push
the
application
to
the
right
location,
maybe
take
advantage
of
a
hardware,
accelerated
environment
that
your
application
may
ultimately
be
dependent
on
to
deliver
its
SLA.
So
this
to
me,
is
is
a
view
of
where
we're
trying
to
go
with
with
cluster
Federation,
and
we
can
take
a
look
at
a
simple
use
case
here.
The
developer
is
using
the
Federation
control
plane
to
do
the
initial
workload
placement
and
the
initial
workload
placement
was
pushed
to
a
bare
metal
cluster
of
kubernetes.
A
Now,
for
whatever
reason
could
be
policy
dependent
or
point
in
time
doing
some
some
upgrades,
the
developer
decides
that
it's
time
to
push
that
application
to
a
different
infrastructure,
so
here
we're
showing
something
moving.
The
application
to
a
cloud
cluster
cloud
based
cluster
and
what's
cool
about
this
is
we're
pushing
the
real
behind-the-scenes
work
into
automated
routines,
so
that
you
can
specify
how
you
want
to
deploy
the
the
application
and
have
the
system
slowly
reconcile
things
like
ensure
that
the
data
is
properly
replicated
in
the
application
can
move
to
the
right
location.
A
You
get
ingress
routing
to
the
application
appropriately,
so
you're
not
bouncing
all
over
the
place,
and
ultimately
our
goal
here
is
to
make
these
collection
of
clusters
feel
seamlessly.
You
know
independent,
so
they
really
look
like
one
large
place
to
deploy
applications,
even
though
they're
they're
managed
as
separate
clusters.
A
So
if
you're
interested
in
that
we've
got
a
couple
folks
here,
I
don't
see,
Paul
he's
usually
easy
to
identify
and
and
Ivan,
and
you
know,
here's
the
github
repo.
We
have
this
this
demo
that
we've
been
working
on
that
shows
application
portability,
and
this
is
just
a
way
that
you
can
get
directly
involved
in
in
Federation,
so
that
some
some
work
has
already
started.
A
Another
area
that
shows
this
de
facto
standardization
around
kubernetes
is
the
work
we've
seen
in
the
serverless
space.
So
it's
not.
You
know
it's
not
new
to
the
industry.
We've
been
hearing
a
lot
about
serverless,
especially
in
the
context
of
ada
AWS
and
lambda,
demonstrated
some
real,
interesting
capabilities
of
making
it
as
easy
as
possible
for
developers
to
create
applications
or
functional
logic
in
the
CNC
F
serverless
working
group
there's
quite
a
few
different
projects
associated
with
that
and
where
I
see
the
de-facto
standardization
of
kubernetes
winning
showing
itself
is
in
the
K
native
project.
A
These
are
the
kind
of
core
building
blocks
and
we're
really
excited
to
announce
just
today,
a
few
minutes
ago
that
we
have
an
open
shift,
developer,
previews
of
K
native
on
open
shift
and
again
this
is
just
the
beginning
of
building
an
infrastructure
that
allows
you
to
create
functions
that
run
entirely
independently
of
that
underlying
infrastructure.
So
the
the
specialized
socket
that
Raisa
was
talking
about
in
the
potentially
vertically
integrated
stack
that
you
find
from
one
single
provider
is
something
that
we
can
neutralize
and
turn
into
a
broad
scale.
A
We've
got,
operators
and
operators
are
an
example
of
creating
that
ease
of
use
that
we
mentioned
the
beginning
of
what
is
a
cloud
you've
heard
a
lot
about
operators.
This
is
just
an
example
of
a
single
operator
comparing
a
simple
containerization
through
cloud
service
to
operators
on
kubernetes,
which
gives
you
the
breadth
of
availability
across
many
platforms.
A
And,
ultimately,
if
you
look
in
Commons
there's
something
like
50
operators-
and
this
is
a
space
where
we
have
the
opportunity
to
create
that
not
the
pure
ease
of
operations,
but
also
the
breadth
of
ecosystem
support
for
a
hybrid
cloud
vision.
So
this
is
something
that
I
think
is
is
a
really
great
advanced,
state-of-the-art
advance
and
it's
a
place
where
the
ecosystem
fundamentally
matters-
and
this
to
me
all
adds
up
to
something.
A
I
got
to
give
kudos
to
raise
up
for
the
the
slide
and
the
quote,
but
it
all
adds
up
to
something
where
what
we're
trying
to
build
is
a
future
vision
where
it's
automated
operations,
it's
so
simple
to
use.
It
runs
like
a
cloud.
I
use
the
term
autonomous
cluster
daniel
reek
who's
here
somewhere
uses
the
term
self-driving
cluster.
A
We're
really
moving
in
a
direction
where
everything
that
we
do
enables
machines
to
manage
the
clusters
and
developers
to
build
the
applications
that
are
disruptive
and
and
really
bringing
innovation
to
the
industry
and
providing
that
platform
for
really
the
next
generation
of
businesses
and
and
an
opportunity.
So
with
that,
thank
you
for
coming
to
the
Commons
and
look
forward
to
collaborating
with
you
throughout
the
week.