►
Description
Join us for Kubernetes Forums Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Stateless applications are frequently very agile in K8s while stateful applications are not. OpenEBS is a solution for containerizing data and abstracting the storage layer so that your Kubernetes applications just work. We’re a CNCF Sandbox project with a strong community of around 1750 members that provides persistent and containerized block storage for DevOps and container environments.
In this webinar, we will cover how to easily get started with OpenEBS, deploy your stateful applications and make them replicated and portable across your clusters, availability zones, and clouds.
We will also discuss the latest features and how to set OpenEBS up with platforms like AWS, D2iQ Konvoy, Red Hat Openshift Operator Hub, Rancher and other platforms.
Agenda:
The problem with persistent applications in K8s and how OpenEBS solves it
Deploying OpenEBS in 30 seconds
Top Use Cases
Demo
Roadmap
Q&A
Get started and Support
A
All
right
we're
going
and
where
she
start
I'd
like
to
thank
everyone.
Who's
joining
us
today
welcome
to
do
today's
CF
webinar,
given
a
tea
storage
is
more
than
CS
I.
Do
it
the
right
way
with
the
open
EBS
way?
My
name
is
Orion
vaselov
and
I'm.
A
software
engineer
at
VMware
and
I'm
also
proud
cloud
native
ambassador
I'll,
be
moderating
the
webinar
today
and
like
to
welcome
our
presenters.
A
A
Also,
this
is
official,
sincere
webinar
and
such
subjects
to
the
CF
code
of
current
conduct.
Please
do
not
add
anything
that
on
the
chat
or
question
that
whoo
violation
of
that
code.
Basically,
this
be
respectful
and
follow
the
participants
in
the
presenter.
With
that
I'd
like
to
hand
over
to
Murad,
Brian
and
Kieran
to
kick
off
the
today's
presentation.
B
Thanks
Warren
hi
everybody
and
thanks
for
joining,
want
to
say
welcome
you
to
all
my
name
is
Brian
and
I'm.
A
developer
advocate
for
Maya
data
I'm
joined
by
two
of
my
colleagues,
Murat
and
Kieran,
and
on
this
webinar
we're
going
to
talk
about
opening.
Yes,
ACNC
f,
manage
open
source
container
attached
storage
solution
for
kubernetes,
open
EDS
is
used
by
many
organizations
and
it's
a
technology.
That's
flexible
across
a
lot
of
different
use
cases.
B
These
organizations
are
using
opening,
yes
to
transform
their
kubernetes
clusters
into
a
resilient
data,
plane
and
they're
turning
kubernetes
itself
into
a
store
jerae.
That's
why
a
lot
of
people
were
talking
about
opening,
yes
at
Cana
in
San
Diego,
and
who
is
my
data?
We
are
contributors
to
the.
We
are
code
contributors
to
the
CN
CF
and
we
will
talk
today
with
open.
B
Ebs
is
founder,
one
of
obdds
as
founders
current
and
we'll
get
some
road
map
info
from
our
Maya
data's
head
of
product
Murat,
as
well
as
the
demonstration
from
me
of
open,
EBS
and
action.
Then
we'll
open
up
the
floor
to
questions
at
the
end,
but
please
do
submit
your
questions
early
in
the
in
in
the
zoom
interface,
using
the
questions
interface
at
the
bottom.
C
Good
to
be
here
so
thanks
to
speak
about
the
stateful
applications
in
communities,
the
short
answer
that
I
would
Q
is
the
state
state
of
stateful
applications
in
kubernetes
is
always
evolving.
I
have
definitely
seen
a
lot
of
improvements
in
the
last
three
years
that
I've
worked
in
kubernetes
and
I
still
see
it's
evolving.
So,
in
fact
like,
if
you
look
back,
the
community
was
mainly
focused
on
making
sure
like
we
reconnect
to
an
external
storage,
and
interfaces
have
now
evolved
into
what
we
call
a
CSI.
C
A
C
Data
management
is
something
beyond
connecting
or
deleting
volumes.
It
involves
running,
distributed,
applications
that
require
multi-tiered
storage.
You
need
some
data
protection
mechanisms
and
ability
to
seamlessly
migrate
from
one
cluster
to
the
weather,
in
fact,
like
with
the
adoption
of
kubernetes,
there's
lot
of
use,
cases
that
are
coming
in
terms
of
migrating
from
norm,
kubernetes
environment
into
kubernetes
cluster.
C
So
in
fact,
as
we
speak
today,
interesting
storage
there's
talk
about
formation
of
a
sync
data
protection
that,
in
fact,
talks
about
or,
like
you
know,
is
going
to
focus
on
resolving
some
of
these
problems.
That
I
just
mentioned,
I'm
also
excited
to
be
part
of
a
new
Linux
Foundation
project
called
soda,
that's
going
to
be
launched,
and
it's
also
going
to
be
focused
on
data
management,
and
there
are
several
projects
that
are
complementing
the
features
that
are
available
in
kubernetes
itself.
Open
EBS
is
one
of
them.
C
Well,
arrow
is
another
project
at
I
mean
closely
associated
with
and
used
so
to
come
back
to
your
question
on
how
open
it
is,
or
you
know
what
aspect
of
the
puzzle
that
we
solve
and
to
just
could
go
back
on
history.
A
little
bit
right
so
kubernetes
is
definitely
a
game
changer.
It
has
changed
how
applications
are
developed
and
deployed,
and
early
on,
we
saw
the
potential
in
communities
which
changed
the
way.
C
The
storage
software
itself
can
be
written
in
open
community
driven
similar
to
coupon
I
test
a
and
that's
how
open
it
is,
kicked
off,
meaning
short,
open
EBS
is
helping
users
convert
kubernetes
into
a
data
plane,
we'll
probably
get
into
that
a
little
more
in
this
talk,
in
fact,
one
interesting
thing
with
kubernetes
is
the
original
authors
never
anticipated
the
VAP
abilities
itself
is
being
used
today.
Definitely
they
would
have
not
thought
of
it.
Has
a
data
plan
data
plane?
B
C
So
one
of
the
primary
reasons
that
I
talked
about
is
kubernetes
itself
that
we
just
touched
the
other
two
things
that
drove
the
interest
in
open,
EBS
I
can
kind
of
attribute
it
to
the
background
with
which
the
contributors
of
only
contributors
in
trim
and
the
ugly
support
that
we
had
from
the
user
community
itself.
So
just
to
talk
about
the
founding
team,
this
team
has
helped.
C
Even
you
know,
you
could
say
like
coined
the
term
software-defined
storage
and
worked
on
several
software-defined
storage
systems
and
in
open
source
as
well
and
in
fact,
like
some
of
the
team,
has
worked
on
the
first
containerized,
this
storage
using
freebsd
chains
right
well.
This
actually
had
us
as
a
team,
to
work
closely
with
universities,
enterprises
and
service
providers
to
set
up
storage
in
their
data
centers
and
look
closely
at
the
challenges
faced
with
monolithic,
lock-in,
kind
of
and
architectures
and
kubernetes
promises
to
solve
some
of
these
problems.
C
It
basically
helps
break
down
this
monolith
into
micro
services
and
then
also
build
on
top
of
open
source
technologies.
So
that's
how
openly
we
are
started
and
oblivious
fields
in
with
the
same
principles.
So
it's
built
using
containers,
it
uses
the
micro
services,
our
design
philosophy,
and
it
is
completely
orchestrated
by
kubernetes
I
think
it
would
be
fair
to
say
that
openly.
This
is
completely
competitive
over.
It
is
native
storage
solution
and
up
to
date
it
only
supports
kubernetes.
B
C
So
CN
CF
it's
become
this
neutral
home
for
any
cloud
native,
open
source
project
that
we
done
up.
It
helps
the
maintenance
to
put
the
entire
project
through
a
much
wider
and
stricter
lens.
It
also
helps
the
adopters
you
know
like
we
have
orange
Alistair
and
Comcast,
not
only
adopters,
also
provide
them
a
commitment
that
it's
not
just
open
source,
but
it's
also
also
follows
the
open
government
rules
that
a
cnc
export.
B
Great
absolutely
thank
you
for
that
Karen
and
thank
you.
Everybody
for
for,
for
bearing
with
us
and
I,
wanted
to
share
a
comment
that
our
CTO
is
fond
of
using,
which
is
that
applications
have
changed,
and
someone
forgot
to
tell
storage
with
kubernetes
app
deployments
are
automated
highly
dynamic.
Open,
EBS
storage
has
the
same
characteristics
as
this.
This
makes
it
easy
for
loosely
coupled
cross-functional
development
teams
to
use
familiar
kubernetes
commands
to
manage
storage
for
their
suite
of
micro
services.
B
B
When
you
have
a
storage
solution,
that's
external
to
kubernetes,
your
whole
cluster
becomes
tightly
coupled
to
that
storage
provider.
If
you
have
an
external
app
storage,
that
is
on
an
on-prem
storage
array,
how
are
you
going
to
move
that
out
to
the
cloud
if
your
external
app
storage
is
from
a
cloud
provider,
will
they
help
you
migrate
your
data
to
a
different
cloud
provider.
B
B
B
Open
EBS
is
implemented
with
a
pluggable
storage
engine
architecture.
The
local
PD
engine
is
often
used
for
provisioning.
Local
storage
in
an
automatic
fashion.
C
store
is
another
storage
engine
with
features
like
replication
and
snapshot.
You
can
create
a
kubernetes
storage
class
that
uses
C
store
to
store
the
data
in
three
replicas
on
three
separate
nodes
where
each
node
has,
for
example,
12
G,
p2
disks
attached
and
aggregated
and
attached
and
aggregated
into
the
C
store
pool.
B
You
can
then
reference
that
storage
class,
whether
it's
locally
remote
and
replicated
in
a
PVC
spec
in
your
application
deployment
manifests
or
you
can
simply
make
it
the
default
storage
class.
When
the
pond
referencing
that
storage
class
comes
up
for
the
first
time,
open
EBS
will
create
a
volume
to
match
the
PVC
since
open
EBS
provides
storage
and
works
in
any
kubernetes.
B
It's
useful
for
just
about
any
stateful
application.
You
might
want
to
run
lots
of
users,
use
it
for
git,
lab
and
other
CIC
frameworks.
We've
also
seen
an
increasing
adoption
as
a
sword.
Substrate
for
Kafka
and
other
data,
pipelining
technologies
and
machine
learning
is
another
application
that
can
really
benefit
from
dealer
agility,
since
the
training
sets
need
to
be
made
available
wherever
the
GPUs
are
so
now,
I'd
like
to
show
you
how
easy
it
is
to
set
up
a
stateful
application
in
kubernetes
with
opening
s.
B
B
D
Brian
and
my
name
is
Murat
Carsten
I'm,
one
of
the
maintenance
of
open
abs
and
also
a
community
observer
I'm
in
the
slack
Channel,
as
well
as
Brian
and
Qian,
and
all
of
our
team.
Opening
beers
is
on
a
monthly
release,
release
cadence
and
we
are
excited
that
we
are
approaching
21.5
release
as
soon
as
maintainer.
D
Today,
Maya
story
is
one
of
our
new
alpha
engine
targeting
high
performance
use
cases
and
recently
got
the
encryption
and
also
adding
replication
and
rebuilds.
At
the
moment,
CSI
Kieran
talked
about
this.
A
bit
community
has
made
a
great
progress.
Oh
pretty
eye
open,
EBS,
CSI
support
is
getting
matured,
and
but
that's
just
the
interaction
with
kubernetes,
and
there
is
much
more
behind
the
scenes
to
get
the
API
calls
executed
in
the
storage
world
of
things
and
not
disk
manager.
Storage
engines
are
big
part
of
our
data
plane
work
on
the
operational
and
infrastructure
side.
D
D
1.4
we
had
armed
64
builds
for
G
Y
in
the
control
plane
now
getting
into
automated
builds,
including
C
store
into
that
soon,
and
next,
please,
and
if
we
look
at
the
next
slide,
if
we
look
at
the
high
level
roadmap
open
areas
in
its
control
and
data
playing
components,
our
core
to
our
community
and
Maya
data's
enterprise
customers
as
well,
enterprise
solution
is
a
bit
more
than
open
areas.
On
top
of
that,
we
have
a
bit
open,
EBS
director
users,
get
user
interface
and
monitoring.
D
We
provide
data,
resiliency
and
cows
engineering
with
litmus
another
open
source
project
in
the
CNC
of
landscape,
and
also
cross
cloud
and
data
mobility,
with
the
cube
move
project,
which
is
new
under
development
and
end
data,
and
then
a
policy
driven,
optimization
operators
for
day
2
operations,
also
in
in
design
review
right
now.
If
you
can
switch
to
next
again
Brian,
we
believe
in
this
mission
to
turn
kubernetes
into
data
plane.
It's
been
a
long
journey
for
us
since
the
days
of
software-defined
storage
to
have
defined,
store,
storage
with
open
abs.
D
We
pro
approved
it
now
trusted
by
10
thousands
of
users.
They
are
running
upon
EBS
on
Premanand
cloud
storage
is
a
big
piece
of
the
puzzle,
always
achieving
them
from
cloud
or
any
type
of
lock-in,
because
data
has
gravity
and,
and
your
help
is
always
appreciated.
They're
seeing
users
help
each
other
in
this
lecture
now
and
also
a
CN
CF
echo
system.
Interaction
between
projects,
accelerating
users,
pipelines,
hearing
feedback
from
users
is
what
keeps
me
and
my
team
always
motivated.
D
You
can
be
part
of
it,
it's
extremely
diverse
community
and
we
have
rust
experts
coding,
very
low
level
storage
part.
Also.
We
have
go
issues
for
beginners.
We
also
have
a
goal
to
train
and
coach
new
graduates
and
bring
them
to
kubernetes
ecosystem.
So
we
had
interns
now
became
core
contributors
to
key
CN
CF
projects
and
also
again
a
Brian
mentioned.
So
we
maya
data
didn't
just
be
become
one
of
the
top
cnc
of
project
contributors
who
we
are
by
coincidence
by
ecosystem
users
come
before
the
company
always
for
us
and
our
mission.
D
A
C
D
Yeah,
let
me
take
one
question:
could
you
compare
GNC
store
historically,
so
Jeeva
came
first
because
we
wanted
to
prove
that
this
DevOps
way
of
providing
storage
can
be
used
or
useful
for
this
new
persona,
but
between
Jie,
why
insist
or
Jeeva,
creates
sparse
files
on
top
of
existing
file
system
most
of
the
time
the
route
route
disk.
So
it
is
a
useful
in
the
environments
where
your
volumes
are
smaller
and
when
you
don't
have
specially
additional
discs
to
manage-
and
let's
say
H
devices
or
small
environment
or
mini
cube
deployments.
D
So
you
only
have
the
OS
disk
from
the
nodes.
You
can
create
a
highly
available
storage
by
creating
sparse
file
on
multiple
nodes
where
C
store
is
a
more
advanced
version
where
it
brings
in
this
disk
management,
capability
or
striping
or
rating
disks
on
multiple
nodes,
as
well
as
where
you
have
additional
nodes
and
very
you
need
larger
volume
sizes
and
then,
on
top
of
that,
it
C
store,
uses
copy-on-write
filesystem
underneath,
which
means
the
snapshots
and
clone
capabilities
are
more
efficient
in
there
with
JIRA.
C
C
Can
over
it
is
cluster
with
open
EPS
act
as
a
dedicated
storage
cluster
for
another
kubernetes
cluster,
though,
with
the
community
project
that
we
have,
we
recommend
using
open
e
BS
on
kubernetes
cluster
itself,
but
we
have
had
conversations
in
the
community
channel
where
users
have
tried
to
do
just
exactly
what
this
person
is
asking.
So
if
you
look
at
the
influence
of
open,
IPs,
open
EBS
is
provides
proc
vol
services
and
the
block
volume
services
in
turn
translate
into
kubernetes
objects.
D
And
let
me
take
this
new
question.
What
about
I
ops
in
my
store?
Is
it
a
fest
comes
from
Sergey?
Yes,
my
store,
so
the
after
C
store,
which,
like
I
mentioned,
uses
the
copy-on-write
file
system.
Our
core
strength
is
storage
and
we
started
this
Maya
store
project.
A
year
ago.
Now
so
I
wrote
everything
from
scratch.
It's
written
in
rust
and
built
from
scratch
like
I
mentioned,
and
he
uses
Intel.
D
Sp
DK
libraries
and
our
goal
was
to
remove
the
overhead
of
I
scuzzy
and
then
other
overheads
in
the
network
layer
and
also
do
this.
In
the
user
space
we
were
able
to
achieve
like
single-digit
loss,
even
with
the
replication
over
network,
so
which
means,
if
you
are
using
Mema
devices
which
are
now
which
you
can
get
multiple
millions
of
iOS.
So
in
a
demo
at
last,
coke
Yukon,
we
demoed
I,
don't
exactly
remember
but
multiple
millions,
I
think,
like
five
six
million
iOS
in
a
single
container,
very
close
to
the
Rho
device
performance,
I.
C
Can
take
another
question,
so
this
question
is
from
anonymous:
we've
tried
through
but
phone
safe
to
be
a
bit
complicated
to
manage.
Why
should
I
consider
open
a
PS
and
how
it
differs
from
rogue
upon
the
aspect
of
how
open
it
is
differs
from
group?
So
Luke
is
a
orchestration
platform,
so
I
see
multiple
storage
engines
being
orchestrated
by
Luke
and
Luke
is
focused
on
just
being
a
orchestration
layer
for
storage
with
open
EBS.
We
have
the
orchestration
layer
as
well
as
the
storage
engines,
and
there
are
multiple
storage
engines
that
open
abyss.
C
Of
course,
we
just
touched
upon
the
C
store
and
chiva,
but
we
also
have
local
PV,
which
is
basically
dynamically
provisioning
of
the
like.
A
local
PVC
is
supported
in
open,
EBS
and
they're
like
different
flavors
of
local
PV,
that
we
can
use
from
host
path
to
block
devices
to
even
using
on
top
of
ZFS.
C
D
If
you're
good
with
time,
let
me
take
another
question
from
my
maji
maji,
sh
I
hope:
I
pronounced
your
name
right
so
for
cloud
g,
ka
k,
SE,
TS,
use,
sister,
I.
Think
a
question
is:
why
should
I
you
see,
store
opening
vs,
obstructs
the
storage
management
and
layer
and
it
unifies
but
comes
with
the
additional
benefits,
of
course,
especially
with
cloud
volumes.
If
you
are
running
kubernetes
on
cloud,
you
can
replicate
volumes
across
multiple
availability
zones.
That's
one
benefit.
Our
users
find
useful
most
in
the
second
one
is.
D
You
can
also
use
locally
attached
discs
which
are
not
persistent
in
a
cloud
environment
and
in
replicate
over
multiple,
so
that
would
give
you
a
lower
cost
higher
performance
storage
devices,
but
also
highly
available
and
another
I'll
tell
another
benefit.
Is
this
a
known
volume
mount
unmount
issues
when
it's
replicated
or
sometimes
mountain
mount
can
take
quite
some
time
or
get
stuck,
and
in
that
case
also
open
EBS,
our
users
find
it
useful
to
have
a
replica,
and-
and
this
probably
would
help
another
question
from
Philippa
hello
I
would
like
to
know.
D
We
are
also
using
in
the
Enterprise
version
of
open,
EBS
or,
but
that
the
plug-in
is
available
open
in
the
open
source
repository
leveraging
Valera.
With
some
of
additional
code
on
top
of
Valero,
we
open
a
BS
as
a
Valero
plugin.
You
can
create
their
scheduled
backups
of
complete
backups
of
your
application
and
pvp
VC's
into
an
s3
back-end,
and
then,
from
that
back
end
you
can
asynchronously
restore
to
any
cloud.
This
solution
is
used
again
by
our
users
in
the
community.
D
C
C
D
D
D
That
gives
you
a
user
interface
for
opening
BS
with
Valero,
which
we
call
D
mass
data
migration
as
a
service,
and
that
is
probably
closes
it
and
get
to
full,
persistent
and
backup
a
solution
for
storage.
So
you
can
take
as
schedules
backup
from
the
user
interface
to
an
s3
target,
AWS,
GCP
or
Mineo,
and
then
recover.
D
D
Yes,
if
you
are
the
same
with
kubernetes
clusters,
if
they
are
spreading
across
multi-region,
they
need
to
have
a
good
network.
Communication
in
between
latency
would
have
an
impact
on
storage
performance
as
well,
but
in
that
case
where
the
latency
is
higher,
we
recommend
the
solution.
I
recently
mentioned
the
D
mask,
so
you
can
take
a
kind
of
a
asynchronous
replication.
You
can
call
it
a
synchronous
replication,
but
it's
more
like
a
disaster
recovery
solution,
backup
on
one
cluster
and
instead
of
synchronously
replicating
asynchronously,
recover
data
on
another
cluster.
C
There's
a
question
from
module
on
now:
I
I.
Think
our
president,
do
you
have
any
plans
of
optimizing
the
rebuild
in
the
case
of
BM
BM,
completely
getting
lost
and
anyway
I'm
coming
up?
I!
Think?
Yes,
that's
in
progress.
You
know
with
each
release.
We
are
also
automating
a
lot
of
operations
around
the
rebuilding
and
optimizing
that.
D
C
D
To
take
this
last
one:
do
you
have
any
benchmark
comparison
itself,
so
apples
their
post
comparison
would
be
difficult,
because
o
open
EBS
is
a
granular
per
a
per
application
storage.
So
it
grows
easily
there
scale-out
storage
solutions,
you
pre-configured
deployed
for
a
different
different
purpose
in
and
and
you
can,
it
has
a
larger
plus
radius,
then
open
EBS
a
so.
We
do
have
some
comparison,
but
it
differs
in
every
every
scales
one.
It
wouldn't
be
fair
to
run
benchmark
on
one
workload
versus
when
you
grow,
two
thousand
workloads
or
open
EBS.
D
C
Yeah
I
think
there's
a
good
one
from
I,
like
maybe
just
try
to
take
this
as
a
last
question,
the
question
is:
can
you
talk
about
how
storage
engine
updates
are
performed?
So
one
cool
thing
about
openness?
Is
it's
all
in
user
space
and
running
as
kubernetes
parts,
so
that
helps
you
to
perform
the
upgrade
just
like
any
other
communities
applications
you
can
actually
do
rolling,
updates
to
get
the
storage
engines
updated
and
with
one
dot
o
open
ups
or
not,
or
that
we
just
released
like
poster
barcelona
cube
con.
A
And
just
reminder
from
the
CSE
f:
don't
if
you're
in
the
area
of
Sydney
or
say,
don't
forget
to
subscribe
yourself
for
the
communities
forum,
it's
a
great
place
to
meet
professionals
and
discuss
your
issues
or
your
desires
about
the
communities
with
that
I
like
to
close.
Thank
you
more
at
brand
and
Kieran
great
presentation.