►
From YouTube: OpenShift 3 Walkthrough
Description
In this video, Grant Shipley, walks you through how to stand up the OpenShift Origin project on your local machine and then shows how to use the platform for development focussing on the web console and command line tools.
After watching this video, you will understand how to start developing and deploying your own container based applications using the OpenShift Container Application Platform.
Check the corresponding blog post for more information:
https://blog.openshift.com/openshift-3-walkthrough/
A
A
Hey
everybody:
this
is
grant
your
friendly
OpenShift
team
member
now
today,
I
just
wanted
to
make
a
quick
video
to
show
you
some
of
the
new
stuff
we've
been
working
on
in
our
upstream
project,
openshift
origin,
which
is
also
called
open.
Chef
3
if
you're
not
familiar
with
open
shift
in
what
we've
been
doing,
we've
been
spending
a
lot
of
time
working
on
both
docker
and
kubernetes
and
making
it
accessible
to
the
developer.
A
The
only
thing
I
need
to
do
to
get
openshift
running
on
my
local
boxes
type
in
vagrant
up,
and
this
will
spin
it
up
now.
The
prerequisites
for
this
is
to
have
both
vagrant
and
VirtualBox
installed
on
your
system.
If
you
go
out
to
blog
openshift,
comm
and
search
for
grant
Shipley,
which
is
my
name
you'll,
be
able
to
see
some
detailed
instructions
on
how
to
get
this
working
on
the
Macintosh
Windows
machines,
as
well
as
Linux
machines.
A
Now,
once
I
issued
the
vagrant
up
command
here,
it's
going
to
head
and
start
up
this
virtual
machine
that
has
openshift
already
running
for
me,
and
a
few
things
to
note
here
is
that
the
IP
address
that
we
use
by
default
is
10.2
to
2.
If
that
doesn't
work
for
your
particular
network
configuration,
you
can
just
look
at
this
vagrant
file
and
change
the
IP
address
on
this
line
to
use
whatever
you
would
like
to
use
for
your
local
environment.
A
Another
thing
to
note
is
the
amount
of
memory
allocated
to
the
virtual
machine
by
default,
I
believe
it's
2
or
4
gigs,
but
my
machine
that
I'm
running
on
actually
has
32
gigs,
so
I'm
going
ahead
and
bumped
it
up
to
just
under
8
gigs
of
memory
allocated
to
open
shift,
and
you
can
see
this
is
the
origin
machine.
So
now
that
we
have
this
up
and
running,
let's
go
ahead
and
start
taking
a
look
at
the
console.
A
Ok,
so
to
get
to
the
console,
all
you
need
to
do
is
go
to
10.2
2,
:,
8,
4,
4
3
is
the
port,
and
let's
log
in
with
the
username
of
OpenShift
and
the
password
OpenShift,
you
can
use
any
username
and
password
you
want
for
the
virtual
machine.
It
doesn't
matter
if
we
allow
any
type
of
authentication
just
for
demo
purposes
and
once
I
get
to
the
console.
The
first
thing
I
see
is
that
I
need
to
create
a
project.
A
So
let
me
show
you
how
this
works:
I'm
going
to
go
ahead
and
click
on
create
project
and
I
am
going
to
name
this
project
demo
PHP
and
we're
going
to
the
display
name
is
PHP
application
and
just
a
short
description
is
my
demo
PHP
application.
Now,
when
I'm
typing
on
my
keyboard,
I
am
doing
this
in
real
time.
A
So
let's
create
this
project
so
now,
I
have
a
project
created,
and
by
default
it's
going
to
drop
me
into
this
menu
to
create
an
application
right
based
off
an
image
or
template,
and
since
I
wanted
to
create
a
PHP
application,
I'm
going
to
scroll
down
and
I'm
most
like
PHP.
You
can
also
you
know,
filter
by
keywords.
Here
you
can
type
in
PHP,
maybe
you're
a
Java
head,
and
you
just
want
to
look
at
the
Java
stuff,
maybe
you're
a
hipster
and
just
want
to
bang
out
some
note.
A
J/S
just
filter
that
in
but
let's
go
ahead
and
do
PHP.
Let's
do
PHP
five,
six
and
you'll
notice
on
this
screen.
There's
this
little
tag
here
called
builder.
Now,
that's
where
the
true
magic
open-source
comes
in
and
openshift,
ladies
and
gentlemen,
is
that
we
have
this
other
project
inside
of
OpenShift
called
source
to
image,
and
we
have
these
builder
images
that
you
can
select.
Let
me
show
you
how
that
works,
real,
quick,
it's
pretty
phenomenal!
It's
almost
like
PHP!
It's
going
to
ask
me
for
a
name
of
my
application.
A
Now,
remember
we
put
in
a
name
before,
but
that
was
for
the
project,
so
you
can
think
of
a
project
as
a
grouping
of
different
assets
for
your
application.
So
you
may
have
a
web
front-end
the
database,
whatever
the
case
may
be,
and
then
you
also
name
each
individual
component
and
that's
what
I'm
naming
now
is
my
PHP
web
front-end.
So
I
can
just
call
this
front-end
and
it's
going
to
ask
me
for
the
get
repository
URL
now.
This
can
be
from
any
get
repository,
including
private
repositories.
A
So
what
I'm
going
to
do
just
hop
over
to
my
github
account?
Real,
quick
and
I
am
just
going
to
click
on
my
repositories
and
I'm,
going
to
find
a
small
PHP
one
here.
Here's
a
simple
PHP
that
we
can
use.
So,
let's
clone
or
copy
this
repo
URL
paste
that
in
and
click
on
create
so
now
what's
actually
happening
is
OpenShift
is
automatically
cloning
that
source
code
repository
it's
using
a
base,
docker
image
with
PHP
in
it,
that
is
a
source
to
image,
enabled
image,
and
so
it's
going
to
clone.
A
That
repository
build
the
source
code
if
it
needs
to
in
PHP
it's
an
interpreted
language.
So
it's
not
going
to
build
anything,
but
it
is
going
to
resolve
any
dependencies
and
then
layer
the
source
code
on
top
of
the
base,
docker
image
and
create
a
new
docker
container
based
on
those
two
inputs
as
the
output,
and
so
the
beauty
of
that
is
as
developer.
A
You
get
to
take
full
advantage
of
docker
and
orchestration
with
kubernetes
without
having
to
learn
all
the
internals
of
either
of
those
technologies
right,
and
so
it
really
frees
you
up
as
a
developer,
just
to
focus
on
your
and
you
still
get
to
be
able
to
take
advantage
of
all
the
cool
things
with
running
your
application
code
inside
of
containers.
Now
I
did
this
in
real
time,
so
you
can
see
that
it
was
pretty
quick
to
deploy
this
application
out
based
on
docker
and
kubernetes,
and
I
have
one
pod
running
now
pod.
A
If
you're
not
familiar
with
kubernetes,
you
can
think
of
a
pod
as
being
a
encapsulation
of
a
docker
container.
So
you
think
of
a
pod
as
a
container,
and
inside
of
this
pot
is
actually
that
new
docker
container
we
just
built
and
under
the
covers.
It
also
created
a
route
for
me.
So
I
can
access
this
application
immediately,
so
I'm
going
to
go
ahead
and
click
on
this
route
that
was
created,
and
we
can
see
that
the
application
just
says
this
is
the
best
PHP
web
app
in
the
universe.
A
Let
me
make
that
a
little
bigger
I'm.
We
need
a
bask
in
all
the
glory
of
this
wonderful
PHP
application
that
I
created
see.
That's
awesome
right.
So
let's
go
ahead
and
close
that
and
one
of
the
great
things
about
OpenShift
is
the
ability
to
quickly
scale
this
up.
So
let's
say
I
wanted
to
actually
scale
this
up.
To
you
know
three
or
four
different
containers
all
serving
the
front
end
and
click.
This
button
is
going
to
scale
up
to
two
click.
It
again.
A
It's
going
to
scale
it
up
to
three
up
to
four
and
then
let's
go
to
five
just
for
fun
here.
So
that's
how
quickly
I
was
able
to
scale
this
PHP
application
up
to
five
containers.
Docker
containers,
all
load
balanced
inside
of
OpenShift,
pretty
phenomenal
stuff
I
didn't
have
to
actually
do
anything
right,
and
so
now,
if
I
hit
this
web
application,
it's
actually
going
to
be
load
balanced
across
those
five
pods.
A
So,
let's
take
a
look
at
some
of
the
key
concepts
that
you're
going
to
want
to
know
in
order
to
start
developing
with
this
open
ship
business
that
we're
talking
about
here.
So
if
I
click
on
browse
I
can
look
at
my
builds
my
deployments.
My
events,
my
image
streams,
pods
route
services,
storage,
that's
a
lot
of
stuff
right!
So,
let's
just
start
at
the
beginning:
let's,
let's
go
to
builds
here
now.
I
had
a
build
running
that
took
52
seconds
and
I
created
it
four
minutes
ago.
A
A
So
you
can
deploy
this
container
out,
it's
pretty
amazing
stuff
and
then
once
we
did
this
initial
build,
you
saw
that
we
were
able
to
scale
up
very
quickly
because
we
just
had
to
replicate
the
copy
of
that
docker
image
that
we
created
on
the
fly.
Okay,
so
that's
builds
in
a
nutshell.
I
can
actually
click
on
this
build
if
I
want
to
get
some
more
detailed
information
here
and
I
can
view
the
log
of
the
build
pretty
cool
stuff
right.
A
It's
just
a
PHP
app,
so
there
wasn't
really
any
build,
but
I
can
open
the
full
view
of
the
build.
I
can
look
at
the
environment
here
and
then
I
can
go
back
to
details.
What's
interesting
is
if
I
wanted
to
also
start
a
new
build.
All
I
have
to
do
is
click
this
rebuild
button.
I
can
edit
the
build
description
if
you
want
to
go
way
into
the
depths
of
OpenShift
and
how
build
strategies
work
and
how
to
kick
off
new
builds.
It's
you
can
see
that
it
pulled
my
information
from
github.
A
Here's
the
docker
image
it
used,
it
uses
a
synth
is
CentOS,
and
so
you
can
go
in
and
actually
modify
this
stuff.
If
you
want
to
do
some
advanced
use
cases
with
it.
So
let
me
go
back
to
browse
and
go
to
deployment
now
on
deployments.
I
have
one
deployment,
but
I
have
five
replicas.
That's
when
we
scaled
up
to
five
ponds
and
it's
going
to
trigger
on
an
image
change,
and
so
what
that
means.
That
is,
if
anytime
I
change
my
base
image.
A
It's
going
to
automatically
redeploy
that
out
to
the
cluster
that
I'm
using.
So
that's
pretty
cool
right,
because
if
the
base
image
that
I'm
using
that
PHP
image
gets
a
security
update
or
whatever
the
case
may
be
by
default,
it's
going
to
automatically
change
that
image
and
then
do
a
rolling
deployment
across
my
my
cluster.
Now
you
can
honestly
modify
that
to
suit
your
needs.
If
you
don't
want
that
to
happen,
there's
all
kinds
of
different
build
strategies
that
you
can
implement
an
open
shift.
A
But
let's
drill
down
into
my
deployment
here
and
so
here,
I
can
look
at
the
detail.
Details
of
this
deployment.
I
can
also
look
at
the
number
of
replicas
right
now
we
have
five
current
five
desired.
I
can
change
that
right
here.
Let's
just
go
up
to
ten
pow
Bob's,
your
uncle,
let's
go
to
ten,
and
so
we
just
scaled
up
to
ten.
Just
by
adding
a
different
things.
We
go
back
to
the
overview
page
sure
enough
we're
up
to
ten
pods.
That's
crazy,
stuff
man,
I
love
it!
A
Alright,
let's
go
back
to
browse
and
deployments
and
poke
around
just
a
little
bit
more
here
we
can
see
some
details
about
the
container
the
image
how
I
could
manually
deploy
this
from
the
command
line.
If
I
wanted
to
what
template,
we
used
number
of
replicas
again
the
pod
template,
we
can
attach
persistent
storage
if
we
want
right
here
now,
that's
pretty
pretty
cool
stuff,
because
everyone
who
uses
doctrine
container
knows
that
they're
ephemeral
in
nature.
A
If
you
store
things
on
the
file
system
inside
the
container,
once
that
container
restarts
or
something
happens,
it's
going
to
be
lost,
and
so
in
open
ship.
We
actually
provide
the
concept
of
mounting
persistent
storage
inside
of
your
pods
or
your
containers,
so
your
data
will
live
on
all
right.
Let's
click
on
environment
here
I,
don't
have
any
specific
environment
variables
set
for
this
little
small
application,
but
if
you
did
have
environment
variables,
they
would
show
up
on
this
page.
We
can
also
redeploy
from
right
here.
A
We
can
edit
the
deployment
yamo
just
like
we
did
with
the
build
strategy
here.
If
you
want
to
get
into
some
advanced
use
cases,
let's
go
back
to
browse
click
on
advanced,
and
this
is
where
we'll
see
all
of
the
events
with
this
little
scenario
that
we
just
did
you
know
creating
scaling,
pushing
building
all
that
cool
stuff.
We
can
dig
into
that
a
little
bit,
so
let's
go
to
image
streams,
and
this
is
showing
the
docker
image
that
we're
actually
using
and
where
it
was
pulled
from.
A
This
is
using
the
internal
docker
registry
that
we
ship
with
openshift,
and
you
can
see
you
know
if
you
wanted
to
pull
this
image
out
or
do
something
with
this
particular
image.
This
is
where
it's
come
from.
We
call
this
image
front
end,
which
is
what
we
named
the
application.
Now
if
we
go
into
pods,
this
is
where
it
kind
of
gets
a
little
bit
cool.
We
can
see
all
of
these
pods.
We
running
that.
We
have
now
keep
in
mind
a
pod.
You
can
think
of
it
just
as
a
docker
container.
A
So
we
had
this
build
pod
that
we
kicked
off
to
actually
run
that
build
to
create
that
docker
image.
We
created
it
nine
minutes
ago,
and
this
one
has
finished.
So
there's
no
containers
running
right
now,
but
if
we
look
at
one
of
the
application,
pods
click
on
that
we
can
do
some
cool
stuff.
Here
we
can
look
at
the
environment.
Again,
we
don't
have
any
environment
variables
set.
A
We
can
look
at
the
metrics,
which
is
pretty
cool,
so
we
have
this
built
in
metrics
dashboard
here,
they'll
show
you
how
much
memory
this
PHP
application
is
actually
consuming.
That's
actually
consuming
51
megabytes
of
RAM,
so
not
much
and
and
little
to
no
CPU,
not
even
enough
to
register.
We
can
also
look
at
the
logs
on
this
particular
pod
and
we
can
see
the
get
request
that
we
did
and
it'll
show
up
here.
You
can
follow
the
logs
or
tell
them.
However,
you
want
to
look
at
that
or
think
of
that.
A
You
can
also
view
them
in
a
full-screen
mode
here
and
once
this
log
gets
down
below
this
page,
there's
a
little
button
that
pops
up
here
that
says
follow
which
will
allow
you
to
basically
tell
the
log.
Another
thing
you
can
do,
which
is
really
cool,
is
just
click
on
this
terminal
right
here
and
we
basically
open
up
a
shell
inside
of
the
remote
docker
continue.
So
you
do
LS
and
you
know,
Who
am
I
and
they'll
tell
you
that
you're
the
user
default.
A
You
can
look
at
your
index,
dot,
PHP
file
and
say
this-
is
the
best
PHP
web
app
in
the
universe
exit
out
of
that
you
can
look
at
log
files
in
here,
whatever
you
want
to
do
right,
so
we're
probably
in
HTTP.
Let's
just
tell
all
those
I
guess,
there's
no
files
in
there
or
don't
have
permission,
but
you
can
look
at
log
files
inside
the
terminal.
A
A
Front-End
is
how
this
is
exposed
to
the
outside
world
internally,
my
pot
or
my
container
is
listening
on
port
8080,
but
we're
going
to
expose
that
via
this
hostname,
and
so,
if
I
click
on
this,
we
can
see
that
it
routes
to
the
service
front
end
now
service
is
something
we
haven't
talked
about
yet,
but
a
service
is
basically
the
entry
point
into
your
application.
So
if
I
looked
at
this
service
front
end,
we
can
see
that
the
service
port,
8080
and
target
port
8080
when
create
additional
routes.
A
A
That's
been
provided
for
you
on
the
platform,
so
you
do
have
to
set
up
those
persistent
volumes
as
an
administrator
before
you
can
mount
them
as
developer,
but
once
they're
there,
you
can
mount
them
into
your
pods
and
containers
and
they'll
live
with
the
life
of
the
application.
Alright.
Lastly,
let's
take
a
look
at
the
Settings
tab
here
we
can
just
see
you
know
the
name
of
the
project,
any
quotas
that
you
have
since
this
is
just
a
local
virtual
machine
that
I'm
running
as
a
developer
at
we
don't
actually
have
any
quotas.
A
Ok,
so
let's
go
back
to
the
main
project
screen.
Here
we
go
our
PHP
application
now,
I
want
to
show
you
the
real
power
of
this
source
to
image
and
building
these
docker
containers
on
the
fly.
I
want
to
go
into
my
builds
so
I'm
going
to
click
on
this
build
here.
I'm.
Sorry,
let
me
browse
into
the
builds.
May
click
on
the
build
front-end
here,
I'm
going
to
click
on
configuration
and
then
over
here
we
have
some
web
hooks.
Now
this
is
really
cool
stuff.
A
So
what
I'm
going
to
do
is
I'm
just
going
to
copy
the
URL
for
this
github
webhook.
Ok,
so
I
put
that
into
my
clipboard
here's,
the
full
URL
I'm
going
to
go
over
to
my
github
project
and
I'm
logged
in
here.
So
what
I'm
going
to
do
is
go
to
settings
and
web
hooks
and
services.
Let
me
delete
this
web
hook
and
then
I
may
log
in
here
and
then
I
can
add
this
web
hook
in.
A
So
let
me
paste
that
in
disable
SSL
since
I'm,
using
a
self-signed,
cert
and
then
I'm
going
to
add
that
web
book
now
anytime,
that
my
application
code
changes
it's
going
to
trigger
a
build
inside
of
OpenShift.
Now,
that's
not
actually
going
to
work
for
my
environment,
because
why
I
am
on
a
private
IP
address,
so
it's
not
actually
going
to
be
accessible
from
the
outside
Network,
but
if
it
was
and
I
made
that
change,
it
would
automatically
update
this
build
with
some
new
stuff.
Okay.
A
So
that's
basically
the
openshift
web
console
in
a
nutshell,
all
right.
We
have
this
great
awesome,
PHP
application
here
that
we
deployed
now
I
do
want
to
switch
over
and
show
you
the
command
line,
just
real
quick.
Let
me
clear
our
screen
here
and
the
command
line
tool
that
we
ship
with
open
shift.
3
is
called
OC,
so
I
can
do
OC,
login
and
say
server
equals
10.22
pull
on
8
4
4
3.
A
Let's
do
HTTP
on
the
front
of
that
and
hit
enter
there
and
we
used
what
do
we
use
open
shift
and
open
shift?
And
so
now
it's
going
to
say
that
I'm
using
the
new
project
called
demo
PHP.
Ok,
so
that's
pretty
cool,
so
I
can
do
OC
get
pods
and
a
list
all
of
those
pods.
Now,
let's
say
I
want
to
scale
down
on
the
command
line.
Now
it's
not
as
intuitive
as
the
web
browser
or
the
web
console,
but
I'm
going
to
show
you
how
to
do
that.
A
The
way
we
scale
is
through
the
deployment
config,
so
I
can
do
OC
get
deployment
config
and
it's
going
to
say
that
I
have
a
deployment
convey'd
called
front
end,
so
what
I
can
do
is
say:
OC
scaled
DC,
which
is
the
deployment
config,
give
the
deployment
config
a
name
and
just
say:
replicas
equals
two
and
that's
going
to
scale
us
down
to
two.
And
so,
if
we
go
over
our
web
console,
we
can
see
sure
enough
that
we
scaled
down
to
two.
A
So
let's
do
something:
let's
go
up
to
23
and
then
I'll
switch
over
to
the
web
console
real
quick.
So
you
can
see
it
actually
scaling
up
here.
So
you
can
see
that
you
know
what
talked
via
the
REST
API
out
to
my
server
and
it's
going
to
scale
this
up
to
20
pods
and
it's
starting
to
go
we're
probably
at
five
ten
fifteen
BAM
all
the
way
up
to
20,
so
pretty
cool
stuff.
A
You
can
also
actually
scale
down
to
zero
believe
it
or
not,
and
that
just
leaves
your
application
there,
but
it's
not
actually
running
right,
and
so,
if
you
just
wanted
to,
you
know,
have
it
sitting
out
there,
maybe
you're
doing
some
maintenance
on
it
or
whatever
the
case
may
be.
You
can
just
have
this
in
there.
So
let's
scale
this
back
to
one,
so
our
application
is
up
and
running
again.
So
let's
do
one
other
thing.
Let's
show
you
how
to
use
application
templates
now.
A
I
have
an
application
template
in
a
openshift
3
MLB
parks
project,
which
is
a
geospatial
based
application,
and
so
what
we
want
to
do
is
show
you
how
to
use
a
command
line
to
create
a
java
based
application,
so
I'm
gonna,
say
OC
new
project,
ill
Mel,
beatbox
hope
that
project
already
exists,
I
must've
created
as
a
another
user.
Someone
call
it
open
shift,
MLB
parks.
So
now
we're
using
this
open
shift,
MLB
parks
project.
A
If
I
come
back
to
the
open
shift
console,
we
can
see
that
we
have
an
open
shift
project
here,
but
we
don't
have
anything
in
our
project.
So
what
we
support
with
open
shift
is
the
ability
to
have
application
templates,
and
this
is
powerful
for
development
teams,
because
once
you
have
your
application
up
and
running
inside
of
the
environment
like
you
want,
maybe
it's
a
complex
application
with
some
front-ends
and
backends
microservices
and
you
have
it
running.
A
You
can
just
create
application
template
and
then
anyone
who
joins
your
team
wants
to
work
on
your
source
code
can
just
basically
recreate
that
entire
project
based
off
of
an
application,
template
and
so
I'm
going
to
show
you
how
to
do
that,
and
so
I
have
my
application
template
here,
and
so
what
I'm
going
to
do
is
just
create
this
application
template
and
this
can
copy
and
paste
the
instructions
here
paste.
This
in
I
must
say:
OC
create
dash
F,
which
means
from
a
file,
but
it
also
takes
a
URL
and
here's.
A
My
JSON
file
that
describes
my
application
so
I'm
going
to
create
that.
So
now
I
have
a
template,
called
MLB
parks,
and
so,
if
you
go
back
to
the
web
console,
if
you
click
on
add
to
project-
and
you
search
here
or
just
it's
actually
the
third
one
down
here-
you
can
see
that
this
was
actually
created
inside
of
the
web
console
as
well.
A
So
as
a
user
of
this
project,
I
can
create
this
and
it's
going
to
create
a
EAP
application
with
MongoDB
and
I
can
also
create
it
on
the
command
line,
just
by
typing
OC,
new
app
MLB
parks,
and
that
is
going
off
cloning
that
git
repository
setting
up
MongoDB
doing
everything
it
needs
to
deploy
this
Java
EE
application
out.
So
we
have
MongoDB
already
running
and
now
it's
going
to
pull
down
and
build
that
Java
source
code.
And
so,
let's
take
a
look
at
this
logs
and
I'll.
A
Show
you
what
I
was
talking
about
with
follow
I
clicked
a
little
follow
button
up
there,
and
we
can
see
that
maven
is
doing
its
build
of
this
java
application.
And
so,
while
that's
going,
let's
create
another
project
and
we're
just
going
to
call
this
guestbook
and
now
I'm
using
this
guestbook
application.
I
want
to
show
you
how
easy
it
is
to
use
containers
or
images
that
are
not
actually
in
open
ships.
I
can
do
OC
new,
app
kubernetes,
slash
guestbook.
A
This
is
the
famous
kubernetes
guestbook
application,
and
it's
going
to
go
out
to
docker
hub
and
pull
this
down
and
run
it
for
us.
Ok,
and
so
you
can
do
this
with
any
image
on
docker
hub,
and
so
let's
go
back
to
our
projects.
Here,
let's
go
to
guestbook
and
we
can
see
that
we
have
this
guestbook
application
running,
but
we
don't
have
a
route
for
it.
Yet
so,
let's
create
a
route
skirt
services
here,
I've
never
actually
created
a
route
inside
of
the
web
view.
I
always
use
command
line.
A
That
looks
like
we
can
click
on
create
route
here
and
we're
just
going
to
click,
create
see
what
happens
alright.
So
it
was
smart
enough
to
figure
out
how
to
create
a
route
force,
that's
addressable,
and
so
now,
if
I
click
on
that
BAM
I
have
this
kubernetes
guestbook
application
running
that
we
pull
down
straight
from
docker
hub.
So
the
world
is
now
open
to
you
in
running
these
docker
containers
locally
on
your
machine,
even
if
they're,
not
source
to
image,
enabled
ricing
just
go
out
to
docker
hub,
find
something
and
spin
it
up.
A
Let's
go
back
to
our
projects
here.
Take
a
look
at
our
OpenShift
dilma,
be
parks,
application
check
on
it.
It
is
a
pretty
hefty
java-based
application,
so
it
takes
a
while
to
build
the
build
just
finished.
So
now
it's
creating
that
docker
image
on
the
fly
that
we
were
talking
about
earlier
and
it's
pushing
that
docker
image
up
to
the
OpenShift
registry
and
then
once
that
image
has
been
pushed
to
the
registry,
you
can
see
it
happening
down
here
on
the
very
bottom
line.
A
That
image
is
going
to
then
be
available
for
deployment,
and
so
this
can
take
a
few
minutes
for
it
to
actually
complete
pushing
this
large
java
image
out
to
the
registry.
The
first
time
so
the
while
that's
going
I
do
want
to
just
show
you
a
few
things
on
the
command
line
here
as
well.
So
I
can
say:
OC
get
pods
on
this
kubernetes
guestbook
application,
and
we
see
that
I
have
one
pod
running
now.
If
you
remember
I
showed
you
how
to
scale
this
earlier
in
the
video
on
the
command
line.
A
The
flow
is
the
same
for
every
application,
so
I'm
just
going
to
walk
through
that
again
say:
OC
get
DC,
which
is
deployment
config.
You
can
also
type
it
out
here
if
you
want-
and
this
name
is
called
guestbook,
so
we
can
say
OC
scale
deployment,
config
s
book,
set
our
replicas
up
to
ten
and
we'll
scale
guestbook
up
to
ten.
Now,
if
I
do
OC
cap
pods
there
we
go
now.
Remember
I
showed
you.
These
are
currently
scaling
so
they're
in
a
pending
state.
If
we
do
it
again,
maybe
there
they'll
be
writing.
A
Some
of
them
are
running.
If
you
remember
on
the
web,
console
I
showed
you
how
to
open
up
a
shell
inside
of
the
browser,
so
I'm
going
to
show
you
how
to
do
that.
On
the
fan
line,
let
me
do
OC
get
pods
they're
all
running
now.
Let's
say
I
want
to
shell
into
this
pot
check
this
out.
I
can
type
in
OC
r,
sh
notice,
I,
have
tab
completion,
pretty
fancy
stuff
guestbook
and
then
give
it
a
pod
name.
A
Maybe
I
want
to
go
into
the
d7
one
and
I
have
tab
completion
there,
courtesy
of
Z
shell
and
oh,
my
z,
SH,
and
if
you're
interested
in
getting
that
set
up,
just
go
to
blog's
OpenShift
comm
search
for
grant
Shipley
again
you'll
see
a
blog
post.
I
wrote
about
how
to
set
this
up
so
I'm
just
going
to
our
Sh
into
that.
Oh,
it
looks
like
a
the
kubernetes.
Guestbook
application
actually
doesn't
have
bash
in
it.
So
that
is
good
to
know
right.
So
you'll
run
into
that
at
some
point.
A
Some
of
these
docker
containers
that
you
have
don't
actually
allow
you
to
execute
a
remote
shell.
So
let's
get
our
projects
and
let's
switch
over
to
the
PHP
one,
because
we
know
that
that
one
allows
you
to
execute
a
shell
session.
So
let's
say
OC
project
demo
PHP
do
OC
get
pods.
Now,
let's
do
OC
rsh
front-end
WX,
and
we
can
see
that
because
this
container
actually
has
the
best
shell
installed
on
it,
I'm
able
to
rsh
into
that
container
and
I.
Can
you
know,
look
at
my
files
do
whatever
I'm
going
to
do
here.
A
So
let's
do
OC,
you
get
pause
again
and
let's
do
OC
get
projects
and
switch
over
to
our
open
shift.
Ll
be
parts
profit,
so
I'm
do
OC.
Project
open
shift
in
will
be
parks
and
I
want
to
do.
Oc
build
locks,
let's
see
OC
get
pods
I
can
do
OC
log
and
then
pass
in
my
build
pod
and
paste
pass
in
f
follow,
and
this
is
how
you
can
look
at
your
log
files
on
the
command
line
just
like
we
did
in
the
browser.
A
So
it
looks
like
that
it's
successfully
pushed
that
image
looking
at
the
last
line
here.
So
let's
go
back
to
our
project
here
and
take
a
look
at
the
application.
Here
we
go.
We
have
one
JBoss
EAP
server
running
with
a
Java
EE
application,
backed
with
a
database
exposed
via
URL.
Let's
see
if
JBoss
has
actually
came
up
yet
sure
enough.
It
has
and
here's
the
application
at
the
geospatial
based
application
that
you
can
look
at
all
the
baseball
stadiums.
So,
let's
see
how
fast
we
can
scale
up
the
old
J
ball
system
here.
A
It's
thinking
about
it,
my
Java,
you
can
do
it
starting
j
ball,
so
I
guess
so,
let's
see
how
long
it
actually
takes
should
be
done
there.
We
go
we're
now
up
to
2
JBoss
EAP
servers
all
load
balance
lists.
What's
a
let's
really
get
some
heat
going
here.
Let's
do
OC
get
pods,
but
project
of
I
am
and
we
know
how
to
do
this.
We
want
to
scale
this
up,
so
we're
going
to
say.
A
So
now
we
can
come
back
here
and
it's
going
to
scale
this
up.
Look
it's
getting
there!
Ok,
so
all
of
the
containers
have
been
created,
it's
being
replicated
now
we're
just
waiting
on
the
container
is
to
become
active,
and
traditionally
that
will
mean
you
know
waiting
on
J
balls
to
come
up
and
for
the
application
to
start.
So
this
should
be
done.
Just
any
second
now
and
so
a
fuse
coming
online,
so
I'll
move
a
little
bit
there.
A
Maybe
I
should
have
scaled
the
other
one
down
to
make
up
free
up
some
memory.
So
actually
let's
go
while
this
is
finished
and
skilling
up,
let's
go
and
browse
our
pods
here
and
now
we
can
see
that
they're
all
running,
so
it
just
took
a
second
there.
So
let's
go
into
our
pods
and
what
we
can
do
is
take
a
look
at
this.
First
one
that's
been
running
for
eight
minutes.
We
can
actually
look
at
our
metrics
here.
Remember
that
PHP
application
was
using
52
Meg's
of
RAM.
A
Initially
this
Java
one
started
with
473
announced
down
to
about
248
and
here's
the
CPU
that's
using.
This
must
have
been
when
it
was
deploying
the
application
and
loading
things
in,
and
then
we
can
look
at
the
CPU
here.
It's
using
three
MillerCoors,
all
right,
so
I've
taken
up
enough
of
your
time
again.
This
was
totally
just
an
unscripted
little
demo
that
I
wanted
to.
A
Let
you
guys
see
kind
of
the
stuff
we've
been
working
on
in
OpenShift
and
hopefully
pick
your
interest
into
downloading
the
all-in-one
image
and
start
playing
around
with
it,
using
that
for
development,
I'll
create
a
another
video
and
perhaps
a
blog
post
later
this
week
to
show
you
how
to
set
up
hooks
inside
of
your
IDE
for
like
PHP
development.
So
when
you
click
on
save
a
file,
it'll
automatically
instantly
be
updated
in
your
container
for
rapid
application
development.