►
From YouTube: Deploying Container Native Storage on Red Hat OpenShift Container Platform 3.4 - Part 1
Description
Watch us walk you through deploying hyper-converged, container-native storage on OpenShift 3.4
A
A
Hi
and
welcome
to
this
video
presentation
for
Red
Hat,
Container
native
storage,
container
native
storage
brings
you
the
ability
to
provide
a
hyper-converged
storage
solution
for
OpenShift.
This
means
that
you
can
use
the
same
hardware
you're,
using
to
run
your
OpenShift
cluster
to
provide
storage
for
open
ship
for
your
openshift
applications.
You
can
do
this
simply
by
using
existing
storage
devices
attached
to
your
open,
shipped
hardware
or
by
providing
additional
storage
like
SSD
devices.
A
A
A
A
A
In
this
case,
you
need
to
specify
what
the
clusters,
which
are
the
glossary,
fest
clusters
that
you'll
manage
for
this
demonstration.
It
will
be
only
one
and
the
nodes
within
that
cluster.
You
need
to
provide
the
hostname
and
the
IP
address
for
each
node.
Don't
be
fooled
here,
I'm,
just
using
the
IP
address
as
the
OpenShift
host
name
for
this
node,
you
will
need
to
specify
a
zone
that
this
belongs
to
the
dis.
Node
belongs
to.
A
You
will
also
need
to
specify
the
storage
devices
that
cns
will
take.
Control
of
and
manage
for
glossary.
Fs.
Take
note
that
any
devices
that
you
list
must
be
bare
devices
with
no
file
system.
On
top
of
them.
Cms
takes
care
of
creating
the
filesystem
on
the
storage
device
and
you
can
using
it
appropriately
for
Gloster
FS.
A
So,
with
this
topology
file
in
hand,
we
can
just
run
CNS
deploy
topology
that
JSON
and
we
need
to
specify
G
to
tell
the
deployment
script
that
will.
It
will
also
need
to
configure
cluster
FS
on
all
the
nodes.
Here.
It
will
go
over
the
requirements
that
this
node
needs.
This
client
node
that
I'm
using
needs
to
deploy
CNS
on
to
the
OpenShift
cluster.
As
since
you
are
logged
in
to
an
open,
shaped
cluster
already,
it
will
use
that
information
to
deploy
to
deploy
the
cns
pods.
A
So
we
continue
here.
We
want
to
deploy
for
open
shift
and
off.
It
goes
now.
This
process
can
take
about
five
to
ten
minutes,
depending
on
the
network
latency
in
particular,
for
downloading
container
images
to
your
nodes,
hover
with
the
magic
of
Internet
video.
We
just
wait
a
little
bit
here
and
we're
done
so.
A
You
can
see
up
here
that
our
deployment
has
discovered
and
formatted
the
starch
devices
attached
to
our
open
chef
nodes,
and
you
can
see
here
that
we
have
a
number
of
pods
now
running.
We
have
three
gloucester
FS
pods
one
corresponding
to
each
open
shift,
node
that
is
now
providing
gloucester,
FS
storage
and
a
hickety
pod
Hettie
is
the
rest
volume
rest
based
or
restful
volume
management
interface
for
gloucester
FS.
We
have
a
route
up
here
that
provides
access
to
HEC
Hetty.