►
From YouTube: CNCF TOC Meeting 2022-04-05
Description
CNCF TOC Meeting 2022-04-05
A
A
B
A
A
C
B
B
B
Nevertheless,
what
it
is
about,
as
you
may
know,
there
are
some
small
minor
climate
changes
around
the
globe
heating
up
a
little
bit
here
and
there,
and
we
have
a
lot
of
little
pieces
which
basically
have
an
effect
on
this.
This
is
like
when
we
travel
with
airplanes
or
drive
too
much
cars,
but
also
the
it
industry
has
a
very
good
impact
on
it.
B
You
have
the
queen
software
foundation,
which
is
specifically
taking
a
look
about
how
to
maybe
optimize
software.
What
are
good
patterns
to
optimize
the
software
you
have
tons
of
other
sustainability
activities,
but
somehow
there's
always
missing
a
little
bit
this
gap
to
bring
it
really
actively
to
the
community
for
sure,
not
because
in
the
first
step,
when
you
start
a
open
source
project
or
you're
working
deep
in
the
open
source
project,
it's
maybe
the
last
thing
you
think
about
that.
B
B
It
should
build
a
bridge
from
all
these
different
teams,
which
are
out
there
and
communities
out
there
and
try
to
bring
their
best
practice
their
ideas
to
our
cloud
native
community
to
help
the
teams
to
shape
an
idea
about
it
to
help
to
identify
a
good
approach,
also
for
each
of
the
projects
to
find
their
own
way
to
optimize
either.
It's
a
software
or
how
they
are
deployed
and
also
in
the
overall
contribution
to
the
projects,
can
be
also
a
good
approach
to
to
support
here.
Now,
again,
let's
think
about
kubernetes.
B
You
have
every
night
every
day
running
hundreds
of
tests
continuously
and
if
you
can
optimize
hear
something,
this
will
also
have
a
positive
impact
and
also
what
you
also
not
should
forget
is
for
sure
also
the
end
user
community
right.
We
have
a
good
approach
or
we
can't
have
a
good
chance
over
the
community
to
also
reach
out
to
the
end
users
and
some
of
our
end.
B
Users
already
got,
for
example,
also
targets
to
reduce
their
emissions,
so
it
goes
hand
in
hand,
and
I
think
all
those
changes
need
some
way,
a
place
where
we
can
bring
it
together,
where
we
can
bundle
it
and
because
also,
I
said
the
whole.
How
to
say
community
is
a
sustainable
community,
is
in
a
constant
move
in
a
constant
research
and
a
constant
change
of
minds
and
making
up
things,
and
this
is
where
the
tech
would
come
in.
B
Try
to
bundle
all
of
these
incomes
sort
a
little
bit
out
what
is
relevant
for
us
in
the
first
move.
What
is
maybe
relevant
in
the
second
move
and
shape
out
of
it
potential
actions
which
we
then
can
give
into
all
of
our
open
source
projects
and
set
up?
Maybe
a
kind
of
I
do
not
want
to
call
it
maybe
standard,
but
a
set
of
good
practices
which
can
be
adopted
also
from
other
projects
out
there
from
end
users,
for
example,
and
so
on
and
so
forth.
C
Thanks
max,
so
this
is
a
really
good.
You
know
effort
that
you
know
we
should
be
definitely
thinking
about
for
sure.
So
one
when
I
saw
this
one
I
was
look.
I
went
looking
for
like
what
has
anybody
else
done
before,
for
example,
right
in
the
space
like
the
one
thing
that
came
to
mind
quickly
was
like,
as
people
started,
measuring
how
much
how
much
energy
energy
electricity
is
used
in
creating
and
maintaining
the
blockchains,
for
example
right.
C
B
Well,
I
mean
we're
talking
always
about
cloud
data
and
somehow
directly
stuck
with
our
head
and
the
clouds,
but
the
reality
is
that
most
of
the
workload
is
still
running
on
premise
right
and
to
measure
on-premise.
The
emissions
electricity
consumption,
for
example,
is
actually
quite
simple
thing,
because
if
you
build
a
data
center,
you
should
have
redundant
energy
supply
and
you
have
energy
contracts
parallel
supply,
so
to
bring
here
and
some
measurements
could
be
an
easy
point
of
view.
B
Another
very
active
community
which
measures
actually
the
resource
consumptions
overall,
would
be
the
finnops
community
right,
however-
and
I
mean
finnops
or
the
optimization
for
costs-
and
therefore
also
the
optimization
of
resource
consumption
is
very
close
together,
but
it
has
two
totally
different.
It
comes
from
two
totally
different
areas
right,
however,
we
can
utilize,
also
a
lot
of
approaches
and
swords
and
models
behind
the
finnops
and
easily
spoken
just
to
replace
the
coins.
B
The
dollar
coins
with
metric
tons
of
co2,
for
example,
right
and
you
see
also
this
move
in
the
major
club
providers
like
aws
and
google
cloud,
currently
publishing
and
open
up
the
apis
for
gathering
all
this
emission
data
out
of
your
workload.
Azure
has
it
since
years
as
a
kind
of
bi
dashboard
available
right.
B
So
there
is
already
a
good
foundation
also
towards
this
direction,
where
we
can
start
working
with.
There
are
also
some
great
open
source
tools
on
the
market
which
have
done
already
all
this
ground
and
foundation,
research
which
can
be
utilized,
so
the
foundation
is
all
given,
but
is
that
there's
a
lot
of
activities
going
around,
and
this
is
what
we
can
bring
very
well
together.
D
C
Yeah
so
again
the
question
is
like
for
us:
what
does
it
mean
does
is?
Is
it
a
tag
or
is
it
a
working
group
and
is
it
going
to
own
like
or
control
or
you
know,
cover
certain
specific
projects,
and
what
would
they
be
because
you
know
for
us
tag,
has
a
specific
connotation
here
right
as
an
organization,
organizing
principle.
B
Well,
I
believe
from
the
perspective
of
like.
Is
it
an
attack
or
is
it
a
working
group?
I
think
a
working
group
always
has
a
very
specific
target,
something
which
is
discussing
about
goals.
Smart,
you
can
measure
it.
You
can
can
see
it.
You
can
touch
it.
I
think,
with
attack.
This
is
more
like
a
strategic,
long-term
thing
which
needs
to
get
on
its
way,
which
can
change
its
shape.
Maybe
we
understand
on
on
half
the
way.
Okay,
all
the
things
we
have
thought
about
is
not
the
thing.
B
Maybe
it's
a
totally
different,
different
direction,
which
we
need
to
change,
and
also
here
I
said
from
also
from
the
explanation
I
give.
I
think
we
have
already
a
good
amount
of
different
work
groups
which
we
can
think
about
under
it,
like
also
like
richie
says,
like
okay,
we
have
a
big
cicd
part
in
it
and
just
to
optimize
this
whole
cicd
and
define
maybe
a
new
standard
or
a
new
best
practice
how
to
optimize
ci
cds.
B
F
What
are
you
thinking
about
from
you've
already
identified
a
few
potential
working
groups
if
this
were
to
become
a
tag?
How
are
you
planning
on
scoping
that
and
I've
read
through
the
proposal
and
it's
fairly
comprehensive,
but
I'm
want
to
ensure,
like
the
tags,
that
we
have
have
charters
and
that's
kind
of
the
guiding
principles
around
them,
and
I'm
curious
where
you
see
this
fitting
in
as
well
as
what
those
capabilities
are.
B
Yeah
yeah,
you
also
highlighted
a
couple
of
very
interesting
parts
in
it,
so
I
think
one
of
the
the
first
major
step
is
really
to
shape
a
relevant
group
of
people
around
us.
I
got
a
lot
of
positive
feedbacks
for
by
email.
Also
on
the
proposal
I've
sent
around
of
at
least
a
handful
of
people
says
like
hey.
This
is
exactly
what
we
are
looking
for,
or
we
are
working
on
this
already
in
this
direction.
B
B
We
have
our
surveys
by
cncf
yearly
going
out.
Why
not
extend
it
by
two
three
four
questions
and
giving
a
first
good
touch
in
this
direction,
because
the
data
in
this
direction
of
environmental
sustainability
is
very
poor,
on
the
one
hand,
side
and
it's
very
complex
together,
so
this
could
be
also
very
good
kickstart
into
this
direction
and
define
and
make
it
transparent.
What
is
actually
going
on
that
there's
a
lot
of
companies
moving
into
this
direction
and
having
thoughts
around
it
but
maybe
getting
lost
in
it.
B
G
Yeah
I
mean,
I
think,
that
working
out
what
is
going
to
be
what
it's
going
to
deliver
is
really
important.
I
think
that
we
we've
got
this
idea.
That
cncf
is
a
project
focused
foundation,
but
we
actually
do
a
lot
of
non-project
work
and
I
think
you
know
tag
security
is
a
good
example
of
it
does
a
lot
of
work.
G
I
think
that
I
think
a
lot
of
people
are
very
unsure
what
to
do
and
it
kind
of
it
in
that
way.
It's
a
little
bit
like
the
security
space
where
people
know
there's
problems,
but
they
don't
know
how
to
solve
them
and
they
don't
know
how
other
people
are
solving
them
and
they
don't
have
a
place
to
go
and
communicate
these
difficulties,
and
so
that
sounds.
That
sounds
really
helpful.
I
think,
from
my
point
of
view,.
C
H
Want
to
summarize
something
oh
yeah,
so
just
from
my
thoughts
in
in
chat
was
from
the
outputs
of
this.
It
looks
more
like
white
papers
and
best
practices
which
has
historically
aligned
more
with
working
groups,
and
there
there
are
working
groups
out
there
that
have
spawned
projects
that
then
enter
sandbox.
H
I
Yeah,
I
think
it's
pretty
much
in
line
with
what
emily
said.
I
always
think
it's
an
important
and
valuable
initiative,
something
that's
very
new
to
a
lot
of
what
this
I
think,
that's
why
scoping
and
initial
deliverables
will
be
crucially
important
because,
like
really
a
wide
field
and
giving
people
something
that
is
easily
usable
and
appliable,
but
then
early
on
will
be
crucial
there.
So
it's
more
as
about
scoping
and
being
like
very
specific
about
deliverables
early
on.
C
Yeah
we
and
the
point
emily
is
making
also
is
like
we
can
start
as
a
working
group
and
then
we
can
move
it
into
tag
if
it
like
outlives
some
stuff
or
it
adopts
some
projects
under
its
wings.
So
to
say
so,
I
yeah,
but
you
know,
definitely
love
the
idea
and
we
should
do
something
and
we
should
do
something
quick,
because
you
know
as
a
as
a
humanity.
We
are
running
out
of
time
at
this
point
right,
so
any
other
last
ricardo
did
you
want
to
say
something.
J
Yeah,
I
think,
having
a
working
group
sounds
like
a
good
idea.
It's
just
having
on
some
sort
of
deliverable,
maybe
creating
a
landscape
around
sustainability,
around
projects
and
things
that
are
related
to
the
other
tags.
I
do
think
it's
kind
of
like
the
scope
is
really
wide.
There's
some
so
many
things
around
sustainability
and
maybe
having
some
sort
of
deliverable
will
help
us
will
help
the
the
community
understand
more
the
scope,
right
and
kind
of
like
narrate,
narrow
it
down
to
do
something.
C
J
E
Yeah
per
discussion
in
the
mailing
list,
I,
as
co-chair
of
of
contributing
strategy.
I
don't
think
this
is
really
appropriate
for
contributing
strategy,
because
it's
not
really
about
the
people,
specifically,
it's
more
honestly
about
the
code
and
what
it's
doing,
and
so
it
doesn't
doesn't
seem
appropriate
to
put
it
under
us.
C
F
Yep,
I
think
it
needs
to
get
back
to
the
mailing
list.
I
think
a
rename
is
going
to
be
important
so
that
we
don't
have
any
collisions
with
other
technical
terms.
I
suggested
conservation
working
group
for
the
time
being.
I
think
this
might
be
beneficial
for
potentially
runtime
or
one
of
the
other
more
operational
tags.
C
I
I
Otherwise,
no
projects
are
in
review,
but
what
we
still
see
very
positively
that
also
sandbox
projects,
also
don't
have
like
forced
to
reach
out
to
it
to
the
tags,
are
still
actively
reaching
out
to
present
to
the
tag
and
thank
members
which
I
think
is
very
good
update
on
the
cooperative
delivery
working
group
there
beyond
our
regular
work,
we
started
to
look
into
a
most
likely
skill
to
be
a
white
paper
on
multi-tenant
app
delivery.
So
this
came
up
in
a
lot
of
conversations
we
had.
I
I
But
for
the
topic
we
saw
one
more
coming
up
here
and
the
goal
with
you
to
draft
the
storage,
a
white
paper,
most
like
the
recommendation
or
just
listing
the
options
that
are
available
there.
They
give
actually
will
turn
out.
These
are
the
options
that
you
have
to
solve
certain
problems
or
then
okay.
This
is
a
good
practice
to
solve
it
or
like.
This
is
the
way
you
should
be
doing
it.
I
The
last
one
I
pretty
much
took
over
from
the
last
one,
so
the
blog
post
is
still
in
the
working
and
we
need
to
see
how
we
can
get
it
posted.
What
app
delivery
is
actually
doing,
because
that
was
the
feedback
we
already
got
from
that
from
the
last
cubecon.
It's
like.
Oh,
you
really
exist.
Yes,
we
do
and
there's
actually
material
out
there,
then
sometimes
people,
but
we
also
see
people
are
starting
to
reference
material,
especially
like
the
operator
white
paper
and
so
forth,
yeah
delivery.
I
We
wanted
to
do
it
an
app
deliberately
at
cubecon
in
valencia
we
started
rather
late
and
probably
were
a
bit
too
optimistic
to
get
to
standing
time.
Nevertheless,
we're
now
heading
for
doing
it
for
detroit
for
north
america
and
yeah,
I
just
updated
the
slide
briefly
before.
There's
one
item
missing
for
some
very
strange
reasons:
how
the
internet
and
most
likely
outlook
works.
None
of
us
got
the
update
on
submitting
our
session
for
the
maintainers
track.
I
C
So
thanks
a
lot.
The
first
one
is
captain.
Sorry,
you
know
we
kind
of
like
dropped
the
ball
as
a
toc
and
we
need
to
get
it
back
on
track
for
sure.
So,
let's
see
what
we
can
do
here,
we
already
have
one
other
toc
member
harry
picking
up
some
of
the
work,
so
hopefully
it'll
be
better
this
time,
so
the
other
one
I
had
the
input
was
the
multi-tenant.
I
The
working
group
is
on
cooperative
delivery
as
a
whole,
which,
like
covers
infrastructure
and
collaboration
and
constantly
shipping
it.
But
one
of
the
big
topics
that
obviously
came
up
is
shipping,
multi-tenant
applications
or
style
applications
that
the
team
is
looking
into
collecting
best
practices
and
so
forth.
Yeah
yeah.
C
At
this
point,
I
think
they
are
working
on
like
how
to
make
kubernetes
multi-tenancy
rather
than
the
apps.
So,
but
maybe
you
know
just
getting
I
mean
starting
to
talk
to
them
might
be
helpful
in
some
shape
or
form,
because
there
might
be
other
people
interested
in
the
app
delivery
side
of
things
there.
I
C
E
E
The
we've
up?
I
had
approved
and
merged
a
readme
template
so
getting
much
closer
to
sort
of
having
a
complete
set
of
templates
for
project
paperwork.
Documentation
full
documentation
for
those
templates
is
trailing
that
a
bit
but
we're
working
on
it.
The
we're
waiting
for
our
toc,
our
new
toc
liaisons.
E
E
The
and
you'll
probably
see
that
next
month,
the
as
well
as
look
for
student
announcements
about
the
next
couple
of
maintainer
circle
items
the
with
a
professional
coach
that
we're
going
to
set
up
for
again
for
the
maintainers
and
please
let
maintainers
that
you
work
with
on
projects,
know
about
it.
When
you
see
that,
because
to
help
maintainers,
I
know
I
promised
that
we
were
going
to
have
a
proposal
by
this
meeting
for
a
mentorship
working
group
under
tag
cs.
E
So
that's
a
little
bit
delayed
and
we
met
with
a
bunch
of
folks
at
the
march
10th
tag
meeting
who
are
working
on
a
proposal
for
a
diversity
and
inclusiveness
working
group
that
will
be
under
tag
cs
for
efforts
in
that
direction.
So
look
for
that
on
the
toc
mailing
list
pretty
soon
and
as
always,
a
reminder
when
you're
doing
due
diligence
or
providing
feedback
or
sponsorship
to
projects.
And
you
see
that
they
need
help
in
specific
areas,
please
feel
free
to
refer
them
to
us.
E
E
C
K
K
Adopted
sandbox
level
project
from
tag
network,
there
have
been
activity
from
the
maintainers
of
iraqi
mesh
and
database
mesh
in
terms
of
their
consideration
toward
proposing
for
sandbox.
I
think
a
rocky
mesh
did
they
just
haven't
presented
in
the
tag.
Just
yet
that's
not
a
requirement
but
but
they
had
asked
to,
and
so
just
a
random
just
a
question
for
me:
do
you
all
recall
if
that
if
a
rocky
mesh
has
been
reviewed
yet
or
if
it?
K
If
it's
proposed
okay,
they
might
have
just
written
up
the
proposal
but
not
actually
submitted
okay
and
so
very
good.
So
that's
a
large
or
that's
a
kind
of
the
focus
of
tag
network,
I'll
mention
I'll
kind
of
go
and
reverse
order
and
draw
your
eyes
to
the
upper
right
hand.
Corner
there's
different.
You
know,
google
summer
of
code
is
coming
up,
there's
a
list
of
a
number
of
projects
that
are
participating,
those
from
tag
network
there.
K
K
Looking
toward
kubecon
and
service
mesh
con,
there's
two
activities
coming
out
of
service
mesh
working
group
that
well,
I
guess
I'll
say,
should
finally
be
published.
There's
there
are
contributors
working
on
an
early
version
of
of
a
performance
dashboard
that
looks
at
some
different
test
scenarios.
Different
performance
test
results,
we've
kind
of
talked
about
this.
A
lot
on
this
on
these
calls.
K
The
tests
are
now
being
run
inside
of
the
cncf
labs.
There's
automation
that's
been
completed.
Since
last
we
gave
an
update
that
runs
those
tests,
there's
a
solicitation
for
anyone
interested
in
a
review
of
the
different
test
scenarios
or
suggestions
to
change
those
or
opinions
and
ardent
opinions
are
most
welcome.
C
K
It
is
super
surprising
to
me
just
the
level
of
interest
that
folks
have
in
service
mesh
performance,
as
as
I
tend
to
think
that
mathematical
numbers
are
somewhat
boring,
but
I
don't,
but
everyone
else
doesn't
and
so
the
open
the
project
office
hours
for
service
mesh
performance
are
like
much
to
my
surprise
and
very
well
attended
the
service
mesh
con
itself,
I'm
not
on
the
program
committee,
but
there's
a
lot
of
there's.
There's
there's
a
lot
of
submissions.
There's
a
lot
of
there's
been
a
something
of
a
question
about
equal
representation.
L
One
of
you,
hello,
hi,
so
I'll
just
give
a
quick
update
here
of
some
current
activities
and
what
we've
had
going
on
last
month.
At
our
last
meeting,
we
had
the
hubble
project.
Come
the
psyllium
psyllium
hubble
project
come
and
give
an
overview
to
the
tag
just
about
what
it
is,
what
the
scope
of
it
is,
etc.
L
So
he's
going
to
give
an
overview
of
the
project
and
we're
going
to
talk
about
sort
of
some
of
the
observability
aspects
of
it
and
how
it
can
contribute
to
the
canon.
There's
a
spelling
mistake
there.
I'm
sorry
hammock,
henrik,
is
going
to
give
a
short
update
too
we've
not
he's
now
launched
and
and
published
the
first
of
this
sort
of
short
format.
What's
going
on
in
open
source,
I
think
it's
gonna
be
bi-weekly
initially,
but
it
might
move
to
weekly.
L
So
we're
gonna
talk
about
that.
We'll
have
an
update
on
a
working
group
that
we
launched
just
about
a
month
ago.
We've
been
talking
about
it
for
a
few
months
called
observe,
dash
k8s
for
those
that
aren't
familiar
where
we
took
a
page
from
tag
app
deploys
playbook
with
the
get
ops
working
group
which
subsequently
launched
open,
get
ops.
Here
we
want
to
do
something
similar.
L
We
formed
a
working
group
to
launch
something
that
has
its
own
life
beyond
the
working
group
called
observe
k-8s,
and
the
basic
idea
is
to
be
alertive
alliterative.
Well,
it's
in
the
slide,
but
it's
a
it's
a
collection
of
case
studies
that
are
cloneable
on
how
to
use
observability,
tooling,
that's
within
the
cncf
umbrella,
combined
with
representative
workloads.
L
We
have
I've,
been
doing
some
some
socialization
of
the
idea
and
reaching
out
to
various
actors
in
the
in
the
community
and
we're
approaching
critical
mass
here
where
we
have
a
number
of
people
that
want
to
contribute
both
good
working
examples
of
microservices
and
other
cloud
native
deployments,
combined
with
ways
to
observe
them
and
there's
there's
different
ways
to
observe
different
workloads
for
the
same
workloads,
and
this
is
meant
to
be
a
starting
point.
That's
accessible!
That's
community,
driven
that
people
can
use
to
get
started
or
to
learn.
L
L
L
That
book
just
came
out,
and
basically
it
covers
a
technique
that
we
used
to
use
almost
20
years
ago
with
windows
ce
where,
unlike
a
regular
sampling
profile,
which
goes
tick,
tick,
tick,
tick,
tick,
you
know
and
records
where
you
were
on
every
thread,
context
switch
or
when
a
thread
wakes
up
it.
It
knows
why
it
woke
up
the
scheduler
knows
why
I
wake
up,
why
it
woke
up
and
so
that
data
set
is
captured.
L
So
you
end
up
with
a
profile
that
shows
the
relationships
between
when
threads
woke
up
and
what
they
were
waiting
on,
and
why
did
they
wake
up?
So
this
provides
a
more
nuanced
view
of
the
interactions
of
systems
and,
as
you
know,
increasingly
we
see
cloud-native
systems
expanding
to
mobile
devices,
edge
networks
or
edge.
You
know
edge
scenarios
with
heterogeneous
networking,
the
rise
of
all
sorts
of
different
hardware,
combined
with
real
movements
on
the
storage
space
as
well.
You
know,
in
many
cases,
storage
is
no
longer
the
bottleneck.
L
It
once
was
so
many
systems
that
were
built,
atop
storage,
with
the
assumption
that
storage
is
slow,
such
as
lsm
trees
that
are
used
to
implement
key
value
stores.
You
know
all
of
these
are
being
turned
upside
down,
so
there's
a
real
need
to
understand
in
more
than
just
simple
terms
how
these
systems
are
behaving,
how
we
can
measure
them
and
how
they're
misbehaving
so
we'll
have
more
on
this
in
incoming
meetings.
I
think
I
hope
I
reached
out
to
dr
seitz
and
we
have
started
a
dialogue
there.
L
I
wanted
to
highlight
something
that
doesn't
fit
neatly
in
all
the
categories
necessarily,
but
some
time
ago
you
know
when
we
launched
the
tag
and
started
making
our
initial
definitions
of
work.
You
know
we
wanted
to
do
something
very
simple.
You
know
make
it
make
a
big
list
of
vendors
and
then
projects
and
who
contributes
to
them,
and
this
this
was
last
summer
and
last
fall
in
the
tlc
meeting
in
one
of
the
tlc
meetings
in
the
talent
of
september.
L
But
basically
there
was
some
ambiguity
about
you
know:
what's
a
project,
what's
a
vendor,
what
kind
of
sectors
and
domains
are
they
in
and
there
was
we
had
identified
a
need
to
have
a
more
nuanced
data
model
and
a
more
nuanced
way
to
look
at
the
landscape,
so
this
kind
of
motivated
us
to
reach
out
as
a
tag
and
say
well,
who
else
is
working
in
the
space
and
the
next
and
last
slide?
Please?
L
L
Well,
well,
the
actual,
the
actual
deck
that
folks
have
a
link
to
has
that
last
slide,
but
the
long
and
short
of
it
is
we
I
reached
out
to
them
and
they
were
kind
of
doing
the
same
thing,
but
for
other,
but
starting
in
a
different
area
than
observability,
and
so
we
are,
we've
been
prototyping
a
way
to
do
this.
That
uses
a
graph
data
model
so
we're
using
neo4j.
We
have
some
early
prototypes.
It's
at
cncf,
slash,
landscape,
dashcraft,
it's
not
yet
public.
L
So
you
have
to
be
a
cncf
member.
You
know
it's
it's
very
very
early
days.
I
just
wanted
to
give
people
a
quick
look
at
it,
but
it
built
a
graph
data
model
instead
of
a
big
rectangular
relational
model.
You
know
so
so,
if
you
want
to
answer
questions
that
you
don't
necessarily
know
yet,
graphs
are
are
quite
well
suited
to
this.
L
So
we
hope
to
provide
a
data
model
that
can
be
used
to
answer
questions
such
as
you
know
for
a
given
project
who
contributes
to
it
and
what
else
do
they
contribute
to
or
for
all
of
the
sandbox
projects?
You
know
for
all
of
the
people
contributing
to
all
of
those
projects
who
employs
them
and
who
funds
those
companies
and
what
else
do
they
fund
right?
L
So
so
these
kinds
of
questions
that
are
very
similar
to
what
we
see
in
chinops
or
ad
tech
and
for
the
last
10
or
15
years
in
various
domains
such
as
biology
and
chemistry
and
whatnot.
You
know
many
of
these
algorithms
and
such
and
the
actual
slides
that
I
tasted
a
little
too
soon
before
this
meeting
provide
some
links
to
to
to
what
we're
up
to
you
know.
L
Those
techniques
can
be
applied
to
the
landscape,
to
help
us
assess
things
and
some
of
the
technology
choices
that
we're
making
should
yield
a
nice
rich,
strict
client
that
can
work
on
windows,
mac.
Linux
as
well
as
ios
and
android,
and
then
using
web
assembly,
we
will
have
a
web
version
of
this
too.
So
so
this
is
sort
of
a
again
a
graph
based
data
model
on
the
existing
landscape
data
sounds.
C
L
Thank
you
yeah
and
that's
a
reasonable
segue
as
well.
Just
to
you
know
not
having
the
slides.
One
of
the
talks
I
saw
at
coupon
last
last
fall
was
by
don
foster
and
it
was
on
just
that
how
to
assess
the
health
of
projects.
You
know,
I
think
it
was
something
like
beyond
github
stars
and
pull
requests.
You
know
the
reason
that
we
want
to
use
a
graph
that
I
think
a
graph.
C
J
Yeah
attack
runtime,
just
a
few
updates,
keep
it
short
on
containers
and
runtimes.
We
had
a
presentation
on
inclinary
containers.
That's
a
different!
Take
on
confidential
computing
from
the
intel
folks,
the
dsx
team,
we're
going
to
have
a
presentation
from
this
project
called
wasme,
which
is
an
interpreter
and
in
terms
of
workloads.
J
Our
next
meeting
will
have
a
presentation
from
open
cruise.
This
is
a
project
that
allows
you
to
orchestrate
workloads
and
deliver
applications,
so
it
does
have
some
overlap
with
tag
app
delivery,
so
they'll
reach
out
to
tag
app
deliveries
too,
if
they
haven't
already
on
k
native.
That's
in
that
was
an
incubation.
That's
already
been
approved.
J
Inconvert
is
out
for
voting.
So
if
you
haven't
voted
yet,
please
go
ahead
and
vote
and
in
terms
of
tag
runtime
activities,
our
bsi
working
group
is
still
in
progress
in
the
github
issue
will
have
an
in-person
tag
runtime
session
at
kubecon,
so
we're
excited
about
that
in
for
kubecon,
north
america,
we're
looking
at
having
a
co-located
event,
possibly
on
on
mlaps
or
ai,
and
and
we
do
have
more
interest
from
more
community
members
to
become
tech
leads.
J
M
N
So
really
one
of
the
things
that
I
hope
to
help
to
instigate,
but
also
expand
within
the
security
tag,
is
helping
to
sort
of
intertwine.
The
the
uk
government
approaches
with
some
of
the
us
ordinances
to
help
bring
a
lot
of
the
very
excited
and
enthusiastic
uk
security,
open
source
security
community
with
me
into
this
effort,
and
also
to
bring
some
of
that
defensive
security
mindset,
along
with
the
excellent
work
that
already
exists
with
the
threat
models
around
a
lot
of
the
existing
audits
and
pieces
of
work.
A
N
M
M
M
Another
thing
that's
happening
is
we've
been
discussing
container
breakouts
that
have
been
a
lot
of
them
recently,
which
are
not
only
tied
to
kernel
and,
and
you
know,
just
operating
system
bugs,
but
in
container
runtimes
as
well.
So
the
discussion
there
was
around
the
micropaper
for
that,
but
instead
we
are
going
to
try
a
new
format
to
kind
of
help
maintain
contributor
attention
to
instead
have
a
blog
post
series.
M
M
O
O
So
this
one
we
had
a
meeting
in
our
tech
storage
to
discuss
about
this
project.
Iron
was
also
there.
So
there
are
a
few
issues
I
want
to
bring
up
here.
So
opps
has
a
storage
engine
named
maya
store,
so
this
one
previously
had
read
some
concerns
regarding
trademark,
because
maya
is
also
part
of
the
name
of
the
company,
my
data
at
that
time.
But
since
then
my
data
was
acquired
by
datacore
and
datacore
dropped
the
maya
branding
and
they
are
happy
to
donate
the
maya
branding
to
cncf.
O
So
the
team
open
ebs
team
is
going
to
open
a
service
desk
ticket
for
cncf
to
adopt
my
branding.
So
that's
in
progress
and
the
second
one
is
regarding
the
zfs
code
that
was
previously
used
in
c-store,
which
is
a
open
ebs,
github
repo,
but
that
one
was
also,
I
think,
it's
resolved,
because
the
code
was
was
removed
from
obs
github
repo.