►
From YouTube: CNCF Serverless WG Meeting - 2018-03-19
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.
B
D
C
Iii
find
so
we
currently
have
the
discussion
on
the
google
group.
Should
we
put
that
in
this
doc,
I
think
it'd
be
easier
to
like
have
it
in
front
of
us
as
a
doc,
so
people
can
comment
on
it
or
should
we
pull
it
into
separate
doc
so
that
we
have
it
with
the
two
words.
B
F
G
C
B
So
yeah,
so
what
I
did
is
I
took
twelve
twelve
cases
that
I
laid
out
for
easy.
That
was
mostly
also
easy,
consumption
and
kind
of
for
people
kind
of
self,
selecting
which
half
way
works
for
a
few
and
then
consolidated
them
into
four
and
then
added
some
further
commentary.
So
now,
I
have
applications
that
produce
applications
that
consume
mill,
aware
that
routes
and
then
frameworks
that
will
help
you
dispatch
to
handlers
and
and
just
generally
provide
abstraction,
great.
A
Just
gonna
ask:
is
there
anything
the
reason
you
put
it
into
the
spec
itself?
Do
you
expect
this
to
be
normative
in
some
way,
as
opposed
to
sort
of
a
more
like
reference
material?
I.
A
B
C
So
so
who
do
we
have
here?
Participants,
hey
Austin,
hi,.
C
B
H
H
A
H
F
C
Great
so,
yes,
I
thought
that
we
could
just
walk
through
these
four
scenarios
and
I
think
that
basically
we're
looking
for
things
that
would
let
us
know.
If
we
cannot
do
these
things,
then
we
must
change
this
back
and
if
something
is
not
required,
we
may
defer
to
like
may
bucket
these
things,
but
in
any
case
the
focus
is
what
are
the
things
that
must
be
supported
in
order
for
this
to
work.
C
B
The
second
is
applications
and
consumers
events
and
their
perspective,
specifically
also
in
how
they
are
and
what
they're
interested
in
and
what
requirements
they
drive
really
on
the
producer,
because
the
producer,
the
distribution
here,
is
that
and
from
a
requirements
perspective
is
the
producers
are
dictating
what
goes
in
the
event,
because
they
sit
on
that
information
right
and
consumers
express
the
interest
of
what
they
eat
in
the
vent
and
then
there's
middleware
between
the
two.
That
kind
of
also
has
requirements
also
on
the
producer
for
things
that
are
required
and
then
there's
the
frameworks.
B
B
B
C
Great,
so,
first
of
all,
before
like
what
I'd
like
to
do
in
this
meeting
is
just
to
die
to
go
through
each
paragraph
and
make
sure
they're
sure
it's
clear
and
and
that
we
were
aligned
on
what
these
things
mean,
but
before
we
do
that
first
does
so
personally.
I
think
this
structure
is
very
helpful,
but
does
anybody
have
any
comments
about?
You
know
these
sort
of
four
categories
and
kind
of
this
approach
to
explaining
the
scenarios
I.
H
Like
these
four
categories,
I
think
it
covers
a
lot.
These
are
very
broad
categories,
there's
a
lot
they
can
go
into
them,
but
just
using
these
categories,
as
our
conceptual
framework
for
approaching
approach,
this
conversation,
I
think
is-
is
great.
It's
inclusive
of
pretty
much
all
the
most
important
pieces.
A
A
C
F
C
On
the
framing
paragraphs,
to
explain
that
the
spec
isn't
going
to
implement
all
these
things
but
enable
these
things,
and
so
that'll
take
some
wordsmith
and
we'll
get
back
to
that,
because
I
think
that
framing
it
after
we
have
alignment
on
what
it
is,
it's
a
little
easier
super.
So
so,
let's
just
go
paragraph
by
paragraph.
B
I'm
saying
there's,
there's
there's
either
context:
yeah
I
mean
yeah.
Ultimately,
it's
a
topic
right.
Yes,
so
you
have
a
context
in
which
a
the
context
is
something
that
I'm
using
these
two
terms
of
both
in
in
this
write-up
context
is
something
where
you
have
a
like
the
device
here.
When
you
have
a
mount
position
in
a
room
with
floor
in
the
building
and
and
then
specifically
about
the
temperature
sensor.
Armée
goes
into
a
mullahs
issue
and
if
that
breaks,
another
temperature
says
it
goes
into
that
mode
position.
B
But
the
context
of
the
company's
of
the
temperature
sensor
is
its
mount
position.
That's
something
that's
a
classification
is
something
that's
a
little
bit
more
abstract
and
that's
I'm,
representing
that
by
the
classification
by,
for
instance,
Liga
team.
If
you
have
a
sports
result,
I
have
and
I
have
an
example
for
the
sports
results
of
them
actually
further
further
down.
In
the
framework
section.
C
C
A
B
A
C
B
A
A
C
C
A
location
in
my
mind,
conveys
geolocation,
and,
if
that's
not
what
something
you
want
it
like,
it
could
be
that
the
temperature
center
also
knows
where
it
is
as
it
moves
around.
If
it
wouldn't
be
like
you
know
what
I
mean
like,
if
that's
something
you
don't
want
to
convey,
I,
don't
think
it
matters.
No.
C
C
It's
just
you
just
like
that
emphasizing
the
anywhere
rather
than
specifying
hosts
you're
like
server
or
device.
You
know
it's
just
a.
C
C
If
you
feel
it
says
something
and
I
think
we're
good
and
then
I
think
this
is
an
important
paragraph
that
Clements
mentioned
in
the
introduction.
The
produced
events
might
be
rendered
and
emitted
directly
by
the
producer
or
by
an
intermediary,
as
example
for
the
latter
consider
event,
data
transmitted
by
device
and
so
on.
Do
we
need
to
be
clear
that
this
does
not
change?
Who
the
producer
is
to
sort
of
clarify
all
of
our
conversations
about
source.
The
producer
is
still
the
original
producer
or.
B
I
C
B
C
B
Kinds
of
reasons
for
why
you
consume
events
anyway
and
from
ends
from
different
and
from
all
kinds
of
different
contexts.
That's
the
that's
the
point
of
this
right,
so
you
may
have
apps
or
the
the
originator
the
the
context
you
care
about,
really
might
be
the
device
or
might
be
person
and
might
or
might
be
an
application.
And
if
the
event
comes
from
a
person,
the
the
producing
application
per
se,
the
bits
may
actually
be
he
material.
So
it's
it's.
B
B
Point
the
point
here
and
no
the
point
is
so
no.
This
is
the
perspective
right.
This
is
just
this
is
a
perspective.
The
app
this
is
what
the
app
you
can
see
me
app
cares
about
all
right.
It
doesn't
care
the
the
the
the
producer
cares
about
its
putting
stuff
on
the
wire
from
its
context,
so
the
other
can
others
can
can
and
help.
It
makes
me
it's
come
takes
more
whole
effectively.
That's
kind
of
the
motivation
for
why
a
producer
does
that
the
consumer
here
doesn't
care
as
much
about
what
the
producer
does.
B
A
B
I
see
I,
think
yeah
I
had
this
distinction
in
the
original
12
points,
I
had
started
doing
the
structurally
structuring
a
little
differently
today
and
then
fell
back
in
making
platform
tools
and
applications
really
just
be
a
paragraph
here
and
I.
Think
the
difference
is
really
the
perspective
of
of
what
you're
doing
like
in
the
I
called
them
out,
because
they
have
a
technical
function
rather
than
a
business
function.
If
that
makes
any
sense
well.
B
C
B
If
we
say
that
the
mom
I
think
that
does
technical
monitoring
is
really
just
another
I'm
fine
with
that
and
just
strike
that
entire
paragraph
yeah.
B
A
B
This
this
is
about
this
is
about
consumer
applications,
but
the
consuming
applications
are
not
I'm
struggling
with
the
difference
between
maybe
I'm
struggling,
but
with
a
difference
between
you
know
what
I
would
call
business,
apps
and
platform
apps
you
know,
and
then
then
then
you
can
always
have
make.
The
argument
of
well
platforms
are
apps.
B
A
B
C
C
B
E
K
C
C
B
The
reason
why
the
reason
why
I'm
choosing
with
the
reason
why
I'm
choosing
that
working
like
this
is,
is
what
do
you
care?
That
is
really.
Is
that
the?
What
do
you
care
about
as
a
consumer
right
if
I
care
about
I
want
to
have
the
temperature
reading
from
the
from
the
sensor
and
pace
in
the
corner,
in
that
in
that
room
in
that
building,
I?
Don't
care
about
the
app
I?
Don't
care
about
the
software
that
produces
it
I?
B
Don't
care
about
any
of
those
things
I
care
about
that
sensor
that
currently
hangs
in
that
slot
in
that
corner,
I,
don't
even
care
about
the
instance
of
that
device
and
if
that
device
device,
silently
or
if
that
device
is
kind
of
breaks
and
the
tank
walks
into
that
corner,
you
know,
takes
a
new
device
plugs
that
new
device
in
in
that
same
slots.
I
still
only
care
about
that
data
from
that
place,
I,
don't
care
about
the
device.
Id
I!
Don't
care
about
any
of
that
thing.
I!
Don't
care
about!
B
For
that
particular
context
interest.
Nobody
cares
about.
You
know
the
the
particular
that
picnic
particularities
of
the
the
producer
is
just
one
of
many
that
can
serve
in
that
particular
capacity.
That's
why
I
draw
that
distinction
is
that
you
are,
as
a
consumer
expecting
event
from
a
particular
user
really,
rather
than
expecting
that
event
from
a
particular
app
yeah.
The
producer
app
obviously
has
a
completely
different
different
perspective
on
this,
because
it's
all
important
for
itself,
but
but
the
consumer
doesn't
care
all
that
much.
C
B
It's
it's
it's
very
practically
so
that
if
you
are
having
a
conversation
with
someone
on-
let's
say
you
know,
GG,
chats
or
on
set
still
alive
or
on
Facebook
message
or
whatever,
and
you
switch
between
the
web
interface
and
the
and
the
phone
interface.
Nobody.
Nobody
really
even
knows
that
you're
doing
something
different,
but
they're,
they're,
they're,
they're
interested
in
the
events
are
coming
from
you,
they're,
not
interested
in
the
events
that
are
coming
from
that
particular
ayah
from
that
particular
phone
or
from
that
particular
web
session.
B
B
G
C
B
C
C
A
Wait
so,
okay
in
the
previous
section,
though,
we've
already
kind
of
defined
context
as
well
as
classification.
Do
we
really
need
to
get
into
that
again
other
than
is
to
say
yeah?
We
have
said
we
have
said
that
there
is
such
a
thing.
Yeah
wait,
I,
don't
think
we
need
to
say
it
again,
I'm
kind
of
little
confused
as
to
why
we're
worth
smithing
this
paragraph
we
already
agreed
to
merge
the
two.
What
more
needs
to
happen?
Well,.
C
C
B
B
A
G
A
B
The
producer
is,
ultimately,
the
producers
persist
the
event,
but
the
years
the
question
of
how
much
does
the
consumer
actually
care
about
the
identity
of
that
producer?
Does
it
care?
That's
the
consumer,
really
care
about
the
producer
and
its
identity
and
and
all
those
things
and
it
doesn't,
the
the
the
the
consumers
concerns
around
the
context
that
the
producer
is
acting
on
behalf
of
that's
what
this
is
trying
to
I'm
trying
to
say.
J
C
C
B
What
what
that
means
is
is
if,
if
I'm
as
a
consumer
interested
in
consuming
events
that
are
that
are
coming
from
people,
I
will
need
to
go
and
collect
events
from
all
the
places
where
that
person
that
I'm
interested
in
goes
and
has
that
same
context.
So,
if
I'm
running,
if
I'm
running
and
this,
and
that
motivates
actually
pops
up
I'm
interested
in
that
person
right
writing
into
the
context
of
a
chat,
a
chat,
conversation
and
a
half
with
them.
B
If
I
have
this
chat
conversation
with
them,
I,
don't
I
care
about
what
the
chat
conversation
and
all
the
lines
that
are
being
transmitted
and
as
Ben's
emanating
from
that
chat
conversation,
but
obviously
that
chat
conversation
can
now
exist
on
three
tabs
in
three
different
web
browsers
and
can
also
exist
on
my
phone
and
on
my
tablet
in
America,
see
in
an
app
in
six
different
places.
But
it's
all
one
chat
application,
so
I
care
about
receiving
events
from
the
chat
context
and
more
from
that
person.
Really
in
that.
In
a
case.
C
B
Not
from
in
particular,
those
six
different
kinds
of
applications,
that's
the
expression!
That's
why
I'm
expressing
your
with
consumer,
my
my
expectation
is
that
I'm
getting
the
information
from
the
chats
or
from
the
information
from
the
person
or
the
information
from
it
needs
to
be
something
more
specific,
but
not
from
an
application.
From
from
a
specific
application,
instance,
I
might
and
I've
made
that
Acacia
application
modular
instances,
but
I
might
also
want
to
have
something
from
a
more
abstract
construct
that
is
then
solvable
using
an
intermediary
that
will
help
me
with
that.
A
C
A
I'm
in
the
chat
in
the
zoo
kind
of
paste
of
it,
it
seems
to
me
we
started
off
in
this
discussion,
can
look
at
the
first
two
paragraphs
of
section
two,
and
so
we
at
some
point
I
thought.
We
agreed
to
merge
the
two
paragraphs,
because
the
word
platform
tools
in
there
was
telling
a
bit
of
a
curve,
so
I
merge.
The
two
paragraphs
together,
write.
B
Land,
so
the
first
part
actually
originated
from
the
event
for
me.
No,
no,
so
I'm,
actually
not
I'm,
not
I'm,
not
happy
with
that,
because
I
didn't
see
the
first
part,
because
it.
What
matters
here
would
matter
see
when
I'm
trying
to
express
when
I'm
trying
to
express
is
that
the
consumer
cares
about
the
it
doesn't
care
about
the
producer
itself.
It.
The
events
are
all
produced
by
producers.
Obviously,
but
it
really
cares
about
context.
A
So
can
I
pick
your
recommendation,
though,
because
if
you
go
to
paragraphs
ahead
down
to
line
92,
you
then
start
talking
about
basically
what
the
consuming
application
is
interested
in
right
and
that's
I.
Think
where
you
should
start
talking
about.
Why
context
matters
and
stuff
like
that,
but
in
the
intro
paragraph
to
what
a
consumer
is
I,
don't
think
we
need
to
get
any
more
complicated
or
detailed
than
to
say
there.
The
receiver
of
these
events
that
we
just
defined
a
pre
in
section
1,
okay,
then
then.
C
B
B
C
Identifying
also,
can
you
add
numbered
lists
just
because
I
think
it
helps
discussion
for
next
time,
then
identifying
selecting
the
origin
context
or
the
producer
assigned
classification
I,
think
that's
the
point
you
were
making
and
then
identifying
the
terrible
order,
yep
and
actually
so.
B
B
So
there
are
cases
where
you
are
omitting
events
without
having
a
clear
notion
of
what
the
wall
clock
is
and
so
you're
using
some
reference
thing.
That
is
not
necessarily
inaccurate.
You
can
see
clock
and
that's
why
I
put
that
in
here
as
a
as
the
thing
that
you
might
be
interested
in,
but
really
what
we're
interested
in
often
is
not
the
the
actual
time
right.
C
Think
that's
a
good
point.
Cuz
there.
Some
things
can
don't
have
time,
but
they
have
sequences
and
that's
come
up
here
as
well.
So
so
we
have
new
people
on
the
call
mark
and
Stanley.
You
want
to
just
do
a
quick
mark.
You
want
to
let
us
know
who
you
are
and
away
from
what
what
context
makes
you
interested
in
cloud
events.
I
D
Hello,
everyone
can
hear
me:
okay,
yeah,
perfect,
so
I
am
here
from
Oracle.
We
are
also
interested
in
a
bunch
of
scenarios.
The
won't
probably
one
of
the
bigger
one
is
the
multi
cloud.
You
know
interoperability
of
events,
one
of
the
things
that
we've
taken
a
very
in
tact
towards
is
armed,
there's,
no
differentiation
between
our
services
and
customer
services
in
Oracle's
clouds,
so
anything
that
our
services
can't
our
services
do.
Our
customers
can
reasonably
expect
to
drop
in
their
own
service.
C
So
we
are
I,
will
zoom
back
out
thanks
for
the
introductions,
I
think
capturing
things
in
the
notes.
So
we
have
we're
talking
about
the
different
things.
A
consuming
application
would
be
interested
in
and
Clemens
and
I
and
Doug
have
talked
a
lot.
So
we'd
love
to
hear
from
other
folks,
in
the
call
whether
you
have
any
additions
or
thoughts
about
these
four
things.
C
So
we
are
we're
trying
to
I
think
this
is
a
sort
of
easier
way
to
get
at
a
shared
language
before
we
start
defining
attributes
in
the
spec
and
and
ideally
we'd
be
able
to
use
these
as
a
way
to
say.
If
we
can't
do
these
things,
then
we
must
make
a
change,
the
spec
and,
and
that
should
get
us
to
an
internal
state.
Is
that
a
fair
summary
also,
you
think.
H
C
B
I
think
I
think
this
leads.
These
leads
to
a
source
discussion
and
we
shouldn't
have
that
very
soon,
because,
ultimately,
the
the
what
source,
the
resolving
in
the
idea
of
what
sources
or
what
source
represents,
will
lead
us
fairly
quickly
to
I
think
a
breakthrough
in
terms
of
what
properties
we
really
need.
I
hope
they
do.
It
does
so
yeah.
H
You
know
sigh
yeah,
I'm
I,
believe
the
same
I
think
our
goal
here
is
to
get
this
to
an
initial
version
right
away.
I
think
all
this
effort
that
we're
doing
around
the
use
of
scenarios
and
design
goals
absolutely
essential
to
helping
us,
but
I
also
think
that
just
resolving
some
of
these
events
or
conversations
and
quickly,
of
course,
will
help
us
get
to
that
dead
version
sooner
right.
C
H
Yeah
and
at
the
very
least
having
the
events
are
such
an
ambiguous
topic
having
a
single
paper
or
a
single
spec
that
really
defines
how
major
industry
influencers
like
Microsoft,
Google,
IBM
and
Oracle,
and
s
ap
VMware,
all
think
about
events.
I
think
is,
will
be
creating
a
lot
of
clarity
for
a
lot
of
people
general.
So,
okay,.
C
Yes,
have
any
things,
and
you
know,
and
then
I
think
there's
these
some
cases
right.
The
application
calls
back
the
consuming
application
might
want
to
call
back
see.
This
is
that
that.
B
Is
not
necessarily
a
call
back
and
I'm
careful
about
that,
so
some
cases,
the
consumer
application,
might
be
interested
in
obtaining
further
details
about
the
event
subject
from
the
original
context,
like
obtaining
detailed
information
about
a
change
object
requires
privileged
access
authorization
that
doesn't
mean
call
back.
That
means
you
might
be
able
to
come
to
that
context.
To
that.
B
To
that
context,
and
to
the
subject
of
inside
that
context,
from
an
angle
that
you
already
know,
so
you
get
notified
through
some
mechanism
that
a
new
file
has
been
created
in
a
blog
for
you,
then
you
have
to
come
through
the
front
door
for
your
blog
API
to
go
and
walk
up
to
that
walk
up
to
your
account
that
you've
got
the
alert
from
and
then
walk
into
that
container
and
find
the
subject
of
that
of
that
notification.
That
means
that
file
and
get
it.
B
C
B
Was
then
that's
a
clarification
that
I'm
not
sure
we
need,
but
it's
really
it's
the
producer.
It
underlines
the
point
that
the
producer
out
of
their
own
out
of
the
own
drive
might
just
go
and
throw
some
stuff
on
the
wire
without
much
structure,
but
it's
really
that
the
consumers
interests
are
motivating.
How
that
how
that
information
ought
to
be
shaped,
and
it
was
an
interesting
point.
It
was
an
important
point
in
my
head.
Is.
C
B
I
A
B
I
had
a
more
like
a
business
level
scenario
in
mind,
like
think
of
an
HR
application
and
raised
an
event
that
you,
a
new
employee,
has
been
created
in
the
system.
The
event
may
actually
raise
only
as
much
as
an
employee
ID,
because
everything
is
PII
and
then
only
an
application
that
is
authorized
to
go
and
get
at
that.
Pii
is
then
doing
a
call
in
to
the
application
to
get
the
detail
out.
Okay,.
B
A
I
think
I
think
what
threw
me
was
the
wording
correct
me
if
I'm
wrong,
but
it
got
me
to
paraphrase
to
make
sure
I'm
fully
on
the
same
page
as
you.
The
first
part
when
you
say
obtaining
for
the
details
about
the
event
subject
from
the
originating
context.
What
you're
I
think
what
you're
saying
there
is
from
the
context?
A
A
C
B
So
because
the
point,
the
point
here
is
I
think
this
is
a
super
common
pattern,
but
I
also
think
that
the
all
the
context,
if
you
need
to
go
back
to
a
different
place,
is
split
between
your
application
and
the
payload
data,
and
it's
really
an
application
of
a
concern.
I
just
wanted
to
call
this
out
as
an
as
as
the
common
application
pattern,
what
we
but
one
that
either
I,
don't
think
we
will
have
to
go
and
address
in
our
common
properties.
B
C
And
again,
it's
just
its
context
because
a
lot
of
that's
what
we're
doing
here.
We
want
to
capture
the
shared
context
that
we've
been
achieving
and
they
work
in
group
meetings
all
right,
so
it's
nine
o'clock
and
I
will
submit
this,
and
so
people
can
look
at
it
and
chime
in
more
and
then
we'll
go
to
the
next
two
sections
in
the
meeting
tomorrow
and
if
we
get
further,
then
we
can
talk
more
about
specific
attributes,
yeah
other
people
on
the
call
who
didn't
talk
as
much.