►
From YouTube: OpenShift 3 Beta Demo Part 1: OpenShift Concepts
Description
Veer Muchandi, middleware specialist at Red Hat, has created a three-part series demoing OpenShift 3. This first video outlines the OpenShift 3 technology stack, how OpenShift 3 is different from version 2, basic concepts, and architecture.
Part 2: http://youtu.be/sjwH8RiDxuY
Part 3: http://youtu.be/OzkoEJP_Rmo
A
A
Most
of
you
may
already
know
that
open
shift
version
3
is
designed
to
run
docker
containers
now
docker
provides
a
means
of
packaging
applications
in
lightweight
containers
right
and
these
containers
are
smaller
than
virtual
machines.
They
have
improved
performance
and
they
are
flexible
to
run
in
multiple
environments.
So,
but
while
docker
defines
a
container
format
and
builds
and
manages
the
individual
containers,
you
would
still
need
an
orchestration
tool
to
deploy
and
manage.
Sets
of
these
docker
containers
and
kubernetes
is
a
tool
for
tool
for
that.
A
It
has
been
designed
to
take
advantage
of
powerful
technology
available
in
rel
7
and
a
revelatory
host
uses
a
saline
X
to
provide
strong
safeguards
in
multi-tenant
environments
when
multiple
containers
are
running
on
the
same
host
and
also
provides
the
ability
to
perform
atomic
upgrades
and
rollbacks,
enabling
quicker
and
easier
maintenance
with
less
downtime.
Now,
both
rel
7
and
the
automic
can
be
used
for
OpenShift
and
relati.
Me
comes
pre-installed
with
darker
and
kubernetes.
A
Now,
on
the
top
of
this
container
driven
model
and
orchestration
using
kubernetes
is
the
containerized
services
that
OpenShift
provides.
The
first
thing
is
X
Pass,
which
is
like
application
server
on
the
top
of
open,
shipped
JBoss
EAP,
for
example,
right
our
integration
on
OpenShift,
using
JBoss
fuse
or
BPM
BRMS
mobility,
for
example.
All
these
are
XPath
services
that
come
on
the
top
of
a
pass.
A
All
these
nice
things
put
together
is
what
you
get
in
in
the
technology
stack
for
openshift
version
3.
Let's
look
at
what's
different
between
openshift
version
3
and
the
earlier
versions
of
open
shirt,
specifically
the
openshift
version
2,
that
is
so
the
new
base
OS
is
going
to
be
rel
7
instead
of
rel
6th
or
x,
in,
for
example,
in
an
open
shift
version
that
we
are
using
right
now.
It
uses
rel
6.6,
which
will
be
moving
to
rel
7
in
case
of
V
3.
A
Now
the
containers
are
going
to
be
docker.
Containers,
instead
of
gears
now
gates,
were
using
the
same
technology
says
what
docker
is
using
today
like,
for
example,
in
in
Gears.
We
would
be
there
still
Linux
containers
and
they
were
using
SELinux
there.
They
were
using
Linux
control
groups
and
the
technologies
are
the
same.
However,
the
packaging
format
in
docker
is
different,
and
since
that
is
kind
of
standardized
across
the
industry,
these
days
we
have.
We
are
moving
towards
the
darker
based
model.
A
The
new
orchestration
engine,
instead
of
a
openshift
broker
in
case
of
version
2,
that's
going
to
be
replaced
by
kubernetes,
specifically
kubernetes
master,
will
take
the
place
of
broker.
The
new
packaging
model
for
technologies
would
be
docker
images
in
place
of
open
shift
cartridges
in
in
version
2,
the
new
routing
layer,
the
platform
routing
layer
would
replace
the
node
based
routing
right
and
you
get
better
better
services
and
better
developer
experience.
A
A
There
is
a
con.
The
first
concept
that
we
would
want
to
understand
is
a
part
and
a
part
would
run
the
docker
containers,
so
a
single
part
would
get
an
IP
address
and
you
can
run
multiple
docker
containers,
multiple
related
docker
containers
inside
each
pod.
Now
the
pod
gets
an
IP
address,
whereas
each
of
those
containers
would
share
the
all.
The
containers
running
inside
a
pod
would
share
the
port
space
inside
that
inside
that
part,
so
a
pod
goes
out
for
comes
down
at
the
same
time.
A
So
all
the
containers
inside
the
pod
go
down
together
with
the
power
or
come
up
together
with
the
power,
so
you
would
put
a
set
of
related
containers,
docker
containers
inside
a
part.
So
in
this
example
that
you
are
seeing
here,
the
my
sequel
database
and
the
administration,
the
PHP,
my
admin
are
running-
are
two
different
containers
running
within
the
same
part.
Now
my
sequel
container
would
expose
port
3306
to
connect
to
a
to
the
my
sequel
database,
which
is
the
standard
port
for
my
sequel
and
PHP.
A
My
madman
would
use
port
8080,
and
these
two
ports
are
within
the
same
part,
and
the
pod
itself
is
getting
an
IP
address
right
now,
when
you
are
thinking
about
in
runtime
how
these
pods
are
going
to
look
like
when
you
are
thinking
in
terms
of
the
host
see
all
the
way
at
the
bottom.
The
hosts
are,
a
host
could
be
running
multiple
parts
on
the
top
of
it
and
each
part
would
contain
one
or
more
containers
right.
So
a
host
a
physical
host
is
running
one
or
more
parts.
On
the
top.
A
There
is
another
concept
called
service
which
kind
of
load
balances
the
a
group
of
parts
of
the
same
type
together
now
think
of
it
as
multiple
instances
of
the
single
part.
They
are
all
load
balanced
by
other
service.
Each
part
gets
a
label,
and
a
service
would
use
a
label
in
this
case.
This
verb
is
the
label
and
both
these
parts
of
the
same
type
of
parts
and
they
are
getting
the
label
Lib,
and
these
two
parts
are
grouped
together
by
the
service
and
they
are
load-balanced.