►
From YouTube: Chaos Engineering WG - 2018-06-12
Description
Join us for Kubernetes Forums Seoul, Sydney, 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
A
A
B
Hi
I
just
want
to
say
hello
to
our
event,
so
since
it's
the
first
time
to
join
this
excellent
online
meeting
and
I'm
long
from
kth
and
I'm
a
yolk
EHD
student
in
computer
science,
my
supervisor
is
Martin
mattress
and
our
team
is
really
interested
in
chaos,
engineering
and
the
self-healing
software,
and
also
some
fault
injection
things.
So
it's
really
related
to
this
work
and
yeah
I'm
very
happy
to
like
contribute
more
to
this
community
in
the
future
cool.
Thank.
C
C
D
A
A
If
you
attend
just
just
makes
it
easier
to
track
who
attends
and
who
doesn't
so
moving
on
slide
four,
so
there's
a
bit
of
a
scheduling
conflict
for
a
couple
of
us,
I'm
just
gonna
propose
that
we
keep
the
same
time,
but
we
move
the
meeting
to
be
every
other,
we're
on
every
second
and
fourth
Tuesday
of
the
month
that
ideon
Pacific
and
we'll
start
with
that
change
on
July
10th
and
July
24th
moving
forward.
Does
anyone
have
any
issues
with
that
specific
timing?
A
Allisyn
scheduling
is
always
a
pain
in
the
ass
Oh,
appreciate
people
being
flexible,
flexible
here,
all
right,
so
I'll
get
that
updated
on
the
meeting,
inviting
the
Google
Calendar.
So
oh,
but
I'll
do
that
after
this
meeting
so
slide
five
and
six
kind
of
cover
the
landscape.
So
one
of
the
kind
of
outputs
of
the
group
that
we
want
to
accomplish
is
to
actually
come
up
with
a
landscape
similar
to
what
we
have
available
currently
in
CNC
F.
A
If
you
go
to
L
dot,
C
and
C
F
dot,
IO,
you'll
kind
of
see
this,
you
know
huge
cloud
native
landscape
which
basically
covers
the
different
companies
and
technologies
in
this
space.
So
you
know,
we've
been
trying
to
take.
You
know
an
index
of
all
the
different
projects
out
there
and
try
to
categorize
them
into
different
categories.
A
E
C
E
A
A
So
there
so
there
is
a
I
mean,
there's
a
tool
that
essentially
the
landscape
that
I've
worked
at
the
repo
that
will
eventually
make
the
additions
and
changes
too,
and
then
we
have
a
design
team
that
will
render
a
pretty
graphic
based
on
that,
but
I
posted
a
spreadsheet,
where
I'm
collecting
is
essentially
I'm
filtering
at
some
of
the
projects
that
we've
added
to
that
sheet
to
be
at
a
certain
level
where,
let's
say
they're
they're,
not
just
like
a
research
project.
Maybe
they
have
a
bit
of
a
community
in
C
and
C.
A
If
we
kind
of
have
this
ridiculous
criteria
of
like
at
least
250
github,
freaking
stars
right
or
whatever,
essentially
it
has
to
be
something-
that's
you
know
has
somewhat
of
a
community
behind
it,
but
I'm
fine
doing
it
in
the
spreadsheet
so
you're
more
than
welcome
to
make
some
additions
there,
I'll
post
the
spreadsheet
in
the
github
issue
too.
If
that
works
for
you,
oh
yeah,.
E
A
Eventually,
that
will
be
dumped
via
pull
request
to
the
CN
CF
landscape,
okay,
cool
yeah,
I'm
in
terms
of
categorization.
You
know:
I've
real
I'm
really
torn
on
the,
like,
obviously
there's
hosted
offerings,
and
then
there
is
basically
tools
that
focus,
maybe
on
different
aspects
of
chaos:
engineering,
whether
it's
you
know,
storage,
security
or
just
general.
A
E
A
A
F
A
Yeah
sounds
good
and
the
challenge
is
some
tools
overlap
and
do
multiple
categories
right.
So
then
you
get
in
this
weird
situation
where
a
tool
appears
on
every
every
section,
which
is
just
weird.
So
it's
the
other
thing
that
you
know
also
came
across
my
mind.
Is
you
know,
do
we
also
have
a
category
for
the
cloud
providers
that
support?
A
7
is
basically
kind
of
the
criteria
that
I
mentioned
that
we
use
for
what
we
add
to
the
landscape.
Essentially,
we
just
want
projects
that
are
more
than
just
research
projects
or
someone's
kind
of
small
project
stuff.
That's
actually
fairly
used
but
slide
8.
It's
basically
my
attempt
of
we
essentially
have
two
options
here.
We
either
create
kind
of
a
new
category
within
the
current
landscape
and
just
add
a
section,
maybe
under
kind
of
where
orchestration
and
management
is
and
create
a
specific
subsection
forecast
engineering
or
create
an
individual,
separate
landscape
specifically
for
kit.
A
You
know,
chaos,
engineering,
group
group
to
group
the
part,
so
my
concern
was,
if
we
don't
have
enough,
you
know.
If
we
have
a
couple
handful
of
tools,
then
maybe
it
makes
sense
to
kind
of
graft
in
the
in
the
bigger
landscape.
If
we
have
more
than
that,
maybe
we
could
have
our
own
separate
landscape,
I,
don't
know
if
there's
strong
feelings
in
the
group
of
which
way
you
know
we
go
forward
with
this.
We
want
to
decide
now.
It's
just
I
thought.
G
F
A
So
I
mean
if
you
look
at
that
landscape.
I
pointed
you
so
the
way
CN
CF
has
organized
it's
it's.
You
know
each
project
is
free
to
create
its
own
working
groups
or
effort.
So,
for
example,
kubernetes
has
SIG's
and
working
groups
around
storage,
security,
node
and
so
on.
Each
other
projects
in
CN
CF
have
similar
setups.
There
tend
to
be
a
little
bit
simpler,
CN
CF
wide.
We
have
working
groups
dedicated
like
server
lists.
You
know
networking
storage,
stuff
that
affects
all
of
our
projects.
Chaos.
A
All
right
so
so
from
my
feedback
from
the
group
is,
will
will
create
our
own
kind
of
smaller
landscape,
similar
to
kind
of
with
the
work
we
did
with
survey
lists
and
kind
of
go
from
there
and
then
see
how
that
works
out
and
grows
over
time.
Okay,
cool
all
right,
slide,
9,
so
so
moving
on
so
not
much,
let's
see
where
we
slide
10
or
slide
12.
Sorry.
A
Basically,
the
main
things
here
is
pointing
people
out
to
the
white
paper
issue
we're
gonna
iterate
on
that
on
github,
instead
of
the
Google
Doc
and
just
send
pull
requests
there,
I
will
formally
work
on
the
proposal
to
C
and
C
F,
the
former
working
group.
We
have
the
scheduled
time
to
present
to
the
technical
board
for
CN
CF,
but
I.
A
Don't
envision
us
doing
that
until
probably
late
July
August
timeframe,
so
are
the
Nets
gonna
open
up
for
any
questions
and
answers'
is
a
couple
reminders
that
Kaos
cough
is
coming
up
believe
in
late
September,
CN,
CF
sponsoring
and
will
be
there
so
be
great
to
see
some
folks.
There
I'm
also
really
looking
for
volunteers
to
present
next
time.
So
I
don't
know
if
you
know
whom
I
maybe
want
to
present
litmus
or
if
anyone
else
has
something
present.
It
would
be
good
to
get
you
slotted
for
ornette
next,
our
next
meeting
any
volunteers,
yeah.
E
I
I
A
J
A
Add
yourself
to
the
maintainers
fall
as
that's
how
I'm
tracking
folks
to
add
to
the
github
team.
So
please
do
that
you'll!
Basically
anytime,
we
make
a
major
decision
or
anything
like
that.
I
essentially
just
want
a
simple
majority
from
the
maintainer
like
when
we
finalized
it
for
Mosel
proposal.
I'll
ask
the
maintainer
x'
for
a
vote
before
we
bring
it
forward
to
the
technical
board,
so
sample
requests.
F
A
A
So
if
there's
something
that
you
basically
you
know
at
the
end
of
the
day,
what
we
developed
will
be
disseminated
to
a
fairly
wide
audience
right
so
that
you
know
that's
kind
of
my
goals
come
up
with
something
that
you
know
anyone
could
kind
of
read
over.
You
know:
10
10,
15,
minutes
and
kind
of
get
a
good
overview.
What
the
hell
is
going
on
and
in
chaos
engineering,
so
so
I'd
I'd
go
for
it
like
what,
if
you
think,
something's
missing
make
a
suggestion
and
we
could
kind
of
all
work
together
on
this.
K
A
So
yeah
we
could
go
there.
You
know
the
other
thing
that
I
that
would
be.
Nice
is
since
I
still
kind
of
consider
this
in
East
and
field,
having
maybe
a
section
around
a
couple,
maybe
a
handful
or
a
few
case
studies.
So
you
know
obviously
internet
scale.
Folks,
like
LinkedIn,
you
know,
are
doing
this
Netflix
some
of
the
bigger
ones.
So,
maybe
highlighting
you
know
a
few
of
those
concrete
kind
of
case.
Studies
in
in
the
white
paper
would
be
a
good
thing.
In
my
opinion,.
A
A
Section
you
kind
of
see.
So
basically
you
know
it's
summarizes,
you
know
what
is
the
fields?
What
are
the
benefits,
pros,
cons,
different
use
cases
and
and
so
on
so
I'm,
not
advising
us
to
go
as
crazy
in
in-depth,
as
as
they
did,
there's
a
I
think
a
lot
more
politics
in
the
service
space
than
there
is
in
chaos.
Engineering,
so
I
think
things
that
are
a
little
bit
simpler
for
us.
K
A
And
you
know
to
be
honest,
like
you
know,
at
least
within
a
CNC.
If
membership,
you
know,
we
have
a
lot
of
companies
a
lot
of
cloud
providers,
so
what
we
do
will
influence
thoughts.
So
as
long
as
we
position
away
like
you
know,
this
is
new.
This
is
being
pioneered
by
some
of
the
you
know.
Internet
scale,
companies
out
there,
we
kind
of
want
to
disseminate
this
practice
for
for
everyone
and
show
them
different
tools
and
and
things
that
they
could
use.
A
You
know
my
my
future
goals
has
always
been
to
have
the
cloud
providers
support
this
kind
of
by
default
and
also
us
having
a
stable
set
of
open-source
tools
available,
for
you
know,
folks
to
use
to
implement
this
on
their
own.
Could
that
be
the
mission
of
this
working
group?
Actually,
the
dot
that
kind
of
is
the
mission
produce,
fly
paper
landscape
and
make
a
set
of
recommendations
to
the
TOC,
and
maybe
projects
that
belong
in
in
CNC
F
and
in
the
future.
A
A
Well,
any
other
questions
or
thoughts
appreciate
everyone's
times
and
getting
this
you
know
we're
still
in
the
bootstrapping
phase,
so
definitely
appreciate
people
taking
time
out
of
their
schedule,
but
it's
great
to
kind
of
hear
from
practitioners
and-
and
you
know,
iterate
on
our
kind
of
white
paper
and
landscape.
So
all
right
thanks
a
lot
all
I'll
close
the
meeting
I'll
the
recording
will
be
post
on
the
CNC
F
YouTube
channel
I'll
make
sure
to
post
it
on
the
slack
once
it's
done,
but
hopefully
within
24
hours.