►
From YouTube: Repeatable DB creation Demo (2021-08-25)
A
A
Those
are
the
priority
one
blockers
and
I
just
wanted
to
highlight
a
few
of
them.
One
of
them.
One
of
the
highlights
here
is
that
since
last
week
we
decided
we're
going
to
have
one
console
server
as
like
one
console
server.
That's
going
to
service
all
the
database
charts
so
because
of
that
we
need
to
make
sure
all
the
service
names
are
unique.
A
A
Item
number
two,
just
to
give
you
an
idea
of
what's
being
worked
on
now.
Right
now,
ahmad
is
working
on
the
ilb.
We
don't
have
support
for
this
and
get
so
we're
gonna,
probably
just
work
around
that
by
creating
our
own.
Well,
ahmad,
if
you're
on
the,
if
you're
here,
could
you
just
give
a
quick
update
on
iob
stuff.
D
But
still
we
need
to
extend
as
the
git
branch
we're
using
right
now
because,
for
example,
all
the
nodes
are
provisioned
in
a
single
zone
and
the
the
group,
as
the
group
says,
the
gcp
groups
expects
that
you
have
it
in
across
all
three
zones
and
so
on.
So
we
still
need
to
change
a
few
bits
in
in-game
itself,
but.
D
A
A
A
I
expect
I
expected
to
have
this
wrapped
up
soon
or
I
expected
expect
to
have
this
wrapped
up
sooner,
but
I
think
we'll
probably
finish
this
week
and
then
it's
going
to
be
a
matter
of
getting
the
prometheus
deployed
into
cooper,
netties
and
figuring
out
how
we're
going
to
hook
it
into
thanos
and
that's
probably
the
biggest
risk
right
now,
because
there
are
just
some
unknowns
around
that
craig.
You
have
item
number
three.
B
A
I'm
not
sure
how
migrations
are
going
to
work
for
the
new
database.
Shards
I
mean
is
that
something
we
have
to
you
know
add.
Is
this
going
to
be
a
disruption
to
the
current
staging
environment?
I
think
that's
why
we
wanted
a
separate
environment
to
hook
up
initially,
so
so
that's
the
other
aspect
is
like
what
we
don't
have
anyone
actively
working
on
creating
a
separate
environment
for
sharding.
B
Yeah,
so
any
environment,
it's
going
to
be
replication
streaming
so
effectively,
we'll
just
have
another
copy
of
the
database
and
then
we'll
drop
or
just
not
use
the
tables
that
we're
not
going
to
use
in
the
first
iteration
just
drop
them.
So
this
our
focus
doesn't
need
to
be
entirely
on
staging.
We
just
need
another
environment
where
we
can
start
testing
the
implementation
start
running
tests
against
it,
etc.
B
A
Yeah
this,
this
tooling,
is
around
creating
repeatable
databases
and
not
creating
repeatable,
like
you
know,
not
creating
a
full
gitlab
installation
that
can
hook
up
to
it.
So
that
may
be
part
of
the
confusion.
I
don't
think
that
would
be
difficult
to
bring
up
a
reference
architecture
that
we
hook
into
this.
A
When
I
was
talking
to
camille
about
this,
he
thought
maybe
like
the
first
or
he
was
thinking
that
the
first
iteration
could
be
just
treating
this
shard
as
a
replica,
and
then
you
know
where
all
of
the
tables
will
be
replicated
to
it
and
then
we'll
just
activate
the
logic
to
kind
of
like
use.
The
replica
as
another
shard,
even
though
like
it,
will
have
all
the
same
data
as
the
main
database.
A
B
C
C
A
So
that's
my
goal
is
I'm
shooting
for
mid-september?
The
monitoring
may
come
after
that.
If,
if
we
fall
behind,
I
think
it
really
depends
on
how
much
of
ahmad
and
alejandro's
time
we
can
have
right
now.
The
registry
db
has
been
taking
up
some
of
our
bandwidth,
so
I
don't
know,
but
that's
the
that's
the
plan.
The
priority
will
probably
just
to
have
a
functioning
patrony
cluster
that's
registered
with
consoles
so
that
the
sharding
team
can
start
using
it.
C
A
Right
now,
what
we're
doing
is
we
are
using
ansible
and
terraform
and
we
are
taking
advantage
of
some
of
the
ansible
and
terraform
that
get
has
written
so
we're
we're
basically
plugging
into
get
where
it
makes
sense.
Does
that
answer
your
answer,
your
question?
I
mean
it's
nothing
beyond
danceable
and
terraform,
though.