►
From YouTube: wasmCloud: Bindle Support Demo, WASI-NN + Machine Learning Demo, Community Callout! - 01/05/2022
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
A
B
Yeah
sure,
hey
guys,
I'm
matt
wilkinson
I've
been
working
on
wash
a
little
bit
updating
some
of
the
the
json
outputs
and
the
tests
and
kind
of
doing
some
refactors
on
that.
I
got
involved
in
wasm
cloud
just
from
seeing
you
guys
on
twitter,
and
I
thought
the
project
was
really
cool,
so
I'm
glad
to
to
contribute-
and
hopefully
you
know
be
a
part
of
this
awesome
project
thanks.
A
C
Sure
my
name
is
jingan,
I'm
based
in
toronto,
and
I've
been
actively
being
involved
into
the
past
platform,
development,
work
and
the
architecture.
So,
while
exploring
new
technologies,
what's
going
to
be
the
next
thing
for
our
product,
we
think
about
them
might
be
a
good
fit
into
our.
You
know
big
product
portfolio,
so
welcome
cloud.
Definitely
already.
You
know
made
some
progress
by
encapsulating
some
comments
and
solving
some
cross
cross
cutting
concerns
so
something
we
want
to
explore
further
yeah.
D
Yeah
shuchi
wang
yeah,
my
name
is
shuchiwang
and
yeah
me
and
jinger
from
same
company
and
he's
my
supervisor
and
we're
working
on
the
same
project
and
currently
I'm
I've
been
I've
been
investigating
a
web
assembly
for
quite
a
long
time,
and
I
recently
I
got
to
know
the
awesome
cloud
and
I
tried
it
out
the
demo
and
which
is
really
amazing,
and
so
I
want
to
dig
it
out.
So
that's
why
I
came
here
to
participate.
This
meeting
yeah.
E
You
hear
me:
okay,
cool
yeah.
My
name
is
connor
smith.
I
just
joined
cosmonic
last
week,
I'm
kind
of
new
to
the
cloud
native
space,
but
I'm
learning
a
lot,
I'm
very,
very
excited
by
this
tech
in
a
way
that
I
haven't
felt
in
a
long
time.
So
everything
I'm
seeing
from
the
community
is
super
exciting
and
I'm
just
very
enthusiastic
about
learning
more.
A
Great
and
we
like
to
start
our
meetings
off
with
a
demo,
and
today's
demo
is
going
to
be
taylor,
taylor,
take
it
over
sweet,
we'll,
go
ahead
and
share
the
screen
which,
for
the
you
long
time,
watchers
of
this
meeting
is
a
is
a
miracle
so
and
let's
go
ahead
and
share
this
okay,
you
should
all
see
the
wasmcloud
dashboard.
The
washboard
is
that
correct,
sweet?
A
A
Now
before
I
go
in
just
the
boring
part
is
just
making
sure
people
know
what
bundles
are
so
bindle
is
a
project
which
I'm
a
maintainer
on
as
well,
which
kind
of
explains
why
this
got
added,
but
we're
all
friends
here,
but
also
there
is
a.
There
are
good
reasons
why
we
want
to
do
this.
This
isn't
just
some
some
pet
project
or
thing
that
we
want
to
try
out.
A
So
bindle
is
a
new
object,
storage
format
that
is
specifically
meant
to
be
used
for
webassembly
and
for
anything
that
where
you
have
like
a
collection
of
various
parts
of
an
application
together,
so
we
call
aggregate
object,
storage.
The
you
can
read
tons
of
information
here
about
the
data.
Bindle
is
both
a
spec
and
we
have
the
reference
implementation
here
in
rest
and
bindle.
We
we
use
a
silverware
drawer
to
describe
it.
So
when
you
have,
if
you
have
a
silverware
drawer,
you
have
multiple
things
there.
A
A
If
you're
eating
a
fancy
dinner,
you
might
need
those
small
little
soup
spoons
that
you
never
do
and
the
chilled
salad,
forks
and
the
and
the
knife
and
the
second
knife
and
the
you
know
all
these
different
things
that
you
need
for
a
more
fancy
occasion,
but
they're
all
stored
in
the
same
place
and
web
assembly
allows
you
to
to
do
that
by
composing.
Different
parts
of
an
application,
and
so
bindle
is,
is
likely
to
become
a
a
good
possibility
for
being
like
the
storage
format
for
webassembly.
So
we've
added
experimental
support
to
it.
A
To
wasn't
cloud
for
bundle.
You
can
actually
find
all
the
documentation
here
now.
I
will
very
very
sorry:
it's
not
merged
yet,
but
the
documentation
will
be
available
on
here.
If
you
want
to
try
it
out,
it's
it's
open
on
a
pr
on
the
docs
repo,
and
it
is
very,
very
alpha
right
now
we
don't
have
any
support
inside
of
wash
yet
for
automatically
creating
a
bundle,
so
you'll
have
to
you'll
have
to
manually
assemble
a
bundle,
but
right
now
this
provides
probably
the
biggest
benefit
right.
A
Bindle
allows
you
to
select
based
on
your
os
and
features
and
download
only
the
stuff
you
need,
and
so
I've
actually
just
created
a
simple
example,
using
a
bundle
server
that
I'm
running
locally
and
then
pointing
it
at
and
then
having
it,
the
echo
actor
and
the
watson
cloud
http
provider
all
together.
So
I'm
just
going
to
show
that
working
here,
so
I'm
going
to
do
it
from
a
registry.
A
So
right
here
we
have
you'll,
see
this
coming
from
bendel
to
use
it
to
use
experimental
bundle,
support
you
just
have
to
preface
it
with
the
bindle
like
protocol,
and
then
this
is
the
bundle
id
and
so
then
we
go
ahead
and
we
submit
this
and
it
will
go
ahead
and
load
it
straight
from
there.
I
actually
cleared
all
my
caches,
so
you
can
see
how
fast
this
is.
A
Yes,
I'm
running
from
localhost,
I'm
not
pulling
across
a
network
but
you're
just
going
to
see
how
fast
each
of
these
go
in
comparison
to
loading,
a
provider
from
a
registry,
the
old
way
and
then
we'll
go
ahead
and
do
bundle
for
the
http
server
and
you'll
see
bam
instant
because
it
only
had
to
download
the
one
binary
and
actually
need
it
actually
needed.
Once
again.
This
is
a
local
network,
so
it's
going
to
run
even
it's
running
faster
but
like
even
with
a
local
one.
A
A
So
there
you
go
pretty
simple
and
straightforward:
we're
planning
on
adding
more
support
for
this
and
having
it
be
something
there's
an
open,
an
open
issue
for
this
in
the
in
the
wasm
cloud,
repo
about
adding
in
support
for
bundle
by
default,
bundles
as
actors,
so
that
this
can
just
be
run
by
default.
So
you
don't
have
to
be
dependent
on
an
oci
registry
and
it's
using
a
storage
format,
that's
more
suited
for
the
type
of
work
we
do
inside
of
webassembly.
A
Taylor
upstream
bundle
servers
are
still
something
separate
that
you
have
to
run
right.
It's
not
compatible
with
like
an
existing
ocr
registry
yeah.
It's
it's
not
currently
compatible
with
it.
There's
I'm
sure
that
people
could
write
an
oci
shim
for
it,
as
as
it
gains
traction
and
we
we
solidify
some
of
the
parts
of
the
spec,
but
the
idea
is
for
it
to
be
kind
of
a
net
new
thing.
The
you
can
read
a
lot
of
the
justification
in
the
initial
readme
for
bindle
about
why
we
did
that.
A
But
oci
is
just
not
a
good
storage
format
for
generic
things.
It's
great
for
images,
it's
just
not
really
great
for
storing
generic
things
and
we've
been
trying
to
shove
all
sorts
of
data
in
there,
and
this
is
a
much
better
way
of
of
representing
an
application
as
a
whole,
so
like
in
in
general,
like
just
to
get
to
for
people
who
might
be
new
to
this
and
are
not
are
new
to
wasm
cloud
and
probably
come
from
kubernetes
or
docker
land.
A
Ca
is
just
out
of
curiosity.
Is
our
artifact
hub,
oci
artifact
hub
is
artifact
hub,
isn't
a
conglomeration
of
of
different
sources,
because
if
I
remember
artifact
hub
also
has
helm,
charts
and
other
things
in
there,
and
so
it's
it's
more
of
a
a
directory
of
where
you
can
find
things
it.
Some
of
them
are
images.
Some
of
them
are
helm
charts.
Some
of
them
are
artifacts
and
it
just
depends
so
yeah.
A
That's
that's
a
different
sort
of
thing,
because
it's
not
backed
by
a
single
store,
it's
more
of
a
directory,
got
it
and
matt
glad
to
see
you're
on
that's
exactly.
What
I
was
thinking
was.
Is
it
worthwhile
for
us
to
talk
to
the
artifact
hub
team
about
adding
bundle,
support
matt
you
want
to
share.
You
want
to
hop
on
share
your
experience.
F
Sorry,
I'm
not
where
I
can
talk
yet
there
we
go
yeah.
So
I
did
talk
to
the
artifact
hub
team
about
this
about
three
weeks
ago,
because
matt
farina
who's,
one
of
the
leads
on
that
was
asking
whether
bindle
is
at
the
point
where
they
would
be
able
to
add
support.
So
they
are
talking
about
it
and
basically
the
idea
is
they
would
ingest
the
invoice.tamil
file
and
be
able
to
provide
all
the
metadata
that
you
would
need
in
artifact
hub
to
search
for
bindles
and
and
find
the
source
of
them.
F
A
G
Yeah,
let
me
go
ahead
and
share
my
screen.
Okay,
you
should
be
able
to
see
github,
so
the
community
call
out
not
everybody
who's
on.
This
call
may
have
seen
it
yet,
but
this
is
something
that
I
like
to
do.
Try
to
do
it
every
week
with
a
couple
of
issues
that
we
have
in
our
org
they're
in
a
marked
as
good
first
issue.
G
So
first
issue
is
in
wash.
This
is
something
that
taylor
filed
a
little
while
ago,
when
you
generate
a
key
using
wash
key
gin.
It
just
writes
to
the
file
system
with
a
permission
of
644.
like
this
is
something
that
happens
automatically
when
you're
signing
an
actor.
We
put
it
near,
like
tilde
or
home
dot,
wash
slash
keys.
G
So,
ideally
because
these
keys
are
at
least
the
private
key
part,
the
the
seed
part
is
a
sensitive
information.
This
should
be
something
that
can
be
you
know,
read
by
the
current
user,
but
not
written
to
not
executed,
etc.
So
the
real
goal
of
this
issue
is
just
to
change
the
permissions
of
the
key,
this
written
disk,
so
if
you're
interested
in
security
or
want
to
contribute
to
watch
for
the
first
time.
This
is
a
great
point
to
chime
in
now.
G
G
This
good
first
issue
is
getting
the
file
system
capability
provider
that
we
wrote
for
pre-otp
or
wasn't
cloud
0.18
importing
that
to
the
some
of
the
new
tooling,
with
smithy
interfaces
and
the
otp
runtime.
Now
the
reason
why
I
picked
this
is,
with
the
with
the
wasmcloud
blob
store
interface
that
we
have
already
written.
G
We
wrote
a
capability
provider
to
access
the
file
system
and
just
as
a
proof
concept,
we
also
wrote
one
for
aws
s3,
which
you
know,
acts
as
a
blob
store
and
accessing
the
file
system
with
actors,
isn't
something
that
happens
all
the
time
for
for
wasm
cloud
applications,
because
the
nature
of
being
fully
distributed.
You
don't
always
know
if
something's
going
to
be
on
the
local
file
system,
but
this
is
something
that's
really
great
for
doing
local
demos,
doing
proof
of
concept
things.
G
So
if
you
have
any
experience
in
rust
or
have
been
looking
to
dive
into
writing
a
capability
provider,
this
is
something
that
all
the
resources
are
available
for
you.
We
have
our
previous
file
system
provider,
we
have
wash
new
provider
which
will
generate
and
scaffold
a
provider
project
for
you
and
we
have
pretty
extensive
documentation
on
creating
a
new
provider.
So
this
would
be
a
great
place
to
dive
in.
If
you're
looking
to
write
a
capability
provider.
G
So
I
guess
just
to
to
wrap
this
up.
These
are
our
two
community
call
outs
if
you're
interested
in
taking
either
of
these.
Please
just
drop
a
comment
on
the
issue
with
any
questions
that
you
have
any
anything
really
in
general,
wouldn't
want
you
to
start
working
on
this
and
then
find
out
that
somebody
else
has
already
taken
it
and
is
already
submitting
a
pr
and
we'll
be
happy
to
go
back
and
forth.
We
also
have
a
a
help
channel
in
our
community
slack.
G
G
G
I
was
like:
okay,
like
I'll,
take
a
look
at
it
right
when
I
get
back,
but
I
finally
got
around
to
looking
at
it-
and
this
is
this
is
pretty
awesome
to
give
like
a-
I
guess-
a
tldr
he's
kind
of
gone
through
and
refactored,
essentially,
all
of
the
places
where
we
return
output
for
the
wash
command
line
into
a
new
struct
called
command
output.
I
think
let
me
find
it
yeah
command
output
and
I
won't
go
super
far
into
the
implementation.
G
G
If
you're
trying
to
script
with
wash
and
in
a
lot
of
places,
we
were
correctly
returning,
json
output
for
successful
commands,
we'd
get
you
know,
here's
your
host,
here's
the
host
inventory
or
something
it
wasn't
pretty
like
it
wasn't
pretty
printed
or
anything
like
that,
but
it
would
output
to
the
command
line.
You
could
pipe
it
into
jq.
Do
all
your
scripting
all
that
stuff,
but
a
lot
of
the
times
when
something
failed.
G
We
would
just
dump
that
error
straight
into
the
command
line,
and
so
you
know
two
of
the
biggest
things
that
have
happened
as
a
part
of
this
pr.
Are
you
know
ensuring
that
pretty
much
everything
unless
there's
a
panic
which
there's
not
really
a
foolproof
way
to
handle
and
rust,
like
even
trying
to
catch
and
unwind,
doesn't
always
work
errors
and
successful
output?
G
When
you
do,
json
will
give
you
a
nice
pretty
printed,
formatted
json
output,
so
this
really
improves
the
ability
for
wash
to
be
scripted,
and
the
only
other
thing
that
I
want
to
say
before
I
give
matt
a
chance.
Is
that
some
of
the
best
contributions
to
wasn't
cloud
are
the
ones
that
add
all
these
new
features
and
take
away
code?
It's
pretty
neat.
G
There
was
all
this
like
copy
pasting
of
the
output
struct
like
whether
it's
text
or
json
and
and
matt,
was
able
to
kind
of
pull
this
up
and
remove
a
lot
of
duplication.
So
just
wanted
to
call
this
out,
because
this
was
super
awesome
and
I
think
it's
a
really
elegant
solution
to
a
problem
we
were
having
so
matt.
I
don't
know
if
you
want
to
you
want
to
say
anything.
This
is
still
kind
of
in
in
review
I've,
given
it
a
once-over
and
everything
is
good.
G
We'll
get
one
more
review
on
this,
and
since
this
is
kind
of
a
it's
not
techn,
I
mean
I
don't
know
it
is
a
breaking
change.
It's
going
to
change
the
way
that
the
output
is
formatted.
So
all
this
stuff
is
going
to
come
out
and
wash,
I
think,
0.8,
which
this
is
cool
enough-
that
we'll
probably
try
to
release
that
pretty
soon
after.
B
Yeah,
the
only
thing
that
I
had
is
that
I
also
changed
all
the
errors
to
use
anyhow,
which
is
an
error
error,
crate
commonly
used
in
a
lot
of
different
rust
projects.
This
makes
it
really
easy
to,
you
know,
add
context
to
errors,
so
something
that
should
make
it
easier
for
people
when
they
want
to
add
new
features
later
to
wash
to
easily
pass
up
their
errors
to
the
using
the
question
mark
operator
up
to
the
command.
A
Great
contribution
and
matt
we've
not
forgotten
about
the
new
contributor
t-shirts,
we're
still
finalizing
some
design
before
we
get
it
shipped
out.
We
want
it
to
be
something
that
you
know
is
like.
You
know
just
embraces
those
folks
that
have
taken
the
time
to
invest
in
the
community
and
done
contributions.
So
we
will
get
those
published
in
you
know
men's,
and
women's
t-shirt
here
shortly.
A
So
please
watch
for
that.
We
will
shout
out
loud
and
proud
to
get
that
out
there
and
then
we'll
be
sending
out
invitations
for
the
program
committee.
We
are
trying
to
focus
the
program
committee,
try
somewhat
central
around
european
participants
for
this
one
and
as
always,
we're
gonna
try
to
pull
in
another
diverse
group
of
stakeholders
to
ensure
that
we
continue
to
build
a
diverse
community
for
cloud-native
wasm
day.
A
If
you
haven't
gotten
your
copy
yet
I
suggest
you
not
only
order
it
and
when
you
do,
I
suggest
you
turn
right
to
page
286
258
for
the
wonderful
section
on
wasmcloud
here.
Actually,
the
book
is
phenomenal.
I've
been
going
through
it
brian.
I
know
you
really
worked
your
butt
off
on
this,
and
I
think
this
is
just
an
absolutely
epic
contribution
to
the
space
and
to
the
community
and
a
huge
round
of
applause
for
you.
Thank.
I
Mostly
extremely
positive,
the
first
review
on
amazon
was
one
of
these.
You
know
it's
not
what
I
wanted.
Therefore,
it
sucks
kind
of
reviews
which
was
a
drag,
but
everything
else
since
then
has
been
extremely
positive,
and
you
know
jay
phelps,
read
it
and
said
what
you
attempted
to
do
was
like
really
hard,
and
I
think
he
pulled
it
off.
So
that
was
that
was
meaningful.
I
People
like
brooks
have
given
me
good
feedback
on
it
as
well,
so
I
it
was
just
trying
to
target
people
who
were
new
to
it.
People
who've
done
it
for
a
while
people,
who've
only
done
javascript
people
who
are
coming
to
it
from
rust
and
c
plus
plus,
but
I
did
want
to
tell
the
big
story-
and
you
know
highlighted
that
there
have
been
fantastic
sort
of
focused
stories
like
kevin's
book
so
far,
and
I
didn't
try
to
like
redo
stuff.
I
A
You
and
I'm
glad
to
hear
that
you're
you're
enjoying
it
well.
I
will
get
my
review
published
on
amazon
shortly.
I
honestly
wanted
to
take
some
time
and
make
sure
I'd
worked
through
it.
So
it
was
like
an
honest
review
and
not
just
like
say,
you're
amazing,
which
I
know
you
are
anyway
and
and
go
from
there.
So
real
quick,
just
open
floor,
any
other
community
call
outs
or
anything
else
happening
around
the
broader
community.
A
So
if
you
are
on
the
wasn't
cloud
slack
already,
there's
a
new
machine
learning
channel,
it's
wide
open,
anyone's
free
to
join
and
just
watch
for
us
to
start
sharing
some
of
the
early
sketch
and
project
work
in
that
in
that
folder
and
we've
kind
of
outlined
a
plan.
Unfortunately,
the
team
member,
the
community
member,
that's
working
on
that
is
european-based
and
they
don't
have
a
a
good
fit
for
joining
us
on
the
meetings.
A
So
we
can
put
it
at
least
up
on
our
youtube
channel
to
share
some
of
the
work
that
it's
going
there,
but
we'll
take
our
sort
of
private
sketch
that
we've
done
and
we'll
roll
that
out,
maybe
as
an
rfc
or
as
a
couple
of
issues
on
github,
just
to
make
sure
that
we
engage
and
get
the
feedback
and
input
from
everybody
across
the
feedback
and
andrew.
I
know
that
I
pinged
you
privately
and
thank
you
for
showing
up
today.
H
A
A
J
Well,
I
wasn't
on
sabbatical,
but
I
was
on
a
boat
for
two
weeks,
so
I'm
kind
of
getting
back
to
things.
So
I
I
haven't
been
working
on
it
in
the
new
year,
but
I
do
plan
on
diving
in
I
saw
there
was
one
question
when
I
was
out
about
the
developer
experience
where,
when
you're
working
in
an
individual
actor
where
you're
writing
the
query,
you're
not
able
to
use
things
that
would
at
compile
time,
tell
you
if
the
scheme
has
changed,
and
that
is
one
bit
of
friction
that
I've
run
into.
J
I
was
interested
in
stuart's
perspective
on
on
that
answer,
but
one
wacko
idea
I
had
was
having
a
concept
of
export
on
a
capability
provider
export
what
you
need
and
then
at
compile
time
use
that
in
your
test,
but
not
at
runtime,
so
that
you
can
have
all
the
same
capability
contracts
that
capability
providers
have
through
the
link,
but
having
a
way
at
compile
time
to
kind
of
bypass
that
so
that
you
can
have
tests
that
give
you
a
better
developer
experience,
but
I
haven't.
I
haven't
posted
that
anywhere
in
github
or
anything
that
was.
J
A
I
don't
see
things
steve
steve's
not
on
today
is
he
I
would
actually
stuart.
I
think
you
would
probably
have
a
good
opinion
on
this
as
well.
You
know,
given
the
epic
wasm
day,
talk
that
you
guys
gave
at
kubecon
us.
I
know
you
guys
are
doing
some
really
cool
things.
A
stewart's
team
was
the
red
badger
team
that
did
the
helping
a
large
european
financial
re-platform
on
declarative.
Multi-Cloud
wasn't
cloud
something
something
on
kubernetes
it
was.
It
was
like
the
longest
world's
longest
title.