►
From YouTube: Cloud-Native Chaos Engineering WG Weekly Sync Up - July 16 2021 | CNCF TAG App Delivery
Description
Check out the recording from the Cloud Native Chaos Engineering Working Group Weekly Sync Up from July 16th, 2021
For more information check out the WG Charter: https://docs.google.com/document/d/1scr9uuvG1g1xpIHPs3314FqeFufE31ustTVnRMrX3gI/edit?usp=sharing
A
A
I
just
wanted
to
get
some
kind
of
a
cadence
started
and
based
on
the
feedback,
thursdays
ep
was
good.
We
just
went
ahead
and
set
it
up.
I
have
not
received
accept
on
the
invitation
from
all
the
members.
You
can
still
go
ahead
and
just
get
started
with
some
discussion,
mostly
around
the
operating
model.
Logistics
of
the
work
group.
C
Hi
hi,
I'm
late
for
this
meeting.
A
So
I
think
I
have
set
a
recording
for
this
zoom
call
and
not
yet
figured
out
where.
A
To
be
uploading,
it
there's
going
to
be
a
dedicated
youtube
channel
for
the
same,
but
nevertheless
we
can
just
go
ahead
and
find
out
those
details.
In
fact,
I've
even
sent
an
email
to
the
cncf
mailing
list
owner
to
give
us
a
mailing
list
for
this
operating
work.
Group
we'll
see
how
that
comes
through
all
right.
I
think
I'll
start
sharing
my
screen.
We
can
get
started
here.
Five
minutes
past
time.
A
B
B
A
Okay,
so
I
think
last
time
we
spoke
about
the
charter,
we
just
went
through
it
very
quickly
and
I
just
tried
to
crystallize
our
notes
here,
our
intros,
our
motivations
and
what
we
discussed
about
the
charter,
the
fact
that
we
needed
a
few
more
goals
and
basically
try
and
address
some
of
the
comments
that
were
raised
by
jericho
and
we
also
went.
A
Our
meeting
timings
and
guidance,
the
need
for
separate
meetings,
as
you
can
see,
I've
been
asking
folks
from
the
eu
side
and
whatever
time
is
for
them,
so
5
pm
london
time
is
what
they
seem
to
suggest
so
we'll
see
how
we
can
go
ahead
and
accommodate
that.
A
I
think
different
personnel
can
attend
these
meetings,
which
I
think
should
still
should
be
fine
as
long
as
we're
able
to
get
some
work
done,
asynchronously
and
yep.
So
this
is
what
we
did
and
on
similar
lines
I
thought
there
would
be
few
other
things
that
would
be
good
to
thrash
out
at
the
beginning
of
the
workgroup
discussions
before
we
delve
into
the
actual
chaos,
engineering
practices
and
discussions
and
presentations.
A
A
I
see
that
newer
groups
that
are
getting
created
have
some
kind
of
a
discussion
around
what
would
be
a
good
name
for
the
work
group.
It's
interesting.
If
you
have
any
thoughts
on
what
we
should
name
this.
I
we've
just
called
it
chaos
engineering
work
group
today,
if
you
feel
that
is
a
little
too
simple
and
want
to
have
something
that's
more
interesting,
you
could
do
that.
I've
seen
some
very
interesting
names
for
for
different
work.
B
A
As
a
shared
video
on
google
drive,
but
I
think
we'll
need
to
identify
a
place
to
put
the
youtube
recordings.
A
Do
you
have
any
idea
of
how
you
can
create
a
new
channel
within
cncf
mila
or
anyone,
or
is
it
something
we
have
to
request
formally,
I'm
not
sure
whom
to
request
for
it?
Do
you
have
any
idea
about
these
things.
A
Yeah
that
will
help
a
lot.
We
can
probably
start
pushing
our
videos
into
that
playlist
yeah,
I
think
one
of
us.
Maybe
you
can
control
the
credentials
for
that
and
or
I
could
do
that
as
well.
So
we
can
go
ahead
and
identify.
B
A
B
A
That
the
workbook
is
generating
is
all
placed
within
that
repository,
I'm
sure
they
also
have
google
down,
but
eventually
they
keep
shifting
things
to
the
repository.
So
that's
one
approach
or
the
other
one
is
to
have
something
under
the
cncf
similar
to
the
cnr.
One
group,
I
think
the
cnn
workproof
is
a
little
bit
more
mature
in
terms
of
how
long
it
has
been
operating
and
things
like
that.
So
I'm
not
really
sure
where
this
fits
or
we
need
a
repository
at
all.
A
But
I
think
if
you
do
tutorials
and
demos
when
I
say
tutorials
mostly
documentation
around
how
some
people
can
go
over
and
tackle
a
certain
situation
or
certain
failures
that
they're
already
getting
what
all
the
tests,
if
you
are
making
some
recommendations,
if
the
white
paper
needs
to
be,
you
know
stored
in
a
persistent
location
rather
than
living
in
a
google
doc
if
it
needs
to
go
into
a
repository
and
what
would
that
be?
A
Where
would
we
store
details
of
this
minutes
and
the
individual
presentations
that
users
are
coming
and
doing
in
this
work
group
etc?
So
I
think
we
need
a
repository.
A
In
my
opinion,
I'm
open
to
hearing
thoughts
from
you
all.
So
what
do
you
think?
Is
it
too
early
for
the
working
group
to
go
ahead
and
create
a
deposit?
You
can
do
this
later
in
time
or
we
can
go
ahead
and
add
this,
I
think,
I'm
sure,
just
like
the
waiting
list
youtube
channel.
There
is
a
procedure
to
ask
for
a
repository
like
this,
maybe
a
me
or
iwo.
You
need
to
speak
to
them
for
something
like
this.
What.
C
B
If
you
ask
me,
I
think
it's
it's
a
good
idea
to
have
it
under
here
on
the
repositories
yeah,
but
both
will
work.
For
me,
more
important
thing
is,
we
should
start
speaking
to
end
users
and
we
need
a
way
to
capture
all
those
results
in
one
place.
So
I
see
there
is
a
need
for
sure
to
put
the
information
together
somewhere
in
one
place.
You
know
for
the
public
usage,
I'm
okay
with
anything.
A
All
right,
this
is
one
of
the
ais
we
will
take
along
with
meeting
this
invitee
before
our
next.
C
I
I
find
many
many
things
such
as
tomorrow,
where
we
find
a
network
tank.
We
also
they
are,
they
are.
They
are
building
a
service
summit
service,
measurable
group
and
and
also
we
find
then
and
before
we
also
your
hands.
We
have
on
calcium
work.
Work
grew
here
in
kubernetes,
including
this
organization.
Do
you
remember
this
yeah?
We
will
I
find,
then
we
have
a
work
on
chaos
and
nearly
work
group
and
before
incognition
organization,
and
we
can.
We
can
we
combine
this
together
or
we
are
this.
C
Another
example:
yeah
yeah
service,
metro
group.
A
A
C
C
B
Let's
try
to
have
this,
is
you
know,
chaos
engineering
is
a
new
work
group.
There
was
a
group
that
started
long
time
back
and
it
was
discontinued,
so
this
is
basically
prior
to
having
any
of
this
chaos
engineering
work
by
multiple
projects
right
so
now
we
are
multiple
projects
and
we
are
trying
to
do
a
chaos,
engineering,
work
group
to
coordinate
across
projects
and
across
tags.
B
So
I
think
it's
that's.
The
idea
of
having
this
work
group
it'll
be
good
to
have
a
new
repo.
If
there
was
a
repo
called
chaos
and
jingle
group,
we
can
try
to
reuse,
but
I'm
not
sure
if
we
had
one.
A
Yeah
I
remember
there,
there
was
a
war
group
that
sort
of
started,
the
goal
of
which
was
to
create
the
chaos
engineering
landscape,
and
I
remember
there
were
a
few
calls
that
we
did
when
chris
chaired
it,
and
I
think
once
the
landscape
was
created,
the
group
sort
of
dissolved-
and
it
was
understood
at
that
point
of
time,
that
the
chaos,
engineering,
work
or
initiatives
would
be
carried
over
to
the
agenda
of
the
tag.
Application,
delivery,
app
delivery
at
that
point
of
time.
A
So
I
think
that
was
what
happened
to
the
older
ks
world
group,
but
I
and
I
think
the
folks
that
created
this
work
group
or
joined
this
work
group
where
also
part
of
the
chaos
engineering
slack
channel
on
cncf.
Today,
I
think
that's
the
one
in
which
mila
and
the
litmus
community
team
and
others
are
active
today.
B
A
C
A
See
interest
from
some
of
them
in
this
work
group
and
added
themselves
as
interested
parties
on
the
one
group
charter.
So
I
suppose
we
can
consider.
C
A
As
the
sort
of
work
group
representing
kia's
engineering
interest,
and
if
there
are
some
artifacts
like
a
git
repository
or
a
document
or
anything
like
that,
that
has
already
been
put
in
place
by
the
previous
team,
then
we'll
be
happy
to
sort
of
amalgamate
that
into
this.
That's
a
good
point
that
you
brought
up.
A
I
I
we
will
take
a
look
at.
We
have
many
artifacts
from
there.
B
I
just
posted
on
the
chat
I
think
shengwin
was
referring
to
that.
A
A
B
So
we
can
yeah
this,
we
tried
to
do
that
and
it
just
got
merged
into
cigarette
delivery.
At
that
time,
we
can
try
to
create
it
under
cncf.
That
may
be
a
good
one,
because
this
this
was
primarily
started
by
tvoc.
This
idea
of
having
a
cross
tag
coordination,
that's
my
opinion.
A
A
I
think
that's
the
model.
Many
work
groups
are
taking.
A
A
Okay,
so
I
think
the
other
thing
development
over
the
last
week,
respect
to
the
workgroup,
is
the
creation
of
some
goals
and
non-goals
from
alloys.
B
A
Okay,
so
I
think
we
had
some
background
problem
statement
and
goals
and
onboard
section
we
went
through
last
meeting
and
we
were
basically
interested
in
adding
more
books
as
one
of
our
agenda
items.
A
So
alice
has
gone
ahead
and
added
that
section
and
he
basically
recommended
to
start
the
charter
with
a
very
quick
background
and
the
goals
before
we
delve
into
the
problem
statement.
Equations
challenges
rest
of
sections.
A
A
So
that's
what
he
has
put
here,
basically
summarize
to
that
which
I
think
is
quite
useful
and
it
is
an
appropriate
summarization
of
what
we
already
have.
Let's
just
go
through
that
very
quickly
one
is
to
establish.
You
know
the
overall
pro
goal
would
be
to
establish
chaos.
Engineering
is
a
widely
adopted.
A
Complication
development,
I
would
say
operations
as
well
right
application.
Development
is
definitely
one
of
the
new
areas
where
chaos
is
much
being
used.
That
is,
the
non-prod
usage
is
used
in
ci
cd
usage
by
developers
or
falls
under
this
bracket.
Maybe
there
is
also
an
ops
angle
to
this
application,
development
and
delivery.
A
Some
goals
one
is
to
have
a
tool,
independent
methodology
on
how
to
conduct
scenarios
and
what
are
the
patterns
variation
of
tests,
the
results
that
people
get
out
of
an
experiment
either
in
whatever
form
they
extract
the
result
and
good
practices
in
application
delivery.
Workflows
people
can
do
it
in
ci,
cd,
the
security
testing
part
of
it
has
been
added
here
and
observability
is
also
something
that
has
been
referenced
here.
We've
talked
about
it
in
the
below
sections
as
well.
A
The
next
goal
is
about
doing
more
complex
scenarios
in
more
complex
environments,
doing
getting
multi-environments
and
hybrid
environments
that
are
both
cloud,
nato,
as
well
as
not
really
cloud
native
people
who
are
doing
migrations
to
kubernetes
or
maybe
still
re-architecting,
their
applications
might
have
older
models
of
deployments
in
the
cloud
or
on
their
own
data
centers
they
might
be
running
monolith
applications.
So
how
do
you
extend
your
native
cloud
native
chaos,
engineering
patterns
to
those
kind
of
environments
also
and
work
in
a
hybrid
model?
So
I
think
this
is
a
fair
summarization.
A
In
the
working
model,
educational
materials
and
white
papers
is
the
eventual
outcome
right
and
there's
also
something
for
tutorials
to
handle
specific
scenarios
which
basically
had
a
question
on.
Are
we
talking
about
what
would
we
say,
handle
or
we
say
about
mitigations
or
are
we
talking
about
how
to
inject
the
specific
failures?
What
do
we
mean
by
tutorials
that
show
how
to
handle
scenarios?
That's
a
little
bit
ambiguous,
so
I
have
created
equation,
but
otherwise
the
work
model
is
very
clear.
A
A
A
Community
involves
both
the
end
users
as
well
as
projects
in
the
cnc
landscape,
those
that
probably
are
not
within
the
landscape.
Also,
there
are
a
lot
of
other
tools
that
we
come
across
generally,
which
are
doing
in
a
way
cloud
native
cares,
but
are
part
of
this
unsafe
landscape
so.
C
B
A
To
why
they
created
something,
what
what
purpose
is
it
solving
and
why
they
took
a
particular
approach
and
add
it,
as
part
of
you,
know,
valid
patterns
going
around
today
and
bring
that
learning
back
into
the
white
paper?
So
I
think
this
is
a
good
set
of
goals
and
working
model
with
elaboration
in
the
subsequent
sections.
A
I
just
wanted
to
check
very
quickly
on
your
opinions
to
this.
Do
you
would
you
like
to.
A
A
As
far
as
the
working
model
goes,
I
think
we
got
started
with
the
white
paper
a
little
bit
in
terms
of
its
structure,
etcetera,
and
then
we
will
continue
to
iterate
over
that
and
we
have
been
doing
the
survey
as
part
of
an
outreach.
A
The
survey
might
be
a
little
bit
limited
in
terms
of
the
questions
it
is
asking,
but
it
gives
us
an
idea
of
general
mood
or
perspective
of
people.
We
will
get
more
details
when
we
bring
them.
You
know
on
to
the
group
meetings
and
talk
more
and
sort
of
get
stuck
in
more
and
they
start
participating
more.
I
think
that
would
be
great,
so
we
will
have
that.
I
saw
a
note
from
mila
last
time
that
she
would
like
to
invite
folks
nikias.
C
A
Sanction
is
jointly
thank
you,
mila
and
thank
you
for
joining,
so
we
would
like
to
hear
how
the
different
projects
are
looking
at
different
problems
in
the
geos
engineering
space,
so
yeah,
I
think
we
are
sort
of
starting
to
do
these
things
hope
to
continue
and
put
formal
goals
for
on
a
short
term
basis.
For
let's
say
each
workgroup
meeting
before
we
get
started
with
that
call,
we
can
identify
what
we
will
achieve
as
part
of
that
sync
up
in
terms
of
you
know
getting
some
end
users
to
speak.
B
A
In
terms
of
the
challenges
that
they
are
seeing
within
their
user
group,
so
to
say
right,
so
I
think
this
summarization
is
quite
good.
Are
there
any
thoughts
about
the
this
summarization
of
the
goals
and
how
we
are
going
to
achieve
this.
A
Thoughts
within
here,
I
sort
of
understand
that
we
are
all
on
the
same
page.
I'm
sure
there
will
be
other
thoughts
coming
in
from
the
folks
in
the
other
meeting
here.
C
Okay,
hello,
I
maybe
I
think
maybe
we
we
want
to
build
a
health
scenario.
C
Ecology
such
as
we
can
share
different
chaos,
scenarios
together
and
share
our
some
tutorials
and
other
things
on
collagen,
and
maybe
I
I
I
try
to
find
a
a
great
way
and
for
for
some
users
to
talk
together
and
to
communicate
a
plan
for
us,
our
uni
our
plan
to
to
to
to
discuss
and
to
share
that
that
the
experience
there
there
and
something
I
saw,
I
think
maybe
we
can
build
a
website
or
our
some
some
plan
to
share,
share
something
and
to
discuss
something
to
share
their
cast
account
scenarios
and
something
maybe.
C
A
That's
great,
yes,
I
am
also
an
agreement.
I
think
we
could
do
something
like.
A
Yeah
we
could
sort
of
create
a
github
pages.
Once
we
have
the
repository,
we
could
create
a
you
know:
github
pages
website-based
website,
oh
yeah
different
scenarios
and
possible
mitigations
around
it.
It's
a
great
idea.
C
Yeah
you
you
can
find
in
chatting
boot
and
some
someone
has
type
in
my
my
my
ideas
and
here.
A
Yeah
makes
sense,
I
think
sayam
was
also
asking
that
question.
Yes,
these
tutorials
same
will
are
about
specific
failure,
scenarios
that
we
might
want
to
put
together
and
go
ahead
and
talk
about
how
people
can
simulate
them
and
how
people
can
mitigate
issues
there.
A
Basically,
information
about
all
that
you
need
to
know
about
handling
certain
specific
failures.
I
think
the
white
paper
did
have
a
section
for
that
which
we
sort
of
went
ahead
and
placed
summary
for
it's,
not
detailed.
We
wouldn't
go
ahead
and
elaborate
yet,
but
there
are
there.
There
was.
C
A
The
requirements,
one
of
our
goals
with
respect
to
the
white
paper,
even
before
the
charter
sort
of
came
about
to
identify
some
common
failures
that
people
are
facing
right,
it
could
be
different
types
of
errors
or
different
type
of
outages.
You
can
say
network
issues,
resource
exertions,
improper
application,
h,
a
incorrect
configurations,
things
like
that.
We
would
probably
go
ahead
and
list
these
scenarios,
as
I
think,
which
is
what
I
suppose
is
being
you
know,
talked
about
as
the
failure
scenarios.
B
A
These
specific
scenarios,
so
we
can
go
ahead
and
list
them
in
one
place
and
provide
some
detail
around
it
and
the
link
changing
said
make
it
available
as
part
of
a
web
page,
maybe
github
pages
or
something
and
give
a
single
point
of
resource.
Or
we
can.
A
That
people
can
direct
themselves
to
other
projects
if
necessary
in
way
of
examples.
The
idea
here
would
be
to
keep
it
more
at
a
scenario
level
and
what
people
can
do
generally
and
they
the
means
of
applying
that
test
or
medication
can
be
through
various
tools
of
their
choice
right.
That
would
be
the
idea.
A
True,
yes,
it
can
have
concepts
and
terminologies
and
general
problems
and
solutions,
humanities
issues
becoming
chaos.
Experiments
perfect,
I
think
that's
another
thought
we
probably
can
add
here,
I'm
doing
it
on
your
behalf,
so
please
feel
free
to
go
ahead
and
change
this
on.
Any
of
this
add
your
own
thoughts
as
well.
Just
noting
this
humanities
issues
turning
into
potential
experiments.
A
A
The
meeting
dock,
the
work
group
meeting
notes,
I
just
created
a
section
called
working
material
and
placed
something
called
as
a
glossary.
Here.
There
is
something
that
is
also
going
on
within
the
white
paper.
There
was
an
idea
to
create
a
glossary
as
part
of
our
white
people
goal.
I
think
we
can
keep
it
separate
from
the
white
paper.
It
could
be
a
general
entity
of
its
own
right.
That's
how
I
see
some
of
the
work
groups
and
tags
handling
it.
They
have
a
glossary
and
a
terminology.
A
A
A
From
one
of
the
mgs.
A
On
the
witness
project,
who
has
created
a
glossary
or
on
fierce
engineering
in
general,
so
we'd
like
to
put
that
up
here
as
part
of
the
work
group
as
an
artifact,
so
that
would
also
go
into
the
skit
repository
whatever
we
we
are
discussing
here
earlier
in
this
meeting
we
talked
about
the
repository,
so
we
will
have
a
section
dedicated
to
it.
So
that's
one
of
the
things
that
we
we
would
do
just
like
the
white
paper
in
charter.
We
have
another
doc
for
a
glossary
and
it
will
find
its
place.
A
It
can
it's
a
live
thing
and
keep
adding
there
as
more
terms
and
because
what
is
getting
popular,
I
just
wanted
to
bring
that
to
the
notice
of
the
team.
The
other.
A
C
A
Being
talked
about
in
the
charter
here,
we
can
do
so
with
the
help
of
a
sample
application.
It
makes
the
story
more
coherent
right.
You
have
a
because
many
organizations
and
teams
will
be
able
to
sort
of
identify
with
their
own
tooling
right,
like
a
common
microservices.
Application
can
be
used
to
create
all
these
scenarios,
common
microservices
applications
residing
on
kubernetes,
and
you
could
do
different
kind
of
faults
against
it.
The
application
themselves,
the
application
itself
comprised
of
different
kinds
of
microservices
right
so
sock
shop,
is
an
example,
maybe
hipster
shop.
A
There's
another
cnc
project
called
potato
head,
which
I'm
sure
you
might
have
all
heard
of
it's
being
maintained
by
folks
at
app
delivery.
It's
basically
a
microservices
application
that
comes
together
to
form
the
different
body.
Parts
of
a
simple
picture
here
called
crystal
potato
head,
and
there.
A
Effort
in
increasing
the
profile
and
complexity
of
this
app,
I
know
that
folks
here
are
working
on
adding
stateful
components
to
it
and
generally
making
it.
You
know
more
sophisticated
to
represent
a
real
world,
microservices
application.
So
when
we.
A
For
chaos
that
we
are
talking
about
right
and
we
might
do
well
to
do
it
against
a
common
application.
If
the
scenario
is
something
that
you
cannot
apply
on
a
regular
application
and
needs
a
dedicated
example,
have
example,
or
an
input
or
a
component
example
to
be
able
to
explain.
That's
perfectly
all
right,
but
I
think
for
most
scenarios
that
people
you
know
get
started
with
explaining
it
in
the
context
of
a
sample
micro
service
application,
would
make
it
easier
for
people
to
relate.
A
Please
feel
free
to
add
that
here
I
think
potato
head
being
curated
within
cncf
makes
it
a
more.
You
know,
sort
of
a
better
example.
It's
my
opinion,
so
we
might
have
to
see
how
to
build
in
the
security
story
for
it
and
how
to
build
this
stateful
chaos,
part
of
it
into
into
potato
head.
So
I
think,
by
the
time
we
get
there,
the
application
might
have
evolved,
the
project
might
have
evolved
or
we
could
deliver
other
examples.
So
please
feel
free
to
share
your
opinions
on
on
this
aspect.
A
There
is
something
on
chat,
so
let
me
see
that
yes,
yes,
I
think
we
were
getting
to
the
same
discussion,
potato
head
or
soft
shop
potato
head.
I
think
sock
shop
is
good,
only
flip
side
being
it's
not
been
maintained,
I
feel
for
a
long
time.
He
works
folks
have
left
it
there.
There
are
a
lot
of
individual
variants
inspired
by
some
shop
that
I
see
that
are
cropping
up.
Yeah
potato
head
is
something
that,
incidentally,
has
also
been
proposed
as
a
sandbox
project.
A
So
feel
free
to
place
your
thoughts
there
yeah
thanks
again,
so
that's
one
of
the
things
and
that's
all
I
had
as
agenda
items
to
discuss
for
today.
A
A
Work
group
names
people
are
coming
up
with.
We
went
ahead
with
the
plane,
chaos,
engineering
worker,
which
is
not
what
we
are
doing,
but
if
you
have
any
interesting
names
you
want
to
give
to
it,
then
you
can
suggest
and
on
a
github
repository
and
what
we're
going
to
do
with
the
older
repository
and
how
we
do
this,
leave
it
as
an
open
item
and
discuss
it
with
folks
on
the
eu
side
as
well.
A
I
want
to
really
take
ais
on
this
right
away
so
that
we
get
more
data
points
on
how
to
proceed
on
this.
We
will
always
record
this.
The
meeting
notes
so
yeah.
That's
another
item
I
feel
would
probably
go
on
to
the
next
group
sync
up
as
well.
We
went
through
the
goals
and
non-goals.
If
you
have
anything
that
you
would
like
to
add
here.
Please
do,
but
I
think
it's
quite
looks
really
great
and
good
summarization
of
what
we
would
like
to
do.
A
And
place
that
here,
probably
in
the
upcoming
week,
and
we
will
discuss
around
the
potato
head
further
as
a
as
a
good
application,
I
think,
as
we
go
into
the
group,
start
actively
documenting
scenarios
a
little
bit
better
idea
and
would
like
to
seek
more
opinions
on
this.
Similar
to
the
dots
I
mean
similar
to
the
repository,
I
think
that's
all
I
had
for
today's
call
kswa
groups,
I
think
sock
shop.
We
have
words
from
siam
ma.
A
Cool,
I
think
that's
all
I
had
for
this
call.
Is
there
anything
else
that
you
would
like
to
discuss
on
the
agenda?
I
will
transfer
this
I'll,
probably
create
some
more
coverage,
notes
on
what
we
discussed
share
it,
but
is
there
anything
else
you
would
like
to
bring
up
any
thoughts
either
on
the
you
know,
agenda
items
or
maybe
something
inside
of
the
work
group
or
maybe
on
the
white
paper.
A
A
All
right,
then,
thank
you
for
taking
the
time
and
attending
this
call,
I
think,
yeah
about
survey.
Yes,
there
is
a
survey
that
is
ongoing.
It
is
linked
inside
of
charter
working
group
charter
document.
I
think
we
got
around
36
responses.
We
had
31
when
we
met
last
time,
so
we
have
five
more
responses,
which
is
great.
We
are
making
some
progress
so
as
we
meet
often
as
we
as
we
sort
of
get
underway
with
the
working
group
agenda.
A
I
think
this
will
increase
more,
I'm
sure
this
is
being
advocated
by
different
teams.
I
think
siam.
A
You
might
also
be
interested
in
sort
of
putting
this
up
on
twitter
or
you
know
in
your
community,
so
people
go
ahead
and
add
more
responses
there.
I'm
sure
that
will
have
a
great
impact
too,
and
we
will
be
able
to
get
some
findings
from
here
and
make
observations
from
this
survey.
I
think
it's
going
in
the
right
direction.
B
I
just
want
a
timing
here.
I
think
last
time,
last
week
at
our
pre-kickoff
meetings,
someone
said
that
they
want
to
put
in
some
more
questions
regarding
security
chaos.
Is
there
any
update
on
that
or.
A
Yeah,
it's
a
good
one.
I
think
aradhana
had
some
interest
last
time.
She
went
and
added
some
goals
into
the
charter
and
then
also
took
the
subway
link,
but
I'm
not
sure
if
she's
obviously
she's
not
already
added
it.
So
we
could
do
a
follow-up
and
basically
check
if
she
would
like
to
add
those
solutions.
A
I
think
there
is
one
general
question
here
around
security:
what
is
the
obstacle
not
really
about
obstacle?
It's
more
about
yeah.
You
could,
you
could
still
say
what
is
an
obstacle
that
people
are
facing.
Is
it
security
concerns
or
what
kind
of
case
testing?
Are
you
doing?
What
kind
of
practitioners
do
you
have,
which
is
a
couple
of
questions
that
we
have
here?
A
More
would
be
good,
but
let's
see
if
another
institute
goes
ahead
and
adds
that,
I
think
is
the
new
respondents
can
go
ahead
and
add
their
security
things
there.
So
that's
a
good
one.
I
am
adding
that
as
an
item
here.
A
A
B
A
Different
kinds,
as
we
go
right
side,
maybe
for
chaos,
practitioners,
we
can
even
talk
about
what
kind
of
failure
they'll
be
is
most
gonna
be
interesting
survey,
so
yeah
we
can
keep
going
going
ahead
and
doing
more
surveys
as
we
go
and
as
the
agenda
works.
A
Cool,
I
think,
with
that
we
can
wrap
up
this
session
of
this
call
once
again.
Thank
you
so
much
everyone
for
our.
A
B
I
think
we
are
just
proposing
the
word
group
name.
We
can
ask
more
people
and
then
take
and
take
a
decision.
A
A
A
B
Okay,
yeah,
I'm
I'm
cool
with
chaos
working
group
by
the
way.