►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
let's
see
the
agenda
so
in
this
agenda,
I'm
going
to
cover
what
is
stateful
and
what
is
stateless
workload
right,
and
I
will
also
do
a
quick
recap
of
kubernetes
storage
concepts,
followed
by
various
options
which
are
there
for
cloud
native
storage
and
then
the
most
important
part
about
choosing
the
right
storage
and
some
of
the
lesson
learned
and
key
takeaways.
A
Started
so
what
is
okay
so
before
we
get
into
stateful
and
stateless
workload,
it's
very
important
to
understand
that
kubernetes
was
originally
created
for
stateless
workload,
but
slowly
it
has
been
realized
that
state
full
workloads
are
also
something
that
needs
to
be
hosted
in
kubernetes
right
and
what
are
stateless
application
or
stateless
workload.
A
Those
are
applications
which
are
not
affected
by
odd
restarts
right.
So
if
a
pod
crashes,
because
part
by
its
nature
is
something
that
can
restart
and
it
can
get
different
iep
and
all
so,
stateless
workloads
are
not
affected
by
those
restarts.
A
A
A
Okay,
some
of
you
might
know
these
storage
concepts,
but
for
those
who
are
not
aware
of
it,
a
quick
recap
of
kubernetes
storage
concepts
and
I'm
not
going
to
go
in
deep
here.
It
will
be
at
very,
very
high
level,
so
that
whatever
we
talk,
we
go
through
next.
That
makes
sense
okay,
so
we
will
just
see
what
is
volume?
What
is
persistent
volume?
What
is
pvc
persistent
volume
claim?
What
is
storage
class
and
what
is
host
path?
A
Okay,
now
volume,
so
volume
is
a
directory
right
and
volume
is
not
a
new
word
in
kubernetes.
It
has
been
used
before
and
there
are
two
types
of
volume:
one
is
ephemeral,
volume
and
other
one
is
persistent
volume.
A
fever
volume
has
a
lifetime
of
a
pot
right.
So
if
you
restart
a
pod,
then
those
things
will
be
gone
right
and
persistent
volume
I'll
cover
in
next
slide.
Now,
in
terms
of
volume
that
is
supported
by
kubernetes.
There
are
many
right.
A
So
if
you
see
a
quick
list
here
on
this
slide,
so
it
supports
aws
ebs,
azure
desk
joe
file
empty
directory,
so
some
of
these
are
inbuilt.
They
like
empty
directory
host
path
are
something
that
you
can
use
and
some
some
other
one
like.
Let's
say,
azure
disk.
You
will
need
as
your
subscription
and
azure
cloud
access.
A
Okay.
So
this
is
about
volume.
Let's
go
to
persistent
volume,
persistent
volume,
as
the
name
suggests,
it's
again
a
piece
of
storage,
and
it
is
persistent
basically
so
like
in
aws.
We
have
ebs
volume
right
where,
if
you
store
something
in
the
ebay
volume,
that
data
does
not
go
away
when
your
easy
to
instantly
start
so
similar
concept
here
that,
if
you
attach
a
persistent
volume
to
a
pot
right
and
then,
if
a
part,
restarts
or
even
part
terminates,
the
data
does
not
go
away,
and
now
how
do
we
create
persistent
volume?
A
A
So
there
are
different
modes
supported,
read,
write
once
read,
write
money
and
read
only
right
so
and
whether
it
is
host
path,
type
or
different
type.
That
is
again
one
of
the
option.
Okay.
So
this
is
a
very
simple
yaml
file
of
creating
a
pv
in
kubernetes
and
persistent
volume
could
be
static
or
dynamic.
What
what
it
means
is
see
if
it
is
a
dynamic,
persistent
volume.
That
means
we
don't
need
to
create
it
and
storage
provisioner
will
take
care
of
provisioning.
A
The
pv
now
coming
to
persistent
volume
claim
so
pvc
is
a
way
the
kubernetes
uses
the
storage
right.
So
if
I
have
created
a
pv
of
let's
say,
50
gig,
then
I
cannot
really
have
pv
shown
to
port
right
or
pv
is
not
visible
to
part.
So
pv
is
consumed
using
pvc.
So
when
a
pod
needs
a
storage,
it
has
to
call
the
pvc
okay.
For
that
we
need
to
create
a
pvc,
and
how
do
we
create
a
pvc?
A
Is
the
sample
script
given
here
we
just
give
the
pvc
name:
okay,
storage,
class
name
access
mode,
and
how
much
is
the
storage
requirement
for
pvc
now
pvc
to
pv
binding
is
one
to
one,
and
this
is
very
important
to
understand,
because
this
is
a
major
major
limitation.
So
let's
say
if
I
have
a
pv
of
100
gig
and
I
create
a
pvc
of
5
gig
right
and
access
mode
and
storage
class
name
matches
there,
then
that
pv
is
going
to
be
bind
to
pvc.
A
Okay,
since
we
have
asked
for
five
gig,
we
will
not
be
able
to
use
another
95
gig
that
will
be
based
and-
and
there
will
not
be
any
other
pvc
that
can
use
that
remaining
pvc.
So
that's
what
one
to
one
mapping
means-
and
this
causes
a
lot
of
wastage
of
storage
right,
because
you
might
not
know
exact
storage
requirement
right
in
the
beginning,
and
you
don't
want
to
run
out
of
storage,
so
you
will
typically
give
a
large
enough
pv
and
map
it.
A
And
then,
if
that
is
not
being
utilized,
then
your
storage
is
not
really
utilized
properly.
Okay.
Now
so
that
is
pvc
coming
to
storage
class,
a
storage
class
is
like
a
profile.
Okay,
so
see
the
kubernetes
support
supports
different
kind
of
storage
right
and
application
also
requires
different
kind
of
storage.
Some
application
requires
very
high,
performing
storage
and
and
some
application
where
there
might
not
be
any
need
of
very
high
performing
storage.
In
that
case,
we
don't
need
to
really
give
high
performing
storage
to
all
kind
of
workload.
A
We
can
create
a
category
of
profiles
of
very
storage
and
those
are
called
storage
class,
so
we
can
create
a
storage
class
for
let's
say,
high
performing
storage,
one
storage
class
for
low
performing
storage
and
so
on
right,
so
these
are
like
tiers.
So
how
does
storage
class
helps?
It
is
useful
for
dynamic,
pv
provisioning
right.
So
one
of
the
example
given
here
yaml
file
is
given
here
so
here.
What
are
we
doing?
We
are:
creating
a
storage
class
class
called
cncf
ebs
storage
class.
A
So
this
is
a
tbs,
specific
storage
class
and
we
are
giving
a
provisional
okay
and-
and
these
are
just
three
parameters
given,
but
there
are
several
options
and
these
options
are
again
not
consistent,
different
cloud
provider.
Different
vendors
give
different
different
parameters
right,
so
you
need
to
find
out
the
right
parameters
for
your
volume
type
and
all
so
here
what
we
are
saying
that
my
storage
class
is
going
to
use
type
io1
and
it
will
guarantee
iops
per
gb
of
10
right
now.
A
So
what
is
what
happens
here
is
when
you
use
this
storage
class
okay
in
any
pvc,
then
you
don't
need
to
create
pv.
So
let's
say
the
same
example
where
my
pvc
is
of
five
gig
right
and
I
did
not
create
any
pvc
if
pv
so
my
pvc
file
game,
I
did
not
create
any
pv,
and
now,
when
my
pvc
is
created
because
this
storage
class
is
mentioned,
there
will
be
automatic
provisioning
of
5
gig
of
pv
using
this
provisional
okay
and
what
is
the
benefit
of
it?
A
You
are
not
wasting
the
storage,
and
this
is
still
one
to
one
mapping,
but
then
the
headache
of
creating
pv
and
maintaining
pv
is
taken
away
from
you.
A
A
Now
there
is
a
concept
called
host
path.
What
is
host
path,
so
host
path
is
a
way
by
which
you
can
utilize
the
storage,
which
is
locally
present
on
the
server
okay.
Now
in
this
example,
if
you
see
this
yaml
file,
it
says
cnc
of
demo
pv.
So
in
this
persistent
volume,
okay,
I
am
mentioning
host
path
and.
A
Now
this
stories
is
coming
from
my
local
node,
so
wherever
whatever
worker
node
is
being
used,
where
I'm
creating
this,
that
storage
will
be
used.
Now,
the
limitation
of
this
kind
of
host
path
is
that
storage
is
local
right,
so
it
is
not
getting
replicated
from
one
worker
node
to
other
worker
node.
So
if
that
broker
node
goes
down
even
though
you're
using
persistent
volume,
your
data
will
go
away
because
underlying
storage
itself
is
not
available,
so
that
is
one
major
limitation.
A
Okay,
and
second,
is
that
it
is
not
recommended
for
production,
the
reason
being
it
has
several
security
risk
right,
so
in
our
sandbox
environment
or
non-production
environment,
it's
perfectly
all
right
to
use
host
path,
okay,
but
in
production
it's
a
big.
No,
no.
I
mean
it's
not
at
all
recommended.
A
A
So
we
we
give
it
in
terms
of
pvcs
so
part,
whichever
part
wants
persistent
storage,
persistent
volume
it
has
to
have
pvc
mentioned
in
its
yaml
file
and
then
that
pvc
maps
to
a
pv-
and
there
is
a
storage
class
option
also
that
we
can
use
for
doing
dynamic
provisioning,
and
that
is
it,
and
if
you
want
to
use
local
storage,
you
can
use
host
path.
A
A
A
And
if
you
are
aware
about
the
concept
of
graduated
project,
then
root
is
the
only
project
which
is
cncf
graduated
out
of
those
56.
Now
a
little
bit
detail
about
these
projects
or
these
options,
one
that
not
all
of
them
are
same
right.
So
it's
not
like
a
cloud
provider
situation
right
where
you
take
a
virtual
machine
from
azure.
It
is
called
as
your
virtual
machine
if
you
take
it
from
database
called
ec2,
but
they
are
same
virtual
machine.
They
are
same
operat.
A
This
will
be
some
operating
system
and
storage
and
so
on
right
they
are
safe.
But
here
it
is
not
like
that.
So
one
example
would
be,
let's
say,
min
io
this
one
right,
so
min
io
is
only
for
your
object.
Storage
right.
So
you
know
there
are
three
types
of
storage:
one
is
object:
storage
like
s3
object,
storage
and
number.
Two
is
block,
storage
right
and
number
three
is
file
system
based
right,
so
yeah.
These
are
the
three
and
file
system
based
means,
nfs,
is
also
part
of
file
system.
A
So
so
one
of
the
difference
between
these
products
is
one
that
they
they
are
catering
to.
A
specific
type
of
storage-
let's
say
mine,
is
only
two
object.
Storage
part.
A
Some
cover
all
three
object,
so
all
three
storage
types
like
chef,
okay,
some
are
so
this
is
like
one
difference
in
terms
of
what
kind
of
storage
options
are
supported.
A
Second
difference
is
that
I
think
this
can
be
understood
from
this
slide,
so
there
are
three
types
of
cloud
native
storage
or
kubernetes
storage,
one
which
is
a
traditional
solution
with
csi
plugin
okay.
So
that
means,
let's
say
neter
now:
netapp
is
there
in
storage
world
from
so
long
and
to
support
container
workloads
or
support
kubernetes
what
they
have
done.
They
have
created
a
csi
plugin
right.
A
A
Some
of
those
cloud
native
storage
are
csi
plugins.
Basically,
okay,
second,
is
some
solutions.
Are
software
defined
storage
with
container
optimization,
so
they
have
design,
so
they
don't
rely
on
plug-in,
but
they
have
a
container
optimization
so
there
as
a
solution
works
for
container
also,
and
they
say
that
they
have
optimized
it
for
container,
so
it
so
that
it
works
for
containers
and
third
category
of
solution
is
cloud
native
solution,
so
there
are
certain
products
which
were
built
ground
up
ground
chip
and
for
this
kubernetes
right.
A
So
those
are
like
cloud
native
solutions,
all
three
different
categories.
Now
the
question
is
the
most
important
part
is
as
an
architect
or
as
a
solution
architect
for
kubernetes.
I
need
to
decide
which
storage
is
right.
Storage
for
me
right.
How
do
we
decide
that?
So
choosing
the
right
storage
option
is
our
next.
A
Agenda
in
this
session,
so
now
in
this
slide,
I
have
listed
20
such
decision
criterias,
okay
and
you
are
free
to
add
more
or
you're
free
to
skip
something
which
are
not
relevant
to
you,
but
these
are
more
or
less
something
that
covers
all
possibilities.
Okay,
now,
let's
go
through
each
one
of
them,
because
this
is
the
most
important
part.
Okay.
So
whenever
you're
choosing
any
storage
solution
for
kubernetes,
you
might
end
up
in
a
situation
where
you
will
have
different
storage
for
virtual
machines,
which
is
like
non-container
world
and
container
world.
A
So
now
the
question
here
is
whether
you
want
two
different
solutions
or
one
right.
So,
ideally,
you
will
prefer
to
have
one
solution
right
so
that
you
have
less
management,
overhead
and,
and
so
many
challenges
go
away.
You
don't
have
to
really
go
with
two
different
vendors
and
don't
have
to
manage
two
different
way
of
maintaining
storage
for
different
type
of
workflow.
Okay,
so
first
question
that
you
should
ask
while
deciding
any
particular
storage
solution,
whether
it
supports
both
virtual
machine
and
containers.
A
Second,
one
is,
as
I
mentioned
before,
there
are
three
types
of
storage.
One
is
block,
object
and
file
system.
So
second
question
would
be
whether
given
solution
supports
all
three
or
one
of
them
or
two
of
them.
How
is
it
because
almost
I
would
say
I
can't
get
the
number
but
yeah
most
of
the
solution
do
not
support
all
three
okay,
all
right
now.
Third,
is
whether
you
have
enterprise
support
available,
and
this
is
again
a
very
common
question
from
open
source
software
perspective
right.
A
So
when
you
are
running
open
source
software
in
production,
you
want
to
be
sure
that
there
is
enterprise
support
available
from
some
vendor
and
they
are
there
to
help
you
24
by
7
for
all
kind
of
7
issues
and
all
all
right
number
four.
So
whether
it
supports
major
cloud
providers
or
not
so
see,
these
storage
options
are
also
applicable.
A
So
that
is
fourth
criteria.
Fifth,
one,
whether
it
provides
any
kind
of
replication
feature.
Why
do
you
need
replication
and
kubernetes?
So
you
need
replication
for
high
availability
and
disaster
recovery
right.
So
many
solution
supports
async
replication.
Some
of
them
are
supporting
sync
replication
also,
so
that
there
is
no
data
loss
right.
So,
based
on
your
requirement,
you
can
decide
what
solution
fits
in
your
account,
whether
if
you
need
sync
replication
based
solution,
then
that
could
be
one
of
your
major
criteria.
A
A
Some
of
the
solutions
are
very
difficult
to
implement
and
they
are
all
command
line
options
and
all-
and
that
is
quite
difficult
right
when
you
want
to
manage
your
storage
at
scale,
then
ease
of
deployment
also
matters
and
many
companies
also
look
for
workload.
Migration
feature
right
so
and
what
I
mean
by
workload
migration
is.
A
This
could
be
first
of
all
across
kubernetes
cluster
right,
so
your
kubernetes
cluster
one
could
be
running
on-premise
or
maybe
cloud
one,
and
you
want
it
to
migrate
from
cloud
one
to
cloud
two,
and
you
want
to
do
this
at
storage
level
right.
You
want
to
create
a
snapshot
copy
that
snapchat
restore
it.
That
could
be
one
option
right
or
you
might
want
to
have
a
single
application
where
your
application
is
always
copied,
or
rather
your
application
data
is
always
copied.
A
So
when
something
goes
wrong
here,
you
have
exactly
same
coffee
available
on
the
other
side
right
and
you
can
do
a
failover
to
other
side
so
whether
that
workload
migration
feature
is
there
or
not
number
11,
whether
it
supports
high
performance
like
now
how
high
performance
might
not
be
a
key
criteria
for
everyone?
Right
so
just
see,
let's
say
if
you
are
hosting
some
telco
great
workload,
let's
say
some
vnf
hosting
you
want
to
do
right
and
there
your
storage
performance
and
network
throughput
everything
matters
right.
A
You
want
to
ensure
that
next
one
is
qos,
guarantee
quality
of
service
guarantee
like
these
many
iops
per
second,
that
kind
of
thing
is
there
or
not
encryption
again,
very
important
from
security
perspective,
so
whether
it
supports
encryption
at
rest,
encryption
in
motion
and
for
all
kind
of
corruption,
issues,
whether
it
supports
checksum
error
detection,
then
whether
it's
a
and
how
does
the
scalability
works
right?
That's
another
point
so
see
when
you
create
this
character
of
storage
solution,
you
will
be
using
multiple.
A
A
A
Next
is
whether
there
is
any
infra
log
lock-in
or
not
right
so
sometime,
it
happens
where
a
certain
storage
solution
work
only
with
their
hardware
or
certain
hardware.
Now
that
is
what
is
lock-in
right
so,
whether
that
infra
lock-in
or
hardware
login
is
there
or
not?
That
is
again
one
point
that
you
should
consider.
A
Is
there
any
backup
and
recovery
feature
and
last
one,
whether
it's
supposed
thin
provisioning
or
not?
Okay,
so,
as
you
can
see,
some
of
these
points
are
related
to
security.
Some
are
related
to
software
defined
storage.
Some
are
related
to
high
availability
disaster
recovery.
Some
are
related
to
key
features
of
type
of
storage
or
type
of
workload
right.
So
you
have
to
evaluate
from
different
different
perspective
and
what
can
happen
here
like
how
do
you
really
evaluate
that?
A
So
you
can
create
a
table
sort
of
thing
where
you
mention
all
these
20
parameters
or
maybe
more
maybe
less,
and
then
you
choose
certain
option.
Let's
say
you
choose
five
option?
Okay,
that
let's
say
you
want
to
evaluate
rook.
You
want
to
evaluate
four
more
okay,
you
put
all
five
that
same
table
now
you
start
exploring
whether
solution
one
fits
in
point
number.
One
point
number
two
point
number
three
and
so
on
okay
and
then
based
on
this
entire
exercise,
you
will
get
to
know
which
one
is
the
right
solution.
A
I
did
not
mention
the
licensing
and
subscription
cost
aspect,
but
that
is
also
important.
Some
of
the
lesson
learned
since
there
are
too
many
option
and
if
you
start
exploring
all
56,
it
might
be
a
long
term
exercise
right,
because
you
cannot
do
it
theoretically
by
reading
literature
that
is
available
in
public
domain,
so
you
have
to
do
certain
pocs
now
you
cannot
do
pocs
of
56
different
solutions.
A
So
one
of
the
recommendation
is
that
at
theoretical
level
you
decide
right
which
one
in
which
five
are
aligned
to
your
strategy
right
very
high,
then
start
from
there.
I
mean,
don't
start
with
all
56
number,
two
very
important
lesson
that
some
of
the
limitation
will
not
be
known
beforehand.
So
I
mean
in
many
public
publicly
available
documentation.
You
will
not
see
a
heading
called
known
limitation,
or
these
are
the
things
which
do
not
work
right.
So
it
will
happen
that
once
you
start
using
it,
you
will
find
out.
A
A
There
are
known
issues,
okay,
so
those
kind
of
things
you
will
get
to
know
only
when
you
do
the
poc.
So
once
you
shortlist,
let's
say
five
of
them,
then
do
a
quick
poc
in
some
test
environment
and
try
to
see
various
features,
whether
I'm
able
to
take
backup
whether
it
is
supporting
async
replication.
Whether
it
is
I
mean
you
can
do
those
smaller
small
pieces
now,
as
I
mentioned
before,
subscription
and
licensing
of
add-on
should
also
be
considered
in
the
beginning
itself.
A
So
what
I
mean
by
licensing
of
add-on,
so
in
most
of
these
products,
core
functionality
is
free.
Mostly
core
functionality
means
the
storage
fabric.
Part
is
free,
so
you
can
implement
their
solution
and
that
will
take
care
of
creating
a
storage
pool,
doing
dynamic
provisioning
and
all
those
basic
things
will
be
taken
care
and
you
can
give
that
storage
to
your
parts.
You
know,
but
when
it
comes
to,
let's
say
sync
replication
or
when
it
comes
to
backup
when
it
comes
to
even
management.
Sometimes
some
vendors
give
command
line
based
management
free.
A
But
if
you
have
to
manage
using
their
management
portal,
then
you
have
to
pay
for
addon
right
and
it's
not
substantial
amount,
but
yeah.
It
is
still
something
one
one
has
to
consider
so
yeah,
that's
what
I
meant
by
licensing
of
addon
should
be
considered,
and
since
you're
dealing
with
open
source
slack
channel
is
the
best
place
to
get
the
support.
Sometimes
the
enterprise
supported
version
also
have
some
support,
email
and
all,
and
you
can
reach
them
and
get
support.
A
First,
one
it's
a
fast
changing
area
right,
so
I
mean,
if
you
have
done
a
poc
one
month
ago,
then
you
cannot
be
sure
that
everything
is
same
now,
because
people
are
introducing
new
features
and
people
are
fixing
bugs
I
mean
a
lot
of
things
are
happening
right
so
sometime.
It
will
be
good
to
find
out
the
road
map
of
given
product
right.
So
certain
thing
might
not
be
there.
Let's
say
out
of
your
10
criteria:
nine
are
meeting.
One
is
not
waiting
now
you
can
always
check
with
their
if
it
is
open
source.
A
You
can
just
check
in
open
source
community
if
there
is
a
roadmap
to
get
that
10th
feature
or
if
it
is
supported
by
any
company
and
that
falls
under
that
company,
then
you
can
ask
them
if
it
is
part
of
their
roadmap
or
not
that
way
you
can
catch
up.
Otherwise,
if
only
on
the
basis
of
nine
parameter,
you
reject
because
you're
not
I
mean
that
solution
is
not
fitting
in
your
10
out
of
10
things,
then
you
should
not
throw
it
out.
A
Number
two
is
lack
of
support
for
vm
and
container
both.
I
think
I
mentioned
it
in
the
beginning
that
very
few
solutions
supports
virtual
machine
and
containers
both
and
the
practical
experience
is
that
very
few
companies
want
to
go
for
two
different
storage
solutions
right,
one
for
kubernetes
and
one
for
traditional
virtual
machine
world
right.
Third,
one
errors
prone
command
line
based
step.
A
I
think
this
is
self-explanatory
and
it
is
it
is
about.
I
mean
you
don't
want
to
do
first,
neither
you
want
to
do
entire
management
using
command
line,
nor
you
want
to
do
automation
on
your
own
to
bring
it
up
to
a
shape
where
it
can
be
used
in
production
right
both
are
not
good,
so
this
is
again
a
common
challenge.
A
Lack
of
application
awareness
now
application
in
kubernetes
is
something
that
is
not
clearly
defined
right.
So
there
is
nothing
no
entity
called
application.
Replication
is
sum
of
various
objects.
It
will
have
forward.
It
will
have
deployment
will
have
some
config
map.
It
will
have
some
secret,
I
mean,
and
all
together
is
one
application
right
so
and
the
storage
which
is
attached
to
it.
A
When
you
say
I
want
to
backup
my
application
now.
Is
this
storage
solution?
Aware
of
your
application?
Can
you
define
your
application?
Can
you
say
that?
Okay,
whatever
is
there
in
this
name
space?
That
is
my
application.
Is
that
kind
of
option
given
right?
So
typically,
it
is
not
there.
So
lack
of
application.
Awareness
is
common
challenge
and
replication
and
disaster
recovery
features
are
something
which
are
commonly
missing
and
sometimes
async
replication
is
there,
but
sync
replication
is
not
there
and
so
on
right.
A
So
these
are
some
of
the
common
challenges:
okay,
coming
to
key
takeaways
number,
one.
So
out
of
those
20
criteria,
decision
criteria,
which
I've
explained
the
most
important
ones-
are
enterprise
strategy.
So
many
companies
have
alignment
with
certain
storage
partner
vendor
right
so
that
and
they
want
to
continue
that
they
don't
want
to
introduce
one
more
vendor,
one
more
complex
thing
in
the
mix,
so
sometimes
that
itself
becomes
a
single
decision
criteria
right
and
of
course,
unless
it
is
limited
by
so
many
features,
but
then
that
itself
is
good
enough
to
choose.
A
A
I
mean
it
can
have
several
other
points
right
so
which
feature
you're
looking
for.
You
will
try
to
map
with
it
now
next,
one
again,
a
lesson
learned
and
the
key
takeaway
that
most
of
the
vendor
supported
product,
do
not
have
exact
same
commercial
version,
feature
and
open
source
question,
and
that
is
obvious.
I
mean
that
is
how
it
works.
A
If
they
give
exactly
same
version,
then
what
is
their
value
at
right?
So
there
are,
I
would
say,
as
I
mentioned
before,
I
mean
most
of
the
feature.
The
core
feature
is
free,
and
it's
always
given,
but
some
of
the
add-on,
like
let's
say,
gui
based
maintenance
and
all
that
that
is
given
as
part
of
subscription.
A
Some
some
vendors
very
few
vendors
give
their,
as
is
commercial
one
version
with
several
restrictions,
so
what
they
say,
I'm
giving
you
exactly
same
product,
which
I
give
you
when
you
buy
my
subscription.
But
then
this
product,
which
I
am
giving
giving
you
for
free,
is
not
going
to
have
same
kind
of
not
same
kind
of
thing.
I
mean
it
will
have
certain
limitations,
so
it
will
work
only
with
5
terabyte
of
storage.
A
It
will
work
with
only
10
nodes
or
whatever
I
mean
those
kind
of
restriction
will
be
there
and
those
are
good.
I
mean
I
mean
for
non-production
kind
of
environment
you're
good
with
the
those
restriction
right.
You
can
still
live
with
those
restrictions.
Yeah
I
mean,
in
such
cases,
feel
free
to
use
those
products
in
non-production,
give
a
special
consideration
for
performance
requirement,
because
not
all
vendors
stress
on
performance,
some
vendors
are
very
good
in
performance
and
they
are
performance
of
their
storage.
A
A
If,
if
a
mix
of
gui
and
command
line
is
given,
then
it
becomes
a
nightmare
in
real
life
and
last,
but
not
the
least
no
one-size-fits-all
solution
right.
So,
though,
I've
mentioned
20
criterias
and
you
might
have
maybe
10
more
20
more
to
be
added
in
that
list,
and
you
can
I
mean
by
this
line.
What
I
mean
to
say
is
that
you
will
not
find
a
single
product
which
will
fit
in
all
those
45
data.
You
will
not
find.
I
mean
there
will
be
some
gaps
somewhere
either.
A
A
Okay,
so
that
is
it,
and
this
is
about
my
company.
So
I
work
for
bipro.
We
are
eight
billion
company.
We
have
got
1120
active
clients.
This
is
our
employee
strength,
and
this
is
as
of
fy
21
results.
We
have
presence
in
66
countries
and
with
that
we
have
come
to
end
of
this
presentation.