►
From YouTube: Tweety - a service for controlling Lotus canary nodes
Description
A
A
A
We
used
twitty,
for
example,
to
compare
the
split
store
functionality
which
is
going
to
be
merged
and
released
under
feature
flag
in
the
near
future
versus
the
lotus,
stable
release,
so
yeah
what
is
tweety?
Basically,
it's
a
web
service
that
very
easily
installs
lotus
notes
on
kubernetes
cluster,
always
on
the
same
hardware,
with
the
same
disks
at
the
moment,
so
you're
pretty
much
getting
the
same
hardware
performance
from
different
nodes.
A
Ci
configuration
to
get
the
same
data,
but
you
can
pretty
much
pull
yeah
any
version
of
lotus
that
has
been
built
over
the
last
like
one
or
two
months
so
yeah.
This
service
supports
like
creating
a
cannery
upgrading
one
installing
from
snapshot
and
deleting
a
calorie,
that's
pretty
much
what
it
has
at
the
moment
and
for
those
of
you
who
have
played
a
little
bit
with
kubernetes
infrastructure.
A
A
A
You
basically
need
to
start
tweeting
and
you
just
issued
like
a
json
rpc
request,
with
the
release
name
for
the
canary
that
you
want
to
deploy
or
that
you
want
to
upgrade
and
with
the
new
image
name,
and
also
it's
at
the
moment
quite
rough
around
the
edges
in
terms
of
acl
and
permissions.
So
it's
kind
of
trusting
the
inputs
that
are
coming
up
in
terms
of
like
ownership
of
those
carries.
So
at
the
moment,
if
two
people
try
to
use
the
same
canary,
yeah,
they're
gonna
have
a
bad
day.
A
That's
something
that
we
need
to
work
on
in
the
future
to
improve
so
yeah.
Let's
do
a
quick
demo
at
the
moment
I
have
twitty
running
in
this
window
and
basically
I
have
the
readme
open
in
another
window
and
also
monitoring
the
kubernetes
cluster
down
at
the
bottom,
and
we
can
see
that
there
are
like
two
canaries
running
at
the
moment,
so
I'm
just
gonna
go
ahead
and
delete
one
of
them
just
so
that
we
have
space
for
a
new
one.
A
A
It's
returning
currently
on
error
because
we're
still
leaving
behind
volumes,
they
need
to
be
manually,
cleaned
and
that's
something
that
needs
to
be
improved
in
the
future.
Whoop,
that's
incorrect,
an
old
version.
So,
okay,
we've
removed
one
of
the
canneries.
How
do
we
create
a
new
canary
I'm
just
going
to
give
it
like
a
new
new
name,
for
example
lotus
4
and
I'm
gonna
release
this
version
from
this
commit?
A
A
It
basically
schedules
the
application
generates.
The
jwt
tokens
assigns
a
volume
for
that
canary
and
then
starts
it
and
on
twitter
we
can
see
some
useful
log
lines
to
basically
see
who
is
doing
what
we're
also
printing
out
the
exact
home
command,
so
that
folks,
who
are
monitoring
this,
can
understand.
A
A
We
also
want
to
build
some
feature
flags
so
that
developers
are
able
to
actually
pass
their
feature
flags
to
lotus
and
not
just
like
create
like
vanilla,
lotus
nodes,
because
when
we
release
new
features,
maybe
some
of
them
will
be
experimental,
so
that'll
be
a
good
way
to
test
them
yeah.
So
that's
pretty
much
all
I
have
for
you
today,
yeah.
The
repo
is
located
here.
A
B
A
C
May
I
just
quickly
step
in
because
we
also
like
I
was
part
of
the
conception
of
this
project.
One
of
the
one
of
the
things
that
that
we
wanted
to
create
here
was
or
give
developers
the
the
ability
to
do
is
basically
hey.
I
have
cooked
up
a
new
feature.
I
have
cooked
up
a
chain,
a
change
on
some
particular
feature.
C
C
So
it's
a
fully
synced
up,
node
that
I'm
not
gonna
have
to
run
on
my
on
my
machine
and
ideally
the
the
the
output
of
all
of
this
is
to
have
a
grafana
dashboard
that
is
constantly
showing
metrics
of
these
like
different
streams
and
different
version,
lineages,
potentially
of
lotus,
so
that
you
can
compare
things
with
one
another.
This
was
initially
built
for
for
also
testing
the
split
store
and
other
alternative
block.
A
A
And
so
I
see
a
question
about:
can
we
actually
use
ipfs
for
a
docker
registry?
We
haven't
really
have
the
capacity
to
do
that.
We
just
want
it
like
the
simple,
the
simplest
build
system
that
works
for
everyone
and
yeah
ecr.
The
public
image
is
just
worked
out
of
the
box.
So
that's
what
we
went
with,
but
I
mean
there's
nothing:
stopping
us
from
building
a
docker
registry
on
ipfs
and
yeah,
storing
the
artifacts.