►
Description
Clayton Coleman and Brandon Philips of Red Hat present the State of the Union of Red Hat and CoreOS and give an update on the road map for the upcoming release of OpenShift and a sneak peek at the Operator Framework
A
There,
without
any
further
ado,
I
want
to
bring
up
one
of
the
newest
Red,
Hat
hat
hers
and
one
of
our
very
favorite
ones
as
well.
Clayton
Coleman
the
lead
architect
for
for
openshift
and
Brandon
Phillips,
who
has
joined
us
from
core
OS
and
is
now
a
red
Hatter.
So
I'm
going
to
let
them
give
you
the
State
of
the
Union.
B
C
Right
good
morning,
everyone
so
Diane
I
think
ruined
our
big
surprise,
which
was
we
bought
core
OS
I,
don't
know
if
you
guys
have
heard
bad
in
the
last
couple
months,
so
I'm
Clayton,
Coleman,
I'm
Brandon
Phillips.
So
when
we
talk
about
State
of
the
Union,
you
know.
Normally,
this
talk
is
somewhat
about.
What's
happened
in
the
last
six
months
or
the
years
since
we
let
me
talked
about
it,
but
I
figured
you
know
when
we
talk
about
Union,
we're
talking
about
core
OS
and
red
hat
coming
together.
C
What
are
the
things
that
matter
to
the
people
in
the
room?
Give
you
a
real
high
low
over
them
over
you
to
me.
The
idea
for
the
red
hat
core
OS
merger
was
really
about
bringing
two
people,
two
groups
of
people
who
cared
very
deeply
about
the
technology
and
kubernetes
in
the
open
source
ecosystem,
bringing
them
together
and
being
able
to
build
something
greater
out
of
it.
I
think
when
this
went
through
we
there
was
kind
of
this
idea
that
we're
gonna
bring
the
two
two
smartest
sets
of
people
in
kubernetes.
B
So
before
before
we
get
too
into
the
technical
weeds,
I
wanted
to
just
give
a
little
context
on
where
core
OS
came
from
and
really
how
we
thought
about
the
space
and
our
overall
mission,
that's
the
company
and
as
a
set
of
products.
So
there's
three
and
a
half
billion
Internet
users
today
and
there's
about
at
any
point.
B
This
is
a
rough
estimate
20
my
29
million
practitioners
of
IT
and
development
in
the
world,
and
the
simple
fact
is,
like
we're
horribly
outnumbered
the
number
of
folks
that
using
the
internet,
actually
a
number
of
folks
coming
out
into
the
internet
versus
the
the
people
who
are
who
are
experts
in
how
the
whole
thing
works
and,
if
you
think
of
it,
we
can
just
educate
our
way
out
of
it
or
if
we
can
expand
the
number
of
jobs
and
catch
up.
That's
simply
not
the
case.
B
There's
a
quarter
billion
of
people
being
able
to
be
owned
every
year.
These
are
just
staggering
numbers
and
the
fact
of
the
matter
is
everywhere:
you
go
across
the
globe,
everyone's
taking
all
of
their.
You
know
everyone
talks
about
mobile
and
the
cloud,
but
these
are
just
a
bunch
of
things
that
end
up
with
a
bunch
of
important
data
ending
up
on
servers
and
so
at
core
OS.
With
these
kind
of
staggering
numbers
we
thought
about.
Well,
how
do
we
make
sure
that
the
about
roughly
a
hundred
million
servers
that
exist
worldwide?
B
How
do
we
ensure
that
those
things
are
well
managed?
How
do
we
ensure
that
the
people
who
are
in
charge
of
manage
them
have
the
tools
to
the
best
possible
job
by
security
by
the
customers,
ensuring
that
there's
uptime
for
those
three
and
a
half
billion
people,
and
what
we
came
up
with?
Was
we
needed
to
change
the
way
that
enterprise
software
ends
up
being
delivered
into
people's
data
centers
and
onto
people's
public
clouds
kind
of
the
culmination
of
what
we've
been
doing
over
the
last
few
years?
B
Is
this
idea
of
operators
we'll
talk
about
it
in
the
context
of
both
the
platform,
the
open
shift
and
kubernetes
platform,
but
then
also
in
the
context
of
applications
on
top,
but
really
what
it
comes
down
to?
Is
we
want
to
enable
this
idea
that
no
matter
where
you
end
up
running
your
application
across
the
hybrid
cloud,
we
want
to
make
sure
that
the
experience
is
the
same.
B
The
application
infrastructure
around
your
app
is
the
same
and
that
you're
able
to
manage
it
in
a
way
that
removes
a
lot
of
the
complexity
and
enables
you
to
simply
use
necessary
infrastructure
to
make
your
application
and
your
team
successful.
So
that's
that's
a
little
bit
about
what
the
Kouros
mission
was
about
we'll
get
in
some
of
the
weeds
now
and.
C
You
know
on
the
on
the
flip
side,
on
the
openshift
mission,
for
those
of
you,
who've
been
with
open
for
very
long
time.
We
started
out
as
a
platform
as
a
service
platform
as
a
service
is
about
making
things
easier.
Deploying
software
specifically
there's
been
lots
of
attempts
at
platform
as
a
service
and
lots
of
different
platforms
as
a
service.
Everyone
different
requirements,
different
use
cases,
come
together
to
to
mean
that
people
build
things
slightly
differently
for
us.
C
The
opportunity
with
kubernetes
and
with
openshift
I'm
starting
just
three
years
ago
was
we
want
to
find
the
easiest
way
to
ship.
The
most
software
iteration
has
to
be
easy.
We
want
to
reduce
that
difference
between
development
and
production,
make
deployment
repeatable
and
automate
a
automatable
and
kubernetes
and
containers
and
the
ideas
of
building
powerful
tools
that
can
be
composed
together
to
build
applications
just
enough
of
the
the
standard
patterns
that
we
all
used,
but
still
allow
things
on
top
to
have
their
own
complexity
in
their
own
flexibility.
C
We've
seen
that
in
the
kubernetes
ecosystem
we've
seen
you
know,
even
in
the
last
I
think
three
months
there
have
been
something
like
15
or
20
different
projects
for
building
images
or
for
making
it
easier
for
people
to
iterate
locally
and
then
push
to
a
kubernetes
server.
This
idea
of
empowering
developers,
while
still
keeping
that
under
operational
control
and
having
the
tools
that
we
as
operations
teams,
need
to
understand
what
our
users
are
doing,
to
keep
the
applications
running,
to
standardize
and
to
provide
a
common
security
base.
C
All
of
those
pieces,
I
think
have
been
really
borne
out.
You
know,
being
three
years
ago,
when
we
stood
up
and
announced
OpenShift
v3
GA
there
were
some
doubters
I
would
guess
for
most
of
the
people
in
this
room
that
there's
not
as
many
doubters
as
there
were,
then
there's
thousands
of
operation
of
clusters
worldwide
and
Undine
releases
ecosystem
is
exploding,
and
so
that
idea
making
it
easier
to
get
ideas
from
to
go
from
ideas
to
production
as
quickly
as
possible.
C
This
is
where
that
complement
with
what
the
core
OS
mission
really
came
to
was,
if
one
side
of
the
story
is
about
keeping
control
of
the
world
with
automation,
because
it's
just
going
to
grow
out
of
our
hands
and
on
the
other
side,
it's
about
empowering
developers
to
be
as
efficient
as
possible,
but
still
to
do
that
in
a
form.
That's
under
control.
What's
the
next
step,
sure.
B
So
essentially,
our
shared
mission
and
I
think
what
we'll
be
talking
about
a
lot
over
the
next
year
or
so
as
we
bring
products
together,
is
automated
operations
and
the
way
that
we
think
about
the
way
we
thought
about
automating
operations
so
is
essentially.
This
cloud
is
essentially
two
parts:
the
traditional
hosting
business,
where
you
rent
some
servers
from
somebody
and
then
the
other
part,
which
I
think
is
the
interesting
property
that
has
caused
kind
of
the
explosion.
B
Around
cloud
usage
is
well
I,
make
an
API
call
and
now
services
available
to
me
I'm,
making
an
API
call
and
that
service
is
now
updated
and
overall
we
call
that
automated
operations
and
that's
that's
kind
of
the
shift
in
enterprise
software.
That
I
think
we
share
as
an
interesting
change,
particularly
as
you
started
to
think
about
hybrid
cloud
over
the
next
year
or
two.
So.
C
There's
a
lot
of
things
that
could
be
automated
and
you
were
somewhat
vague
today,
because
there'll
be
a
bunch
of
big
announcements
coming
up
tomorrow
and
at
the
summit
sessions
that
I
will
have
a
list
at
the
end
for
everybody
to
go
see
so
we're
going
to
stay
really
high
level.
I'll,
just
tease
you
a
little
bit
and
want
to
get
everybody
go
into
the
sessions.
We
don't
steal,
anybody's
thunder,
but
the
things
we
want
to
automate
our
applications
in
the
platform,
whether
that's
the
operating
system
in
kubernetes,
the
install
and
update
mechanisms,
the
infrastructure.
B
All
right,
so
what
I
wanted,
as
shown
here,
is
the
automation
that
we
ended
up.
Building
into
core
OS
tectonic,
which
was
the
name
of
the
product
that
we
had
built
as
part
of
core
OS
kubernetes
product
seems
like
there.
We
go
all
right,
so
this
is
the
chorus
tectonic
dashboard
when
you
first
log
into
it.
We
have
a
few
things
that
are
useful
and
interesting
when
you
first
get
in,
we
have
high-level
metrics
one
of
the
things
that
we
wanted
to
do
right
off.
B
The
bat
was
to
ensure
that
the
system
gave
you
monitoring
information,
so
whether
the
system
is
up
to
date,
whether
the
system
is
healthy,
etc.
So
that's
the
first
thing
you'll
and
at
the
at
the
login
screen
with,
but
one
of
the
unique
properties
and
going
to
this
whole
concept
of
automated
operations
that
we
had
was
that
Kouros
tectonic
had
kind
of
a
one
click
update
experience.
B
So,
if
you're
familiar
with
the
experience
on
your
iPhone
or
your
Android
device,
where
you
click
a
button
and
then
your
device
updates
over
time,
Kouros
tectonic
had
a
very
similar
experience.
Now.
This
cluster
has
automated
updates
already
in
running,
so
the
last
upgrade
that
we
released
a
few
weeks
ago
has
already
been
applied
to
this
up
this
cluster.
B
B
Health
is
the
exact
same
software
that
we
use
to
monitor
the
health
of
the
cluster
and
alert
on
the
clusters,
health,
and
so
we
get
all
of
these
properties
automate
automatically
for
free
like
well.
What
what
is
the
CPU
and
RAM
and
memory
usage
of
the
scheduler,
for
example,
or
if
I
need
to
write
a
piece
of
software
to
update
the
cluster
I,
can
use
the
kubernetes
api
to
do
that.
B
C
And
I
think
that
to
add
to
that
compliment,
while
we're
going
back
to
the
presentations
since
the
beginning,
the
focus
of
Red
Hat
has
been
making
kubernetes
the
best
place
to
run
applications
BarNone
and
to
build
on
top
of
that
layer
to
make
it
too
easy
to
deploy
and
run
containerized
applications.
And
as
we
worked
with
brandon
and
the
rest
of
the
core
OS
team,
it
was
really
obvious
that
we
had
picked
complementary
approaches.
C
What's
going
to
be
coming
this
year
and
next
because
every
one
of
these
builds
on
the
strengths
that
we
already
have
to
deliver
for
every
end-user
and
reinforces
those
so
that
every
time
we
make
a
user's
life
a
little
bit
better
who's
building
applications.
On
top,
we
make
administrating
the
platform
just
that
little
bit
easier
and.
B
Then
the
last
thing
I
want
to
touch
on
was
that
this
isn't
just
administration
of
the
system.
The
kubernetes
system
we
put
automate
operations
and
the
namesake
of
the
company
is
this
operating
system.
We
built
called
core
OS.
We
put
these
automated
operations
all
the
way
through
the
platform
down
to
the
individual
hosts
in
the
cluster.
So
this
is
just
a
looping
demo
of
where,
when
a
machine
gets
an
update,
we
actually
coordinate
that
update
through
the
kubernetes
api
as
well.
B
So
you
get
this
full
system
view
all
the
way
down
to
the
hardware
or
the
virtual
machine
of
whether
the
system
is
up-to-date.
What
the
state
of
the
update
is
for
each
individual
host
in
the
system
and
actually
control
the
rollout
of
that
the
big
difference
between
automated
operations
and
these
update
experiences
between
your
phone
and
the
server
environment
is
obviously
we
have
to
keep
the
server
environment
running,
and
so
these
it's
it's
slightly
inconvenient
when
your
phone
is
down
for
like
three
minutes,
it's
probably
like
the
worst
feeling
in
the
world.
B
At
this
point,
2018,
like
I,
don't
know
where
I
need
to
go.
I,
don't
know
I'm
not
in
touch
with
anyone,
but
on
the
server
side
we're
able
to
control
these
things
so
that
only
one
machine
or
a
handful
of
machines
in
the
cluster
are
down
in
a
given
time,
while
the
updates
are
happening
really
taking
advantage
of
the
distributed
nature
of
kubernetes
all
right,
all.
B
The
other
thing
that
we've
been
thinking
about
is,
over
the
last
five
years.
We've
been
really
focused
on
how
to
deliver
a
platform
that
has
this
concept
about
automation.
But
then
the
next
bit
is
well.
How
do
we
make
it
easier
for
open
source
projects
for
ISPs
for
really
anyone
to
deliver
software
on
top
of
kubernetes
for
the
sole
reason
of
supporting
applications?
B
We
really
wanted
to
want
to
see
more
and
more
of
these
operators
come
into
existence
and
a
red
hat.
We
kind
of
have
the
horsepower
to
ensure
that
that
happens.
So
this
is
an
open
source
project
to
ensure
delivery
of
not
just
a
platform
filled
with
automated
operations,
but
supporting
services
and
applications
on
top
of
that
platform
and.
C
It's
really
about
extensibility.
So
if
you're
going
to
build
a
platform,
it's
really
critical
that
that
platform
can
actually
support
the
use
cases
on
top
of
it.
So
from
the
very
beginning,
kubernetes
has
had
this
idea
that
it
was
a
small
core
of
a
distributed
operating
system
for
the
cloud
and
each
of
the
pieces
that
you
build
on
top
of
it
would
complement
other
pieces.
B
So,
to
give
a
practical
example,
so
two
years
ago,
we
introduced
a
thing
called
the
Prometheus
operator,
which
makes
it
really
easy
to
deploy
instances
of
a
monitoring
service
on
top
of
kubernetes.
And
what
we
had
hoped
was
that
application
developers,
if
getting
monitoring
for
the
application,
was
just
an
API
call
away
that
they
would
more
properly
monitor
their
application.
B
As
a
proof,
point
of
this
ticketmaster,
which
is
a
customer,
ended
up
making
this
Prometheus
Operator
available
to
all
their
users
across
all
their
clusters,
all
their
kubernetes
clusters
and
ended
up
with
about
400
copies
of
Prometheus,
supporting
their
applications,
making
it
possible
for
the
application
engineers
to
set
up,
alerting,
set
up,
monitoring
and
support
themselves
with
the
services.
They
need
to
make
sure
that
their
application
had
good
uptime
at.
C
This-
and
this
is
just
an
evolution
of
the
story
that
we've
believed
for
a
really
long
time,
we're
building
a
platform
that
makes
it
easy
to
take
ideas,
turn
them
into
reality
and
to
keep
them
running.
Automation
is
a
key
part
of
that
having
capabilities
available,
so
you
know,
I
I
drew
this.
You
know
really
quickly
and
just
threw
a
bunch
of
buzzwords
on
there.
C
Whatever
the
buzzword
of
the
the
last
six
months
is
all
of
these
ideas,
all
the
pieces
that
make
up
an
application,
those
will
change
and
people
will
evolve
and
will
build
new
tools
and
new
ways
of
taking
advantage.
Serverless
is
up
here
because
you
know
that's.
The
hot
topic
today
is
how
I
can
I
make
these
really
really
simple
applications
run
easily
in
it's
scale
and
I.
C
So
we
alluded
to
some
of
the
sessions
Brandon
and
I
are
in
or
speaking
of
these,
a
number
of
p.m.
these
are
kind
of
the.
These
are
the
top
four,
if
you're
interested
in
some
of
the
the
deeper
details
on
the
ideas
that
we
talked
about
here,
the
core
OS
and
Red
Hat
session
on
Tuesday,
the
kubernetes
and
the
platform
of
the
future.
C
Talk
that
Brandon
and
I
are
giving
with
Steve
watt
3:30
on
Tuesday
will
kind
of
go
into
some
of
the
deeper
details
of
the
trends
here:
container
Linux
and
Red
Hat
Enterprise
Linux.
The
road
ahead
will
give
will
talk
about
what
the
story
is
for
the
operating
system
pieces
that
Brandon
alluded
to,
and
the
OpenShift
roadmap
on
Wednesday
is
always
a
perennial
favorite.
So
we're
kind
of
at
the
end
of
the
prepared,
stuff
and
Joe
was
gonna,
come
and
join
us.
D
So
hi
everybody,
I'm,
Joe,
Fernandez
I,
run
the
product
management
team
myself
and
Mike
Barratt
will
be
running
around
with
mics.
So
as
yet.
If
we
have
time
for
questions
after
each
session
just
raise
your
hand,
I
do
have
a
couple
of
questions
to
help
clarify
things
for
the
audience.
So
Brandon
you
showed
the
tectonic
console
and
I
know.
One
of
the
things
we've
been
doing
is
bringing
that,
together
with
the
existing
open
shift
console.
B
So
the
tectonic
console
really
the
focus
of
that
was
people
who
are
administrating,
kubernetes
objects,
and
so
that
meant
people
who
were
carrying
about
deployments
we're
carrying
about
application
monitoring
we're
carrying
about
the
cluster
settings.
We
went
in
like
identity
upgrades
role,
based
access
control
for
a
cluster
level,
and
so
that's
been
kind
of
the
focus
of
that
which
to
go
to
this
idea
that
a
lot
of
these
ideas
are
complementary.
C
I
think
you'll
see
some.
You
know
art
our
story
is
always
gonna,
be
we're
trying
to
make
sure
that
if
you
fit
a
role
on
the
platform
that
there's
an
experience
that
works
really
well
for
you
and
so
I
think
you
know
as
we'll
talk
about
in
some
of
the
sessions
coming
up
those
two
users
where
they
blend
you'll,
actually
be
able
to
see
those
pieces
coming
together
and
where
there's
a
there's
value
in
focusing
on
one
of
those,
we'll
have
a
really
strong
experience
around
that
particular
user.
Like
a
cluster
admin,
yeah.
D
And
at
the
open
ship
roadmap
session,
Mike
Barrett's
leading
that
you'll
be
able
to
actually
see
a
video
of
a
demo
of
how
these
things
are
already
coming
together.
So
we
have
actually
mocks
where
the
consoles
are
now
converged.
It'll
be
tied
to
your
rolls.
So
if
you
log
into
OpenShift
as
a
user
you'll
as
a
developer,
say
you'll
see
the
open,
shipped
console
the
Service
Catalog
and
be
able
to
act
as
a
user.
D
If
you
log
in
as
an
administrator
you'll,
get
to
see
the
users
view,
but
then
you'll
get
to
see
all
of
the
administration
views
that
that
Brandon
showed
so
state
of
your
cluster
state
of
the
services
and
stuff,
the
things
that
a
cluster
admin
should
have
access
to,
and
so
it
should
be
seamless
just
based
on
how
you
log
in
the
other
question
I
get
a
lot
is
about
operator
framework
and
service
operators.
Last
year,
we're
spending
a
lot
of
time
talking
about
the
service
catalog
in
service
brokers.
D
D
And
to
make
one
more
plug
tomorrow
afternoon,
there'll
be
a
Red
Hat
keynote
that
also
features
some
of
our
partners
like
Microsoft
and
IBM,
will
actually
be
doing
a
demo
of
the
operator
framework
with
one
of
our
ISV
partners,
which
is
Couchbase,
and
you
know
kind
of
to
echo
what
these
guys
said.
You
know
the
service
catalog
is
about
end-users,
consuming
those
services
and
for
those
folks
who
are
have
used
it.
You
know
that
there's
provision
and
bind
operations
to
make
that
seamless.
It
also
deals
with
on
platform
services,
as
well
as
off
platform
services.
D
So
last
year
we
did
a
demonstrate
demonstration
with
Amazon
and
then
at
AWS
reinvent,
we
launched
an
Amazon
Service
Catalog,
where
you
could
bind
in
provision
provision
and
bind
to
Amazon
services
from
OpenShift
itself.
But
what
you'll
see
tomorrow
in
the
keynote
is,
you
know
answering
this
question
of
when
you're
running
a
platform
service
on
the
platform
who
operates
it
for
you
right.
D
The
developer,
who
wants
to
consume
Couchbase
is
not
the
DBA
who
needs
to
run
it
right
and,
and
you
know
at
the
end
of
day,
we
need
to
be
able
to
automate
the
operations
of
the
services
or
of
the
apps,
not
just
automate
the
operations
of
the
platform.
So
so,
please
try
to
attend
that
keynote
and
you'll
see
I
think
a
pretty
cool
demo
of
how
this
all
comes
together.
So
how
are
we
doing
on
time?
You're.