►
From YouTube: OpenShift Commons Gathering Seattle 2016: Emerging Technology Trends with Chris Wright & Matt Hicks
Description
OpenShift Commons Gathering in Seattle on Nov 7, 2016 Keynote by Matt Hicks and Chris Wright (Red Hat) on emerging technology trends and challenges and how Red Hat's Full Stack Strategy solves them and enables continuous innovation.
A
B
Thank
you
guys.
Thank
you
guys
very
much
so
I'm
Matt,
Hicks
I
have
been
working
on
openshift
for
a
while
now,
so
why
don't
you
take
a
quick
poll
just
to
understand
how
long
how
much
experience
people
have
with
it
so
raise
your
hands
if
you
fall
in
the
group,
I'll
keep
making
it
progressively
tougher,
take
your
hands
down
John,
so
how
many
people
have
worked
with
open
shift
for
at
least
six
months?
Raise
your
hand?
Okay,
that's
good!
That's
a
good
premise
that
what
about
one
year
on
two
years,
three
years,
that's
good!
B
Yeah!
That's
right,
and
these
guys
are
cheating
so
we're
getting
close
to
six
years
now,
since
when
we
started
open
shift
and
it's
pretty
crazy
going
back
to
what
we
were
thinking
of
six
years
ago
to
standing
here
in
front
of
this
room
and
sing
all
of
the
momentum,
the
different
organizations
what's
happening
in
the
industry.
So
I
really
appreciate
that.
I
want
to
say
thanks
on
behalf
of
especially
the
red
hat
team,
but
as
well
as
a
lot
other
people
working
with
these
technologies,
because
it's
a
it's
an
exciting
time.
B
So,
given
that
what
Chris
and
I
were
going
to
talk
with
you
about
was
the
why
this
is
an
exciting
time,
we
both
have
the
opportunity
to
get
to
talk
to
hundreds
of
customers
in
various
states-
large
ones,
small
ones.
So
we
broke
down
the
trends
that
we
see
happening
both
the
technology
trends,
some
of
the
challenges
that
people
are
having
we're
all
excited
about
this
technology,
but
not
everyone
is
able
to
apply
it
right
now.
Why
is
that
the
case?
There
was
a
note
to
the
elections.
B
I
will
be
the
depressing
part
of
this,
and
then
Chris
will
bring
you
up
at
the
end
of
the
conversation,
talk
about
how
we
as
Red
Hat,
think
about
this.
What
we
see,
what
we're
focusing
on
to
solve
the
problems,
but,
let's
start
with
this
most
of
us
I
think
are
here.
I
T
is
just
a
means
to
an
end,
we're
trying
to
build
that
application
for
our
business
or
for
ourselves
or
for
our
company,
and
something
that
is
it's
pretty
unique
in
the
last
couple
of
years.
B
Is
that
the
next
generation
of
these
applications
that
are
going
to
win,
they
have
to
utilize
dynamic
infrastructure?
No
long
can
we
sort
of
have
a
great
idea
and
build
an
app,
and
that's
going
to
be
all
we
need,
because
user
expectations
of
these
apps
scaling
never
going
down
being
able
to
be
borderline
like
artificial
intelligence,
with
recommendations.
Those
things
are
at
a
flawless
expectation.
B
We
joke
sometimes
like
Google
search,
never
goes
down,
but
that
is
the
user
expectation
for
everything
these
days
and
it
requires
this
combination
of
both
the
applications
as
well
as
the
infrastructure.
Now
this
has
really
been
driven
by
three
technology
trends
that
we've
seen
application.
Architectures
are
changing
quite
a
bit.
Those
of
us
have
been
in
the
field
for
a
while,
we've
probably
built
our
monolithic
like
pl/sql
applications
or
our
massive,
like
single
instance,
jsb
applications,
but
that's
been
slowly
breaking
up
into
more
componentized
use.
B
Call
microservices
today
same
things
been
happening
on
the
development
process.
We
used
to
plan
everything
up
front.
We
know
our
accuracy
rates
with
that
waterfall
they
weren't
great
and
we're
trying
to
adjust
those
to
get
more
towards
dynamic
and
agile
processes,
and
then
application
infrastructure
has
changed
quite
a
bit
as
well
from
monolithic
proprietary
stacks
to
on-demand
cloud-based
infrastructure.
So
these
are
pretty
big
trends.
B
We
all
know
about
them
and
one
of
the
things
that
is
starting
to
link
and
amplify
these
as
containers
because
container
sits
in
the
middle
and
it
really
starts
influencing
all
three
of
these.
And
how
do
you
how
you
would
use
them
now?
One
of
the
challenges
we
have
structurally
with
this
is
cool
stuff
like.
Why
aren't
we
all
using
it
is
that
when
we
look
at
how
IT
has
grown
up
most
companies,
it's
really
in
two
separate
world.
So
we
have
an
operational
side
of
the
world
that
carries.
B
Pagers
keeps
things
running,
we
have
a
development
side
of
the
world
and
maybe
they
meet
at
our
CIO,
and
maybe
they
don't
and
this
the
problem
with
it
is
that
it's
worked
really
really
well
for
a
long
time.
You
think
they
like
the
history
of
IT.
You
build
muscle
memory
round
things
that
work.
This
is
a
pattern
that,
for
20
years,
has
arguably
worked
well
now.
This
pattern
is
starting
to
fundamentally
break
down
because
of
our
users
or
user
bases.
B
More
diverse,
it's
more
volatile,
diverse
in
terms
of
clients
how
they're
going
to
access
things,
geography
volatile
in
terms
of
five
years
ago,
the
chances
of
launching
a
great
app
and
having
20
million
users
show
up
in
the
first
week
generally
not
possible.
It
just
wasn't
going
to
happen.
Maybe
it
would
happen
to
like
point
one
percent:
that's
a
reality
for
apps
at
launch
day,
if
you
hit
that
good
idea,
that
is,
the
user
base,
you'll
have
I
think
even
a
Pokemon
go
probably
come
up.
B
That
was
roughly
like
their
first
week,
adoption
that
they
had
come
in.
So
this
means
this
separation
across
our
groups.
It
doesn't
work
anymore.
This
is
one
of
the
structural
things.
I
think
we
have
to
look
at
connecting
these
now
to
compete,
going
forward
both
development
and
operation
alignment
as
well
as
applications
and
infrastructure.
These
are
a
key
area
that
we're
going
to
have
to
balance
cross.
So
if
you
take
a
step
back,
it's
pretty
obvious
right,
it's
like
well,
we
have
to
use
both
groups,
we
have
to
use
their
talents.
B
What
actually
is
getting
in
the
way
like
we're
excited
about
the
technology.
We
know
there
are
things
we
could
apply
and
use
with
it.
What
keeps
companies
from
actually
applying
this
earlier,
and
so
we
broke
this
down
to
three
areas
again:
I'm
the
problem
guy
and
then
we'll
bring
up
Chris
to
talk
about
what
we
are
doing
so
the
first
problem
infrastructure,
more
likely
than
not
is
viewed
as
limiting
your
apps,
which
is
a
little
crazy.
You
think
about
it
like
if
you
own
infrastructure,
you
own
servers
already
racked
they're
accessible.
B
B
Expectations
for
resources
have
changed,
so
that
means
like
you're
on
the
operational
side,
what
you
built
your
infrastructure
for
is
probably
what
not
what
apps
need
today.
This
creates
a
challenge
in
terms
of
that
that
asset
or
what
should
be
that
asset,
might
not
be
that
well
applied
to
your
applications.
The
second
challenge
that
we've
seen
talking
to
companies
is
that
if
we
picked
one
area
where
there
is
almost
ubiquitous
investment
on
the
operational
side,
it's
with
virtualization
phenomenal
technology
lets
us
take.
B
You
know
big
iron
servers
and
carve
them
up
into
smaller
pieces
that
changes
the
supply
side
of
operations.
They
can
provide
more
virtual
machines,
it
never
really
cracked
into
the
demand
side
of
developers.
There
was
a
select
group
that
knew
how
to
take
these
machines
and
use
them
better,
but
it
didn't
hit
the
mainstream
developers.
So
those
two
things
leave
us
at
odds
of
the
infrastructure
we
have
and
what
that
infrastructure
needs
to
do.
So
that's
the
infrastructure
problem.
The
second
problem
we
hit
is
that
operations
teams
just
curious.
B
How
many
people
here
in
the
room
raise
your
hands.
If
you
would
consider
yourself
on
the
operations
side
of
the
house?
Okay,
that's
cool!
That
I
have
carried
a
pager
before
so
I
speak
with
some
empathy
of
if
you're,
on
the
operations
side.
Your
world
is
pretty
challenge
right
now,
and
one
of
the
reasons
is
that
companies
of
about
any
size
have
a
span
across
these
environments.
B
Physical
environments,
dare
I
say
even
like
mainframes
are
out
there
and
more
companies
and
not
virtual
environments,
private
cloud
environments,
public
cloud
environments
and
then
some
of
us
actually
said
you
know
what
the
public
cloud
will
save
us
all
like
we're
going
to
move
everything
there
in
life's
going
to
be
good,
even
the
companies.
We
know
that
it
push
very
hard
in
terms
of
how
much
they
can
move
their
end
up
being
multi-vendor
in
public
clouds.
B
So
what
your
life
is
an
operations
person
looks
like
is,
the
span
of
environments
is
not
going
away,
and
so
you
need
a
way
to
operate
in
this
space
so
that
you
have
an
abstraction
point.
You
can
apply
something
to
all
of
these,
so
that
you
can
actually
free
up
that
time
to
start
investing
in
new
technologies.
So
this
is.
The
second
challenge
is
just
the
operational
complexity
is
killing
us.
The
third
challenge
we
go
through
is
scaling
development,
so
it's
exciting,
I'm
a
technologist.
B
This
becomes
pretty
challenging
clustering,
I,
always
love
to
use
as
an
example,
because
clusterings
take
jboss
use
something
like
J
groups.
It's
worked
forever
as
well
as
far
as
you're
considered
as
a
developer.
Then
you
move
to
the
public
cloud
and
it
doesn't
work
anymore
and
you
have
to
learn
like
well.
It's
dependent
on
this
thing
called
multicast
you're,
not
a
networking
guy,
and
you
have
to
dig
in
and
figure
out
what
that
means.
But
it's
different.
It's
changed!
B
That's
not
available
to
you
anymore
and
I
like
to
use
the
analogy
of
fewer
a
carpenter
like
I,
like
woodworking.
You
spend
a
lot
of
time
like
learning
how
your
saw
works
and
your
hammer.
So
you
don't
hit
your
thumb.
Imagine
if
every
house
you
walked
into
your
tools,
worked
differently.
That's
sort
of
the
modern
day
challenge
as
a
developer
every
place
your
operations
team
puts
the
app
it's
going
to
work
subtly
different.
Your
operations
teams
are
struggling
with
actually
understanding
all
of
this.
B
They
certainly
know
what
multicast
is,
but
they
don't
have
the
time
to
explain
it
to
you
as
a
developer.
You
have
to
dig
in
layers
and
layers
and
layers
deeper
when
you
just
wanted
clustering
to
work,
so
that
becomes
a
big
challenge
in
terms
of
how
we
scale
up
to
large
development
teams,
whether
you're,
a
startup
trying
to
go
from
10
to
20
people
or
whether
you're
a
fortunate
in
enterprise
going
from
10,000
20,000.
B
So
these
are
the
challenges,
but
I
think
more
excited
is
how
do
we
get
past
them
because
been
in
the
space
for
a
long
time
and
I
think
this
is
the
best
point
in
time
where
I've
actually
seen
technology
solutions.
That
I
think
will
make
a
huge
dent
in
these
challenges
going
forward.
So
with
that
I
want
to
introduce
Chris
right
and
Chris
will
do
the
more
uplifting
side
of
how
we're
going
to
solve
all
these
Chris.
C
The
next
wave
of
I
guess
innovation
or
evolution
of
the
IT
space.
So
let's
take
a
look
at
some
of
the
technologies
involved
and-
and
this
is
a
kind
of
a
red
hat
view
of
the
world.
So
if
you
look
at
the
base,
it's
all
grounded
in
Linux,
and
this
is
something
that,
as
a
as
a
long
time,
Linux
person.
Of
course
we're
excited
about
Linux
is
found
yet
another
way
to
really
make
a
huge
impact
on
the
industry.
As
you
go
up
through
this
stack,
you
see
in
the
middle.
C
We
have
open
shift
so
today
we're
here
all
about
open
shift
and
it's
that
that
open
shift
component
that
brings
the
different
technologies
together
and
then
at
the
top
you're,
still
seeing
that
same
core
Linux
exposed
to
applications.
So
what
we're
seeing
here
is
for
the
first
time
we
have
all
the
technology
pieces
that
brings
together
the
different
constituents.
We've
got
developers
that
are
trying
to
just
get
real
work
done
and
and
write
code
and
put
services
in
into
production.
C
We
have
a
bunch
of
subject
matter:
experts
that
are
helping
kind
of
scale,
those
development,
those
developer
populations,
and
we
have
operations
teams
that
now
have
a
set
of
tools
where
we
can.
We
can
combine
our
efforts
and
communicate
through
the
tools.
So
let's
dig
in
a
little
bit
to
that.
The
first
challenge
we
had
was:
how
can
we
overcome
infrastructure
limiting
our
apps?
C
This
one's
obvious
containers,
containers,
containers
right,
we're
all
excited
about
containers,
there's
only
one
answer:
it
doesn't
matter
what
the
question
is:
it's
containers,
but
there's
a
reason
for
that
and
I
think.
The
reason
is,
we've
spent
a
lot
of
time,
trying
to
figure
out
how
we
build
applications
and
put
applications
into
it.
C
A
runtime
environment
and
containers
has
have
given
us
an
awesome,
basic
building
block
that
building
block
is
both
lightweight
and
it
captures
the
essence
of
the
application,
its
immediate
dependencies,
without
kind
of
carrying
on
the
baggage
of
everything
else
in
your
infrastructure
and
dragging
it
down
from
the
developer
side
down
into
the
to
the
operations
teams.
So
containers
is
really
a
critical
piece,
and
it's
this
notion
that
with
containers
we
can
connect
the
application
to
the
infrastructure
in
an
intelligent
way.
C
So,
in
the
past
it
sort
of
been
developers,
writing
the
apps
and
throw
it
over
the
wall,
and
it
becomes
an
Operations
challenge
of
how
do
you
figure
out
how
to
put
this
app
into
production?
How
to
match
it
to
the
infrastructure
that
you've
built
in
theory
as
Matt,
was
highlighted
earlier,
to
support
the
applications
and
and
if
we
have
an
impedance
mismatch
there.
C
With
the
exception
of
this
slide,
containers
create
consistency,
so
we
were
looking
at
this
earlier
and
Matt
so
else
java.
The
java
problem
java
is
the
one
the
one
outlier
here,
but
but
the
the
concept
here
is
with
a
container.
You
can
build
common
images,
so
you
can
leverage
some
of
your
subject
matter.
Experts
who
really
understand
the
guts
of
the
runtime,
that's
important
to
your
application.
Those
images
can
be
moved
around
across
all
the
different
footprints
that
we've
talked
about
and
made
made
accessible
to
your
developer
population.
C
So
you
create
consistency
in
the
runtime
environment
because
you're
isolating
the
application,
its
immediate
runtime
from
the
underlying
infrastructure
and
you're,
allowing
a
set
of
experts
to
really
focus
their
their
expertise
in
a
space.
That's
not
accessible
to
the
entire
developer
population,
and
it's
it's
this
kind
of
container
and
container
platform
that
is
creating
this
new
opportunity
for
us
and
that's
connecting
the
operations
teams
and
the
developer
teams
through
a
platform
through
kind
of
a
communication
mechanism
that
allows
developers
to
express
their
needs
to
the
Ops
teams
in
ways
that
actually
make
sense.
C
C
How
do
you
write
your
application
to
express
your
resource
requirements
and
connectivity
requirements
across
across
this
infrastructure
that
we've
been
building
for
a
long
time
and
never
quite
figured
out
how
to
give
the
right
level
of
API
as
an
abstraction
to
allow
developers
to
to
take
a
more
active
role
in
the
application
deployment
phase?
And
you
hear
a
lot
about
micro
services,
and
then
you
hear
this
kind
of
argument
back
and
forth
in
the
industry
of
they're,
not
really
new,
service-oriented
architectures
been
around
for
a
long
time.
C
If
you
go
back
before
we've
had
object-oriented
programming,
we've
had
this
promise
for
decades
of
somebody
somewhere
is
going
to
write
something,
and
somebody
else
is
going
to
reuse
that
and
it
turns
out
that
we've
failed
and
that
in
that
ability
to
express
kind
of
a
high
level
abstraction,
that's
easily
reusable.
So
we
have
object,
oriented
programs
and
there's
some
reuse
within
a
single
program.
C
We
have
service-oriented
architectures
into
a
degree
we've
been
able
to
leverage
reuse
of
those
services
here,
we're
really
just
refining
our
view
on
how
do
we
implement
independent
services
that
are
reusable
and
one
of
the
things
that
I
think
is
is
really
a
sort
of
a
powerful
display
of
this
working
I
was
just
recently
talking
to
a
bank
in
asia-pacific
and
two
things
that
were
impressive
to
me.
This
Bank
went
from
concept
to
production
with
an
application
in
six
months.
C
This
is
a
container
based
application,
microservices
based
application
container
to
production
in
six
months
and
in
my
experience,
working
with
banks,
sorry
not
container
to
production
concept
to
production
and
my
experience
working
with
banks.
It's
usually
concept
to
the
first
exhaustive
hundred
page
document
takes
about
six
months,
and
so
here
they
wrote
the
entire
application
deployed.
C
It
took
that
technology
in
a
different
group
and
reuse,
some
of
the
components
that
the
initial
group
had
built
and
that,
if
that's
not
what
we're
trying
to
achieve
here,
I'm
not
sure
what
is,
and
that
to
me
was
really
impressive
from
an
organization
whose
typically
not
capable
of
moving
this
quickly
and
creating
code.
Reuse.
C
Just
looking
at
how
we've
historically
allocated
services
to
infrastructure
as
we
provide
better
tooling
and
use
a
container
and
use
a
language
to
describe
how
an
application
fits
together,
we
can
make
better
use
of
those
resources.
So
we're
not
confining
a
single
application
to
a
single
server
or
single
VM
and
hoping
that
somehow
that
service
that's
trapped
in
there
is
reusable
because
there's
actually
a
lot
more
information
in
that
VM
or
even
better
metal
server
than
just
a
single
application
or
a
single
service
in
an
application.
C
So
how
do
we
keep
pace
and
how?
How
can
we
really
allow
the
operations
teams
to
work
efficiently
in
an
environment
where
everything
is
changing,
all
the
time
and
I
think
the
most
important
piece
here
is
providing
consistency.
So
if
you
look
at
all
of
the
deployment
environments
on
the
right
hand,
side
it's,
it's
varied
its
internal
bare
metal.
It's
your
virtualization,
which
in
many
enterprises
that's
not
an
open
source
tool.
That's
doing
the
virtualization,
it's
VMware!
If
private
clouds
on
Prem
you
have
public
clouds
off
Prem.
C
Just
building
from
some
common
building
block
like
Linux,
is
really
a
huge
step
forward
in
in
creating
operational
efficiency
and
we're
taking
that
concept
here
and
just
moving
it
to
the
next
level.
So
we'll
talk
a
little
bit
more
about
how
a
container
applica
container
platform
or
a
pass
platform
creates
that
same
kind
of
consistency
for
applications
across
all
these
footprints,
but
really
it's.
How
do
you
create
efficiency
for
the
operations
team,
its
consistency?
And,
finally,
everything
is
moving
so
quickly.
C
I
have
a
lot
of
developers
and
how
can
I
enable
my
developers
to
scale
and
really
provide
the
business
impact?
That's
driving
all
this
I
mean
we're
not
building
infrastructure
just
for
fun,
we're
building
it
to
run
apps
we're
not
even
building
apps
just
for
fun,
building
apps
to
run
businesses
and
more
and
more
businesses
are
fundamentally
about
the
software
that
they're
creating.
So
how
do
you
really
stoke
that
fire
see
a
similar
picture
here?
C
Where
now
we
have
a
platform
layer,
abstraction
for
providing
developers
a
way
to
interact
with
all
of
those
different
infrastructures,
so
they
can
really
focus
on
building
the
applications
and
combining
the
different
services
into
an
aggregate
application.
Rather
than
trying
to
dig
down
into
those
details
of.
Do
you
know
what
multicast
is?
Should
you
even
care
as
an
application
developer
when
you're
trying
to
just
get
your
app
to
cluster
and
that
clustering
could
be
functional
in
one
environment
in
house
using
multicast?
C
It
could
be
X
in
your
private
cloud
using
something
like
kerber
Nettie's
ping,
to
discover
a
component
of
service
in
your
application,
or
maybe
running
in
a
in
a
public
cloud
you're
using
some
dns
mechanism
to
update
dns
when
you
have
service
components
coming
and
going,
and
that
is
something
that
requires
some
operational
expertise
that
is
just
burden
to
a
developer.
It's
not
really
the
developers
core
competency
or
really
interest
where
that
that
developers
focus
is
on
building
code
and
helping
the
company
differentiate
itself
in
whatever
market
segment.
C
It's
in
so
this
platform,
subtraction,
creates
this
consistency
for
the
IT
side
that
we
talked
about
analogous
to
Linux
and
creates
an
abstract
for
developers
to
work
with,
so
they
can
focus
on
their
real
job.
And
then
you
have
organizations
who
are
growing
and
scaling
and
with
a
large
number
of
developers
the
chances
are
there's
a
relatively
small
number
of
those
developers
that
have
expertise
in
a
key
area.
C
So
let's
bring
those
subject
matter,
experts
to
the
forefront
to
help
us
understand
key
pattern,
so
they're
going
to
be
the
in
the
best
position
to
inform
your
average
developer
in
your
enterprise.
What
the
best
mechanism
is
to
ensure
your
service
level
agreement
is
met
based
on
a
deployment
model
of.
Do
I
do
a
canary
deployment
or
a
Bluegreen
deployment?
How
do
I
ensure
that
I'm
introducing
change
and
and
not
taking
a
hit
against
my
SLA?
C
C
So
this
is
what
we
think
of
as
the
new
foundation
for
continuous
innovation.
You
know
we
have
a
notion
here
that
the
world
is,
it
is
speeding
up,
and
it's
not
really
going
to
plateau
I
mean
it's
just
really
accelerating
and
part
of
it
is
because
we're
giving
tools
to
people
so
that
you
can
automate
things
and
focus
your
energy
on
innovating
and
bringing
new
ideas.
So
this
kind
of
platform
is
what's
critical
to
bringing
innovation
to
the
forefront,
and
this
is
a
very
red
hat,
centric
view
of
the
world.
C
We
work
with
our
community
partners
and
ecosystem
to
really
broaden
this
to
what
we
are
excited
about
as
a
major
change
in
the
industry,
so
from
the
low
level
infrastructure
from
the
bottom
of
the
stack
all
the
way
up
to
the
top
of
the
stack.
This
is
a
space
where
we're
we're
working
together,
both
our
internal
developers
and
our
community
members
to
build
out
this
platform
and
focusing
both
on
the
operations
teams,
where
the
infrastructure
portion
of
red
hats,
developer
focus
has
been.
C
You
know,
therefore,
really
a
couple
of
decades
at
this
point
up
through
the
application
layer
which
we've
really
brought
two
too
I
think
a
new
space
with
with
open
shift
where
we
can
combine
different
middleware
components
and
and
see
icd
kind
of
pipeline
modern
thinking
around
how
you
build
and
develop
software
all
together
with
with
a
single
stack.
So
again,
this
is
that
picture
that
we
started
with.
This
is
how
we're
bringing
together
all
the
key
stakeholders.
B
So
one
of
the
things
we
have
been
very
passionate
about
since
we
started
was
we
don't
just
want
to
be
able
to
tackle
that
new
applications?
We
want
to
make
sure
that
we
can
run
that,
like
eighty
or
ninety
percent
of
what
you
have,
we
have
some
customers.
One
customer
I
blows
my
mind
that
they're
successful
this.
They
moved
over
a
thousand
applications
on
to
the
platform,
and
these
are
not
like
exciting
new
applications.
These
are
lift
and
shift
and
run
them
now.
B
What
comes
with
that
is
you're
not
going
to
like
pick
up
an
EE
application.
That's
written
seven
years
ago,
drop
in
an
open
ship
and
then
like
magic
happens,
you're
dynamically
scaling,
but
what
you
are
doing
is
chris,
I
think,
articulate
well
is
an
operation
steam
you're
building
some
primitives
they're
like
you're,
going
to
keep
a
core
fabric
running,
and
your
dev
teams
can
now
say
like
hey,
you
move
my
eee
app
over
here
and
I
can't
actually
do
a
deployment
without
taking
down
time.
That's!
B
Okay,
like
that's
the
life
you
live
in,
you
get
an
idle
change
request.
You
can
make
changes
every
three
months
like
that's
where
most
companies
live,
but
if
you
put
in
a
little
investment
now
on
this
platform,
if
you
can
cluster,
you
can
scale,
maybe
now
you
can
get
to
a
canary
deploy,
and
so
we've
seen,
customers
lift
and
shift
literally
thousands
of
apps
and
then
start
applying
patterns,
because
now
it
actually
makes
sense
to
put
a
little
investment
in
that
app.
And
now
my
change
windows
I
can't
do
it
once
every
three
months.
B
B
If
we
are
not
letting
you
move
the
vast
majority
of
your
applications
into
the
platform,
we
are
doing
something
wrong
in
it
won't
fit
everything
don't
come
back
to
like
Oracle
e-business
suite
you
want
to
pick
up
and
drop
it
in,
but
but
I
think
you
know
broad
swath
is
spaced.
It
really
really
is
a
good
candidate.
His
great
question:
do
you
want
to
talk
about
the
data
cider
sure.
C
And
I
totally
agree:
we
we
talked
to
a
lot
of
customers
and
we
can't
abandon
today.
Net
new
is
a
insignificant
fraction
of
what
a
large
enterprise
is
doing.
So
we
cannot
abandon
that,
and
we
also
have
to
realize
that
there
may
be
components
that
never
fit
naturally
into
a
container
platform,
but
services
immediately
around
those.
C
On
the
on
the
data
side,
there
was
some
some
data
shown
at
the
cloud
native
day,
the
end
of
cloud
con
in
Toronto,
which
showed
adoption
rates
of
container
containers
in
the
enterprise
in
the
kind
of
teen
percentage
rate
and
which
was
which
you
know
face
value
compared
to
how
much
we
hear
about
it
feels
low.
If
you
looked
a
year
ago,
it
was
half
that
so
what
you're
really
seeing
is
it's
very
early
days
and
it's
its
accelerated
growth
and
in
a
red
hat
perspective
we
see
kind
of
similar
numbers.
C
So
it's
you
know
it's
good
to
see
it
from
a
more
kind
of
agnostic
industry
view,
but
early
days,
there's
no
doubt
that
it's
it's
kind
of
up
into
the
right
and
I
think
part
of
that
is.
It's
been.
Containers
and
container
technology
have
been
really
successful
in
the
new
application
space,
and
so
helping
enterprises
understand
where
we
can
bridge
the
gap
between
the
traditional
applications
and
the
next-gen
applications
is
going
to
be
critical
to
helping
at
least
a
mass
wide-scale
enterprise.
Adoption
for
containers
and.
B
B
Okay,
I
see
well
so
those
two
hands
in
the
back
there,
at
least
that
if
you
have
raised
your
in
its
high,
so
people
can
see
any
data
questions
you
guys
have
whether
it's
from
like
data
storage
options
we
have
on
Cooper
net
is
to
like.
Can
you
run
spark
analytics
on
it?
Ask
those
two
guys,
so
it
will
fail
the
tough
questions
test.
They
will
not
so.
D
D
B
Yeah
sure
so
the
question
was
basically
the
is
the
cluster
type
technology
we
talked
about
today.
Is
that
basically
becoming
the
new
OS
or
the
new
computer
that
people
talk
to?
You
know
I
think
real,
quick
from
my
perspective,
a
lot
of
times
like
computers?
Are
things
we'll
talk
to
about
the
in
our
the
interfaces
that
people
are
used
to
working
with
whether
it
was
G,
Lib
C
back
in
the
day
for
see
developers
and
I?
Think
for
a
majority
of
developers?
B
If
we
do
things
right
in
these
communities,
these
will
become
the
new
interfaces
that
they're
used
to
interacting
to
it's.
What
you
will
build
your
applications
to
as
an
Operations
team
member,
it's
what
you
will
be
building
infrastructure
to
serve
and
I
do
think
the
cluster
nature
of
it
is
really
critical
because
of
that
introduction,
it's
like
you
have
building
applications
that
can
only
scale
to
a
single
box.
B
C
Mean
for
a
while
Google
had
a
bumper
sticker
type
thing.
That
said,
my
other
computer
is
a
data
center.
It
is
definitely
part
of
our
modern
environment,
where
you
have
really
spiky
loads,
unpredictable
response
to
application.
You
know
application
development
essentially
and
then
I
I
do
like
to
paint
a
picture
where
the
you
have.
E
My
question
is
the
right:
now,
with
our
company.
We
have
basically
basically
two
factions
in
our
development
teams,
won
its
pro
container
and
trying
and
working
towards
doing
that,
and
one
that's
kind
of
a
old
school.
You
know
with
the
speed
of
deployment
of
VPS
and
whatnot
100.
You
know
it's
like
why
I
don't
want
to
use
containers,
then
they
will
generate
a
bunch
of
the
reasons
why
what
would
you
say
was
well.
E
D
E
The
anti
container
the
anti
container
is
a
split
group
of
the
the
experience
will
go
with
the
experience
gentleman
term
and
the
some
of
the
newer,
their
facto
one
guy.
That
I
have
in
particular
he's
really
about
like
let's
launch
a
bunch
of
VPS
is
with
Erlang
and
we'll
just
use
their
engine.
So
we're.
B
I
would
say
you
know
one
approach
might
be
for
the
group
that
if
it's
do
they
really
not
want
to
use
it,
or
do
they
just
not
want
to
have
to
learn
it,
and
if
it's
the
I,
don't
want
to
have
to
learn
it,
but
I'm
fine,
utilizing
it
I'm
sourced
image
and
those
abstractions
to
keep
them
where
they're
comfortable,
but
still
be
able
to
apply
a
common
technologies,
pretty
good
those
that
want
to
learn
it.
We
never
try
to
put
up
barriers.
You
know
it's
a
think.
B
C
The
other
thing
is
I
think
it's
important
to
know
the
limitations
of
technology
and
not
oversell.
So
just
because
you
could
containerized
something
doesn't
mean,
that's
always
the
right
answer
and
you'll
build
a
lot
of
credibility
with
the
naysayers.
If
you
can
talk
them
through
some
of
the
benefits
and
maybe
acknowledged
in
a
certain
situation,
it's
not
the
right
tool
for
the
job
and
there's
an
that's
okay,
we're
not
trying
to
reinvent
the
entire
world.
Containerized
I
mean
maybe
some
are
but
there's
there's.
C
It
really
are
a
spectrum
of
tools
for
the
job
and
the
better.
We
can
understand
each
other
and
know
what
the
limitations
are.
We
can
really
put
containers
in
the
part
of
the
org
that
really
makes
sense
and
I
mean
the
VPS
case
feels
like
it
could
make
sense,
but
I'm
sure
there's
a
bunch
of
details
in
there
that
having
a
real
direct
dialogue
or
meaningful
technology-based
dialogue,
I
think
without
pixie
dust
and
hype
helps
look.
C
A
Work
for
red
hat
is
so
I
cover
the
public
sector,
a
lot
of
federal
agencies
that
are
adopting
container
technologies.
Usually,
when
I
get
that
question,
it's
usually
from
operations
and
I
think
you
know
one
of
the
things
that
people
don't
talk
about
is
all
the
benefits
for
operations
with
containers
and
my
background.
I
came
from
Department
of
Defense
and
I
worked
for
doing.
R&Amp;D
and
I
worked
in
operations,
and
you
know
when
something
blows
up
on
a
Sunday
in
your.
Your
cell
phone
starts
going
off
your
pager.
A
If
you're
in
operations
you
go
in
you
have
to,
if
you're
on
a
vm,
you
have
to
figure
out
what
the
old
version
of
the
application
was.
You
have
to
undo
all
the
middleware
steps.
You
know
undo
any
configuration
changes
that
were
done
to
the
guest
OS
or
the
middleware.
You
know
it
can
be
a
really
cumbersome
process.
So
when
you're
using
containers,
you
know
roll
back
to
the
old
version
and
you
have
that
immutable
image.
A
I
mean
I
think
that's
really
big
for
four
operations
aspect
and
then
you
know
there's
a
lot
of
visibility
for
operations
that
you
also
get
with
containers
so
you're,
knowing
how
different
services
are
all
linked
together.
You
know
as
operations,
you
don't
really
know
or
have
that
visibility
in
the
traditional.
You
know
vm
worlds.
You
know
java
developers
just
deploying
wars
or
something
out
to
tomcat.
You
know
you
don't
lean,
oh,
how
all
those
pieces
are
connected
together,
but
when
you
use
a
container
platform,
you
have
more
visibility
into
it.
A
You
know
exactly
what
ports
are
listening.
You
know
exactly.
You
know
what
services
are
talking
to
each
other,
so
you
know
going
going
down
those
types
of
things
with
operations.
I
think
you
know
helping
them
see
the
benefits.
How
can
we
help
make
their
life
easier?
Is
is
really
helpful
as
well.
It's.