►
From YouTube: CNCF TOC Meeting - 2018-09-04
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
B
A
Yep,
so
quick
agenda
today
will
be
essentially
welcoming
a
new
project
in
the
sandbox,
a
little
discussion
around
the
safe
working
group,
and
we
have
two
community
presentations
today
from
The
Awl
about
Alibaba
folks.
So
one
is
dragonfly.
The
others
open
messaging,
we'll
discuss
a
little
bit
about
the
community
backlog
of
presentations
that
we
have
to
review
and
then
open
it
up
to
any
questions
from
the
community
so
slide.
6
simple!
Welcome
to
the
TI
kv
community
to
CN
CF.
They
entered
the
sandbox
on
August
28th.
A
This
is
also
our
second
project
that
was
born
from
China
in
C&C
F,
which
is
kind
of
exciting
for
me
on
a
personal
level
and
kind
of
shows
how
global
our
community
is,
but
other
than
that
welcome,
TI
kv
and
looking
forward
for
you
to
grow
within
the
foundation
slide.
7
is
kind
of
our
backlog
of
presentation,
proposals
that
were
asking
for
review
from
the
toc
contributor
and
wider
community.
So
two
big
things
cortex
and
build
packs,
have
both
secured
TOC
sponsors
and
are
kind
of
working
through
the
project
proposal
process
to
enter
the
sandbox.
A
We
have
a
backlog
of
net
data
and
key
cloak
coming
up
for
presentations
in
the
future
next
slide.
This
is
something
I'd
like
the
TOC
to
discuss.
I,
don't
know
if
we'll
have
enough
time
to
kind
of
go
over
this,
and
we
may
move
this
discussion
email,
but
we
have
a
handful
of
projects
that
have
asked
to
present
themselves
to
the
TA
and
wider
community.
We
have
to
essentially
make
a
decision
on
whether
we
would
like
to
invite
them
or
not.
A
If
they're
good
fits
I,
don't
know
if
any
to
see
members
have
taken
a
look
at
these
yet
have
any
opinions
of
which
ones
we
should
at
least
include
and
kind
of
start
from
there.
Brian
or
any
folks
have
any
comments
on
these
particular
ones
of
whether
we
should
include
them
or
exclude
them
from
presentations
be
good
to
make
a
decision
on
D.
Some
of
these
have
folks
have
been
waiting
for
a
while.
C
B
C
C
B
Here,
just
just
to
repeat
what
I
mentioned
to
you
before,
which
is
that
I
think
we
need
a
blanket
inclusion,
exclusion
principle,
especially
for
the
sandbox,
because
at
the
moment
our
exclusion
criteria
are
essentially
non-existent,
and
so,
if
we
follow
them,
then
you
know
all
of
these
should
get
to
present
and
potentially
get
into
the
sandbox.
And
if
not
going
to
do
that,
then
we
need
to
come
up
with
a
clear
distinction.
B
A
Yeah
I
definitely
I
agree.
I
have
some
thoughts
of
basically,
you
know
at
least
one
toc
person
needs
to
approve
a
project
to
be
presented,
at
least
as
kind
of
a
bit
of
a
gate,
but
we
could
kind
of
move
this
discussion
on
to
the
mailing
list
to
kind
of
firm
this
up,
since
the
interest
has
definitely
spiked
a
bit
in
the
last
couple
months,
all
right,
so
you
will
move
that
discussion
to
the
mailing
list.
Moving
on
next
slide
governing
board
working
updates.
So
just
working
about
working
group
updates.
A
We
have
four
official
working
groups
that
meet
more
importantly,
we
have
one
new
working
group
that
is
being
voted
upon
related
to
the
security
space.
So
I
kicked
off
that
vote
this
this
morning,
so
I
appreciate
any
feedback
to
the
safe
security
working
group.
You
could
see
their
full
project
proposal
linked
off
that
messaging
thread.
A
A
D
And
we
applied
teams
to
present
in
black
I'm
Alan
from
Alibaba
Group
and
I'm
responsible
for
the
container
ecosystem
in
Alibaba,
and
what
is
dragonfly
dragonfly
is
a
open
source,
p2p
based
image
distribution
and
the
file
system
distributed
system.
Dragonfly
is
an
intelligent
and
p2p
based
at
container
imagery
distribution
system,
and
it
provides
native
imitative
revolution
solutions
for
cloud
native
applications,
and
currently
we
can
integrate
integrate
integrated
dragonfly
with
group
netlist,
very
native
things.
Okay,
and
here
we
list
some
features
of
Jagga
in
cloud
native.
D
We
dragonfly
focuses
answer
imitative
distribution
parts
about
the
distribution
part.
We
can
live
to
three
kinds
of
distinguished
features.
The
first
is
the
efficiency
we
provide
p2p
based
image
and
the
third
distribution,
and
we
can
provide
another
gsdd
and
to
avoid
a
repeatable
downloads
to
reduce
the
cost
and
the
second
is
under
flow
control
site.
We
can
provide
a
task
level
and
a
hook
to
let
about
NAT
speed
limits
with
the
letter
speed
limit
dragonfly
can
potential
host
disk
and
protect
you
from
hi,
hi
user
input
and
output.
The
third
one
is
security.
D
Dragonfly
can
encrypt
your
image
distribution
when
image
transmission,
okay
and
last
but
not
least,
dragonfly
is
very
easy
and
very
simple
to
use.
We
can
say:
dragonfly
does
nothing
invasive
to
all
kinds
of
currently
constant
technologies
like
the
most
Republicans
in
engine
talker
like
another
container
engine
open
sourced
by
Alibaba,
which
named
launch
container
with
artists
continue
engines.
You
can
pull
container
images
with
dragonfly
as
usual.
D
Okay,
so
if
you,
if
you
met
issues
we
can
see,
dragonfly
can
cover
such
kind
of
use
cases
if
you
want
increase
image
downloading
speed,
if
you
want,
if
you
want
to
reduce
your
been
quick,
then
twist
close
to
attend
laser
50%
off
and
if
you
want
to
distribute
a
large
container
image
negatives,
are
these
images
on
largest
and
10
in
parts
we
can,
we
can
say
well
lots
of
traditional
application
moving
to
cloud
native
at
first
as
a
very
feelings.
Their
images
are
very
large,
so
dragonfly
can
improve
the
distribution
efficiency.
D
Also
if
the
cluster
is
at
a
very
large
sphere,
I
sing
dragonfly
is
your
best
choice.
So
gently
also
Kane
shows
us.
The
ability
of
business
services
is
not
affected
by
the
tongue,
downloading
task
causing
their
production.
We
have
met
lots
of
issues
Laxus,
Kendall
scenaries.
You
can
also
prevent
data
from
leaking
in
transmission.
Security
is
another
matter.
We
should
take
more
care
of
okay,
so
next
slides,
we
are
very
happy
to
see.
D
You
see
browser
and
Markham
and
also
Alabama
cloud.
They
are
also
using
dragonfly
to
speed
up
co
distribution
to
ensures
a
distribution
transmission
and
in
the
and
financial
on
the
financial
part.
We
are
very
happy
to
see
and
finance
you
say
a
dr.
Jack
and
fly
in
tens
of
thousands
of
nodes
in
theatres,
the
center
to
provide
financial
services
globally.
In
addition,
Sonya
and
Tim
are
double
toe
box.
They
are
also
adopter
subjective
lab
this.
This
is
all
Mouse
production
near
spice.
D
Here
we
were
here
all
of
us
a
little
bit
about
the
architecture.
As
the
first
level,
we
can
see
the
German
flight
controller.
This
is
the
controller
which
takes
advantages
of
the
dragonflies
API
to
manager.
What
is
working
inside
of
dragonfly
as
a
second
level.
We
can
see.
Supernova
supernova
is
know
that
which
managers
so
distribution,
part
in
in
the
data
center
or
in
innocence
access.
Sir
level,
we
can
see
as
a
host
as
a
host
of
Nod.
We
definitely
have
continued
angel.
D
And
the
in
the
a
cap
or
the
scheduler
or
models
we
can
see
p2b
scheduler,
providing
lots
of
ad
region
and
a
lots
of
management
in
the
CDN
manager.
We
can
manage
an
image
cache
locally
and
the
transmission.
We
can
limit
the
rate
and
we
can
ensure
security
and
we
also
provide
the
pre
pre
feature
functionality,
tools
or
the
deployment
of
the
cloud
native
applications
in
the
file
manager.
Part
we
can
provide
the
functionality
of
GC
disk
and
also
an
interface
for
all
kinds
of
file
systems
to
catch
the
data.
D
D
If
the
image
is
does
not
exist
hounds
a
supernova
definitely
know
that
we
are
download
from
the
registry
to
catch
the
image
locally
at
the
fourth
pass,
as
you
can
know,
that
will
replies
and
knows
so
speeches
of
boughs
of
tears,
which
already
has
the
image
blocks
and
the
winds
of
feast
par
fifths
apart
sir-sir
proxy.
We
are
transpose
of
blocks
among
all
the
peers
network.
That's
a
master
step.
We
will
finish
the
whole
calling
with
all
blocks
downloaded
and
here's
a
graph.
D
Currently
we
are
very
happy
to
have
more
than
28
doctors,
not
only
in
China,
but
also
global
adopters,
like
la
vida
and
though,
with
the
ecosystem
building,
we
integrate
the
punch
container
and
darker
and
the
for
the
CNCs
part.
We
have
already
do.
Corporations
with
the
habit
project
have
a
projective
responsible
for
image,
storage,
other
images
assessments,
but
dragonfly
can
take
over
the
distribution
path
for
the
sea
of
CN
CF.
Also,
we
try
to
make
dragonfly.
It
should
be
deployed
by
fire
here
and
Lazarus.
Okay.
Next,
here
is
the
community.
D
Currently
we
have
to
solve
more
than
2,000
stars
and
we
provide
a
user
group
discussion
group
and
a
develop
discussion
prove
the
following
is
a
major
nerdy
cares
that
we
have
one
internal
team
in
Alibaba
and
we
are
very
happy
to
see
we
have.
We
have
already
one
outside
of
a
trainer
from
ebay,
china
via
they
are
also
a
total
of
dragonfly
Bulacan
contributor
side.
D
We
have
one
team
works
on
July
15,
some
some
some
engineers
are
part-time
and
we
have
also
another
full-time
engineer
which
is
focusing
on
the
open
source
outside
eBay
tuner
and
the
matron
companies.
They
are
very
active
beauteous
of
genuflect
projects
and
we've
already
won,
have
won
our
set
a
clatter
and
also
we
are
very
happy
to
see
toc
members,
the
sponsor
sees
project
dragonfly
to
the
same
box.
Okay.
D
Next
here
we
will
see
a
little
bit
about
the
dragonflies
blonde
man
as
November
this
year.
We
were,
we
will
make
Adam
fly
super
and
know
the
deployments
use
here
and
IDF
Kent
TF,
teaming
with
human
states
and
with
the
integration
with
hammer.
We
will
release
the
general
and
about
g8
version
before
November
this
year
and
before
in
the
later
2018,
we
were
my
ex
security.
D
A
lot
of
improvement,
support
supports
that
are
built
into
the
image
or
authentication
in
supernova
API,
and
we
will
also
support
different
encryption
encryption
algorithm
in
data
transmission
with
the
efficiency
patch.
We
will
definitely
improve
the
dynamic
reach
limiting
when
downloading,
and
we
also
to
provide
intelligent
scheduling,
algorithm,
improve
distribution
efficiency,
and
we
also
will
investigate
the
possibility
to
integrate
ipfs
openness
parts.
We
will
make
the
assignment
of
dragonfly
to
be
valuable.
D
We
try
to
make
dragonfly
in
the
cloud
native
production
wizard
scalable
component
and
makes
the
components
of
dragonfly
more
music
attic
customers.
Also,
we
will
try
to
reflect
the
super
node
in
column
to
attract
more
developers
with
the
stability.
We
will
simplify
the
complexity
and
we
sustainability.
We
will
class,
as
you
can
know,
that
it
to
decrease
the
possibility
of
panic,
and
what
do
we
want
from
the
field
year?
D
We
should
say
at
first
we
need
to
improve
the
improvements
of
the
dragonfly
and
step
tender.
We
once
the
CNCs
to
allow
more
people
more
doctors
to
use
dragonfly.
Then
we
can
attracted
more
active,
a
contributor
to
the
project
and
finally,
a
dragonfly
control
very
fiercely.
Okay,
that's
all
for
my
presentation
and
any
questions,
and
there
here
is
a
link
of
the
dragonfly
on
github
and.
E
D
A
D
D
Okay,
so
currently
we
can
support
all
kinds
of
containers
around
texts
we
can
integrate
it
with
dragonfly
wizard,
toxic
waste,
container,
D,
talker
and
and
and
the
launch
container
with
the
file
system.
Currently,
the
casted
imagery
is
only
supported
on
locally
local
local
storage
I
mean
the
future,
so
we
will
support
more
file
system
to
to
to
cast
the
image
in
supernova.
D
D
E
D
I
think
we
are
going
to
make
our
P
to
be
scary,
scheduling
at
reason,
mark
plat,
draggable
and
the
currently.
We
only
support
a
contact
protocol
which
is
or
implemented
by
Alibaba
I
think
this
is
more
may
tip
through
the
scenery's
we
met,
but
in
the
future
we
will
try
to
support
it.
Alright,
yeah
is.
C
C
D
C
C
C
D
A
G
Next
light,
yeah.
Thank
you
good
morning,
ladies
and
gentlemen.
In
the
next
10
to
15
minutes,
I
will
give
a
presentation
on
open
messaging
specification.
I'm
Jerry,
one
of
the
TSE
members
of
open,
messaging
and
and
I'm
really
sorry
to
tell
you
that
long
Gosselin
does
not
feel
well,
so
I
will
represent
him
to
report
today,
he's
sitting
next
to
me
anyway.
Now,
please
next
slide
good
morning.
Sorry,
it's
it's
quite
late
in
Beijing
now,
and
we
can
barely
keep
our
eyes
open.
G
So
if
there
is
panic,
it's
not
clear,
no
worries
we'll
follow
up
in
the
email
list.
For
you
later,
my
presentation
is
comprised
of
six
parts.
Well,
I
will
introduce
our
group
and
the
motivation
about
open
messaging
I
will
then
describe
of
the
messaging
open
standard
and
community
developed
development
in
details
and
the
last
two
parts
are
our
roadmap
and
future
plans.
G
You
know
rocky
MQ
robustly
provides
stable
infrastructure
with
the
with
the
transfer
through
food,
more
than
one
trillion
message
just
in
alibaba's
November,
11th,
Shopping
Festival,
and
has
also
been
widely
used.
Thousands
of
companies
outside
Alibaba
Group
until
now
rugged
MQ,
currently
has
more
than
5,000
stars
and
more
than
2,400,
Fox
and
github,
which
we
believe
is
a
heart
proof
of
our
capabilities
to
run
a
thriving
community.
Well,
in
the
past
10
years
we
have
focused
on
providing
messaging
services
to
traditional
users.
However,
there
are
increasing
demands
for
cloud
users
on
native
messaging
services.
G
Independent
standard
provides
industry
guidelines
for
areas
of
finance,
ecommerce,
IOT
and
big
data,
and
aims
to
develop
messaging
and
streaming
applications
across
heterogeneous
systems
and
platforms
well
compared
to
other
protocols
or
standard
like
XMPP
or
a
QP
or
MQTT
or
JMS,
etc.
Open
messaging
is
not
limited
to
Java
environment
and
wire
level
protocol
and
not
like
other
standards.
We
have
specified
guidelines
for
for
load
balance
for
tolerance,
administration,
security
and
straining
features
which
perfectly
support
the
need
of
modern
cloud
native
messaging
and
the
streaming
applications.
G
Next,
please
well
in
order
to
create
a
cloud
native
messaging
standard
and
reduce
developer
access
costs
over
messaging
has
several
spotlight
features,
as
shown
in
this
slide.
Well,
first,
open
messaging
not
only
provides
Al
and
a
large
range
of
supports,
including
finance,
ecommerce
in
IOT,
but
it's
also
programming,
language,
independent
and
secondly,
an
in
big
data
ecosystem.
G
The
nesting
also
provides
streaming
and
connecting
abilities
to
exchange
data
with
other
systems.
The
third
open
messaging
is
a
standard
for
cloud
native
applications.
We
define
a
specified
URL
access
to
the
cloud
vendors
and
a
low
specified
messaging
driver
and,
last
very
importantly,
open
messaging,
does
not
limit
the
implementation
of
vendors
but
provide
a
standard
benchmark
for
developers
to
evaluate
the
implementations
of
each
vendor
fairly.
G
Next,
please,
we
have
been
included
in
the
CN
CF
landscape
and
thank
you
very
much
for
appreciation
for
that,
and
we
sincerely
hope
that
we
can
work
together
to
create
a
more
perfect
ecology
with
a
CN
CF
hosted
project.
Next,
please
well
as
a
cloud
native
messaging
standard.
Open
messaging
is
not
only
a
very
useful
complement
for
the
ecology
obscene
CF,
but
we
can
easily
integrate
with
other
projects
already
in
the
CN
CF
as
well.
Well,
open
messaging
can
be
integrated
with
G
RPC
to
provide
asynchronous
support.
G
The
second
of
a
messaging
can
be
finded
to
cut
the
event
standardizing
all
events
in
contents,
as
well
as
transmission
processes.
Third
open
messaging
can
be
integrated
with
fluent
D
and
Prometheus,
as
as
a
connector.
The
finally
of
the
messaging
can
also
be
integrated
with
operator
to
make
useful
state
you
stateful
messaging
platforms
easier
to
manage
next
week.
G
The
messaging
domain
model
is
based
on
Q
model,
where
Q
lists
the
carrier
of
messages.
It
is
a
logical
destination
which
receives
messages
from
the
producer
and
then
transfers
to
the
consumer
is
not
worthy
that
a
Q
should
be
divided
into
partitions,
where
a
message
is
routed
to
a
specified
partition
by
an
asset
key
in
the
message.
Header
and
the
domain
model
also
supports
multi
operations.
A
message
can
be
routed
from
queue
to
another
kill
or
be
filtered.
G
Users
can
therefore
combine
various
operations
to
meet
various
scenarios,
such
as
a
group
subscription
map
sending
and
so
on.
Moreover,
open
messaging
supports,
pool
and
push
model
consumers,
so
it
can
be
easily
integrated
to
streaming
solutions
next,
please
well.
This
slide
describes
our
core
contribution.
The
open
messaging
specification
I
think
which,
which
is
also
the
essential
value
of
this
project,
open
methods
in
specification,
is
derived
from
the
abstraction
of
the
domain
model.
G
In
the
previous
slide,
in
which
the
schema
is
used
to
describe
the
domain
model
of
the
message,
it
contains
not
just
the
data
but
the
common
metadata
of
a
message
as
well.
In
the
meantime,
it's
not
aware
why
level
protocol,
therefore
it
is
no
limitation
at
all
for
vendors
realizations
or
the
messaging
also
provides
an
optional
runtime
interface
for
binding
these
schemas
to
implementations,
I
think
it's
the
first
and
very
important
step
towards
portability
of
a
union
message
platform.
G
Next,
please,
in
on
this
slide,
I
will
introduce
our
community.
Well.
This
page
page
shows
the
operational
data
for
our
communities.
So
far
we
have
released
the
1.0.0
preview
version
and
have
already
got
more
than
500
stars
and
160
folks
on
github.
Our
group
is
currently
composed
of
70
se,
members
from
4
organizations,
9
maintainer
from
6
organizations
and
15
community
enthusiasts,
who
are
constantly
contributing
to
us
up
to
now.
6
versions
have
been
released
and
more
than
600
commits
have
been
made.
G
Next,
please,
our
founding
members
include
companies
in
organizations
from
a
variety
of
industries.
Alibaba
is
a
Chinese
company
that
provides
c2c,
b2c
and
b2b
e-commerce
services,
as
well
as
cloud
services.
Yahoo
is
globally
known
for
its
search
engine
and
related
services.
Deedee
is
one
of
the
largest
right
sharing
companies
in
the
world,
providing
transportation
services
for
more
than
four
hundred
million
users
in
China,
and
we
Bank
is
China's.
First
private
commercial
bank
established
one
of
its
major
shareholders
is
tension.
G
The
last
to
stream
stream
leo,
and
the
data
pipeline
are
two
startup
companies
that
concentrate
on
Big,
Data
and
streaming
solutions.
Next,
please,
we
also
got
Universal
supports
from
commercial
and
open
source
vendors,
where
Alibaba
cloud
tens
in
cloud
out
rocky
MQ,
Ramy,
MQ
and
Natasha
have
already
confirmed
their
contribution.
Villainess
AWS,
Asia,
Google,
Kafka
Nats,
have
also
shown
great
interests.
Our
current
open
messaging
solution
has
already
been
commercialized
over
Alibaba
cloud,
and
it
has
a
yearly
revenue
of
more
than
15
million
u.s.
dollars.
G
G
Okay,
next,
please
an
X,
please
yeah!
Thank
you.
Our
roadmap
is
divided
into
four
phases,
and
currently
we
have
released
do
1.1,
1.0.0
preview
version.
We
really
hope
to
get
support
from
CN,
CF
and
major
popular
messaging
platforms,
and
then
we
will
try
to
integrate
with
copy
events
in
place,
for
we
will
focus
on
ecosystem
building,
providing
open,
connector
and
straining
specification
next,
please,
and
in
the
last
part,
I
will
introduce
our
vision
in
a
future.
G
Next,
please,
and
in
the
future,
we
also
hope
to
fully
commercialize
of
a
messaging
over
major
calendars
to
make
open
messaging
a
common
messaging
standard
like
Alibaba
clouds,
AWS,
Asia,
etc.
Ensuring
that
users
have
a
friendly
connection,
specifications
of
every
cloud
service
providers
next
phase.
G
But
that's
all
my
report
about
open
messaging
in
the
right
corner
is
our
Twitter
QR
code
and
our
official
website
is
open
messaging
duck
cloud.
We've
been
working
very
hard
to
participate
in
the
cause
of
CN
CF
and
the
Lynx
foundation
in
China
we
became
Platinum
Member
of
since
EF
last
year
and
become
the
top-level
sponsor
of
lc3
and
the
Cooper
Kong
in
Beijing
and
Shanghai
respectively.
The
two
flagship
events
for
Linux
Foundation
and
the
scenes
have
held
in
China
this
year.
G
B
I
had
one
it's
Quinton
here:
could
you
just
clarify
at
what
level
the
standard
is
so
you
mentioned.
This
is
not
a
wire
protocol
standard
and
it's
also
multilanguage.
So
it's
not
entirely
clear
to
me
for
someone
wanted
to
implement
this.
Well,
what
exactly
is
the
standard
that
they
have
access
to?
Where
does
that
fit
in
a
stack
yeah.
H
He
has
remembers
about
the
messaging
and
I
will
require
him
to
answer
his
question.
An
open
messaging
is
a
application
standard.
Others
came
up
and
the
it's
a
specification
for
users.
It's
about
a
met,
it's
about
him
and
the
user
succumb
pending
with
open
messaging,
Rand
Paul
in
transporter
all
cable
Samuel.
All
we.
We
also
also
made
a
song.
We
prosper,
we
will.
We
also
provide
some
interface.
H
C
I
have
a
related
question:
I
mean
I,
might
guess
that
it's
similar
to
cloud
events
and
that
the
common
metadata
properties
could
be
represented
in
multiple
data
encoding
formats.
How
similar
or
dissimilar
is
this
from
cloud
events
since
I
saw
a
cloud
events
was
supported
cloud
events
or
vice
versa,
or
something.
H
H
C
H
P.M.
team
members
and
working
on
queue
is
a
implementation
of
a
messaging,
an
open
messaging
and
the
user.
Last
user
Nestor
warning
of
locator
can
program
q5.
We
will
support
her.
We
only
come
full
supporter
of
messaging,
but
a
user
in
the
category
of
working
on
Q.
We
have
a
peer
implement
to
the
0:03
worry
of
the
messaging
and
you
can
founder
some
implementation.
You
may
our
github.
C
H
H
C
C
H
C
Yahoo
from
Google
have,
you
is
involved
with
this
since
they
were
mentioned,
so
I
can
follow
up
with
them.
So,
even
if
you
know
sorry
please,
it
was
mentioned
that
Google
Cloud
was
expressed.
Interest.
I
was
wondering
if
there
was
specific
people
that
I
could,
whether
you
were
aware
of
who
those
people
were.
We.
H
Asked
you
computing
with
Google
cloud
leader
and
I
have
a
Saba
leader
to
make
her
a
ProQuest
fall
legal
progressed
of
all
the
integrator
being
Google
cloud
platform,
but
Google
column.
How
the
platform's
do
evaluating
our
project
and
I
think
if
we
can
evolve
lovely
UCSF
we
can.
We
can
make
a
poodle
collaborate
in
the
future.
Okay.
H
Yeah,
our
our
messaging
standard
in
Orrantia
is
a
cloud
of
native
originated
and,
if
you
can
find
another
Lauren,
lasered
exam,
PPO,
AMQP
or
other
imputed
here
on
summer,
implementation
of
Kafka
of
RabbitMQ
didn't
support
her
Carol
to
cloud
and
eat
him.
How
the
media
move
in
a
modern
cabinet
here
period.
They
cannot
provide
a
flea.
H
They
cannot
make
the
user
access
to
eight
without
her
Perry
and
the
cloud
and
open
messaging.
If
an
specify
a
URL
to
assess
re
cloud.
The
winners
and
the
universe
can
because,
as
open
as
open
that
you
know
using
our
messaging
having
easily
focus
a
pseudo
besides,
Lucas
eyes
are
very
clouded
plentiful
and
we
are
will
be
messing
in
a
cloud
or
a
theater
standard.
A
A
So
moving
on
just
kind
of
standard
links
to
our
project
review,
/
backlog
moving
to
the
next
slide,
big
events
coming
up,
hopefully
we'll
see
many
of
your
shiny
faces
in
Shanghai
on
November
14th
through
15th
for
Q
Khan
China.
It's
our
first
event
there.
So
we're
super
stoked
about
that.
And
of
course
we
have
our
flagship
event
in
North
America
in
Seattle,
December,
11,
13th,
13th
and
then
Europe
next
year,
May
21st
through
23rd,
so
moving
on
slide.
A
Oh
this
needs
to
be
updated,
but
our
next
meeting
will
be
the
18th
and
we'll
be
hearing
from
the
net
data
project.
So
next
slide.
Thank
you
very
much,
and
hopefully
everyone
has
a
good
Tuesday
and
thank
you
again
to
our
community
presenters
from
China
who
definitely
were
staying
up
late,
so
I
appreciate
the
time
and
we'll
try
to
do
better
on
time
zones
in
the
future.
So
thank
you.
Alan
de
Bono
and
Jerry
Oh
take
care
of
one
Chris.