►
From YouTube: wasmCloud: Host Configuration Demo, Roadmap Review, Community Callout! - 11/10/2021 Community Call
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.
B
C
B
That'd
be
nice,
we
get
our
own
video
conferencing
software
and
everything
too
cool
all
right.
Everyone
well
happy
to
start
the
the
day
out
today,
with
the
demo,
I'm
gonna
be
showing
off
two
things
that
have
made
it
their
way
into
wasm
cloud
host
process
and
is
being
proposed
right
now
for
wash,
which
is
the
host
config
and
wash
contacts.
B
Okay.
Now
I'm
going
to
kill
this
real
quick.
Just
because
I
want
to
show
you
the
what
we've
added,
which
is
the
host
config.
Now
there's,
I
don't
know
17
to
20
different
variables
that
you
can
use
to
configure
a
watson
cloud
host
at
startup,
and
previously
you
would
have
to
do.
You'd
have
to
do
that
with
environment
variables.
B
If
we
take
a
look
at
what
this
host
config
json
is.
This
is
auto-generated
using
all
of
our
quote-on-quote
like
reasonable
defaults
that
we
use
so
like
connecting
to
nats
locally.
We
auto-generate
a
cluster
key
and
cluster
seed
for
you,
so
that
you
can
stitch
together.
Multiple,
wasn't
cloud
hosts
and
give
like
default.
Lattice
prefixes
things
like
that.
B
This
is
automatically
written.
If
you
use
environment
variables,
it
overrides
the
values
in
this
host
config.
But
the
net
result
of
this
is
that
if
I
launch
another
host
immediately,
it's
going
to
read
that
configuration
file
and
launch
the
host
with
those
settings.
So
I
can
launch
this
host.
I
can
launch
another
host
on
my
local
and
it
would
automatically
be
connected
to
the
same
lattice
and
from
the
from
the
wash
context.
If
we
run
wash
cuttle
get
hosts,
then
we'll
automatically
pick
up
that
host
and
if
we
type
in
help
here
we
can
see.
B
Arguments
that
you're
providing
for
wash,
but
I'd
like
to
show
you
how
this
is
a
little
bit
different
now,
and
this
starts
at
the
nas
level,
so
to
show
off
this
example,
I
want
to
configure
nas
with
some
authentication
the
probably
one
of
the
easiest
ways
we
can
do.
This
is
with
an
in-key
public
private
key
pair,
which
we've
talked
a
little
bit
about
nasa
authentication
before
I'm
not
going
to
go
100
into
it
today.
But
what
I
do
want
to
say
is
like
a
big
benefit
of
the
in-key
authentication.
B
B
C
B
The
seed
key
because
we're
going
to
use
it
in
a
second,
so
I'm
going
to
do
the
same
thing
launch
my
nat
server
with
jetstream
I'm
going
to
instead
use
this
I'm
going
to
give
it
a
configuration
file,
this
user
off
and
then
just
for
fun.
I'm
going
to
go
ahead
and
configure
a
couple
other
things
to
show
you
some
some
different
things
we
can
change.
So
I'm
going
to
listen
on
127002
and
I'm
going
to
use
the
port
433.
B
So
if
we
launch
this
nat
server,
you
can
see
we're
using
that
configuration
file
jet
stream
and
we're
listening
on
instead
of
zero,
four
zeros
and
four
two
two
two,
it's
one,
two,
seven
blah
blah
blah.
This
is
basically
just
kind
of
simulating
like
if
you
were
doing
this
on
a
server
with
a
different
ip.
B
So
now,
if
I
go
back
to
run
my
wasn't
cloud
host,
we're
going
to
try
to
connect
on
localhost
422
we're
not
going
to
have
any
authentication,
so
it's
not
going
to
work,
but
with
this
host
config
we
can
actually
pretty
fairly
easily
fix
that.
So
in
here
this
is
a
a
big
one
line.
Json
string,
but
it's
not
going
to
be
too
hard
to
modify
so
I'm
just
going
to
like
group
override
where
we're
connecting
to
127.001.
B
Instead
I'll
change
it
to
12702
and
that's
going
to
be
for
the
control
interface,
the
provider,
remote
procedure,
call
host
and
the
remote
procedure
call
host,
and
then
I'm
also
going
to
change
the
the
default
that
we
have
for
port
422
to
four
three
three
three
and
we
could.
This
would
be
prettier
if
I
opened
nvs
code
and
like
beautified
it
a
little
bit.
But
I
just
kind
of
wanted
to
get
through
this
part.
B
B
So
now
you
know
the
host
configuration
makes
this
a
little
bit
easier
to
change
your
nas
settings.
Now,
if
we
go
to
what
the
the
wash
side
of
things
and
we're
to
run
like
wash
cuddle
get
hosts,
we
need
to
like
completely
reconfigure
this
in
order
to
connect
to
our
new
nas
cluster
with
the
oh,
that's
weird,
we
got
a
response
there.
I
thought
that
our
okay,
so
the
default,
is
localhosts422.
B
B
B
B
As
I
showed
you
a
little
earlier,
we
can
also
edit
these
contexts,
which
you
can
provide
a
text
editor
to
use,
but
we
can
edit
or
look
at
that
community
demo
context
that
I
just
created
and
then,
of
course
we
can
delete
them
and
set
different
contexts
for
our
default.
If
we
want
to
use
those
for
various
operations
in
wash
so
in
the
end
just
to
wrap
up
the
demo,
bring
it
all
home.
We
have
two
big
benefits
here.
B
The
the
host
configs
make
it
a
lot
easier
to
provide
like
an
easy
way
to
configure
a
wasm
cloud
host.
What
you
previously
have
to
do
with
a
ton
of
different
environment
variables
and
context
make
it
so
that
you
automatically
connect
to
your
local
wasmcloud
hosts
without
any
configuration
changes,
and
then
you
can
manage
additional
contacts
from
here
on
out.
A
A
B
You
know
the
interaction
between
a
host
config
and
a
wasn't
cloud
context
is
something
that
I've
been
kind
of
answering
questions
for
in
our
slack.
So
I
think,
as
soon
as
I
can
clear
up
that
interaction
for
everybody,
it's
ready
for
review
and
wash
so
by
by
the
end
of
this
week.
It
should
be
in,
I
would
say.
A
B
A
C
C
E
C
You
might
have
seen
there's
an
open,
open
ticket
for
that
and
that'll
be
a
more
efficient
way
to
download
capability
providers
because
it's
got
links
to
download
just
the
binary
that
you
need
and
not
all
of
them,
we'll
also
be
developing.
Some
additional
capability
providers
and
one
of
the
keys
is
one
of
the
most
important
ones
is
blob
interface
with
aws
s3
back
end.
We're
also
going
to
start
work
on
us.
C
E
D
I've
extracted
some
core
lattice
observer
logic
into
an
elixir
application
that
can
be
used
from
any
other
elixir
application.
So,
in
short,
I
have
a
an
otp
supervision
tree,
that's
responsible
for
observing
any
given
lattice
and
so
that
that's
being
used
I've.
I've
got
that
working
to
observe
lattices
in
some
sample
code,
and
so
once
I
get
a
free
moment
of
time
somewhere,
I'm
going
to
go
back
out
into
the
atlantis
controller
and
upgrade
the
lattice
controller.
D
So
it
uses
this
new
observation
supervision
tree
and
once
once,
the
lattice
controller
is
able
to
observe
using
that
library,
then
we'll
use
the
functions
that
are
already
in
it
to
come
up
with
the
recommendations
for
the
autonomous
agent
part,
and
so
then
the
next
step
after
that
is
just
in
converting
those
recommendations
into
commands
sent
out
on
the
lattice
controller
for
management.
So
there's
still
a
lot
of
work
to
do
yet,
but
you
know
the
I
can.
I
can
see
the
tunnel
from
here.
A
Yeah,
jordan,
let
me
jump
on
that.
One
real
fast
we've
got
a
bunch
of
enterprise
customers
that
are
using
lawson
cloud
that
we're
kind
of
talking
through,
and
what
I
think
will
happen
here
is
is
that
that
those
engagements
will
drive
the
prioritization
of
that
work
so
one.
So
let
me
just
leave
it
at
that
and
say
I
agree
with
you
that
there's
more
things
to
show
up
on
this
list,
but
we're
really
trying
to
figure
out.
A
You
know
which
customer
priorities
really
need
to
go
to
the
top
of
the
list.
I
would
say
this
is
the
the
start
of
what
the
roadmap
looks
like,
and
you
know
some
of
the
things
that
we'd.
Additionally,
you
know
you
and
I
have
discussed
you
know.
How
can
we
you
know?
Should
we
be
posting
a
you
know,
vlog
and
posting
videos
to
the
watsoncloud.com
site
or
wasn't
that
website?
You
know
weekly
and
things
like
that.
A
A
A
Okay,
well,
thank
you
so
much
steve.
I
really
appreciate
you
pulling
that
together
and
grooming
that
out,
we've
spent
a
lot
of
time,
the
last
few
weeks
as
a
team
together
just
trying
to
figure
out
what
our
priorities
are
and
getting
them
getting
them
lined
up
and
make
sure
that
they
line
up
with
all
the
folks
that
are
using
wasm
cloud.
So,
let's
maybe
turn
back
to
brooks
brooks.
B
Yes,
I
do
I'm
going
to
monopolize
as
much
time
of
this
meeting
as
I
can
I
kind
of
talked
about
it.
Last
week
I
was,
I
was
calling
as
a
contributor
call
out,
I
think,
or
the
community
call
out.
I
really
like
the
idea
of
having
this
section
in
our
meetings
where
we
do
like
a
contributor
call
to
action
and
over
the
over
the
last
weekend,
I
was
able
to
go
through
some
of
our
issues
across
our
repositories
and
find
some
that
were
relatively
scoped
out.
A
B
B
This
is
in
the
wasm
cloud,
otp
repo,
so
this
is
going
to
involve
writing
some
elixir
part
of
the
goal
of
what
we
wanted
to
do
with
using
elixir
and
using
rust
is
to
increase
the
language
spread
that
we
had
and
if
you
have
not
done
any
development
in
elixir.
Yet
you
know
I
added
a
couple
of
documentation,
links
here
and
we're
happy
to
kind
of
talk
through
this
if
you're
looking
to
contribute
so
this
one.
Basically,
when
you
start
an
actor,
we
tell
it
to
send
a
health
check
in
30
seconds.
B
It'd
be
high
impact
for
us
relatively
low
effort.
If
you
can
make
the
actor
do
a
health
check
right
away,
which
kind
of
documented
with
these
two
like
elixir
functions,
the
second
one
is
in
the
wash
repository.
Thank
you
jordan
for
filing
this.
Basically,
when
we
wrote
the
github
actions
for
wash,
we
were
using
some
outdated
stanzas
things
like
check
out
v1
and
I
don't
know,
create
a
release
with
this
action.
That's
now
like
deprecated
and
not
maintained,
you
know
it
all
still
all
still
works
okay,
but
we're
looking
to
upgrade
those.
B
So
if
anybody's
poked
to
get
hubastions
before
it
should
be,
it
should
be
a
fairly
quick
thing
to
to
do
and-
and
you
can
take
inspiration
from
some
of
our
other
actions
too
and
the
last
one
wash
in
in
the
wash
repository.
This
is
one
that
I
feel
like
would
have.
A
really
big
impact
on
us
is
creating
parity
with
our
environment
variables.
So
in
wash
we
have
plenty
of
environment
variables
for
specifying
things
like
the
rpc
host
rpc
port,
and
we
have
similar
environment
variables
in
wasm
cloud.
B
D
B
A
F
A
Well,
I
I
trust
you
you've
got
all
the
creds
man,
you
know
you've
been
doing
a
really
great
job
with
it,
and
I
really
appreciate
what
you're
doing,
and
I
hope
you
know
that
that's
just
as
important
as
everything
else
that
we
do.
You
know,
writing
the
code.
Organizing
you
know
it's
all
part
of
making
the
recipe
taste
good.
You
gotta
have
lots
of
different
ingredients
and
that's
you
know
an
especially
you
know
hard
one,
because
it
you
have
to
just
be
so
consistent
and
timely
and
respond.
A
B
A
A
You
know
move
to
multi-cloud
architecture
with
wasmcloud,
something
along
those
line.
I
paraphrased
a
little
bit,
but
it
was
phenomenal.
I
love
the
enthusiasm
and
the
excitement
and
I've
probably
emailed
that
video
to
a
hundred
people
in
the
last
last
month.
Sister.
Thank
you
so
much
for
that.
Well,
if
there's
nothing
else,
you
know
open
floor.
We
do
have
some
things
upcoming,
soon
re
invent
which
we're
gonna
talk
about
privately
as
a
team
afterwards.
A
I
hope
that
we're
gonna
at
least
host
the
meetup
for
watson
club
folks,
while
we're
out
there
in
las
vegas
in
a
month,
and
then
we've
got
some
planning
already
under
flight
underway
from
barcelona
in
2022
that
we'll
maybe
start
talking
about
over
the
next
few
weeks.
But
if
there's
nothing
else,
I
hope
everybody
has
a
wonderful
wasn't
cloud
wednesday.
Oh
valencia,
is
it
valencia,
valencia
oranges
have
a
great
week.