►
From YouTube: Scalability Team Demo 2021-04-29 - Call 1
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Great
well,
thanks
for
joining
for
the
first
demo
call.
I
see
that
hongman
has
already
put
some
things
on
the
agenda
for
today.
All
yours.
B
Yes,
so
in
the
our
current
project
I
have
finished
the
implementation
of
the
psychic
routing,
runes
and
the
merchandise
only
merged
into
master
and
right
now
is
only
deploying
to
staging
I'm
watching
the
deploy
and
to
see
what's
going
on.
So
basically
after
the
deployed,
everything
is
stayed
the
same
and
nothing
changed.
So
if
we
work
on
something
like
the
place
worker
or
something
it's
still
is
still
scheduled
into
the
base.
B
B
Okay,
here
we
go
again
and
right
now,
after
we
reschedule
it,
we
go
into
the
hello
kill
and
if
we
put
the
white
card
here
and
put
everything
inside,
it
is
the
exactly
what
is
the
current
production
configuration
of
life
and
we
still
have
like.
We
will
replicate
everything
in
direction
unless
that
we
have
to
put
on
the
q
net
into
node,
and
if
we
put
the
q
name
to
noon,
it
will
be
exactly
what
the
q
name
looks
like
right
now
with
this
it
will.
B
The
job
will
schedule
into
the
name
generated
by
the
worker
name,
and
it
is
what
we
want
and
after
we
put
the
configuration
into
the
omnibus
and
we
got
a
kubernetes
chart
and
we
still
have
the
current
name
configuration
and
we
can
try
to
schedule
something
like
the
particular
worker
into
a
particular
cure,
which
is
the
default.
And
if
we
test
with
some
worker-
and
it
works
quite
well-
we
continue
to
pronounce
the
horizon,
which
is
the
worker
here
right
at
the
bottom,
and
just
that's.
It.
C
B
Yes,
after
we
finish
the
deployment,
we
want
to
put
the
configuration
into
what
omnibus,
shaft
and
the
kubernetes
chart,
and
after
that
on,
the
key
will
be
known.
It
means
that
everything
will
stay
the
same
and
we
are
really
defensive
to
try
out
each
group
right
now
to
each
worker.
B
C
C
A
No
worries
I've
been
trying
to
put
the
the
meeting
at
different
times
to
encourage
different
people,
different
groups
of
people
to
to
join
in
yeah.
So
for
some
people
it
was
a
bit
of
a
surprise
that
it
was
an
hour
earlier
and
for
others
it's
a
surprise
that
there's
one
in
the
evening
so
well
in
the
in
the
uc
utc
evening.
C
I
I
might
be
able
to
join
the
one
tonight
as
well,
depending
on
how
easy
film
is
tonight,
how.
A
Things
go.
No,
that's
fine,
like
I'm
trying
to
just
find
different
ways
of
of
trying
to
get
the
demo
to
join
different
people
together,
so
they'll
the
times
will
probably
fluctuate
for
the
next
couple
of
weeks
until
we
find
something
that
works.
A
That
is
true.
I
mean
it
only
takes
a
couple
of
minutes
on
a
monday
morning
to
decide
when,
when
I
should
book
them,
yeah,
unfortunately
also
overlapping
with
the
delivery
demo
this
morning
didn't
help
either.
So
that's.
A
A
E
B
No
not
yet
it's
still
in
draft
and
I'm
getting
it
to
be
ready
until
I'm
not
quite
sure
about
the
process
of
deploy.change.
I
mean
it
changed
a
lot
since
the
last
time
I
touched
like
I
have
to
create
an
issue
in
the
qa
bar
as
well,
so
I'm
not
sure
what
it
is
so
yeah.
I
have
to
go
out.
C
I
don't
know,
but
have
you
already
been
able
like?
Have
you
already
packaged
to
change
up
and
tried
it
out
on
a
vm
somewhere
for
yourself.
B
Yes,
yes,
it
works
quite
well.
I
think.