►
From YouTube: wasmCloud Community Meeting - 24 May 2023
Description
Welcome to the wasmCloud community! Tune in live where we discuss the latest developments in the wasmCloud ecosystem, WebAssembly standards, and break out sweet demos.
Agendas for wasmCloud community meetings can be found at: https://wasmcloud.com/community
A
Foreign
welcome
everybody.
We've
got
a
pretty
short
agenda
today.
I'll
share
our
agenda
over
here
in
Arc.
A
So
we've
got
an
update
from
wadam
from
Taylor
I'll
go
over
some
of
the
RFC
new
RFC
that
we
got
in
from
Kevin,
and
you
know
like
we
usually
do.
We
talk
a
little
bit
about
what's
happening
in
the
broader
Watson
community,
so
Taylor
hey
you're
up
first,
would
you
like
to
share
your
screen
if
you're
able
to.
B
I
should
be
able
to
I
was
just
making
sure
I
spun
everything
up.
Let
me
Fairway,
oh
Liam
I
require
sharing
powers
or
Bailey
I'm,
not
sure
who
asked
you.
Oh
excellent.
Okay,.
B
Let's
go
ahead
and
chair
the
desktop
there.
We
go
okay,
so
what
I
just
did
here
we'll
see
if
this
actually
works
at
the
very
minimum
I
can
show
you
in
the
terminal.
I
cannot.
B
Show
you
in
the
washboard
okay,
so
I'm
gonna
go
ahead
and
go
to
localhost
4000
excellent,
okay,
I.
C
B
I
have
a
I'm
using
the
docker
compose
file
we
use
for
our
ed
test.
So
this
is
five
five
different
like
hosts
that
are
running
as
part
of
a
single
lattice
you'll,
see
that
this
one's
on
the
moon
and
I
can
do
like
ones
in
the
US
Taylor
West
anyway.
So
we
have
that
all
running
and
I'm
gonna
go
ahead
and
go
back
over
here
and
we
have
a
EB
copy.
I'm.
Sorry
right.
C
B
So
this
is
the
the
Manifest
that
we're
doing
so.
This
is
just
like
a
simple
manifest
that
runs
four
replicas
wherever
we
want
and
actually
I'm
gonna,
just
I'm
gonna
go
Bolder
and
try
to
run
it
everywhere.
So
let's
do
we'll
run
it
across
all
hosts.
B
B
Like
I
have
my
name:
I
have
the
names
of
the
components
I'm
running
what
image
it
is
and
then
I
can
say
like
I'm
running
five
of
them
and
they're
going
to
be
balanced
across
two
on
the
East
Coast,
two
on
the
west
coast
and
two
on
the
moon,
and
then
we
have
the
linked
F4
it
and
then
we're
going
to
run
a
HTTP
server
on
every
single
one
of
the
hosts.
B
So
that's
all
that's
all
running
there
and
yeah.
So
we
ran
this
in
the
meritranquilitatis
that
one,
the
Tranquility
C,
that
is
the
region
on
the
moon,
we're
running
uncon,
and
so
let's
go
ahead
and
get
this
started
first
things
first,
we're
gonna
run
with
am.
B
This
is
just
a
big
long
thing,
so
I
have
all
the
logs
if
something
goes
wrong
and
we're
just
running
it
just
with
some
simple
Flags.
This
is
basically
no
configuration
so
I'm
going
to
run
this
and
then
I'll,
actually
just
for
the
fun
of
it
also
run
a
second
one.
B
Just
so
you
guys
can
see
that
this
is
really
easy
to
run
distributed
so
I'm
just
going
to
do
the
same
one
I'm
going
to
get
a
second
host
ID
we're
going
to
use
that
for
some
logging
stuff
in
the
future,
and
it
just
gives
a
unique
ID
so
now,
I'm
running
a
second
one,
you'll
see
I
didn't
have
to
provide
any
additional
configuration
as
soon
as
it
gets
started.
It's
still
building,
of
course,
why
it's
taking
so
long,
but
it's
building.
B
Sorry
I
literally
had
just
built
this,
but
apparently
okay,
there
we
go
so
now.
Let's
all
started
up:
we
have
them
both
running
no
extra
configuration
added.
If
you
haven't
seen
Madame
before
it's
able
to
do
this,
you're
able
to
run
it.
However
much
you
want
and
then
we'll
come
over
here
and
make
sure
I
still
have
that
in
my
buffer
and
I'm
going
to
sew
the
thing,
that's
correct
and
I'm
going
to
go
ahead
and
put
it
so.
A
B
Okay,
we're
going
to
deploy
it.
It's
deploy
the
model,
we
can
go
back
and
we'll
see
a
bunch
of
things
like
starting
to
pop
up
on
the
on
the
thing
here
and
we'll
give
it
a
second,
because
it's
probably
going
to
try
to
set
everything
up
and
I'm,
taking
a
risk
running
this,
because
I
haven't
fully
tested
this
this
scenario
yet
but
we'll
see
if
everything
shows
up
so
am
I,
know
it's
going
to
take
a
second
for
providers.
A
I
mean
we
were
pretty
sure
that
it's
like
the
Azure
Registries
says
if
Taylor
yeah.
B
That's
what
we
personally
think,
but
anyway,
actors,
though,
should
be
starting
here
if
I
just
I
could
have
also
been
missing.
Something.
A
And
this
is
especially
great
because
I
know
you
were
just
debugging,
something
like.
B
Okay,
so
that
should
deploy
somewhere
I
just
don't
know
where,
because
I
didn't
specify
a
host,
it
also
could
be
there.
We
go
okay,
so
this
is
spinning
up.
Don't
ask
me
why
the
washboard's
giving
me
bad
information
here,
but
we
can
see
that
it's
spun
up
like
five
actors
on
on
us,
Brooks
East
over
here
for
me
and
eventually
the
provider
will
start
I
would
have
to
sit
around
here
for
another
minute
or
two
until
I
solve
what
the
heck's
going
on
with
my
internet
connection
and
Azure
registry.
B
But
oh,
hey
perfect!
It's
like
it
heard
me.
So
there
is
the
provider
and
the
link
definition
for
it.
So
it
just
all
popped
up
and
we
might
actually
start
seeing
the
other
ones
pop
up
too
we'll
see
if
they've
yeah
we
can
see
at
least
the
the
provider
on
every
single
host
and
we
have
the
five
of
them
running
there
yeah
it
looks
like
so
yeah
there's.
It
looks
like
there
is
an
issue
and
it
spreads
it
across
it.
B
B
So
now,
if
I
set
this
to
like
two,
it
probably
probably
won't
even
have
time
to
to
do,
or
it
might
actually
reschedule
it
to
other.
Oh,
no.
There
goes
bam
right
up
to
four.
So.
A
B
No
Jitter
it
gets
to
exactly
where
it
needs
to
go,
and
does
it
pretty
quickly
so
anyway,
the
update
here
is:
we
have
one
task
left
and
it's
just
a
minor
thing:
that's
going
to
make
it
so
the
logs
are
less
noisy
and
there's
there's
less
spamminess
going
on
it's
pretty
spammy
when
it
doesn't
when
we
don't
do
what
I'm
about
to
change
and
then
I'm
writing
the
ed
test
to
figure
out
exactly
why
you
know
this
use
case.
B
If
it's
not
spreading
across
the
host
like
it
should
works
works
properly,
so
we're
we're
going
to
go
ahead
and
and
test
those,
and
then
this
is
going
to
be
released
so
I'm
hoping
on
Friday
I
can
cut
this
out
for
people
and
then
it'll
be
fully
ready
to
start
using
for
things
and
giving
it
a
whirl
with
whatever
awesome,
Cloud
stuff
you
have
so
anyway.
That
is
the
demo
any
questions.
Anything
people
want
to
see.
A
Not
really
a
question,
but
you
put
together
this
really
cool
board
project
board:
hey.
B
Yeah
this
is
stuff
like
some
of
these
are
gonna,
be
okay
like
right
now
like
when
a
node's
reap.
We
don't
necessarily
like
trigger
reconciliation
and
stuff,
and
these
are
going
to
probably
be
moved
on
to
other
stuff
like
this
task.
Right
here
is
the
one
that
I
need
that
I
have
left.
B
I
actually
forgot
to
mark
this
as
done,
and
then
we
have.
Let's
see,
we've
documented
it.
Oh
yeah,
that's
something
else.
I
can
show
while
we're
here,
because
it's
a
it's
a
good
update.
B
So
if
we
look
at
the
Watson
cloud,
.com
go
to
Docs.
So
inside
of
getting
started,
sorry
fundamentals.
We
have
a
managed
application
deployment,
so
this
has
all
your
documentation
for
one.
This
has
the
introduction
to
why
it
exists.
How
you
can
Define
applications
like
what
it
looks
like
the
different
things
like.
What's
a
trait?
B
What's
a
component,
why
does
it
matter
that
goes
through
everything
right
here
and
then,
when
we
go
to
yes,
the
logo
is
the
best
there's
a
reason
we
we
call
it
wadam
most
of
the
time
and
it
sounds
like
a
punch
from
like
a
comic
book.
So
that's
why
we
have
that
logo.
B
You
have
how
you
can
deploy
the
applications
using
wash
so
I
was
doing
it
directly
to
the
API
watched
as
it
with
like
a
nice
command
line,
and
this
has
the
the
documentation
for
the
API
everything
that's
in
it
and
then,
if,
for
some
reason
you
get
Beyond
just
using
it
locally,
we
even
have
deploy
guide
deployment
guides
for
if
you
want
to
run
run
this
in,
like
an
environment,
you're
running
like
whether
a
local
lab
or
whatever
it's
going
on
like
how
to
run
it.
B
As
you
can
see,
you
can
run
as
many
as
you
need
for
your
availability
guarantees
and
the
nice
thing,
because
it's
Nats,
you
can
actually
run
it
anywhere
so
long
as
it
can
connect
to
Nets.
We
also
have
we're
going
to
hopefully
move
this
to
another
thing
later,
but
this
actually
is
the
first
time
we've
put
together
something
on
here.
B
That
shows
you
how
to
do
some
more
of
the
it's
kind
of
the
intro
to
if
you're
doing
this
for
real,
and
you
need
to
set
up
your
Nats,
here's
how
you
do
the
basic
credentials
and
stuff.
So
that
you
can
have
different
credentials
for
different
people
if
you
wanted
to-
and
this
shows
like
how
to
how
to
use
that
all
so
anyway,
that's
all
in
here
inside
of
the
dock,
so
this
is
all
fairly
well
documented.
B
A
I,
don't
see
any
right
now,
and
that
was
a
really
great
update
and
so
to
summarize,
you've
got
Woodham,
basically
ready.
We
want,
we
want
as
much
feedback
and
users
as
we
can
get.
This
will
be
its
first
big
release
right.
This
is
kind
of
us
saying
we
think
it's
feature
complete
and
you
should
be
able
to
build
real
things
on
top
of
it.
Yeah.
B
And
feature
complete
is
to
be
very
clear
means
it
is
it
is
there
it
can
be
used,
it
does
all
the
basic
features.
It
says
it's
supposed
to
do
with
the
exceptions
that
we
call
out
in
the
readme
of
stuff.
That
we
know
is
missing
and
we
want
like
feedback
on
it.
If
people
are
like
yeah,
this
part
really
sucks
or
I
really
wish.
It
could
do
this,
like
that's
what
we
want
from
you.
C
Serious
fans
I
do
just
the
process
model,
then
so,
when
you
run
your
wadum
job,
you're
running
it
locally.
So
that's
all
of
that
coordination
is
taking
place
in
a
process
where
you've
started
it
right.
B
B
I
am
sorry
I'm
going
to
create
a
whole
architecture
diagram
because
there
are
some
complexities
to
the
architecture
of
how
it
all
works,
though
it
mostly
manages
it,
for
you
is
that
you
are
everything's
connected
to
Nats,
and
so
the
state
is
stored
in
Nets
and
different
messages
or
quartets
coordinating
things
using
messages
across
Nats,
and
so
all
the
processes
can
handle
different
can
handle
one
thing
at
a
time
from
each
lattice.
So
there's
no,
this
isn't
being
synchronized
locally.
This
is
being
synchronized
across
the
processes
running
in.
B
However,
many
with
Amazon's
is
you're
running.
If
you
have
one,
then
it's
just
one,
that's
handling
all
of
it.
If
you're
running
three
or
four,
then
it's
being
balanced
across
the
the
different
Witham
instances
you
have
running
and
to
answer
Bailey's
question
the
core
design
of
how,
like
things
get
distributed,
the
work
gets
distributed
is
the
same
there's
just
some
other
stuff
that
has
been
added
to
do.
B
Some
of
the
coordination
between
it
that
wasn't
present
in
the
original
RFC
that
I
want
to
document
so
yeah
there's
this
isn't
like
handling
it
locally.
This
is
handling
it
through.
Basically,
a
work
queue,
a
message,
work
queue
that
comes
in
with
each
message,
and
then
it
does
something
with
it.
A
Yeah
I
think
the
original
RFC
has
some
cool
tips
from
you
and
Kevin
brainstorming
around
how
you're
able
to
work
with
different
streams
and
and
that
helped
you
solve
some
of
the
concurrency
issues.
C
Well,
it
gave
me
some
some
hints
on
what
I
need
to
do
to
understand
it
more
completely.
So
great,
that's
fine!
Thank
you.
Yeah.
B
I'll
get
the
architecture
diagram
out
sooner
rather
than
later.
I
wanted
it
out
there
for
people
who
were
curious
about
how
it
worked,
but
the
the
key
part
of
it
is
it's
using
a
work
queue
where
you
have
to
everything
gets
put
into
a
message
queue,
and
then
you
have
to
act
and
say
this
was
done
and
then
it
can
proceed.
B
So
it's
pretty
fault,
tolerant
and
I'm,
really
good.
At
the
distributed
side
of
things.
C
A
Okay,
our
next
agenda
item
is
to
talk
about
another
RFC
that
Kevin
has
written.
This
is
something
that
we've
talked
a
lot
about
in
the
community
stream
and
we've
given
different
types
of
motivations,
for
why
we
want
to
move
here,
Kevin
kind
of
wrote
them
all
up
together
for
what
the
rationale
is
right
now
we're
on
Smithy,
and
we
want
to
come
up
with
a
path
to
go
from
Smithy
to
Whit.
That's
not
too
frictionful.
A
This
describes
a
couple,
different
phases
for
being
able
to
do
that,
and
once
you
go
through
here,
another
place,
that's
worth
checking
out
is
Kevin,
went
through
and
came
up
with
some
of
the
initial
sort
of
interfaces
that
we
think
we
will
use.
We
intend
to
use
Wazi
Cloud
once
that's
more
standardized
and
stabilized,
but
getting
some
interfaces
that
will
get
us
working
with
our
current
set
of
features
is
the
priority
and
Kevin's
been
working
with
Dan,
carolini
and
Joe
over
from
Deus
Labs
on
on
standardizing
some
of
the
Wazi
Cloud
interfaces.
A
But
there's
there's
quite
a
lot
here.
So
this
is
an
RFC
AKA
request
for
comments
really
interested
in
what
the
community
thinks
about
this.
This
path,
if
the
risks
are
are
kind
of
acceptable.
A
You
know:
we've
I've
shown
off
a
kind
of
like
a
prototype
of
a
lot
of
those
working
at
the
wazam
io
conference,
and
that
was
you
know,
kind
of
a
hit.
I
I
think
we
are
somewhere
in
the
range
of
65
000
views
now
on
that
talk,
which
doesn't
make
sense
to
me
or
how
that
could
ever
happen.
A
But
you
know
it
was
one
of
the
first
examples
of
showing
a
component
built
into
and
running
in
real
systems,
with
wit
interfaces
defined
from
some
of
the
earlier
wazzy
cloud
apis
and
that
all
ran
within
wasmcloud,
which
was
pretty
cool.
A
Now
we
only
got
two
interfaces
brought
over
messaging
and
key
value,
and
obviously
the
goals
to
do
all
of
them
and
all
the
ones
that
we
have,
but
it
was
a
pretty
good
prototype
and
a
good
starting
point.
We
learned
a
lot
so
now
I
think
we're
able
to
pick
a
path
and
kind
of
and
run
it
down.
A
Okie
dokie
moving
right
along
and
so
the
next
one
is
kind
of
like
our
normal,
broader
Community.
Before
I
go
into
this
one.
Do
we
have
any
other
wasm
Cloud
topics?
Anybody
wants
to
add
anything.
We
want
to
talk
about.
A
Yeah,
okay:
this
can
be
a
lighter,
lighter
Community
update
today.
So
I
wanted
to
give
a
little
bit
of
update
from
you
know,
I'm
putting
on
my
by
code
Alliance
hat
now,
and
that's
certainly
my
boss
and
Claude
one
within
the
by
code.
Alliance
we've
been
making
a
ton
of
progress
on
implementation
of
the
component
model
specification.
A
Blossom
time
now
has
the
adapter
brought
over
into
it.
Actually
let
me
show
you
that,
so,
if
I
go
over
to
by
code,
Alliance
and
I
go
to
the
runtime
that
we're
using
within
wasmcloud
that's
wasm
time,
and
now
the
adapter
in
here
we're
in
here
is
the
preview
2
adapter
and.
A
A
So
if
you
watch
the
the
talk
that
I
talked
about
before
the
POC
that
we
had
built,
the
one
of
the
key
things
is
that
you
basically
build
for
onesie
preview,
one.
So
the
thing
that
basically
all
the
languages
around
support
right
now,
if
they
say
they
have
webassembly
and
quasi
support,
and
then
we
take
this
plasma
module.
That
is
an
adapter
that
takes
the
preview
one
and
adapts
it
and
outputs
a
component
model
binary.
So
it's
still
a
dot
wasm.
A
A
Jordan
was
here
because
I
can
finally
say
like
yeah.
We
can
take
all
these
things
that
we
write
with
go
and
we
can
combine
them
with
the
all
these
other
things
that
are
written
in
Rust
and
any
other
language
that
supports
the
component
model
and
create
one
unified
app
there.
It
is
okay,
I
just
had
to
talk
through
it
and
then
I
found.
A
It
was
right
there
at
the
top-
and
this
gives
you
some
of
those
steps
to
be
able
to
run
that
that
adapter
so
before
when
I
talked
about
it,
I
pointed
people
to
a
different
repo.
So
I
wanted
to
just
give
a
little
update
that
this
is
kind
of
the
new
home
for
a
lot
of
this
stuff,
especially
within
Blossom
time.
A
Do
we
have
any
questions
around
that
I
think
that's
that's!
The
biggest
update
is
that
we're
no
longer
working
in
this
like
side,
Preview,
2,
prototype,
I'm,
trying
to
figure
out
what
the
heck
is
is.
This
is
all
going
to
work
and
how
it's
going
to
come
together
and
now
we're
really
starting
to
land
things
with
them.
Time
and
I
feel
like
if
I'm
being
very
optimistic,
I
think
a
lot
of
this
will
be.
A
You
know
a
call
for
people
to
start
building
call
for
Builders
in
June
on
the
Gian
wasm
time,
release
which
is
really
exciting,
and
obviously
we
will
bring
that
boy
over
as
quickly
as
we
can
into
Watson
Cloud
the
Watson
Cloud
host
and
be
able
to
enable
that
and
give
feedback
from
our
side.
A
Okay,
well,
hey
today
was
a
pretty
pretty
lightweight
meeting
I
think
I'm
going
to
stop
it.
There
I'm
gonna,
stop
the
recording,
and
so
thank
you
for
tuning
in
and
see
you
around
on
the
internet.