►
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
A
Okay,
so
we
have
this
wonderful
helm.
Chart
you
to
be
able
to
access
this
helm
chart
it's
still
not
in
a
host
right
now,
because
all
right,
what's
that
called
a
repo,
I'm
thinking
awesome
cloud.
It's
still
not
in
a
repo
right
now
we
will
put
it
somewhere
eventually
and
we're
just
trying
to
let
people
start
trying
it
out
right
now,
so
to
be
able
to
use
it.
You'll
have
to
just
clone
the
repository
and
go
into
wasmcloud
host
directory
and
then
you'll
see
a
chart.
A
Lsd,
wow,
okay,
so
this
is
going
very
smoothly.
You'll
see
a
chart
directory
that
contains
the
actual
helm
chart
for
this.
So
this
home
chart
has
a
couple
different
options.
The
three
options
are
kick
the
tires
mode
which
is
the
default,
and
then
you
have
leaf
node
deployment
and
connecting
to
an
external
nat
server
deployment,
they're
just
two
different
deployment
methods.
If
you
don't
know
what
those
are?
That's
just
fine,
you
can
take
a
look
at
those
later,
but
we'll
all
show
two
of
those.
A
A
A
Do
port
4000,
which
is
the
wasm
cloud
host,
and
then
I'm
going
to
go
here
and
reload
this,
since
we
had
it
headed
up
from
practicing
the
demo
and
you'll
see
that
we
have
the
one
host
up
and
we
can
start
interacting
with
it.
Just
like
we
would
a
normal
awesome
cloud
host.
This
is
completely
standalone.
You'll
have
to
forward
the
port
and
do
all
those
things,
but
this
just
shows
that
you
can
get
it
up
and
running
inside
of
kubernetes.
A
Now
there
is
another
I'll
go
ahead
and
display
the
other
one
I'm
going
to
have
to
install
it
on
on
another
screen
because
it
uses
credentials
so
also
I'm
going
to
set
this
up
in
leaf
node
mode.
So
it's
connected
to
a
bigger
wasm
cloud
cluster
or
wasn't
cloud
nat's
cluster
and
we'll
go
ahead
and
wait
for
it
to
spin
up
and
you'll
see
that
it
came
up
and
is
running.
That's
the
old
one!
That's
deleting
right
here!
A
So
there's
a
new
one,
that's
running
so
the
nice
thing
here
is
actually
the
scalability,
and
so
this
is
how
we
anticipate
people
using
it,
because
people
have
kubernetes
environments
that
they'll
want
to
bridge
into
the
future
with
wasmcloud,
and
this
allows
you
to
put
things
in
your
kubernetes
so
that
you
can
bridge
that
gap.
You'll,
have
access
to
these
things
through
kubernetes
and
then
be
able
to
transition
things
as
you
write
new
things
in
wasm,
but
you
can
also
scale
these
very
easily.
A
A
And
we're
going
to
go
ahead
and
hit
that
and
you'll
see
that
we
have
the
various
hosts.
The
other
host
hasn't
popped
up
yet
so
it
could
still
be
joining
waiting
for
a
heartbeat,
but
you'll
see
that
we
have
the
host.
Oh
there
we
go
all
the
different
hosts.
I
spun
up
the
this
is
because
it's
connected
to
a
lattice
that
has
other
hosts
that
are
existing
outside
of
kubernetes
right
now.
A
One
of
them
is
actually
steve's
host
sitting
somewhere,
it's
a
linux
box
and
then
all
the
other
hosts
that
I
have
connected
from
kubernetes
and
so
now
all
of
these
are
part
of
the
lattice
and
they
can
be
scaled
up
and
down
dynamically,
with
no
additional
configuration
from
the
kubernetes
side.
So
that's
what
the
helm
chart
allows
you
to
do
with
with
a
wasm
cloud.
So
there
you
go
any
questions.
A
Stunned
silence,
okay,
I'll,
take
that
so
everyone
can
give
that
a
whirl
feel
free
to
contribute
any
fixes
or
stuff.
It
isn't
perfect.
It's,
but
it's
a
good
start
supports
those
three
main
methods
and
people
can
start
it
out
and
we'll
let
people
know
once
we
figure
out
a
place
where
to
put
it
for
for
long-term
storage,
taylor.
That's
awesome
man!
Thank
you!
So
much
for
all
the
hard
work
in
making
that
happen.
A
I
think
it
also
lowers
the
barrier
to
experimentation
so
for
orgs
that
are
all
in
on
kubernetes
now,
which
there
are
a
ton.
I
think
this
is
going
to
be
very
useful
for
us
to
reach
out,
so
we
should
get
this
integrated
into
documentation
and
you
know
get
a
demo
up
on
how
to
use
this
very
quickly.
But
thank
you
so
open
floor.
Any
other
topics
we
wanna
discuss
today
and
we've
kind
of
bounced
around
a
little
bit
janitor
and
kevin.
A
You
guys
were
going
to
talk
about
the
lattice
controller.
I
think
kevin
did
you
maybe
want
to
pull
up
and
maybe
see
about
taking
jonathan
to
some
of
the
next
few
items
on
the
roadmap
for
there
or
you
could
pull
up
share
codes.
You
have
something
to
talk
through
or
you
can
just
continue
to
talk
to
it
verbally,
whatever
you
guys
prefer.
B
So
I
can,
I
can
go
over
some
of
the
short-term
plans
for
it.
Hopefully
that
will
a
little
clear
up
where
and
where
when
and
how
people
can
contribute
to
the
lattice
controller
if
they're,
if
they're
interested
right
now,
the
lattice
controller
is
really
nothing
more
than
a
functional
model
for
observing
state.
In
the
lattice
part,
one
of
the
roadmap
is
to
extract
that
functional
model
for
observing
lattice
state
into
a
new
application
called
lattice
observer
that
can
be
used
by
any
other
elixir
project
step.
B
Two
is
the
washboard
or
the
wasmcloud
dashboard
currently
has
its
own
proprietary
state
calculation
from
event.
Monitoring
so
step.
Two
is
to
take
out
that
logic
and
replace
it
with
the
same
shared
logic.
That's
in
the
net,
the
newly
shared
lattice
observer
application
and
then
step
three
is
to
have
the
lattice
controller
rely
on
the
new
lattice
observer
for
calculating
the
observed
state
of
a
lattice
and
then
once
that's
in
place.
B
A
C
I
think
one
of
the
questions
that
I
probably
lost
a
little
bit
on
was
like
how
to
organize
a
code
in
terms
of
what
part
it
would
actually
go
into.
I
know
that
kevin
actually
mentioned
that
there
was
already
examples
and
I
wasn't
entirely
clear
whether
that
was
from
otp,
because
that's
kind
of
where
I've
been
looking
to
steal
code
from
in
terms
of
getting
things
off
of
or
using
gnats
and
not,
but
I
I
lost
that
or
I
didn't
understand
it,
because
I
don't
have
enough
context.
I
should
say.
B
C
So
I
think
I
can
yeah
I
mean
I
didn't
find
any
references
in
there.
I
guess
the
question
was
to
me
at
least
it
seems
like
it
can.
I
can
probably
add
some
scaffolding
in,
but
I
mean,
of
course,
reorganize
it,
but
I
can
play
with
it
still
and
to
get
the
messages
off
of
the
operator
into
the
lattice
controller,
which
I
think
is
a
step
that
would
be
independent
from
what
you're
doing
with
the
observer
and
then
that
needs
to
get
hooked
up
into
the
apply
events.
B
Yeah,
so
the
repository
that
has
an
example
of
how
to
use
configuration
environment,
variable
configuration
to
create
the
nets,
consumer
supervisor
and
the
nets
connection
supervisor
is
in
the
wisdom
cloud
otp
repository.
That's
for
the
you
know
where
our
otp
host
runtime
is,
and
so
it's
the
the
same
pattern
that
we
use
there
for
establishing
our
nats
connection
for
the
for
the
the
host
runtime
is
what
we'll
do
for
the
lattice
controller
for
establishing
its
nets.
B
Connection,
okay,
you're,
you're,
exactly
right
that
the
the
act
of
subscribing
to
aladdin's
event
stream
and
decoding
those
events
out
of
json.
That
is
something
that
you
could
definitely
or
that
anybody
could
definitely
work
on
independent
of
the
refactoring
that
I'm
doing
for
the
lattice
observer.
A
D
A
You
know
I
don't
know
that
we've
done
the
pet
clinic
demo
on
here.
We
probably
want
to
do
that
at
some
point,
but
I
don't
think
anybody's
ready
to
do
it
right
now.
We
did
do
it
on
the
0.50
release.
So
actually
we
probably
have
a
decent
version
of
that
out
in
recording
and
jordan
did
move
that
over
to
our
youtube
channel.