►
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
B
Someone
can
probably
speak
more
elegantly
to
it,
but
I
wanted
to
play
with
it
and
see
how
quickly
we
could
get.
You
know
wasmcloud
deployed
into
nomad,
so
I
spent
a
few
days
created
this
repo
and
more
or
less
is
exactly
what
it
is.
I
have
a
vagrant
file
here
which
spins
up
an
environment
with
nomad
and
console
the
reason
I'm
doing
that
is.
I
had
a
lot
of
problems
getting
the
networking
working
on
my
mac
and
it
seemed
to
work
just
fine
on
linux.
B
So
if
you
pick
this
up
and
just
try
and
do
the
nomad
pack
run
on
your
mac,
you're,
probably
gonna
get
an
error
or
something
along
the
lines
of
like
the
networking
layer
is
not
working.
So
that's
a
something
to
figure
out
eventually,
but
until
I
mean
it's
a
very
simple
readme,
but
I
mean
we're
gonna
go
through
it
here
and
and
see
what
we
can
do.
So
how
do
I
now?
I
need
a
new
share.
B
Can
you
see
this
okay?
So
I
have
two
new
terminals,
so
all
I've
done
here
is
I've
gone
and
I've
I've
cloned
that
repo
down
and
started
the
vagrant
file
and
in
the
background
I
didn't
want
to
do
that,
live
because
it
takes
like
five
minutes
to
get
up
and
running.
So
at
this
point,
we
we
have
I'll
flip
back
to
the
terminal
in
a
second,
we
have
nomad
and
console
being
ran.
You
know
what
we're
just
going
to
share
the
whole
desktop.
B
We
have
nomad
console
being
running
locally,
so
nomad
pretty
much
in
its
generic
developer
deployment
and
console,
and
it's
generic.
You
know
developer
and
deployment,
and
at
this
point
what
we're
gonna
do
is
you
can
do
two
of
you
know
one
of
two
things
you
can
do
like
a
nomad
pack
run
and
then
point
it
straight
at
the
pack
like
that
or
the
pretty
cool
thing
about
this
is
once
it's
deployed
into
github.
B
B
We'll
start
to
see
awesome
cloud
pop
up
and
it
takes
about
30
seconds
for
it
to
get
healthy,
but
once
it
is
running
we
have
more
or
less
so.
I
have
two
jobs
running
right
now:
a
match
job
and
a
wasm
cloud
job
and
they
actually
talk
via
the
the
console
nope
via
the
the
console
service
mesh.
So
in
essence,
if
we
went
over
here-
and
you
know
added
an
intention
and
did
not
allow
wasm
cloud
to
talk
to
nats,
you
know
things
would
stop
working
sorry.
B
The
zoom
bar
keeps
covering
up
my
tabs,
making
this
impossible
yeah.
So
now
that
we've
got
wasmcloud
up
and
running,
we'll
click
on
this
allocation
and
then
it's
kind
of
like
you
know,
kubernetes
we'll
have
you
know.
We
see
this
http
port
down
here,
4000,
which
is,
and
then
we
have
watson
cloud
running
in
what
running
in
nomad
being
exposed
via
you
know,
nomad
mechanisms.
Now
there
is
a
current,
I'm
not
going
to
call
it
a
bug,
because
it's
not
a
bug.
B
B
B
I
I'm
not
a
not
an
expert
on
nomad,
I'm
an
expert
on
console
but
spent
about
a
three
days
playing
with
this
and
it
you
know
other
than
the
websocket
problem
that
I'll
I'll
figure
out
it's
it's
been
a
very
enjoyable
experience
very
in
and
at
this
point
as
long
as
you
point
wash,
I
didn't
set
it
up
at
the
right
port
and
everything
it
it
works
as
expected
as
well.
So
I
really
haven't
experienced
that
many
issues
with
it
at
this
point,
so
that
is
about
it.
C
B
So
so
nomad
is
running
on
the
vagrant
box,
specifically
only
because
I
was
having
networking
issues
with
osx,
so
vagrant
is
not
necessary.
If
I
were
to
be
on
like
a
straight
up
linux
box,
I'm
sure
there's
a
way
to
get
the
networking
working
on
the
mac.
I
just
hadn't
figured
it
out
yet
so
then,
what
is
happening
is
nomad
is
using
the
docker
driver
and
deploying
it
on
so
it's
scheduling
onto
docker.
That
is
also
running
on
the
vagrant
box.
B
So
you
can
kind
of
see
that,
let's
see,
if
we
go
to
the
host
templates,
the
template
we
can
see
it
is
there.
You
go
the
runtimes
just
using
the
driver
docker
using
the
image,
I'm
not
even
sending
it
any
fancy
flags
and
then
up
here.
I
don't
know
why.
I
call
that
web-
that's
nats,
but
that's
that's
running
in
docker
as
well
and
they're
they're
connecting
via
the
console
connect
sidecar.
D
B
B
And
something
I've
kind
of
breezed
through
if
we
were
to
go
to
console
and
we
click
on
the
wasm
cloud
host
here
we
get
this
topology
john's
in
its
own-
is
pretty
simple
at
this
point,
but
we
do
have
the
ability
if
we
were
to
expose
some
sort
of
like
prometheus
metrics
to
in
this
same
topology
view.
Have
them
configured
right
there
in
that
gray
box.
B
Don't
really
know
what
that's
going
to
do,
but
we
can
do
it
so
yeah
I
mean
it's
a
pretty
fun
project.
I
can
see
that
there's,
there's
there's
a
lot
of
a
lot
of
things
we
could
do
here
and
even
to
the
point
where
nomad
gives
you
the
ability
to
do
custom
drivers.
So
there
is
a
world
where
we
could
use
the
same
nomad
tech
thing
to
say
something
like
driver
equals
wasm
cloud
and
then
the
config
be
like.
B
D
A
A
Yeah
yeah,
it's
just
great
jordan
you're
such
an
awesome
community
member.
I'm
so
glad
that
you
care-
and
you
see
the
vision
here
for
where
we're
going
and
you
know
you
continue
to
show
up
and
just
contribute
in
so
many
ways.
So
I
really
appreciate
it
and
I
think
that
you
know.
I
really
think
that
we
are
working
on
what
it
looks
like
you
know.
Is
this
what
we're
doing
so?
Thank
you.
I'm
just.
A
D
Yeah
same,
you
know
same
physical
cube
of
of
work
in
in
this
area,
but
you
know,
I
think
we
kind
of
talked
about
it,
maybe
about
two
weeks
ago,
but
today
is
actually
my
last
day
at
capital
one.
So
I
will
officially
be
full
time
doing.
Wasn't
cloud
and
cosmonic
things
come
tomorrow,
which
is
super
exciting?
I'm
I'm
really
excited
to.
You
know,
continue
growing
the
project
more
than
just
as
a
as
like
a
passive
maintainer.
A
D
D
D
I
know
that
we
call
this
the
community
call
out,
but
I
want
to
call
out
a
couple
community
members
and
say
thank
you
for
either
completing
a
good
first
issue
that
we
had
in
our
community
call
out
and
earning
yourself
a
student
to
come
contributor,
t-shirt
or
just
doing
their
first
contribution,
so
matt
wilkinson.
Thank
you
so
much
for
taking
on
one
of
our
good
first
issues,
updating
our
github
actions
for
wash.
D
D
Thank
you
so
much
for
this.
This
is
like
part,
two
of
a
two-part
pr
addressing
one
of
the
things
that
we
wanted,
help
on,
which
is
like
giving
a
hint
or
correcting
users
that
are
taking
a
look
at
wash,
and
you
know,
especially
since
a
lot
of
our
scripting
now
relies
on
things
like
copying
and
pasting
in
keys,
which
are
those
like
56
character.
Uppercase
things
we
use
for
actor,
ids
provider
ids.
D
So
stewart
came
in
and
did
some
to
be
completely
honest,
magical,
rust
things
that
I
didn't
even
know
you
could
do
the
thing
that
I
that
I
thought
was
really
impressive.
Was
this
like
public
id,
which
is
like,
has
a
constant
character
like
it's
like
a
generic?
I
just
thought
this
was
super
neat
and
and
using
that
and
I'll
go
ahead
kevin
I
was
gonna.
D
Yeah
yeah
so,
and
it
works
great
for
for
this
type
of
thing
you
can
see
like
we
can
kind
of
easily
start,
you
know
check
out
an
id
for
an
actor
or
for
a
host
or
a
provider.
Things
like
that.
So
this
is
awesome.
We're
looking
to
build
off
this,
to
do
all
of
the
input,
validation
for
anything,
that's
in
a
public
key
and
wash,
and
I
think
matt
joe
bride
is
actually
taking
a
look
at
doing
some
of
that
too.
D
They
were
going
through
our
documentation
and
going
through
some
of
our
examples
and
like
proactively,
found
a
place
where
we
made
a
breaking
change
without
like
proper
backwards
compatibility,
which
is
awesome
to
have.
Somebody
like
help
us
us
resolve
that
and
get
the
fix
back
into
wash,
but
bailey
was
making
contributions
across
a
bunch
of
our
repo.
D
So
thank
you
so
much
for
doing
that.
Maybe
we
can
talk
about
this
like
pr
like
the
the
wadm
a
little
later
in
this
community
call,
if
there's
stuff
to
to
talk
about-
and
I
know
that
janice
was
on
today,
so
hello.
Thank
you
all
right.
So
that's
that's
our
little
our
shout
out
section!
So
thank
you
to
everyone
in
the
community
and
now
is
the
community
call
out
section.
D
D
There
are
a
couple
different
scenarios
where
we
attempt
to,
for
you
know,
for
example,
we'll
try
to
put
a
link,
and
if,
in
this
example
you
don't
have
proper
connectivity
to
the
to
the
nats
cluster
you'll
get
an
error.
You'll
you'll
get
a
fairly
descriptive
error
that
we
can't
advertise
the
link.
The
connection
has
been
refused,
etc.
So
it's
pretty
easy
to
tell
what's
going
on,
but
this
actually
exits
with
like
a
successful
error
code.
D
So
this
wouldn't
ever
really
affect
you
if
you're
you're
just
typing
in
these
commands,
but
if
you're
scripting
something
you
would
ideally
want
this
to
exit
with
a
failure
code
so
that
you
can,
you
know
whatever
scripting
you're
doing
you
can
tell
that
that
was
a
problem.
So
first
community
called
here
is
to
take
a
look
at
some
of
the
wash
control
commands
and
if
you
can
reproduce
using
one
of
those
commands
and
not
actually
connecting
to
an
app's
cluster
and
you
get
a
successful
error
code,
I'm
just
changing
that.
D
You
know
there
this
this
command
when
you
put
or
delete
a
link,
death
has
a
couple
of
positional
arguments
so
for
link
put,
you
have
to
do,
let's
see
my
zoom
is
backwards,
actor
id
and
then
provider
id
and
then
a
contract
id
and
then
for
delete.
You
need
to
do
actor
id
and
contract
id
so
fairly
easy
to
mix
up
the
the
order
here
and
if
you
do
it,
we
don't
currently
say
hey.
D
You
know
this
looks
like
a
provider
id,
but
you
probably
should
have
a
contract
id
here,
so
it
would
be
great
to
have
you
know.
I
put
a
couple
of
references
here
into
the
prs:
it'd
be
great
to
have
this
kind
of
input
validation.
So
we
don't
accidentally
put
you
know,
link
definitions
that
are
not
actually
going
to
anything
and
last
but
not
least,
I
have
kept
this.
I
this
one
has
been
in
the
community.
D
Call
out
before,
but
I
really
want
to
keep
it
because
I
think
that
this
is
a
great
introduction
to
like
contributing
to
the
otp
runtime.
If
you
haven't
touched
elixir
before
this
would
be
a
great
starting
point
to
just
contribute
a
little
bit
of
functionality
and
we
have
a
hashtag
help
channel
now
in
awesome
cloud.
D
So
if
anybody
you
know,
if
you
want
to
take
this
on
and
you
haven't
like
used
elixir
before
we're
happy
to
point
you
in
the
right
direction
here
and
I
listed
left
a
couple
of
links
that
might
help
so
yeah
we've
got
two
two
wash
issues
and
one
for
the
otp
runtime
this
week
as
usual.
I
will
put
these
into
slack
so
that
you
all
can
can
pick
them
up
and
if
you're
interested
just
leave
a
comment
on
the
issue
so
that
you
know
nobody's
duplicating
efforts.
D
A
I
really
appreciate
how
many
of
them
there
were.
I
mean
the
it's.
I
think
it's
you
know
we
can.
Actually
you
know,
measure
and
see
you
know
how
quickly
people
responded
to
having
an
easy
onboarding.
You
know,
I
think
sometimes
people
want
to
help,
but
they
just
aren't
sure
where
to
get
started,
and
I
know
that,
like
like
janita
like
you
and
kevin,
did
some
pair
programming
recently.
You
know
to
help
move
something
down
the
field
and
that's
incredible
but
brooks.
A
I
think
what
you're
doing
is
super
important
and
super
scalable,
because
it
just
continues
to
bring
people
along
and
help
them
feel
included
and
part
of
the
team.
Because,
ultimately
you
know,
when
you
look
at
you
know
we're
approaching
pretty
elite
metrics.
You
know,
as
we
cross
100
contributors,
not
many
projects
get
that
far,
but
the
most
elite
contributors
you
know
elite
projects,
have
you
know
more
than
300
on
a
monthly
basis
or
over
I
mean
it's
a
six
month
rolling
window
or
something
like
that.
Bvp
has
got
some
great
metrics
on
that.
A
If
anybody
ever
wants
to
read
or
be
interested
in
that,
so
I
think
the,
but
so
these
behaviors
and
taking
the
time
to
do
this,
is
super
critical
to
building
a
healthy,
inclusive
and
diverse
community.
So
we
help
to
make
the
best.
You
know
what
listen
we
run
time
that
we
can
be
so
thank
you
brooks
for
all
the
hard
work
on
this.
A
B
A
Cool
I've
got
most
of
them
a
link,
so
I
will
share
those
with
you:
offline
cool.
Thank
you
coming
around
the
bases
community
stuff,
we're
still
working
on
the
on
a
event
in
dc
that'll,
be
out
there
we're
early
stages
on
the
webassembly
day
for
valencia,
but
we
do
have
our
like
planning
committee
going
and
we're
working
on
sort
of
putting
together
the
the
program
committee
to
go
from
there.
A
I've
already
spoken
to
a
bunch
of
users
and
already
encouraging
people
to
start
doing
user
talks
and
getting
submissions
together.
So
I
think
the
the
more
the
merrier
there,
as
we
you
know,
continue
to
build
this
out
would
be
great.
At
this
point
I
don't
have
anything
else
on
on
the
agenda
open
floor.
E
I
am
went
actually
done
much
more
than
what
I
did
for
the
pr.
I
did
see
kevin's
issues
and
I
need
to
wrap
my
head
around
exactly
what
needs
to
be
done.
But
I'll
try
to
pick
up
from
where
I
did
the
demo
with
going
from
the
operator
the
kubernetes
operator
into
whatever
now,
which
is
kind
of
what
I
got
blocked
on
when
I
was
trying
to
run
the
test
and
why
I
actually
ended
up
fixing
or
trying
to
fix
most
of
what
was
there.
C
Yeah,
I've
still
got
some
more
some
more
stuff
that
I
want
to
do
in
there
specifically
around
things
like
what
you
did
with
the
demo,
where
you
know
it,
it
accepts
the
the
oem
model
over
a
nas
interface
as
part
of
the
api,
and
some
things
like
that.
So
I
think
I
think,
there's
some
more
progress
that
can
be
made.
I
just
need
to
repair
my
time
machine,
so
I
can
get
in
there
and
and
work
on
it.
E
A
question
of
later
that,
actually,
so
I
guess
the
workflow
is
going
to
be
call
the
applies
and
then
call
the
reconcile,
and
I
think
the
call-out
that
you
had
in
there
was
trying
to
make
it
functional.
But
are
you
imagining
that
there's
going
to
be
some
sort
of
queueing
mechanism
similar
to
what
the
controller
does
in
k-8s
to
retry?
If
the?
E
C
Exactly
what's
what
needs
to
happen
there?
So
the
the
like,
you
said
it's
it's
kind
of
set
up
to
be
functional
so
that
we
could
test
that
you
know
given
any
given
any
state
of
the
lattice
and
any
application
deployment
model
we
know,
or
we
can
predict
the
set
of
reconciliation
measures
that
are
supposed
to
take
place
in
order
to
bring
about
the
right
state.
So
it
makes
the
model
fairly
testable.
C
That
way,
but
what's
missing
from
the
implementation
is
exactly
what
you
said
where
what
we
need
to
do
is
take
that
list
of
reconciliation
actions
and
toss
them
into
a
word
dispatch
queue,
and
then
something
is
pulling
off
of
the
word.
Dispatch
queue
and
converting
those
those
items
into
lattice
control,
function,
calls
and
then
at
some
point.
C
E
Yeah
I
was
going
to
try
and
take
some
examples
out
of
controller
runtime,
because
that's
all
abstracted
out
now
to
the
control
runtime
and
then
try
and
map
it
to
x,
elixir,
which
is
still
kind
of
alien
to
me.
I
think
in
terms
of
the
syntax,
but
I'm
getting
used
to
it,
and
thank
you
for
the
suggestion
of
using
a
language
server.
That's
definitely
made
my
life
a
lot
easier
because
I
was
using
a
different
plugin
before
nice.
I'm
glad
that
helped
yeah.
A
A
I
don't
remember
what
the
other
one
was,
but
sometimes
I
just
you
know,
rather
than
like
throwing
a
bunch
of
like
swearing
in
my
pr
commits,
which
I
mean
that's
a
great
twitter
one,
the
one
that
scrapes
github
for
profanity
laden
commits,
but
rather
than
doing
that,
I
try
to
just
do
it
into
dark
humor.
So
anyway
yeah
I
had
one
today
yeah
yeah,
maybe
that
maybe
that's.