►
From YouTube: The OpenShift Profiles: Grant Shipley
Description
For this new video in the OpenShift Profiles series, we invited Senior Manager Developer Evangelist Grant Shipley to discuss with us the incredible success of the OpenShift RoadShow.
He also gives us a thorough explanation of the improvements in OpenShift 3.1 and the many of the developments that we can expect this year.
A
A
Hello
grant,
how
are
you
doing
hey,
pretty
good,
an
area
while
I'm
doing
fine,
and
thanks
for
having
this
conversation
with
me,
it's
really
great
to
have
members
of
the
open
shift
team
talking
with
me
and
sharing
all
your
opinions
and
experiences
about
open
shift
and
open
source
as
a
whole,
and
I
would
like
to
start
like
asking
you
like
well
about
you.
If
you
can
introduce
yourself
and
tell
us
a
little
bit
about
you
and
your
work,
a
double
shift:
okay,.
B
A
B
Think
last
time,
I
counted
was
like
30.
Some
cities
that
we
ended
up
going
to
over
a
three-month
of
spans
was
pretty
busy
each
of
the
locations
we
tried
to
do
somewhere
fun,
for
instance,
I
was
in.
I
think
it
was
minneapolis
one
of
the
first
ones.
We
did
the
baseball
stadium
there,
and
so
we
had
the
roadshow
event
to
where
people
could
try
out
open
shift
at
the
stadium,
and
then
we
all
stayed
and
watched
a
great
game
afterwards.
B
We've
also
done
them
at
tech,
centers
and
even
bars
and
breweries
before
so,
it's
been
pretty
great.
You
know
each
city
I
think
we
if
we
could
fit
50
people
in,
we
would
normally
get
150
to
200
people
wanting
to
actually
sign
up
and
go,
which
was
just
crazy,
and
you
know
there's
a
lot
of
work
because
we'd
have
to
add
cities
on
the
fly.
B
B
A
B
So
the
big
deal
with
open
shift-
three
is
open,
shift
has
been
around
for
many
years
and
a
lot
of
other
platform
as
a
service
offerings
have
been
as
well
but
they've
all
kind
of
been
based
on
their
own
implementation
of
Linux
containers,
whether
that's
LXE
or
you
know,
with
open
shift.
We
created
our
own
linux
container
based
on
sa
linux,
linux
control
groups
and
Pam
namespaces
for
poly
instantiated
directories.
B
B
Because
of
all
that
work,
we
ended
up
and
still
are
the
number
two
contributor
to
dr.,
and
so
we
took
this
docker
container
format
and
we
wanted
to
make
it
readily
available
to
developers
to
use
the
doctors
pretty
easy
to
use
as
a
developer
on
your
local
machine.
But
where
things
get
pretty
complicated
is
when
you
want
to
run
your
applications
or
your
containers
as
scale
and
I'm
not
talking
about
massive
scale.
B
Even
though
that's
part
of
the
benefits
of
the
open
shift
platform,
but
even
just
running
two
or
three
containers
load
balance
with
h,
a
proxy
or
whatever
the
case
may
be.
That
gets
pretty
complicated,
pretty
quickly
for
developers,
and
so
once
we
had
implemented
the
the
doctor
stuff
inside
of
the
next
version
of
open
shift.
B
And
so
those
two
things
are
important,
both
doctor
and
cooper
Nettie's,
because
it's
it's
good
to
know
that
as
a
team
openshift
and
as
a
company,
we
bet
on
those
technologies
way
in
advance
we're
talking
years
ago
to
make
them
viable
and
so
the
reason
we
needed
Cooper
Nettie's,
if
you're
not
familiar
with
it,
is
to
do
orchestration
and
scheduling
of
your
containers.
And
so
what
happens
is
you're
docker
container
actually
runs
in
this
concept
called
a
Cooper
Nettie's
pod.
Then
you
can
easily
scale
those
pods
up
create
replicas
of
them.
B
Cooper
daddy's
working
I
know
this
is
very
long
answer,
but
we
realize
that
Cooper,
Nettie's
and
docker
are
great,
but
they're
not
very
accessible
for
the
average
developer.
So
think
about
you
know
your
non
startup
non
hipster
developer,
that's
kind
of
behind
the
bleeding
edge
curve.
They
want
technologies
to
be
trusted
just
a
little
bit
more
before
they
start
working
on
them.
We
realized
that
the
tool
sets
provided
like
I
said
we
just
wasn't
very
accessible
to
developers.
B
A
It
was
quite
detail,
and
the
viewers
are
going
to
appreciate
that
your
point
of
view
on
that,
and
but
now
you
talk
all
about
that
mode,
openshift
three
and
even
before
the
entire
road
showed
was
over
openshift
31
was
already
announced.
That's
all
right!
It
seems
that
you
basically
have
to
keep
adapting
to
everything
that
is
there
and
that
the
entire
pipeline
is
really
fast
is
changing.
So
what
what
can
we
expect
to
have?
Would
double
shift
31.
B
B
That's
what
I
do
is
the
ability
to
do
just
some
great
things
inside
of
the
web
console
itself,
so
you
can
look
at
aggregated
logs
across
all
of
your
containers
and
have
them
streamed
in
the
web,
console
via
WebSocket
connection,
it's
very
cool,
so
you
don't
have
to
like
fire
up
your
command
line
and
log
into
pods
and
tell
files
and
all
that
stuff
you
just
with
a
single
click
from
the
pod.
You
can
look
at
the
log
files.
B
We
also
have
this
topology
visualization
tool
right,
and
so,
if
you
have
an
application
deployed
on
the
open
shift
platform-
and
let's
say
that
application
consists
of
you
know
five
front-end
containers-
that's
servicing
your!
You
know
your
web
UI,
whether
that's
JavaScript,
nodejs
or
whatever
the
case
may
be,
and
then
that
talks
to
a
set
of
micro
services
or
some
back-end
services,
that's
deployed
across
three
different
containers
and
then
all
that's
talking
to
a
replicated
database
across
five
containers
and
it's
all
front
end
with
the
H,
a
proxy
load.
B
Balancer
with
that,
you
know
when
you
start
talking
about
real
applications
like
this.
It
gets
very
complicated
and
to
understand
all
of
the
touch
integrations
between
these
two
containers,
and
so
we
develop
this
tool
that'll.
You
know
you
just
click
a
button
inside
the
web
UI
and
it
draws
this
map
of
your
application
and
shows
all
of
the
pods
and
how
the
communication
happens
between
how
the
traffic
flows
out
through
the
external
route
down
into
the
database,
and
so
that
allows
you
to
quickly.
You
know
visualize
the
topology
of
your
application.
B
Another
one
of
my
favorite
features
is
the
about
the
ability
to
open
up
a
shell
or
command
line
tool
into
a
specific
container
right
from
inside
of
the
web
browser,
and
so
you
don't
have
to-
and
this
is
I
actually
started
using
Windows
10
not
long
ago
and
Windows
10
was
was
kind
of
a
pain
for
me
to
get
set
up.
As
a
you
know,
linux
guy,
because
I
live
and
breathe
by
the
command
line,
and
so
you
know
I
hate
the
command,
dot-com
or
cmd.exe
or
whatever.
B
It's
called
that
the
default
shell,
the
ships
with
windows,
because
in
you
gotta
install
openssh
em,
you
gotta,
you
know
generate
keys
and
the
terminal
just
sucks
right,
and
so
what
this
allows
to
be
able
to
open
up
a
terminal
inside
of
the
web
browsers
is
with
a
single
click
of
the
button,
as
a
Windows
user.
I
can
completely
ignore
all
this
stuff.
That
I
need
to
do
whether
that's
installing
putty
or
whatever
the
case
may
be
to
open
up
a
execs
bash
shell
on
the
remote
containers.
A
B
So
I
believe
the
future
of
open
shift,
we're
going
to
be
focusing
more
on
the
developer.
Experience
on
the
user
interface
designs,
whether
that's
inside
of
the
IDE
or
in
the
web
UI,
or
even
great
console
tools
or
rest
api
s
to
really
continue
down
the
path
of
making
a
container
application
platform
like
over
chipped
is
accessible
to
as
many
developers
as
possible.
So
they
can
have
the
benefits
of
running
these
new
technologies
without
changing
how
they
work
on
a
day-to-day
basis.
A
Okay,
well,
thank
you
very
much
grant
for
all
your
time
and
your
questions
and
I
do
hope
to
have
you
here
like
a
soon
we're
going
to
talk
with
other
members
of
the
team
in
and
any
time
that
you
want
to
share
your
opinion
about
open
shaved,
open
sores,
redhead
as
a
whole
or
just
software
development.
You're
welcome.
Okay,.