►
From YouTube: CNCF Serverless Working Group Meeting 10.5.17
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! 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.
A
A
A
A
A
A
A
All
right,
it
is
for
past
the
hour.
When
are
we
going
to
get
started?
Let's
go
me
Jenna
today,
not
a
whole
lot
of
big
things
to
talk
about
I
just
wanted
to
highlight
some
of
the
changes
that
we
recently
made
to
the
dock.
Just
so
people
aware
of
them.
First
off
is
the
changes
to
the
what
is
service
section.
We
decided
to
go
ahead
and
accept
Sarah's
edits,
and
your
on
suggestions
add
the
word
usually
when
it
came
to
the
cost
perspective
things.
A
A
We
also,
as
we
talked
about
in
the
last
call
moved
I,
think
it
was
a
Appendix
A
which
listed
out
all
the
areas,
projects,
open-source
projects
and
possible
services
that
are
out
there
a
spreadsheet
and
so
here's
the
spreadsheet
at
Stuckey.
That
should
be
able
to
see
that
and
added
a
link
to
it
from
the
documents.
A
In
the
conclusion
section
men's
making
mentioned
the
fact
that
we're
expecting
this
thing
to
be
a
living
breathing
document
and
something
that
people
can
add
to
over
time
as
things
change,
but
that
way
we
don't
worry
about
updating
the
document.
Did
the
white
paper
itself
as
things
change,
we
can
just
up
this
depth,
update
the
spreadsheet
okay,
any
questions
on
those
two
things.
So
far,
all
right
Kathy
had
some
edits
to
the
conclusion
section
talking
about
portable
work,
clothes
I
accepted
that
and
it
was
merged
into
the
other
section.
A
I
talked
about
looking
at
some
portability
or
harmonization,
around
definition
of
functions
and
and
now
obviously
work
function.
Workflows
are
now
mixing
there,
because
they're
tightly
related
seemed
like
it
made
sense
to
put
their
little
spots
or
put
both
those
things
in
one
spot.
The
one
question
I
personally
had
as
I
was
reviewing.
The
document
was
in
Sarah's
edits.
She
started
talking
about
how
a
surrealist
computing
platform
may
provide
one
or
both
of
two
different
things.
Let
me
show
you
this
section
in
particular
I'm
concerned
about.
A
Okay
right
here,
the
service
platform
may
provide
one
or
both
of
the
following
functions
as
a
service,
obviously,
and
then
back
in
as
a
service.
Now,
what
jumped
outta
me
is
that
the
way
it's
worded
implies
that
a
surrealist
computing
platform
could
be
just
a
set
of
back-end
as
a
services
back
in
services.
Every
area
wants
a
head.
Basically,
it
doesn't
have
to
provide
function
to
the
service.
Is
that
consistent
with
everybody
else's
point
of
view,
because
in
my
mind,
I
always
thought
service
implied
hosting
things
for
end-users,
not
just?
A
B
I
know
this
was
one
of
the
earlier
definitions
right.
So
there
was
the
idea
of
the
compute
the
functions
as
a
service
platform
and
then
creating
like,
for
example,
a
single
page
app
that
had
no
no
server
logic
on
it,
except
it
called
out
things
like
auth,
I,
zero
and
and
backing
data
stores
and
stuff
like
that.
So.
B
A
B
A
A
All
right,
you
guys,
are
awfully
quiet
today,
I'm
not
sure
what
to
make
it
bet
is
Chris
on
the
call
Chris
Hanna
Chuck,
no
okay,
I
was
gonna
get
with
him
later.
The
reason
I
wanted
to
talk
to
him
is
I,
wasn't
sure
if
we
should
keep
things
like
that
spreadsheet,
that
we
just
created
in
a
single
person's
Google
account
or
whether
the
CNC
F
has
Google
account
that
maybe
we
should
host
these
things
under
that
way.
A
D
I
am,
and
it's
fine,
if
you
just
want
to
transfer
it
to
me
and
Chris,
but
the
way
Google
Docs
doesn't
officially
let
organization
own
em,
and
so
it's
we're
sort
of
happy
to
to
be
the
official
owners
of
it
and
then
can
give
you
write
permission
on
it.
I
was
just
gonna
mention
earlier
I'm,
not
sure
if
folks
have
seen
it,
but
the
software
conformance
working
group
has
been
keeping
this
spreadsheet
of
all
node
kubernetes
offerings
and
it
actually
gives
of
Jack's
originally
created
it,
and
it's
it's
kind
of
insane
now.
D
D
E
A
Ever
that's
gonna,
be
the
next
topic
on
the
agenda
was
I
know
at
one
point
we
talked
about
moving
the
white
paper
itself
into
github
as
individual
markdown
documents,
so
people
could
issue
PRS
against
it.
What
wasn't
clear
to
me
was
really
want
to
do
the
spreadsheet
over
there
as
well,
because
my
experience,
markdown
tables,
aren't
really
the
most
user-friendly,
but
I
want
to
get
some
opinions
on
that.
One
I.
B
Think
it
should
be
consistent
with
what
the
storage
working
group
is
doing,
which
is
the
spreadsheet
in
Google,
Docs
and
I.
Think
that
there's
there's
definitely
a
richer
way
to
to
include
info
than
C
and
then
then
doing
markdown.
But
a
compromise
might
be,
as
you
associate,
you
know,
possible
changes
to
the
spreadsheet
with
the
github
repo
that
you
log
your
shoes
against.
A
D
Would
be
with
the
TOC
print
like
we
did
with
the
TOC
principles
at
the
quote.
Official
version
of
it
would
be
in
markdown,
but
I.
There's
just
I
have
a
an
editor
that
I'd
like
to
have
one
more
kind
of
detailed
round
of
edits
on
it
and
I
do
want
to
be
clear
that
just
because
I'm
gonna
be
paying
this
person
doesn't
mean
you
need
to
to
adopt
their
edits,
that
every
edit
they
make
is
a
suggestion.
D
But
if
you
guys
would
would
be
comfortable
giving
it
another
week
or
two
to
take
in
these
edits
and
then
hopefully
we
could
say:
okay,
I,
don't
know
if
you
want
to
call
it
one
that
oh
or
something,
because
it's
certainly
not
for
everything,
but
then
I'd
love
to
convert
it
to
to
markdown
and
have
it
be.
You
know
officially
published
okay.
A
Okay,
so
that's
the
separate
the
discussion
later
in
the
agenda.
How'd,
you
talk
about.
Actually
the
very
next
item.
I
said:
look,
let's
go
through
a
review
process.
I
was
just
talking
longer-term
once
we
think
we're
done
with
this
thing.
Do
we
want
to
keep
it
as
a
Google
Doc
or
shifted
over
to
markdown?
Just
the
white
paper
itself,
not
the
spreadsheet,
so
Dan,
your
preference
is
marked
down.
Anybody
else.
Have
that
preference.
A
B
Think
that
makes
sense,
but
in
terms
of
readability
it's
a
longer
document
than
I
guess
the
Tio's
any
the
TOC
document
deserve.
Is
there
a
way
to
make
it
readable
like
generate
github
pages
from
it
or
put
it
in
C
and
C
F
dot,
IO
or
so
even
if
the
the
source
is
his
markdown
is
in
github?
Is
there
another
place
there?
You
know
people
would
read
it
and
find
it.
A
So
I
was
kind
of
assuming
that
as
we
uploaded
it,
we
would
not
have
thought
it
as
as
one
gigantic
markdown
we'd
have
individual
markdowns
per
section
so
that,
for
example,
the
TOC
and
introduct
an
abstract
would
be
one
section.
So
you
should
be
able
to
traverse
from
page
to
page
and
not
be
swamped
with
a
34
page
single
markdown
document.
Would
that
help
it
all
there
yeah.
D
To
format
it
nicely,
so
it
doesn't
have
to
be
just
this
incredibly
plain
thing,
but
my
other
comment
to
you
is
even
if
it
officially
lives
on
on
github
CDF
is
going
to
be
actively
promoting
the
document,
so
both
link
linking
it
from
our
main
page
doing
press
announcement,
probably
press
release,
rounded
featuring
it
on
the
blog,
etc.
So
I
don't
think
we're
just
going
to
sort
of
drop
it
and
say:
oh
now,
it's
public
and
it's
done
I
mean
I.
Think
we
want
to
really
promote
the
work.
That's
been
done
here,
okay,.
A
A
So
maybe
we
should
defer
the
exact
structure
in
terms
of
once
again
versus
multiple
or
I'm
sorry,
github
pages
versus
just
marked
on
documents
until
later,
but
for
right
now,
I
think
what
I'm
hearing
is
general
consensus
that
we
will
move
it
to
mark
down
but
keep
the
spreadsheet
as
a
Google
Doc
and
we'll
do
that
after
we
go
through
the
reviews
and
basically
right
before
we
claim
or
we're
done-
that's
not
fair.
Yes,.
A
C
A
E
D
Yeah
so
I'm
hoping
for
the
next
week
for
10
days
on
the
outside,
to
get
these
detailed
edits
done.
But
then
my
my
hesitation
is:
are
you
gonna?
You
know
be
incredibly
unhappy
with
the
edits
and
need
months
to
back
them
out.
I,
don't
think
so.
I'm
not
I'm,
not
looking
to
have
an
editor
coming
to
rewrite
the
substance
of
yeah.
E
D
So,
let's
say
Chris
and
I
I've
spoken
to
Chris
about
this-
that
you
and
I
are
both
intent
on
having
this
an
outside
headed
process.
So
can
we
say
ten
days
for
for
those
edges
to
be
made
and-
and
though
you
know,
they'll
all
be
done
as
suggestions
and
then
I
guess
a
week
after
that
for
this
for
this
working
group
to
sign
off
on
them.
That
is
essentially
to
push
back
on
any
that
you're
concerned
about.
You
feel
like
change,
the
meaning,
etc.
Okay,.
A
So
well,
the
reason
I'm
hesitating
is
because
ten
days
is
kind
of
an
awkward
a
number
of
days.
E
A
I
refer
that
and
I'd
rather
aim
for
a
week
and
then
slip
out
greet
okay,
excellent.
So,
let's,
let's
do
that
so
Dan's
gonna
have
his
editor
look
for
a
week.
Okay,
then
working
group
kicks
in
for
review
and
are
we
looking
at
approximately
two
weeks
for
us
or
just
one
week
for
us?
What
do
people
want
to
put
that
in
intently.
C
A
C
F
A
Yeah,
that's
actually
a
good
point.
They
and
I
would
agree
with
that
at
this
point,
I'd
rather
not
have
anybody,
including
myself
or
Ken,
or
anybody
just
blindly
make
changes.
I'd
rather
have
everything
go
through
review.
Otherwise
things
might
slip
in
that
people
may
be
mentally
disagree
with
so
I'd
like
to
require
request
that
everybody
go
through
making
suggestions
as
opposed
to
straight
at
it.
Even
if
you
have
the
access
to
do
so.
A
I
guess
one
thing
I
should
mention
is
that
while
Cathy
thank
you
very
much
did
make
changes
to
the
conclusion
section
I'm
still
a
little
nervous
that
there
haven't
been
other
suggestions
and
maybe
everybody's
okay
with
it,
but
just
remind
people
again
to
please
look
at
that
conclusion
section
because
that's
probably
the
most
important
part
of
it,
because
that's
gonna
be
our
next
steps
or
recommendation
for
next
steps.
So
please
look
at
that
sooner
rather
than
later.
A
D
B
C
A
Think
it
would
be
maybe
weren't
your
slides,
just
cuz
slides
are
easy
for
you
to
look
at,
but
yeah
I
think
it
would
be
sort
of
a
very
high-level
summary
of
what
we
talked
about
and
the
white
paper
itself.
But
then
yeah
mainly
focus
on
the
recommended
next
steps
more
than
anything
else,
but
I
think
that's
something
that
we
should
probably
work
on.
B
Leah's
Oh,
weird,
okay,
so
Doug
what
I
was
gonna
say
is
actually
the
last
item
in
the
agenda
that
would
get
you
later.
That
could
actually
be
the
straw
man
for
what
you
presents.
The
doz,
which
is
this
lightning
talk
that
I
have
next
week
at
surhoff
on
kind
of
what
we've
been
doing
so
maybe
that
becomes
the
set
of
slides.
I'm
I
have
15
minutes
to
talk
about
what
we've
been
doing.
So
we
can
kind
of
use
that
if
it's
the
following
week
anyway,
okay.
A
So
tell
you
what
okay,
let's
hold
off
on
the
discussion
that
all
we're
gonna
present
COC
until
we
get
to
that
point
in
the
agenda,
but
I
think
that's
a
good
idea,
then.
So,
let's
talk
about
the
next
thing,
which
is
the
eventing
proposal
now
I
know
I
know
he
said
on
the
call.
It's
gonna
wonder
if
Euron's
on
the
call
to
talk
about
his
wedding
stuff,
but
Austin
I
know
you're
on
the
call,
so
I
believe.
Actually
a
lunch.
G
Sure
sure
thing
hi,
everyone
I'm
Austin,
calling
some
a
CEO
founder
of
Cerberus
calm
and
the
service
application
framework.
For
the
past
month,
almost
two
months
now,
we've
been
working
with
a
major
cloud
provider
on
a
vendor,
neutral
standard
for
format
for
event,
data
and
it's
pretty
exciting
and
we're
seeking
the
participation
from
some
of
the
other
major
cloud.
Vendors-
and
this
is
this-
is
a
very
ambitious
effort,
but
so
far
we've
had
a
lot
of
interest.
G
I
think
we
have
our
second
major
cloud
vendor
joining
us
in
about
a
week
here
and
about
four
other
cloud.
Vendors
have
expressed
interest
in
participating
and
we're
keeping
this
scope
pretty
small
right
now.
It's
we're
just
focused
on
this.
On
this
event,
data
format
and
we're
going
to
actually
submit
a
PR
today
with
our
initial
proposal.
For
this
and
for
clarity,
this
is
not
final.
This
is
just
a
starting
point,
another
conversation,
but
we
love.
You
know
broader
comment
from
all
the
CNCs
stakeholders,
so
look
out
for
that.
G
G
So
a
lot
of
details
like
doing
deep
implementation
dives
and
what
is
called
and
what
it
ultimately
ends
up
to
be
we're
kind
of
treating
as
secondary
our
first
priority
is
just
to
see
who
we
can
get
at
the
table
and
see
if
we
get
some
some
significant
influencers
to
to
collaborate
on
this
so
I
think
only
if
we
could
achieve
that
goal.
First,
will
we
be
able
to
make
a
big
impact
here?
All.
B
G
Close,
it's
not
far
off
there's
some
different
names,
of
course,
for
some
of
the
properties
in
there,
but
it's
pretty
close,
it's
actually
narrower
in
scope.
It's
became
obvious.
The
first
day
we
started
working
on
this
with
only
like
six
people
in
the
room
that
we
could
go
over.
These
implement
implementation
details
for
ten
years,
so
we
we
really
trimmed
it
down
and
just
said,
and
just
put
a
quick
version
on
it
and
decided
just
to
take
that
and
start
bringing
it
to
some
of
the
other
providers.
So
what
we's?
A
Cool
excellent,
okay
and
I
said
believe
Jim
it's
technically
on
vacation
today,
even
though
he
was
respond
to
my
slack
request.
So
what
I
may
do
is
have
him
I,
certainly
ask
the
question:
do
you
guys
want
me
to
suggest
that
he
submit
his
thing
as
a
PR
request
as
well,
or
would
you
guys
prefer
to
have
Austin's
go
up
there
first
and
then
that
you're
on
perhaps
make
suggested
changes
to
that
proposal?
I've
got
I'm
a
little
nervous.
A
A
D
Standing
here,
I
just
want
to
say
I'm,
very
supportive
of
this
effort,
and
so,
if
there's
in
particular
any
introductions
that
I
can
do
and
I
guess
more
explicitly,
if
there's
some
specific
cloud
providers
that
you're
just
trying
to
get
them
to
pay
attention
to
this
and
and
state
an
opinion.
Please
please
ping
me
and
I'm
happy
to
help
with
that.
We'll.
G
Do
Dan
and
appreciate
your
help?
I
actually
had
lunch
with
Chris
on
Monday,
and
he
expressed
the
same
so
yeah
really
appreciate.
The
support
so
far
were
we're
having
a
lot
of
success.
I
think
it's
because
we
were
keeping
the
scope
pretty
small
and
and
tapping
some
of
these
big
providers
on
the
shoulder
kind
of
kind
of
early
and
getting
them
involved
right
away.
So,
but
anyway
appreciate
the
support
and
it's
likely
I
might
reach
out
to
you
at
some
point
great.
A
B
A
another
service
conf
in
New
York
next
week,
so
I
had
submitted
a
couple
months
back
basically
a
work
in
progress.
You
know
just
basically
a
snapshot
presenting
a
snapshot
of
what
we
were
doing
so
that
was
accepted
and
it's
15-minute
lightning
talk
so
not
too
deep
on
the
content.
But
basically
you
can
see
the
abstract
I
submitted
it's
not
in
the
public
website
agenda,
but
there
it
is.
So
you
know
what
what's
involved
and
why
I
think
was
interested
to
this
audience.
A
Okay,
so
Dan
I
think
was
last
week
a
folder
was
created
and
our
github
repo
for
presentations
for
people
to
share.
Maybe
you
can
upload
your
presentation
there,
and
then
people
can
take
a
look
at
it
and
in
that
Creek
we
can
decide
whether
we
think
it
was
a
good
starting
point
for
the
material
we
want
to
present
to
the
TOC.
Okay.
B
A
B
C
B
A
C
B
Yeah
I
understand
it's
just
it
wasn't
over
I,
just
an
overview.
I
just
have
added
a
couple
of
examples.
There
mainly
think
about
the
big
service
providers
that
people
might
know
of
as
providing
a
commercial
public
service,
but
I
totally
get
your
point
and
I'm
gonna.
Add
you
in
there
sorry
about
that?
Okay,.
G
A
G
G
A
Good
all
right,
any
other
topics-
people
wanna
bring
up
all
right.
In
that
case,
just
a
little
reminder,
please,
if
you
do
get
a
chance,
please
review
the
document
itself,
but
in
particular
the
conclusion
section
sooner
rather
than
later,
otherwise,
I
believe
that's
it
for
today.
Thank
you
guys
very
much.
We'll
talk
next
time.
Bye.
C
I
mean,
though
attendees
yes,.