►
Description
Testing with a small OpenShift POC environment is an easy way to experiment with container DevOps and the deployment process. Transitioning from a POC to a large scale production requires much planning around scale, HA, backup/recovery, security, change management and collaboration with other IT units. Learn about the governance, processes, deployment and platform considerations required for putting OpenShift into production. We will also highlight how HPE can accelerate this transition through the OpenShift solution that we are jointly developing with Red Hat.
Learn more: https://agenda.summit.redhat.com/
A
So
you
guys,
okay,
as
far
as
our
voice,
the
you
guys
can
all
hear
or
cool
all
right
sounds
good.
So
this
is
the
agenda
for
today.
So
what's
a
little
bit
about,
you
know
bringing
containers
into
production.
You
know
some
are
different
adoption
paths
and
some
of
the
different
considerations.
While
we
tend
to
be
more
technology
people,
we
know
it's
a
really
combination
of
people,
process
and
technology.
So
we'll
talk
a
little
bit
about
that.
A
Some
of
the
technology
considerations
and
obviously
you
know
when
we
look
at
containers
and
one
of
the
reasons
we
had
Mike
here-
talk
about
the
data,
protection
and
container
data
management
is
at
the
end
of
the
day.
Data
is
critical
right.
Something
goes
wrong
in
your
containers.
You
could
basically
we
spend
that
up
again.
Something
goes
bad
with
your
data
you're
toast.
So
the
data
management
piece
is
really
critical
piece
and
we'll
definitely
cover
that
later
on.
A
A
We
will
hold
questions
at
the
end,
if
you
guys
don't
mind,
save
couple
minutes
all
right,
so
container
adoption
options
just
before
we
start
so
how
many
of
you
guys
are
doing
POC
above
containers
just
do
evals
cool
how
many
are
actually
going
into
production,
maybe
like
half
of
you
yeah?
Why
so?
What
we
have
seen
is
you
know.
Hpe
is
a
large,
so
we
we
have
very
large
customers.
I
would
say
about,
like
20
percent
of
our
customers
are
engaged
in
pocs
and
maybe
five
to
ten
percent
of
them
are
looking
at
containers.
A
But
the
good
news
is
every
single
one
of
our
enterprise
customers
that
we
speak
with
or
I
have
container
plants
alright,
so
which
is
good,
there's
different
ways
when
it
comes
to
deploying
containers
and
that's
why
I
kind
of
ask
their
questions,
so
our
customer
tends
to
look
at
different
type
of
journeys.
So
the
easiest
way
to
kind
of
look
at
containers.
You
take
some
simple
off-the-shelf
applications
like
my
sequel
and
some
Microsoft
applications.
You
can
just
grab
a
container
version.
A
You
know,
try
it
out
internally
before
your
IT
organizations
and
just
look
at
the
benefits
right
and
the
fast
role
to
market
and
just
get
a
quick
sense
of
learning,
but
a
lot
of
our
customers
I
actually
look
at
two
choices.
One
word:
they
are
retooling
legacy
based
applications.
You
know
there's
like
hundreds
and
thousands
of
these
applications
where
there's
UNIX
page,
you
know
solaris
IBM
windows-based,
so
a
lot
of
them
are
looking
at.
How
do
we
transition
these
applications
to
containers?
So
I?
Think
that's
one.
A
So
it's
not
as
simple
as
you
know,
going
to
containers,
it's
the
whole
transformation
right
and
that's
the
impact.
So
those
are
the
things
that
we'll
talk
about
a
little
bit
because
at
the
end
of
the
day
you
know
it's
one
thing
to
move
for
my
simple
POC
when
you
look
at
maybe
tier
2
applications-
and
you
know
you're
not.
The
point
is
a
scale
to
moving
to
consider
two
containers.
So
there's
some
key
considerations.
A
As
far
as
the
impact
on
your
kind,
your
organization
and
a
lot
of
them
will
be
no
brand
new
adaptive
release
process.
You
know
your
whole
governance
around
how
you,
how
the
different
organizations
sign-off,
for
example,
for
these
applications.
Of
course
there's
you
know
technologies
and
platform
considerations,
so
one
things
that
we'll
cover
is
in
a
wide
platform
matters
right,
because
we
know
at
the
end
of
the
day,
you
guys
have
your
choices.
You
could
take
all
your
containers
and
move
it
to
the
cloud
or
actually
keep
them
on
Pam.
A
So
it's
the
best
capex
not
backs
type
of
decisions,
so
touched
a
little
bit
about
that.
Certainly
those
are
the
things
that
we
hear
a
lot.
So
again,
it's
not
just
a
pure
technology
play
when
people
look
at
moving
containers
into
production,
okay,
so
within
HPE
we
actually
went
through
this
process
ourself
with
our
IT
organizations.
So
you
know
we
were
doing
tens
of
thousands
of
bills.
You
know
if
you
guys
are
familiar
with
one
of
our
software.
It's
called
one
view
if
they
it's
a
platform
management
software.
A
A
You
know
DevOps
process
you're,
looking
at
your
developers
doing
police's
every
single,
maybe
every
single
week
or
so
you
know,
there's
certainly
implications
as
far
as
organization
is
concerned.
Right
people
need
to
work
with
it
tightly
together.
Now
you
have
to
remove
these
boundaries.
You
know
there's
constant
meetings,
so
it's
not
as
simple
as
the
product
manager
or
the
business
owners
just
drop
off
the
product
requirements
like
what
we
traditionally
do.
It's
gonna
walk
away
and
let
the
developers
roll
on
their
own
right.
So
it's
constant
tight
integration
among
these
organizations
a
lot
of
times.
A
You
also
get
into
what
we
see
potential
politics.
So
with
this
new
model
in
a
suddenly
certain
organizations,
they
control-
and
sometimes
that's
within
IT
ops
in
lessons,
because
you
know,
there's
more
control
being
given
to
the
development
teams
as
far
as
police's
are
concerned,
so
there's
definitely
organizations
their
roles
and
responsibilities.
A
So
these
are
some
of
the
different
type
of
cut
the
before
and
after
you
know
it's
more
from
a
commanding
control
to
what
we
call
integrated
and
empower
that
development
teams
right,
so
just
interesting
and
adult
so
Amazon,
so
Amazon
in
the
old
days.
You
look
at
the
Amazon
started
many
many
years
ago,
so
they
have
these
big
monolithic
applications
which
runs
their
website
and
they
realize
that's
not
happening
because
they're
doing
these
releases
you're
every
many
many
months.
A
So
this
had
building
micro
services
and
adopting
containers
right
and
what
they
have
done,
what
they
look
at,
what
they
call
a
two
piece
of
model.
So
the
two
piece
of
model
is
your
development
teams.
You
only
be
large
enough
to
feed
two
pieces
so
anytime,
you
have
your
development
teams,
that's
larger
than
you
can
feed
two
pieces
that
you've
to
watch
the
development
team
again,
how
kinds
about
building
agile
development
teams,
building
ownerships
and
the
tapping
micro
services.
A
So
it's
an
interesting
spin
on
this,
so
it's
definitely
a
lot
of
implications
for
this
new
model.
For
example,
you
know
the
whole
change
control
is
different
right.
You
know
in
the
old
days,
instead
of
going
to
ite
request
to
change
control
so
now
we're
both
DevOps.
You
go
to
a
CICP
pipeline
like
Jenkins
or
whatever
favorite
CI
CD.
You
guys
want
to
use
and
everything
is
recorded
and
you
could
put,
for
example,
manual
Gator
process
in
there,
so
it
makes
the
whole
change
controller
software
release
process
much
much
more
faster.
A
The
other
thing
what
we
see
is,
instead
of
having
the
developers
control,
just
build
everything.
It's
a
nice
cooperations.
It
should
be
a
nice
cooperation
between
the
teams
right,
so
the
developers
are
free
to
build
their
container
images,
but
was
was
the
IT
ops
people
there?
You
guys
proved
us
or
ninety
apps
should
control
the
type
of
base,
images
that
you
have
sanctioned
and
you
put
out
like,
for
example,
with
some
of
the
open
chef
catalogs
that
your
developers
should
have
access
to
right.
A
It
should
not
be
kind
of
the
wah
wah
with
where
they
could
just
download
stuff
on
github.
You
just
want
to
run
anything
they
want.
Of
course,
this
is
home
security
and
ownership,
which
we
will
talk
about
so
in
the
past
ops
kind
of
own
security.
So
now,
with
this
new
model,
where
your
developers
might
be
adopting
these
first
images
from
github
or
you
know,
from
Red
Hat's
Red
Hat's
repository
they're
downloading
these
images,
so
security
gets
kind
of
move
more
upstream
to
your
business
owners
and
developers.
A
A
So
there's
actually
a
lot
of
IT
organizations
who
leverages
the
party
consultants
and
there's
lots
of
consultants
like
centures
who
goes
in
and
do
these
transformation,
it's
actually
pretty
complex.
So
again,
I
think
what
we're
trying
to
say
is
just
by
wrapping
your
technologies
around
container.
Let
me
get
you
fully
to
this
agile
kind
of
release
model
that
you
guys
are
looking
for
right.
It's
got
to
be
people,
process,
technology
and
investment.
Ok,
technology
considerations,
so
just
because
you
know
we
know
container
is
relatively
new.
A
You
know
just
because
they're
containers,
it
doesn't
mean
they're
from
IT
organizations.
You
know
you
need
to
neglect
lifecycle
management,
orchestration
security,
everything
you
guys
are
comfortable
with
for
the
IT
side
needs
to
apply
for
containers
right.
The
difficult
part
is
with
containers
a
lot
of
these
tools
that
breathily
brand-new.
So
it's
not
easy
to
take.
Some
existing
tools,
for
example,
like
security,
is
a
good
example.
A
So
you're,
basically
looking
brand
new
next
generation
type
of
tools
that
you
know
you
might
not
have
long
experience
with,
but
yet
at
the
same
time
you
want
to
roll
this
into
production.
You
know
you
need
to
address
that.
You
know
from
from
IT
arts
perspective
and
that's
one
of
the
reasons
we
saw.
You
know
as
much
as
customers
like
Fairmeadow.
We
also
saw
a
strong
number
of
customers
tokens
to
just
roadies
continuous
on
top
of
VMs,
whatever
p.m.
A
flavors,
because
they're
comfortable
running
VMs,
you
know
it's
just
in
other
applications
running
on
top
of
VMs
and
VM.
Today
the
support
all
these
type
of
capabilities
instead
of
bringing
in
in
a
brand-new
tooling
and
going
through
the
whole
corporate
governance
process
right.
So
that's
another
option
so,
but
something
to
keep
in
mind.
So
we
just
touch
upon
you
know
a
couple
of
them
before
I
turn
it
over
to
my
colleague
Mike.
So
security
is
obviously
very
important.
A
So
when
you
look
at
security,
it's
more
than
just
your
typical
network
intrusion
protection,
so
we
look
at
security,
at
least
from
the
HPE.
You
know
from
the
bottom
up.
So,
for
example,
with
a
gent
M
platform.
We
have
something
called
rural
trusts,
so
why
this
is
important
right
because
they
seem
you
guys,
use
white
boxes.
So
you
get
these
firmware,
updates
or
BIOS
updates
from
your
vendor,
so
god
knows
where
they
come
from
and
actually
I
believe.
A
There
was
a
famous
hacked
because
somebody
up
leveraged
some
updates
firmware
updates
from
a
white
box
vendor
that
has
security
flaws
in
there.
So
within
HPE
without
platform,
we
actually
sign
everything
that
we
release.
So
you
know
that
comes
from
HPE
and,
of
course,
on
the
OS
area.
There's
various
you
know:
OS
selinux
OpenScape.
You
know
things
that
you
could
secure
scanning
on
the
OS.
So
that's
just
a
lot
of
good
stuff
happening
on
OS
area
and
within
HPE
we
actually
have
a
product
called
wazza-wazoo,
which
is
work
low,
aware,
secure
linux.
A
So
we
offer
that
as
part
of
our
open
shift
package,
which
they
quickly
looks
at
the
operating
system
of
security,
clinic
quality,
ohm
parameters
or
we
actually
look
at
the
NIST
security
recommendations.
So
so
we
look
at
that
from
from
an
OS
perspective,
but
the
end
of
the
day
is
really
your
registry,
your
container
registry
and
also
your
containers.
So
your
things
what
I
know
can
take
containers.
A
How
do
you
try
to
peek
in
there
right
to
make
sure
that
this
something
that's
doing
something
wrong,
and
also
with
your
registry
with
your
developers,
downloading
stuff
of
the
internet?
You
know
you
want
to
make
sure
that
you
have
fakest
scanning
capabilities,
so
there's
a
lot
of
tools
out
there
like
black
belt,
for
example,
so
there's
a
third
party
partner
or
valves
called
aqua
technology
who
basically
could
scan
in
all
these
code,
so
making
sure
these.
A
If
these
images
that's
being
used
within
the
pipeline,
my
actually
secure
you
could
blast
this
and
you
could
actually
fear
your
access
control.
You
know
make
sure
that
the
right
developer,
you
know,
go
to
certain
type
of
gates
and
certain
type
of
developers
with
the
right
privileges.
You
know,
could
then
ship
things
into
production
so
make
sure
you
build
kind
of
access
control
into
your
whole
CI
CD
pipeline
as
to
who
could
do
what
right,
but
continuous,
is
definitely
pretty
secure
so
from
a
third-party
applications.
A
A
So
what
you
want
to
do
is
you
know,
once
these
containers
are
spinned
up,
be
able
to
detect
abnormal
patterns
so
for
whatever
reason
so
in
case,
if
your
developer
happen
to
have
some
broad
containers,
for
whatever
reasons
you
want
those
type
of
security
software
to
build
attack
like,
for
example,
if
that
container
is
trying
to
open
up
some
ports
right,
try
to
access
some
resource
where
it's
not
supposed
to.
So
you
want
your
security
software
to
be
to
flag
those
alarms
and
potentially
just
kill
off
those
containers.
A
So
again,
I
think
you
might
want
to
look
at
aqua
twist
lock
and
we
also
have
a
partnership
with
a
company
called
sis
and
there's
some
pretty
interesting
stuff,
because
they
do
a
combination
of
both
monitoring
the
security
or
roll
into
one
product,
and
so
that's
something
that
we
offer
also
from
our
stack.
So
that's
the
security
side,
I
think
just
in
general,
just
education
process
right.
Yes,
because
these
relatively
new,
so
you
guys
start
moving
these
applications,
giving
the
developers
more
control
on
the
whole
CI
CD
release
process.
A
You
know,
developers
a
lot
of
times
needs
to
be
sensitized
to
some
of
these
security
implications
right
immature
they
for
security,
best
practices,
so
I
think
just
having
the
right.
Education
is
really
important
for
security
awareness
and
for
the
development
teams,
okay,
so
monitoring
so
monitoring.
It's
also
definitely
key
I
mean
for
IT
ops.
Monitoring
is
critical
for
any
any
deployment.
So
you
need
to
look
at
monitoring
from
kind
of
a
host
order
within
kubernetes,
look
at
the
kubernetes
infrastructure
or
your
services.
A
There's
not
a
lot
of
from
what
we
know
not
a
lot
of
these
container
based
monitoring
software.
That's
out
there
from
a
legacy
vendor.
So
a
lot
of
new
stuff
late
date
at
all,
so
Red
Hat
has
call
forms,
but
again
be
you
know
we
partnered
with
cystic,
because
we
thought
they
were
pretty
good
monitoring
software,
so
they're
things
you
guys
want
to
look
at
formal
monitoring.
Software
is
making
sure
they
have.
These
can
can
be
traces
and
dashboards.
So
you
don't
want
to
build
up
like
20
30
different,
your
own
monitoring
scripts
yourself.
A
So,
for
example,
we
know
but
cystic
they
have
like
30.
40
can
basically
monitor
matrix
for
various
off-the-shelf
containers
for
kubernetes,
for
some
of
the
open
source
databases
for
example.
So
that's
one
things
I
would
tend
to
look
at
and
when
you
look
at
some
of
this
monitoring
software,
ok
so
last
thing
before
I
turn
over
the
mic
is
resource
management.
So
you
guys
are
familiar
this
kubernetes
manifest
right.
You
need
to
set
developers,
you
need
to
specify
CPU
or
resource
usage
usage
a
lot
of
times.
Developers
are
pretty
conservative
right,
not
my
money!
A
Don't
care
so
I'm
gonna
specify
the
most.
You
know
CPU
consumption
and
resource
usage.
Alright,
so
what
you
want
to
do
is
make
sure
clear
some
really
good
resource
management
software
out
there,
or
else
you
would
be
running
you
would
have
lot
these
containers.
That's
sucking
up
like
empty
spaces,
especially
if
you
have
these
containers
you're
sitting
over
AWS
you'll
be
paying
through
the
nose
as
far
as
buildings
are
concerned,
so
we
actually
have
been
working
with
third-party
core
densify.
So
there's
a
bunch
of
third
parties
out
there
who
looks
at
these
resource
management
right.
A
So
certainly
we
think
the
leaders
are
in
this
space
is
densify
or
to
capernaum
--ax,
so
you
guys
might
want
to
take
a
look
into
them,
because
what
they
do
is
take
a
look
at
your
resource,
consumptions
of
on-prem
burn
off
time
and
give
you
actually
a
projection,
not
only
what
you
have
right
now,
but
also
in
the
future,
and
they
could
tell
you,
for
example,
which
hosts
how
to
use
or
likely
use
so
we've,
some
of
the
use
cases
we
have
seen.
We
saw
a
customer
saving,
hundreds
or
thousands
of
dollars.
A
You
know
being
able
to
build
that
map
of
resource
consumption
on
their
containers.
So
it's
something
that
you
guys
definitely
look
at.
It's
not
something
that
people
actually
think
about,
but
once
you
roll
this
into
large-scale
productions,
you
definitely
want
to
have
a
very
strong
resource
management
capability
out
there.
A
So
I
guess
in
the
interest
of
time,
I'm
gonna
skip
this
one
make
sure
my
colleague
could
talk
about
storage
and
data
management
if
I
have
time,
I'll
jump
back,
but
you
have
this
in
your
slides.
So
this
is
just
some
recommendations.
You
know,
as
you
guys
look
at
production
right,
what
types
of
size
of
configuration,
but
you
want
to
choose
your
depending
on
large
scale,
small
medium,
so
special
size,
small,
medium
and
large.
So
you
have
time
I'll
jump
back
to
it,
but
I
want
to
miss
you,
my
colleague
at
some
time.
A
B
Right,
excellent,
excellent,
so
I'm
gonna
talk
about
a
few
minutes
about
what
we
do
with
the
data
management
and
data
protection
and
persistent
storage
for
containers
in
general.
So
a
little
bit
of
background
is
that
so
I
come
from
limbo
and
we
HP
also
has
a
storage
platform
called
prepar
and
we
provide
the
data
services
that
each
of
those
platforms
provide.
We
abstract
up
into
OpenShift
and
and
and
darker
and
so
forth
right.
So
those
are
external
storage
arrays,
so
to
speak
and
talking
to
customers
and
prospects
for
the
last
two
years.
B
My
job
has
been
nothing
but
kind
of
analyzing,
the
use
cases
and
so
forth.
For
persistent
storage
and
some
of
the
the
use
cases
that
we
see
there
are
popular
out.
There
is
obviously
the
CI
CD
right
and
we
have
a
bunch
of
different
features
for
CI
CD.
That
will
help
you
to
orchestrate
your
your
pipeline
more
efficiently.
B
So
a
lot
of
popular
use
case
we
have
is
lift
and
shift.
We
see
customers
want
to
migrate
their
traditional
applications
that
they
have
running
in
their
infrastructure.
This
could
be
anything
from
lamp,
apps
and
new
yorky
systems.
They
might
be
migrating
from
virtual
machines
to
bare
metal.
Our
our
container
integration
have
tools
to
allow
you
to
move
your
workload
from
your
legacy
environment
into
a
container
and
carry
the
data
with
you.
B
That
is
a
feature
that
we're
pretty
alone
with
in
the
market
at
the
minute
so
and
that
allows
you
to
kind
of,
even
if
your
application
is
20
years
old,
it
probably
have
it's
like
traditional
kind
of
silo
type,
but
you
can
break
down
the
monolith
and
legacy
application.
They
always
have
some
state
somewhere
right.
They
weren't,
born
2018,
were
ephemerality
and
and
and
and
distributed
storage
was
pretty
common
today,
all
right,
but
migrating
those
legacy
applications.
You
still
need
a
reliable,
persistent
storage
solution.
B
You
need
to
bring
your
SLA
s
and
s
loz
into
your
container
deployment
with
them.
A
very
popular
pattern.
I'm
sure
that
many
of
you
recognize
this
that
IT
operations
they
see
container
frameworks
such
as
kubernetes
and
open
shifts
and
and
so
forth,
as
as
means
to
deploy
applications
for
their
organization,
all
right,
so
we're
an
engineering,
heavy
organization
that
nimble
we
use
all
the
Atlassian
tools
right
and
and
those
you
can
run
in
containers
today,
supported
by
the
vendor.
B
The
elk
stack
is
another
popular
tool
for
the
operations
team
to
deploy
in
containers
and
again
they
all
require
persistent
storage
for
for
those
containerized
applications
again,
lamb,
pops-
it's
like
another
popular
use
case
so
container
as
a
service,
is
another
one
right,
so
the
IT
ops,
folks
that
want
to
monetize
their
their
infrastructure.
They
basically
want
to
deploy
open
shift
clusters
for
others
to
consume
right
and
key
to.
That
is
also
that
they
need
to
consume
persistent
storage
in
a
safe
and
reliable
way
and
make
sure
that
data
is
being
backed
up.
B
They
have
that
right,
right,
I,
ops,
limits
said
and
so
forth,
and
and
and
have
controls
for
for
noisy
neighbors
and,
and
things
like
that
right,
so
that
we
that
we
see
a
lot
that
the
service
providing
the
service
providers
bays,
that
they
require
features
that
are
Amazon
like
from
their
volumes
right.
So
they
need
to
be
able
to
provision
our
thousand
I
of
for
him
to
a
certain
application,
a
certain
user,
and
they
can
then
monitor.
B
So
something
I
want
to
compare
it.
Real
quickly
is
especially
on
the
topic
here
when
we
move
from
open
shift
from
from
POC
to
production.
Is
that
the
paradigms
that
are
out
there
for
persistent
storage
they're
there
they're
very
different
right,
so
in
nimble
and
3por,
for
instance,
we
wear
like
an
external
storage
solution
that
is
basically
orchestration
is
being
made
in
the
background
to
provision
a
volume
format.
A
file
system
attach
that
to
the
host
and
have
the
container
by
mount
into
that
container.
B
It's
a
very
simple
construct
right
and
the
software-defined
storage
solutions
out
there
they're
fairly
they're
very
different
on
how
they
protect
their
data
on
how
data
is
stored,
how
its
replicated
and
it
doesn't
really
have.
It
might
not
have
the
right
data
services
that
you're
looking
for
and
so
forth
in
our
traditional
enterprise.
So
I
just
want
to
bring
this
comparison
sheet
up
here.
Right
and
I.
Don't
want
to
talk
to
each
and
every
point
here,
I
just
wanted.
B
These
are
like
learnings
that
we've
had
from
from
from
from
our
customers
they're,
where
they
basically
deployed
software-defined
storage
in
their.
You
know,
proof-of-concept,
environment,
and
the
thing
is
that
the
developers
love
it
because
they
can
deploy
it
on
their
laptop
and
be
productive
from
day
one
and
somehow
that
slips
into
the
green
field
and
further
it
slips
into
production
right
and
some
of
these
software-defined
storage
solutions
that
they're
not
built
for
the
type
of
scale
of
to
handle
enterprise
applications
right.
B
So
the
CIO
might
come
and
ask
for
so
what's
the
ocsla
even
and
rpoS
and
RTOS
for
for
this
particular
data,
and-
and
they
might
not
even
be
aware
of
that,
the
the
rights
are
not
even
consistent
for
the
application.
They
don't
know.
If,
if
how
to
restore
from
snapshots,
they
don't
know
if
the
data
has
been
replicated
to
a
different
site
or
into
the
cloud
or
or
whatnot
right.
So
because
migrating
traditional
enterprise
apps
into
containers,
the
the
stores
requirements,
usually
don't
change
right.
B
So
that
is
something
that
we
need
to
be
aware
of
when
we
migrate
stateful
applications
over
to
open
ships.
So
I'm
going
to
do
some
promotion
here.
What
we
do
here
with
in
terms
of
integration,
we
have
we
integrate
into
all
the
major
kind
of
frameworks
for
containers,
OpenShift,
we're
OpenShift,
primed,
we're
part
of
the
readiness
program
we're
also
looking
into
going
down
a
certification
route
with
the
weed
rat.
We
have
certified
plug-ins
for
docker.
We
integrate
very
well
with
upstream
kubernetes.
B
We
interrupt
with
the
external
volumes
provider
in
in
in
vessels
and
and
eCos
using
the
dr.
volume
driver
isolator.
Our
storage
platforms
also
have
very
comp
and
comprehensive
REST
API,
so
you
can
kind
of
integrate
this
into
any
type
of
DevOps
system
that
you
might
have
right.
So
we,
whatever
the
form
and
pattern
you
have
with
ansible
or
poverty,
we
can
distort
our
form.
You
manage
just
like
any
any
node
in
your
infrastructure.
B
We
have
very
powerful
tools
and
integration
into
the
public
cloud,
especially
on
the
nimble
side,
where
we
can
replicate
data
into
our
storage
as
a
service,
as
we
happen
that
we
have
on
a
shore
and
Amazon.
We
support
multiple
use
cases
on
how
you
can
do
on
ramping
up
your
data
from
from
a
containerized
containerized
app
that
you
have
on
Prem
absolutely
cloud.
B
We
also
want
to
make
sure
that,
from
an
Operations
standpoint
that
this
is
a
simple
and
easy
to
graph,
so
we
have
a
bunch
of
capabilities
that
allows
you
to
set
all
these
like
characteristics
of
the
storage
in
provision.
That
makes
sense
for
your
particular
workload
and
and
the
the
applications
being
being
deployed
so
and
I'm
gonna
talk
a
little
bit
about
the
next
few
slides
here.
Excuse
me.
B
So
the
persistent
storage
platform
for
read-out
OpenShift
that
we
have
supports
OpenShift
contain
a
3.5
to
3.9.
We
also
support
best
effort
with
the
OpenShift
origin.
If
your.
If
you
want
to
run
that
in
your
dev
and
test
environment,
for
instance,
the
integration
is
very
simple:
we
are
the
Flex
volume
plug-in
that
is
available
in
kubernetes
and
OpenShift
allows
vendors
as
ourselves
to
write
flex
volume
drivers.
B
B
Today
this
is
using
the
dr.
volume
api,
so
it
is
all
built
on
the
open
api
sand
and
the
the
Flex
volume
driver
and
a
provision
er.
It's
it's
an
open
source.
It's
open
open-source
software
available
on
github,
but
we've
integrated
that
into
our
product,
so
because
we
did
a
lot
of
investments
in
in
our
container
journey
with
docker,
so
we
just
reusing
our
docker
ballgame
plug
in
4
for
open
shift
and
kubernetes
as
well.
So
we
just
shimmed
that,
with
a
flex
volume
driver
and
a
probationer.
B
So
this
type
of
paradigm
works
very
well,
but
with
both
of
our
stores
platforms,
we
also
have
integration
coming
with
the
with
Asher
and
AWS
to
be
able
to
use
this
the
same
type
of
deployment
in
the
public
cloud
as
well.
We
can
replicate
to
the
cloud
today
with
nimble.
In
a
few
months,
I'd
say
we
will
be
able
to
run
100%
cloud
native.
B
B
So
what
you
see
here
on
the
right
hand,
side
is
a
bunch
of
features
that
we
have
on
the
nimble
platform
right,
so
you,
for
instance,
we
have
full
lifecycle
management,
it's
it's
highly
available
and
so
forth,
and
we
have
really
cool
provisioning
controls
depending
on
how
you
want
the
the
volume
to
be
destroyed
when
you,
when
you
actually
delete
it
and
stuff
like
that
to
kind
of
preserve
data.
In
in
case
of
a
human
error,
we
have
very
sophisticated
performance
controls.
We
have
something
called
performance
policies.
B
So
if
you
have
100
terabyte
database
that
you
wanted
to
clone
to
a
new
volume,
start
up
a
new
container
and
run
some
tests
work
out
on
that
volume,
we
will
be
able
to
do
that
in
an
instant,
also
the
volume
import.
These
are
very
cool
features
with
which
enables
us
to
migrate
a
virtual
machine
from
any
foreign
storage
system
onto
a
nimble
array
and
then
convert
that
volume
into
a
volume
to
use
for
either
docker
or
openshift
or
anything
else,
and
that
is
a
rather
kind
of
seamless
migration.
B
B
So
in
this
case,
when
the
user
actually
creates
a
persistent
volume
claim
that
he
was
to
map
to
not
to
his
pod,
he
calls
out
the
storage
class
name
and
and
a
size
of
the
volume
he's
requesting.
The
provisioner
will
then
provision
the
volume
and
in
this
case,
an
encrypted
volume
with
a
ops
limit
of
1,000
use
the
performance
policy.
B
If
you
want
to
protect
this
volume
with,
would
snapshots
and
so
forth,
right
and-
and
we
also
have
ability
to
those
snapshots-
gets
enumerated
or
the
volume,
and
we
can
very
cool
things
with
that.
So
the
user
can
actually
clone
that
volume
into
a
new
container
and
to
do
any
type
of
analysis
or
reporting
stuff
like
that,
and
that's
all
I
had.
B
A
A
What
happened?
We
have
slice
our
sequence,
okay,
there
we
go
so
at
the
end
of
the
day
when
we
talk
to
customers-
and
they
don't
want
to
spend
like
months
and
months
standing
up
the
platform
they
don't
want
to
spend
months
and
months
going
out
there
and
copy
off
their
own
tooling
sets
right
and
then,
when
a
farewell,
manage
and
production
ready
platform.
So
last
week
what
we
have
done
was
we
have
announced
a
press
release,
a
joint
solution
with
between
HP
year
and
Breathitt
to
join.
A
A
Hopefully
we'll
make
you
customers
after
this
change,
your
Dell
boxes
anyway,
okay
enough,
self-promotion,
alright,
so
what
we
have
done
was
we
have
t-mobile
HP
with
Red
Hat
to
deliver
John
professional
services,
as
I
mentioned
earlier,
when
you
look
at
this
whole
journey,
a
lot
of
it
upfront
work
is
gonna,
be
service.
Heavy
and
not
every
single
customer
is
equipped
to
handle
that
transition
right.
You
know
going
from
an
on
container
to
container
eyes
environment,
adopting
DevOps
and
going
through
all
these
copper
changes.
A
So
you
know
having
a
strong
service
offering
is
a
big
plus,
so
we're
peanut,
Timo
Perez
have
to
offer
that
up
front
to
you,
but
once
you're
ready
to
deploy,
there's
what
we
call
day,
zero
and
day
one
right.
So
what
we
have
done
with
red
head
is.
We
have
been
working
together
to
develop
validated
reference
architectures.
A
So
not
only
do
we
have
reference
architectures
relative
reference
architectures.
We
actually
have
spent
resources
in
building
these
ansible
playbooks
a
lot
more
Red
Hat.
So
in
essence,
we
could
give
you
in
two
hours
on
our
synergy
platform,
which
is
a
composable
platform,
a
complete
openshift
production-ready
stack
that
has
a
KA
your
persistent
storage
integration
with
our
storage
back-end
as
NFS
has
monitoring.
We
actually
was
deploy
some
third-party
map
monitoring
tools
on
top
along
with
security.
So
you
that
was
a
product,
a
world
low
security
product
that
I
talked
about
which
PE.
A
So
the
goal
is
to
get
you
to
a
as
close
to
production
stake
as
possible
in
less
than
two
hours,
and
the
cool
thing
is:
with
these
ansible
deployment:
playbook,
we
will
open-source
them
we'll
put
them
up
on
github,
so
you
could
take
them
and
modify
to
any
way
that
you
choose
to
write.
This
is
cool.
If
you
guys
are
a
service
partner,
for
example,
you
can
leverage
it
as
a
service
offering
you
know
to
your
end
user
customer
base,
so
those
play
books
will
be
available
in
September
timeframe.
A
We
have
some
early
versions
of
dos
for
cluster,
but
the
more
robust
version
version
two
will
be
available
in
September
timeframe.
So
you
guys
interested
talk
to
us
afterward,
we'll
give
you
a
sneak
peek,
but
the
other
things
that
we
definitely
want
to
promote.
Is
you
know
platform
at
the
end
of
the
day,
and
we
want
to
say
you
have
your
choice
on
platforms
right
for
you
is
the
choice
of
either
cap
X
or
op
X.
A
So
we
have
some
interesting
capabilities
in
a
synergy,
composable
platform
that
we
think
lends
itself
to
very
large-scale
container
deployments.
So
I
talked
about
these
playbooks,
so,
along
with
these
play
books,
we
then
leverage
our
synergy,
composer
and
Emma
streamer
to
enable
customers
to
capture
these
golden
images
and
also
quickly
configure
our
synergy
systems
on
the
fly.
So
you
could
do
this
in
two
hours.
It's
not
easy
if
you
don't
have
the
symmetry
platform,
so
the
other
thing
about
the
synergy
platform,
which
is
really
cool
for
containers,
is
we
have
this
aggregated,
compute
and
storage?
A
So
we
have
customers
who
want
to
say
you
know
I
the
daytime
and
I
want
to
have
these
very
heavy
compute
environments
and,
like
storage
night
time
I
want
to
have
you
know,
maybe
like
compute
and
heavy
storage
right,
because
I
want
to
run
these
different
jobs
so
using
a
composer
as
a
user
using
these
api's
and
graphical
user
interfaces
they
could.
Basically,
we
compose
the
system
to
take
on
these
different
type
of
were
close.
So
it's
pretty
easy.
A
So
just
point
and
click,
it's
not
something
that
you
could
easily
do
when
you
have
these,
like
pizza
boxes
or
I,
just
generate
one
of
the
mail
servers.
So
that's
definitely
big.
Plus
we
talked
about
the
data
management
piece,
which
is
a
big
piece
and
I.
Think
the
other
big
piece
is
using
our
capabilities
with
composers
and
image.
Streamers
allows
you
to
pre-bake
these
IT
apps
sanction
images
that
you
can
then
use
our
technologies
to
rapidly
deploy
them
to
all
the
hundreds
of
notes.
A
So
again
doing
change
management
is
really
critical,
I
guess
doing
change
management
effectively.
It's
really
critical
when
it
comes
to
mass
scale
container
deployment,
because
you
have
a
big
stack
of
stuff.
The
changes
over
time
right.
So
once
you're
locked
out
that
go
to
images,
you
want
to
have
a
rapid
way
to
quickly
blast
them
out
there
all
those
hundreds
of
notes.
So
we
gave
you
that
capability,
along
with
red
head
using
ansible
and
our
composer
and
image
streamer
technologies,
so
some
pretty
cool
stuff.