►
Description
From the March 28th 2017 OpenShift Commons Gathering in Berlin @KubeCon https://Commons.openshift.org/Gathering
A
A
We
started
realizing
that
the
the
kernel
of
the
containers
that
we
had
framed
up
for
ourselves
needed
to
be
more
reproducible
and
more
community-based,
and
so
it
led
us
to
start
investigating
community
containers
and
around
that
time
was
when
dr.
was
getting
off
the
ground
I've
been
around
in
the
open
source
community
for
a
number
of
years.
It's
fun
running
into
people
at
conferences
like
this,
because
we
realized
that
some
of
us
have
contacts
that
we've
been
working
with
each
other
for
ten
or
more
years,
but
in
different
contexts.
A
So
I
want
to
say
it
is.
It
is
fantastic
and
completely
ironic
that
I'm
the
first
person
that
gets
to
command
their
slides
and
have
animations
today,
and
I
have
zero
technical
content
to
cover
in
this
presentation.
You're
going
to
see
lots
of
cat
gifts,
so
containers
as
you've
seen
I
could
go
with
the
longshoremen
analogy
here
and
all
the
fantastic
tools
that
they
have
and
crane
lifts
and
all
this
kind
of
stuff
and
how
to
how
to
pack
containers.
But
it's
still
just
a
box
to
deliver
goods
in
at
the
end
of
the
day.
A
There's
any
number
of
conforming
containers
that
people
use
to
package
goods
deliver
goods
and
see
how
that
they're
actually
going
to
get
used
in
production.
It
really
doesn't
matter
people,
people
you
could
just
as
well
look
at
actual
shipping
containers
and
how
people
are
using
them
and
people
are
using
them
to
build
houses
and
do
all
kinds
of
stuff
where
I'm
sure
the
people
that
are
actually
shipping
goods
from
China
to
San
Francisco,
look
at
a
health
being
built
out
of
shipping
container,
and
you
say:
that's
clever,
that's
not
what
it
was
meant
to
do.
A
That's
clever
and
it's
it's
lettuce
and
a
lot
of
interesting
directions,
and
what
the
last
three
years
have
been
about
is
mostly
seen.
How
are
people
using
these
containers?
I
mean
a
lot
of
the
technology
has
been
there.
It's
either
been
not
approachable
or
there
weren't
enough
patterns
that
had
arisen,
I
mean
LXE
has
been
there,
but
nobody's
really
wanted
to
touch
it
in
a
meaningful
way.
A
So
now
we
have,
we
have
a
lot
of
patterns
and
people
have
done
a
lot
of
interesting
things
with
them.
There's
a
few
years
ago,
Simon
ago,
0
person,
if
anybody's
used
log,
the
LA,
giris,
syrups
ins,
lagos
container,
a
guild,
eng
library,
it's
a
great
logging
library,
Simon
was
giving
a
talk,
and
he
gave
the
example
of
before
I
think
as
the
Queen
of
England
had
ever.
She
had
heard
about
a
walrus
and
she
wanted
to
see
what
a
walrus
was,
and
so
somebody
went
on
the
expedition
and
found
you
know.
A
Gilda
walrus
tanda
hide
brought.
It
brought
back
a
box
of
bones,
and
this
tanned
hide
and
the
people
that
were
reassembling
it
for
the
Queen
in
a
stuffed
manner
had
never
actually
seen
the
live
animal
and
so
what
they
reassemble.
Dhone,
Austria
sover
blown
monster
of
a
creature
and
Simon
was
saying
this
is
pretty
much
what
we're
at
the
phase
we
are
in,
and
he
said
this
two
years
ago
with
containers
that
most
of
us
are
doing
all
kinds
of
things,
and
it's
only
in
a
couple
of
years.
A
From
now,
when
we
start
to
see
what
that
pattern
is,
that's
a
proper
way
to
assemble
it.
How
is
it
going
to
come
together?
There's
lots
of
ways
that
you
can
use
containers,
but
now,
let's
move
the
conversation
up
a
little
bit.
How
are
we
making
it
useful
so,
in
the
container
ecosystem,
particularly
I
mean
we've.
A
We
as
an
industry
have
gone
through
patterns
like
this
and
I'm,
not
saying
the
technology,
but
the
types
of
iterations
over
and
over
whether
it
was
operating
systems,
whether
it
was
virtualization,
whether
it
is
orchestrating
virtualization
with
like
stack
and
so
forth,
and
out
is
this
kind
of
turn
to
keep
refining
the
method.
For
whatever
reason
the
ecosystem
is.
A
Is
the
big
question
now
because
it's
it's
exciting
but
to
some
extent
it's
a
foregone
conclusion
that
a
lot
of
us
is
happening
in
the
open,
so
now
it's
open
source
and
how
companies
that
are
going
to
compete
with
each
other,
how
they're,
working
together
and
in
the
container
community.
That's
for
whatever
reason
led
to
a
lot
of
conversations
in
a
lot
of
trepidation
and
mixed
feelings,
and
so
people
ask
well
what's
what's
happening
in
the
container
ecosystem
and
for
a
lot
of
us,
I
feel
like
I
say
us
developers
involves.
A
Even
if
there
are
higher
level
constructs
that
people
are
worried
about.
So
some
of
the
fights
are
that
people
feel
like,
and
you
know
tit-for-tat.
At
the
end
of
the
day,
it's
actually
us
just
trying
to
figure
out
where
it
is
that
we're
going
and
find
the
common
ground
so
that
we're
not
fighting
fighting
with
ourselves
and
realizing
that
I've
made
a
decision.
You
know
I
invented
it.
A
You
I'm
not
going
to
use
your
stuff
because
you
didn't
invent
it,
and
you
know
you
end
up
fighting
against
yourself
because
of
some
decision
you
made
at
some
point
it's
difficult
because
there's
humans
involved,
and
so
as
soon
as
we
can
move
past,
that
the
conversation
gets
a
lot
easier
yeah,
that's
that's
where
some
people
that
have
been
been
involved.
You
can
ask
I
sympathize
with
this.
A
If
you
don't
sympathize
with
this
good
for
you,
some
of
the
conversations
when
they
go
round
and
round
it
leads
you
to
a
state
of
just
ready
to
ready
to
make
it
boring
like
a
lot
of
the
things
that
people
get
really
hyped
about,
especially
their
laces
over
the
last
few
years.
It's
time
to
move
the
conversation
up
the
next
level-
and
this
is
where
the
last
almost
two
years
but
I'll
say
year
and
a
half
the
conversation
that
I've
been
most
involved
in
my
primary
focus
has
been
in
the
open
containers
initiative.
A
A
It
boasted
the
ability
to
have
this
distributable
code,
and
you
know
like
configuration
files
that
were
portable
at
the
time
that
all
that
was
going
on.
It
was
mostly
library
calls
that
wasn't
actually
a
command-line
tool
or
a
lot
of
things
that
we
were
working
on
over
a
period
of
probably
six
months
or
so
we
made
that
into
eating,
as
a
conversation
has
started,
with
standards
for
better
or
worse
and
at
the
time
standards
to
a
lot
of
people
met
de
facto
de
facto
meaning
it's
it's.
A
A
You
know,
like
your
fhc
file
system,
is
completely
compliant
you're,
putting
all
your
files
in
the
right
place
and
people
people
grind
their
teeth
because
they're
doing
it
how
they
know
works
for
their
application,
but
not
to
somebody
specification
somebody
else's
specification,
so
we
have
brought
standards
in
and
it
as
soon
as
you
start
saying,
we're
going
to
specify
this
like
it
was.
It
was
one
of
the
things
that
I
think
because
we
had
gone
round
and
round
and
the
developers
involved
just
wanted
it
to
work.
We
wanted
it
to
be
consistent.
A
We
needed
that
base
run
time,
the
distribution
of
images
to
work
right,
no
matter
what,
whatever
application
platform
you're
working
on,
we
needed
to
move
on
it's
a
time
when
it
was
like.
We
need
a
standard
I,
think
that
got
a
lot
of
people
very
excited
and,
by
the
same
token,
that
got
a
lot
of
people
very
like
Oh
God,
but
you
know
like
you,
have
14
or
what
is
it
13
competing
standards,
so
we
need
to
unify
these
now.
A
You
have
14
competing
standards,
and
that
was
where
we're
at,
but
the
conversation
has
progressed
and
such
an
open
and
the
open
containers
initiative
Oh
see,
I'm
has
been
about
a
year
and
a
half
in
the
works.
We
are
working
on
the
image
specification
and
the
runtime
specification,
and
some
folks
within
the
industry
ask.
Why
is
it
moving
so
fast
because
I
think
in
many
industries
to
have
something
that's
going
to
be
industry
adopted?
You
know
that's
two
years
in
the
making
and
only
has
like
fledgling
adoption
within
various
tools.
A
That's
pretty
fast
moving
I
feel
like
by
a
lot
of
technology
firms
and
even
startups
that
that
a
year
and
a
half
is
an
eternity
like.
Why
are
we
not
done
with
this
already,
but
the
best
part
about
this
is
that,
as
we
are
working
our
way
through
just
these
two
building
blocks,
the
process
has
been
entirely
Oakland,
open
and
equitable
between
the
companies
involved
and
we've
we've
effectively
started
with
just
the
two
basic
building
blocks,
with
an
oci
and
that's
packaging
and
runtime.
How
are
you
going
to
distribute?
A
A
So
this
is
just
a
little
bit
of
backstory
on
it.
It
started
around
June
to
15
2015,
and
at
that
time
it
was
the
open
container
specs.
It
was
all
one
big
umbrella
project
it
around
I
forget
a
little
more
than
a
year
ago.
We
decided
that
to
have
it
all
under
specs
was
a
little
confusing,
so
we
split
up
to
a
runtime
spec
and
an
image
spec.
Currently
the
runtime
spec
is
that
a
v100
rc5
we're
about
to
enter
the
voting
period
for
a
1
dot.
A
0
final,
so
I
could
pretty
safely
say,
expect
that
v1
dot
0
final
on
the
runtime
side
within
the
next
month,
the
plug
for
network.
These
are
a
little
out
of
order.
The
primary
one
like
but
goober,
Nettie's
and
many
different
backends
are
using
is
C&I.
There
are
some
others
out
there.
The
sea
and
I
has
been
most
widely
adopted,
demott
to
my
knowledge.
A
So
this
is
where
the
packaging
said
that
I
personally,
like
spending
most
of
my
time,
the
de
facto
standard
has
been
the
docker
image,
whether
that's
on
disk
or
when
you
dock
or
save
and
load
it,
whether
you
push
and
pull
it
the
actual
pieces
involved
here.
How
do
you
see
realize
what
it
is
that
you're
needing
to
move
around
has
been
the
de
facto
standard
and
because
of
that,
what
what
we've
been
working
through
on
the
OC
otta
image
spec
has
been
a
carryover
from
largely
as
a
docker
v2
schema
to
format.
A
So
what
you
push
and
pull
is,
if
you
have
any
tooling
or
implementations
that
are
there.
If
you
already
have
like
Clayton
was
talking
about
a
registry,
it
will
not
be
a
large
leak
to
add
just
this
additional
mime
type
or
media
type
and
we're
already
seeing,
even
though
this
is
pre-release.
Also
it's
an
RC
size.
It
might
get
through
one
more
release
candidate,
we're
already
seeing
industry
adoption.
There's
there's
a
number
of
tools
that
are
supporting
it
already.
A
I,
don't
have
it
on
here,
but
recently
even
Amazon's
elastic
container
registry
ECR,
South
Africa
litter
is
the
ecs
ACR
yeah
elastic
container
registry.
They
added
a
oci
support
and
that
you
could
actually
push
a
docker
image
and
then
ask
for
the
mime
that
same
image
that
you
just
pushed,
but
in
the
mime
type
of
the
oci
format,
and
it
would
do
the
translation
on
their
backside.
A
Likewise,
you
could
push
an
oci
I'm,
my
more
media
type
to
it
and
pull
a
docker
v2
schema
to
back-
and
this
is
this
is
what
is
intended
to
happen
it
since
it's
a
low
risk
step
says
that
you
have
actually
has
specified
like
v1
version,
a
commonality
point.
As
long
as
you
know
that
you've
produced
this
artifact
or
can
consume
this
artifact,
you
have
a
compatibility
layer
on
the
low
level
building
blocks
precisely
what
is
intended
to
do
is
intended
to
be
boring.
A
A
Pretty
slim,
so
what's
interesting
is
container
d
is
pretty
much
what
some
of
the
underbelly
under
belly
execution
of
the
dr.
Damon
or
dr.
engine,
originally
a
thin
execution
layer.
Now
various
features
like
dr.
a
the
image,
cushion
pool
some
aspect
of
like
what
was
the
graph
driver.
Now
the
snapshot
layer
are
being
moved
from
the
engine
down
into
the
container
d
layer.
It's
it's
an
independently
useful
tool.
It's
for
pulling
pushing
running
images.
A
Likewise,
Rockets
been
around
for
two
and
a
half
two
years,
a
little
over
two
years
about
two
years
and
three
months
that
has
formats
the
ACI
formats
and
under
the
app
CE
spec,
as
well
as
supporting
docker.
Both
rocket
and
container
d
are
being
donated
or
have
the
conversation
started
to
donate
to
the
CNC
f
umbrella.
How
this
is
interesting
is
like
was
talked
about
earlier.
A
The
CR
I
interfaced,
the
container
runtime
interface
for
cooper
Nettie's,
allows
for
as
long
as
it
meets
you
can
write
access,
CRI
shim,
to
talk
to
any
container
runtime
because
nobody
expects
there.
Nobody
really
expects
there
to
only
be
one
winner,
because
there
might
be
different
use
cases
and
that
gets
into
talking
about
thin
VMS
or
anything
like
that.
There's
there
might
be
more
than
one
container
runtime.
You
just
write
a
CRI
shim
and
you
can
choose
that
use
case.
A
Redhats
working
on
called
cryo
used
for
a
little
while
is
called
ocid
but
cryo,
and
it's
pretty
much
a
thin
CRI
shrimp,
shim.
Just
to
call
out
to
run
see
these
two
options
give
a
little
bit
more
in
that
sense
of
like
a
full
feature
tool
that
also
will
be
callable
october
Nettie's,
and
it's
pretty
much
what
a
lot
of
people
have
asked
for
over
the
years.
They
didn't
particularly
special
in
the
cooper
Nettie's
use
case.
A
We
didn't
need
all
the
functionality
but
most
of
the
execution
and
push
and
pull
of
images,
and
so
there's
now
within
the
cnc
f
umbrella.
There's
there's
collaboration
there.
There's
there's
a
way
forward
that,
hopefully
will
be
boring
and
people
are
trying
to
get
things
done,
can
just
go
work
on
a
project
together
and
have
open
governance,
even
if
the
conversation
gets
long
and
drawn
out
and
there's
a
lot
of
people
involved,
because
there
are
people
involved.
The
conversation
conversation
needs
to
stay
open.
A
It's
a
very
exciting
time,
if
you're
into
the
space,
if
you
like,
working
on
boring
stuff
that
has
meaning
I
recommend
you
get
involved,
I
say
that,
because
a
lot
of
the
hike
will
burn
you
out
and
sometimes
it's
working
on
the
boring
stuff
that
oftentimes
nobody
else
wants
to
get
involved
in.
That
can
have
meaningful
impact.
All
the
way
up.
The
stack
and
I
feel
like
that's
where
we
are
at
this
point
so
that
we
can
get
the
conversation
to
orchestrating
containers
so
that
we
can.
We
can
distribute
these
things.
A
We
can
actually
have
a
higher
level
application
like.
We
can
actually
talk
about
a
lot
of
fun
concepts
that
you
see
coming
down
the
pipeline
for
open
shift
in
Coober
Nettie's,
so
it
particularly
as
a
call
to
action
in
my
and
my
world
is
getting
involved,
the
open
containers
initiative.
We
have
IRC
channels,
we
have
mailing
list.
There's
a
deaf
at
open
containers.
Org
email
list
is
welcome
to
get
involved
in.
A
You
need
to
make
sure
that
this
stuff
works
for
you,
so
that
we
can
take
that
feedback,
but
as
well
get
involved,
because,
as
as
it's
already
being
adopted,
it
will
mean
some
point
of
interoperate
interoperability
which
would
further
leverage
whatever
it
is
that
you're
working
on,
but
also
make
sure
that
other
people
consume
the
work
that
you're
doing
so
yeah.
It's
an
interesting
time
for
this
line
of
work
and
any
other
questions
feel
free
to
hit
me
up
later:
I'm
V
bats
at
most
places
or
V
bats
at
redhat.com,
yeah.