►
From YouTube: The Stateful Landscape: The Then and Now and the Future - Erin Boyd, Quinton Hoole & Alex Chircop
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
The Stateful Landscape: The Then and Now and the Future - Erin Boyd, Apple, Quinton Hoole, Facebook, & Alex Chircop, StorageOS
This talk will discuss how the CNCF storage SIG in the CNCF operates, identifies projects for Cloud Native admission and where we see the future of storage in the Cloud Native Ecosystem heading. During this session we will cover: - Overview of the SIG, how to join and how to help - Overview of storage projects in the CNCF - Projects that are currently being being reviewed - Areas we would like to see, and gaps in the landscape - Overview of the CNCF Storage Landscape document - Overview of the Performance and Benchmarking document
https://sched.co/etT1
A
Hello
and
welcome
to
the
introduction
to
the
cncf
sig
storage.
Today
we're
going
to
be
talking
about
the
cloud
native
storage
landscape
and
what
we're
what
we've
been
seeing
and
what
we've
been
working
on
and
the
what
we're
seeing
in
the
future
for
cloud
native
storage,
my
name
is
alex
kirkup,
I'm
the
founder
and
ceo
of
storage
os
and
one
of
the
co-chairs
of
the
sig
storage
and
I'm
here
with
micro,
presenter,
erin
boyd.
B
B
B
We'll
also
take
a
look
at
a
couple
of
the
projects
that
are
currently
in
review
and
then
alex
is
going
to
go
into
areas.
We
would
like
to
see
more
projects
participate
in
possible
gaps
in
the
landscape,
an
overview
of
the
cncs
storage
landscape
document
that
was
published
earlier
this
year
and
an
overview
of
the
performance
and
benchmarking
document
that
has
recently
been
published.
B
B
It
also
has
a
link
to
the
current
conference,
call
that
we
use
every
time
we
meet
so
that
you
can
just
bookmark
that
and
then
our
agenda,
which
is
open
for
anyone
to
add
items
that
they
would
like
to
discuss
within
that.
Also
within
the
agenda.
We
try
to
keep
very
thorough
meeting
minutes
and
then
there's
the
recordings.
So
if
you
have
time-
and
you
want
to
go
back,
you're
welcome
to
watch
any
of
the
previous
recordings
of
the
meeting
and
then
lastly,
we
would
love
for
you
to
join
the
mailing
list.
B
The
mailing
list,
we
send
out
information
questions
that
may
come
up
also
links
to
the
recording
in
the
agenda
when
we're
done
with
each
one
of
the
calls.
So
our
calls
and
our
membership
are
always
open,
we're
completely
transparent.
So
if
you
have
any
questions
or
concerns
you
can
reach
out
to
us
through
any
of
those
means.
B
So,
who
is
on
the
storage
sig?
What
is
it
comprises?
So
I
would
say
currently
the
participants
within
the
cncf
storage
sig
are
a
very
diverse
group
of
both
users
and
developers
of
cloud
native
technologies,
and
we
all
have
a
strong
storage
focus
and
we're
all
leaders
and
early
adopters.
Many
of
us
have
been
involved
in
kubernetes
since
the
beginning
and
have
seen
the
progression
of
how
storage
has
changed
from
being
a
technology
where
we
pre-provision
volumes
and
connected
to
them
to
dynamically
provision.
B
To
you
know,
adopting
object,
storage,
for
instance,
and
so
we're
organized
into
three
different
leads
all
from
different
vendors
or
companies
alex
myself
and
quentin.
And
then
we
have
tech
leads.
Who
are
volunteers,
that
help
also
review
projects
and
do
due
diligence,
jing,
luis
and
then
saad
saad
is
also
a
toc
member.
So
he
helps
perform
some
of
the
tocd's
to
the
storage
sig
as
a
liaison
between
the
two.
B
So
what
do
we
do?
What
exactly
is
involved
in
our
participation
in
the
cncf
storage
state?
So
the
idea
of
the
sig
was
to
have
subject
matter.
Experts
in
storage
be
able
to
review
projects
or
talk
to
different
projects
and
early
adopters,
so
that
the
toc
could
then
scale
those
contributions
in
a
way
that
they
feel
like,
were
you
know,
reviewed
technically
their
due
diligence
was
done
on
it
and
also
be
able
to
reach
out
to
the
end
user
community
for
storage,
to
retain
that
integrity
and
quality
and
therefore
support
the
cncf
mission.
B
There
are
a
multitude
of
projects
that
apply.
You
know
weekly
monthly,
that
want
to
be
part
of
the
cncf
and
it
became
a
bottleneck
to
be
able
to
review
those
fully.
So
the
idea
of
the
six
was
created,
separated
out
by
different
components
within
the
cloud
native
landscape,
and
here
we
are
with
storage
again.
The
storage
safe
was
one
of
the
first
things
to
be
created,
and
most
of
us
have
served
since
then.
So
what
we
do
as
part
of
that
mission
is
we
educate.
B
We
review
the
storage
project
proposals,
we
engage
with
the
user
community
and
we
work
with
toc
and
other
cigs.
So
what
does
that
mean?
Other
cigs,
so
many
times
projects
cross
over
these
different
lines?
They
don't
meet
into
these
nice
little
containers
for
a
pun,
so
many
times
a
project
will
come
into
the
cncf
and
they
will
have
a
component
of
storage
within
that
they
might
have
a
key
value
store.
They
might
have
a
database,
that's
associated
with
it.
B
B
So
part
of
that
end,
user
education
is
publishing
white
papers
and
various
other
items
that
help
educate
our
end
users
on
how
to
select
the
best
storage
for
the
use
case
that
they're
wanting
to
use
and
adopt,
and
so
white
papers
presentations,
videos.
All
of
these
things
are
a
form
of
training
to
better
teach
people
new
to
kubernetes
or
to
go
to
cloud
native
or
who
may
be
coming
from
legacy
applications
and
how
they
need
to
change
them.
We
try
to
develop
generalized
vendor-free
best
practices
around
this.
B
It's
on
version
two
and
the
white
paper
is
long,
but
it
is
extremely
comprehensive
in
trying
to
net
out
what
are
all
the
different
components
involved
in
traditional
storage
and
also
within
cnc,
also
within
the
cloud
native
landscape.
What
do
those
things
mean
when
we
start
running
them
in
a
cloud-native
fashion?
B
B
It'll
be
a
version
one
to
be
able
to
articulate
how
we
could
do
performance
and
benchmarking
within
this
cloud-native
landscape,
because
it's
very
different
than
it
would
be
done
in
a
normal,
traditional
storage
and
then
as
much
as
possible.
We
provide
that
information
and
we
publish
it
out
to
our
users
and
we
strive
to
be
very
vendor
agnostic,
open
and
publish
everything
that
we
find.
B
And
then
part
of
the
project
review
there
are
within
the
cncftoc.
If
you
go
into
github,
you
can
see
many
of
the
different
processes
laid
out.
You'll
see
this
nice
little
graph.
We
have
at
the
bottom,
published
there
as
well,
and
so
this
shows
how
the
sig
is
involved
in
the
review
of
many
projects,
and
so
our
part
of
our
job
is
to
first
identify
to
the
cncf
gaps
that
we
see
in
the
project
portfolio,
but
then
to
also
go
through
the
current
projects
and
make
sure
that
they're
still
tracking,
where
they
should
be.
B
Ideally
when
projects
are
accepted
into
sandbox.
The
idea
is
that
we
see
a
viability
of
that
project
and
we
want
to
see
it
progress
through
the
different
levels,
incubation
and
then
graduation
and
so
part
of
that
we
call
them
health
checks,
but
it's
really
projects
moving
from
level
to
level
and
seeing,
if
they're
meeting
the
criteria
from
one
to
the
next,
it's
also
to
perform
discovery
and
outreach
to
different
projects.
We
may
hear
of
a
project
within
the
community
or
some
may
reach
out
to
them.
B
We
also
help
those
candidate
projects,
so
part
of
our
job
is
not
to
be
the
yes
or
no,
let's
say
within
these
projects,
but
part
of
it
is
to
identify,
maybe
where
there's
gaps
and
work
with
that
project
to
help
them
remedy
any
issues
that
we
might
see.
That
would
prevent
them
from
being
part
of,
you
know,
incubation
or
graduating
project,
and
so
once
we
have
the
projects
assigned
it's
assigned
to
the
sig.
B
B
We
engage,
we
really
try
to
reach
out
to
end
users
to
gather
their
input
and
feedback
regarding
where
they
see
pain,
points
on
either
using
these
technologies
or
integrating
the
technologies
into
their
roadmap.
What
are
their
primary
use
cases
that
they're
using
that
technology?
We
try
to
document
that
and
gather
that,
and
we
try
to
put
that
in
a
consumable
report
either
that
be
a
presentation
or
then
into
our
white
paper
as
a
new
version,
and
we
try
to
include
in
there.
B
You
know
what
is
what
are
the
different
components
of
that
technology
that
make
it
unique?
Maybe
it's
the
design
of
the
architecture,
maybe
it's
the
ux,
but
we
try
to
capture
all
that
information
and
publish
it.
We
also
try
to
enable
the
community-
our
probably
biggest
thing
is
within
our
bi-monthly
meeting
and
taking
those
agenda
and
notes,
sending
information
out
on
the
mailing
list
and
keeping
our
communications
open,
and
the
documents,
of
course,
are
obviously
openly
published
and
maintained
and
we're
continually
open
to
feedback.
B
And
lastly,
I
believe
we
work
as
a
trusted
advisor
to
the
toc
so
many
times
the
tocs
formed
a
limited
number
of
people
and,
depending
on
the
year,
there
isn't
always
a
representative
who
can
speak
to
a
subject
matter:
expert
level
for
storage.
So
the
idea
as
well
of
having
a
storage
sig
is
to
be
able
to
be
the
trusted
advisor
to
them
to
provide
input
in
terms
of
how
the
project
can
scale
if
it
adheres
to
the
cncf
values
and
also
the
health
of
the
project.
B
B
Maybe
you
don't
have
anything
that
you
want
to
bring
forward,
but
you
want
to
be
involved
in
the
process
and
have
input.
We
completely
welcome
that
and
they
are
openly
published
and
can
be
commented
on,
and
you
know,
though,
we're
just
have
looked
mainly
at
management
frameworks
and
block
stores.
You
know
we're
really
focused
on
trying
to
get
possibly
more
object,
stores
in
or
databases.
You
know
the.
B
I
don't
feel
like
we're
at
the
limit
of
what
we
can
accept
within
the
storage
thing,
and
there
are
many
projects
that
have
presented
on
the
bi-monthly
meeting.
Just
some
of
them
listed
here.
You're
welcome
to
go
back
through
the
meeting
minutes
of
the
agenda,
search
for
any
one
of
these
and
find
the
reporting
so
that
you
can
go
learn
more
about
these
projects
listed
below.
A
Yeah,
just
just
a
small
interjection
to
to
echo
the
sort
of
the
the
passion
we
have
for
the
community.
You
know
we're
we're
a
really
diverse
community
covering
sort
of
vendors
and
leads
and
maintainers
from
different
projects
as
well.
As
you
know,
just
independent
contributors
and
and
we're
the
the
most
exciting
thing
for
us
is,
is
to
discover
new
projects
and
discover
new
concepts
which
which
help
the
the
cloud
native
storage
environment.
B
B
Stick
and
so
what
wasn't
mentioned
on
that
slide
as
far
as
the
levels
is
the
cncf
sandbox,
so
the
sandbox
process
has
changed
dramatically
within
the
past
few
years,
and
the
sandbox
is
meant
to
be
an
early
stage
to
identify
potential
projects.
That
would
be
a
good
fit,
but
don't
yet
meet
the
criteria
of
incubation
or
graduation.
B
So
you
can
go
to
this
link
below
look
at
the
different
inbox
projects.
Are
there
and
then
also
look
at
how
you
can
contribute
your
project
as
a
sandbox
project?
The
idea,
though,
of
the
sandbox,
is
truly
to
grow
and
cultivate
the
project
into
a
viable
incubation
project.
So
both
the
toc
and
the
sigs
are
committed
to
helping
projects
get
visibility,
that
they
need
contributions
and
advice.
B
A
A
The
attributes
that
make
up
a
storage
system
is
is
really
important,
as
is
understanding
all
the
different
layers
in
in
a
storage
solution,
as
as
nowadays,
there
are
a
variety
of
layers
that
that
affect
the
virtualization
or
the
integration
with
with
an
orchestrator
and
and
understanding
those.
Those
layers
is
also
impactful
to
the
the
attributes
of
the
storage
system
and
then,
finally,
we
review
the
different
data
access
interfaces
in
terms
of
both
volumes
and
apis
and
and
also
the
definition
of
the
the
management
interfaces.
A
So
I've
I've
put
in
a
little
summary
in
the
next
couple
of
slides
the
cover
of
things
like
the
the
data
access
interface,
which
is,
which
is
the
way
that
you
that
you
persist
or
or
access
data
in
the
system.
We
we
tended
to
group
this
in
the
white
paper
into
into
two
main
buckets,
the
the
first
being
volumes.
A
A
A
The
key
here
is
that
each
storage
system
may
have
may
have
a
number
of
different
attributes,
and
often
attributes
can
be,
can
cause
compromises
with
different
attributes.
So,
for
example,
you
know,
scalability
and
and
performance
and
consistency
might
have,
projects
might
have
different
optimizations
in
each
of
those
in
each
of
those
attributes
to
to
hit
different
use
cases.
A
B
A
B
A
In
the
storage
world,
there
are
lots
of
lots
of
factors
that
can
affect
performance.
Everything
from
things
like
compression
or
different
caching,
or
different
physical
infrastructure
or
different
virtualization
parameters,
or
even
things
like
you
know,
encryption
and
and
and
other
types
of
data
protection
can
can
affect,
can
dramatically
affect
the
the
performance
of
different
systems.
A
A
A
So
what
we
always
recommend
is
that
end
users
run
their
own
tests
on
their
own
storage
in
their
own
environment,
so
they
can
understand
how
their
particular
environment
behaves
with
with
their
storage
environments
and
that
ultimately
gives
them
a
better
understanding
and
the
better
and
a
better
capability
of
figuring
out
what
their
application
needs
and
what
their
application
demands
are,
and
that's
it
with
that.
We
finish
our
presentation
and
we'd
love
to
hear
questions
and
we'll
be
hopeful,
we'll
be
we'll,
be
online
to
take
questions
and
and
hear
any
comments.