►
Description
In his latest demo, Veer Muchandi will focus on talking about CloudForms as a management engine for container management environments such as OpenShift.
NOTE: For the latest information on OpenShift 3.1, please visit https://enterprise.openshift.com or subscribe to the OpenShift Blog (https://blog.openshift.com).
A
Hello:
everyone,
this
video
is
about
cloud
forms
as
a
management
engine
for
container
management
environment
such
as
open
shift
or
atomic
enterprise
platform,
open
shift,
Enterprise
shifts
with
cloud
forms
as
its
management
engine,
and
in
that
context,
let's
look
at
how
we
can
use
cloud
forms
as
a
container
management
cloud
forms
as
a
tool
does
a
lot
of
things
other
than
managing
open
shift.
But
for
this
discussion
in
this
video
we
are
just
going
to
focus
on
the
container
management.
A
So
all
the
tabs
that
you
are
seeing
here
are
the
other
features
that
cloud
form
for
us,
but
will
just
focus
on
the
containers
part.
What
you're
seeing
here
is
an
overview
page
under
containers,
and
it
shows
that
there
are
two
open
shift
environments
that
are
being
managed
by
this
cloud
forms
setup,
and
there
is
one
atomic
enterprise
platform
that
is
being
managed
as
well.
These
cloud
forms
can
also
manage
a
coupon
I
discussed
or
as
well,
so
we
are
talking
about
three
clusters
being
managed
by
or
three
providers
being
managed
by
this
environment.
A
It
also
gives
a
summary
of
how
many
nodes
are
there,
how
many
powers,
how
many
containers
services
and
things
like
that
now
moving
on,
if
I
click
on
this
providers
link,
it
takes
me
to
this
provider
staff,
and
you
see
this
three
different
provider
environments
that
I
have
here.
So
let
me
put
it
in
the
list
view
there
is
a
atomic
enterprise
platform
and
the
URL
is
here.
There
is
a.
There
are
two
different
open
shift
environments
as
well.
A
Right
now,
I
can
add
additional
environments
by
clicking
on
add
new
containers
provider,
and
it
gives
me
options
to
add
additional
providers
if
I
have
to
so
I
can
give
a
name.
I
can
choose
what
type
it
is,
whether
it
is
atomic
enterprise
or
openshift
R,
and
then
I
can
provide
a
token
that
I
set
up
in
the
openshift
environment
and
once
I
give
the
token
the
cluster
gets
added
for
this
cloud
forms
environment
to
manage.
A
I
can
also
look
at
all
the
projects
cause
all
these
environments
right
that
it
shows
everything
here,
but
I
can
go
drill
down
into
each
provider,
for
example,
and
I
can
see
all
the
projects
there
are
14
projects
under
this
demo,
v3
provider
right
I
have
14
projects,
16
routes,
the
number
of
services,
replication
controllers
parts,
the
number
of
containers
nodes
image
registry
images.
It
gives
me
a
summary
of
all
the
things
that
are
running
here
and
every
everything
here
is
clickable.
A
So
if
I
click
on
this
project
sit
shows
me
a
list
of
all
the
projects
and
there's
an
one
if
I
go
back
and
click
on
the
routes,
it
shows
me
all
the
application
routes
that
are
available,
so
I
can
look
at
each
route,
for
example
by
getting
into
the
details,
and
it
gives
me
what
is
the
host
name
by
used
using
which
I
can
access
this
route
now
there
is
also
a
monitoring
feature
here.
So
if
I
click
on
this
guy,
it
shows
me
the
time
based
on
timelines.
It
pulls
up
all
the
events.
A
A
It
says
that
so
in
Sopot
got
so-and-so,
bill
got
started
in
a
pod,
so
you
can
monitor
all
the
management
events
it
can
change
the
frequency
the
interval,
as
well
as
how
many
days
back
you
want
to
go
to
kind
of
stuff
here
now,
I
can
also
look
at
the
list
of
nodes.
You
can
see
that
this
cluster
has
four
nodes
and
when
master,
that
is
also
acting
as
an
or
right
and
then
I
can
drill
down
into
each
and
every
individual.
A
Nor
look
at
what
the
footprint
of
the
node
is
and
now
I
can
also
see
what
routes,
what
services,
what
replication
controllers
and
pods
are
running
on
that
particular
node,
so
affect
become
these
parts.
It
shows
me
that
there
are
these
X
number
of
parts
running
on
that
particular
node,
which
is
node
1
right.
So
you
can
drill
down
from
a
bunch
of
clusters
to
a
single
cluster
and
from
single
cluster
to
each
node
to
see
what
is
going
on
on
each
box.
It's
going
back
so
now
back
to
the
cluster.
A
There
is
another
thing
that
is
pretty
useful.
This
is
a
topology
view
when
I
click
on
the
topology
view.
It
shows
that
there
is
an
open
shift
cluster
and
all
the
things
that
are
running
in
that
cluster.
So,
for
example,
looking
at
the
labels
here,
which
explained
what
these
symbols
mean,
the
these
things
are
nodes
right.
So
it
shows
there
are
one
two
three
four
five
nodes
here
and
then
there
are
routes,
services,
containers,
parts
and
replicators,
each
one
shown
with
their
own
symbol.
A
Now
things
of
interest
here
you
can
see
when
I
hover
over
this
guy,
this
particular
part
has
failed
and
it
is
shown
with
the
red
circle
showing
that
test
failed,
whereas
the
other
pods
are
actually
running
right
and
there
are
some
that
are,
for
example,
this
container
is
gray
and
it
shows
that
the
status
is
terminated.
It's
it's
done
with
this
job
right.
So
that's
that's.
A
How
you
can
look
at
the
topology
view
and
decipher
some
information
of
your
interest
now
another
way
of
using
this
is,
let's
say,
I
disabled
everything
by
clicking
on
these
symbols.
Right
and
now
there
is
an
open
shift
cluster
if
I
just
want
to
see
all
the
nodes
that
are
on
this
cluster
I.
Just
click
on
the
notes
now,
I
see
that
there
are
five
nodes
here.
A
I
can
display
the
names
and
it
shows
the
names
of
each
of
these
nodes
right
and
then,
let's
say
I
want
to
see
all
the
containers
that
are
running
on
these
nodes.
Now
the
containers
come
up,
but
let
me
take
off
the
names
here.
The
containers
come
off,
but
they
are
not,
although
they
are
running
on
the
nodes,
they're
not
seen
as
a
as
connected
to
the
nodes
right
now,
let's
enable
the
parts.
A
Now
you
see
that
the
containers
are
running
in
the
context
of
a
pod
on
a
particular
node,
so,
for
example,
this
particular
part
has
two
containers
running
in
it
right
when
I,
who
or
it
is,
is
a
logging
part
and
it
has
a
Cabana
container
running
and
it
has
another
cabana
proxy.
Two
containers
to
talk
containers
are
running
inside
this
part.
It's
pretty
useful.
A
You
can
enable
and
disable
whatever
you
want
to
see
and
what
you
don't
want
to
see
same
thing
for
the
entire
set
of
clusters
that
are
being
managed
by
the
cloud
forms
engine
can
be
seen
in
the
topology
view
on
the
top
level
right.
So
if
I
click
on
the
topology
at
the
top
level,
now
I
am
seeing
multiple
open
shift
clusters
here.
This
is
one.
This
is
another
and
there
should
be
a
atomic
enterprise
platform
circle
somewhere
right.
A
So
there
are
so
if
I
disable
all
these
guys
again
with
the
ease
of
it
now
I'll
start
seeing
the
so
there
are
three
different
and
ones
that
I
am
managing.
This
guy
has
eight
nor
syska
has
five
nodes,
and
this
guy
doesn't
have
any
nodes.
That's
that's
how
I
can
use
this
topology
where
and
I
can
see
the
things
that
I'm
interested
in
now
I'm
back
again
to
the
cluster
summary.
Another
thing
there
are:
it
shows
that
there
are.
There
is
one
image
registry
here.
This
is
the
internal
registry
on
on
running
on
openshift.
A
Let's
click
on
that
to
see
what
what's
in
there
here,
it
shows
the
IP
address
of
that
registry.
This
is
the
open,
shipped
generated
service
IP
for
the
registry.
Now,
let's
see
what
images
are
there
in
this
case
that
there
are
ten
images
in
this
registry
and
there
are
thirteen
containers.
So
let's
look
at
what
those
images
are
and
it
gives
the
list
of
images
right
and
they're
darker
IDs
as
well.
A
What
I
can
do
is,
for
example,
select
one
of
this
image
and
get
into
additional
details
of
what's
the
full
full
name
of
this
image.
The
docker
ID
of
this
image
and
I
wanna
also
initiate
something
called
a
smart
state
analysis
to
look
at
all
the
packages
that
are
inside
this
image.
So,
for
example,
once
I
have
this
image
selected
I
can
go
to
configuration
and
say
I
want
to
perform
smart
state
analysis.
This
will
schedule
a
job.
A
It
will
take
some
time
to
collect
all
the
packages,
so
once
the
smart
state
analysis
is
done,
it
will
have
this
configuration
information
with
all
the
packages
that
are
part
of
this
image
listed
here.
So
I
can
on
this
guy
at
that
one
of
time
and
look
at
all
the
details
of
all
all
the
packages
that
are
involved
in
that
image.