►
From YouTube: Repeatable Database Creation Demo (2021-07-28)
A
Okay,
let's
get
started.
This
is
the
repeatable
db
creation
demo
for
july
28th
start
off
with
a
discussion.
We
have
some
new
sandbox
environments
that
we
created
to
allow
more
people
to
work
simultaneously.
A
The
way
this
works
is
we
just
assign
each
of
us
to
a
sandbox
and
then
there,
and
then
that
allows
you
to
have
like
your
own
project
and
your
own
infrastructure,
it's
statically
configured,
so
it's
not
very
dynamic,
but
so
now
we
have
a
new
pipeline
on
ops,
where
we
have
a
list
of
environments
and
then
a
manual
trigger
that
triggers
the
you
know,
provisioning
of
the
environment
and
also
the
tear
down.
A
So,
for
example,
like
I'm,
using
alpha
alejandro's
using
beta
and
then,
if
we
want
to
like
run
configuration
changes
in
ci,
we
can
do
that
separately.
A
Number
two
I've
started
the
document,
the
limitations
for
get
and
pg
bouncer.
This
is
just
an
fyi.
If
you
want
to
take
a
look,
this
is
sort
of
the
first
roadblock
that
we
encountered
so
far
in
the
project.
A
I've
also
scoped
out
the
work
for
the
ansible
configuration
epic,
so
I
think
most
of
the
issues
are
there.
I've
currently
like
thinking
around
like
70
confidence,
that
this
will
be
this
whole
project
will
be
done
by
september
17th
and
for
what's
next,
I
think.
Next
week
we
can
probably
demo
I'm
hoping
we
can
demo
a
full
petroni
cluster,
but
we'll
see
how
it
goes
and
for
this
week's
demo
I'm
going
to
hand
it
over
to
alejandro
who's.
Going
to
demo
the
ansible
configured
console.
A
B
Yeah,
so,
as
I
was
saying
this
week,
we
tried
our
first
ansible
configure
service.
We
chose
console
because
the
simplest
it
doesn't
have
dependencies.
We
can
start
it
on
its
own,
so
we
have
a
pipeline
like
the
one
that
jar
was
saying.
We
have
a
child
partnering
for
each
project
and
each
side
pattern.
This
is
what
we
demonstrated
on
the
last
demo.
We
now
have
there
of
a
miniature
from
planter
from
apply,
and
I
kicked
those
off
to
save
us
some
time
because
we've
already
demoed
this.
B
B
B
Hitler
beam.
There
is
one
it's
the
placeholder
one.
So
what
we
will
do
is
kick
off
the
sp
beta
console
workshop,
which
will
run
from
ci
the
ansible
playbooks
that
will
configure
all
this
so
we'll
trigger
this
manual.
B
B
But
the
get
raw
currently
does
other
stuff
that
we're
currently
not
interested
in
doing
like
secret
management
and
they
there's
an
nfs
mount
that
they
use
for
secret
management.
So
our
current
role
is
very
simple:
just
set
up
the
gitlab
configuration
file
and
we
use
the
template
that
comes
from
get,
and
then
we
just
reconfigure
console,
but
because
the
template
that
comes
from
get
already
gets
the
ips
of
all
the
hosts
tagged
as
console.
A
A
A
B
B
A
B
B
One
thing
I
hadn't
wondered
about
is:
does
unto
18
come
from
get.
Is
that
determining
on
get.
A
I
think
we
passed
it
in,
it
might
be
the
default.
I
don't
remember,
but
it's
something
we
can
override
in
terraform.
Maybe
I
explicitly
said
it
I
I
don't
remember.
A
C
It's
an
overhang
from
the
nightly
packages
from
the
only
being
built
for
ubuntu
18.
That's.
C
Now
there
is
actually
more
with
the
distributed
teams
actually
expanded
that
so,
but
18
still
the
default.
I
guess
there's
probably
will
be
an
argument
in
the
future
switch
to
20,
but
you
kind
of
write
it
in
the
settings
for
gcp.
That's
relatively
easy.
If,
yes,
it's
actually
a
bit
harder.
C
Doable
as
well,
it's
just
either.
You
actually
need
to
actually
get
the
disk
image
for
the
specific
os
version
you
want,
and
that's
what's
attached
to
you.
Forevermore
is
the
disk
image.
So
it's
it's
a
mess,
but
yeah
gcp
should
be
fine.
You
can
change
them
to
terraform
settings,
but
don't
do
it
on
an
existing
environment.
It
also
will
destroy
the
whole.
A
Thing
there's
a
there
are
a
couple
changes
we're
going
to
need.
I
I
don't
know
if
there's
an
issue
for
this
already
grant,
but
to
be
able
to
pass
in
a
sub
network
that
belongs
to
a
vpc,
is.
C
There
an
issue
for
that
already
before
there
is
one
there
I
raised
it
actually,
yesterday
we've
been
planning
to
do
it
for
a
while.
Okay,
even
a
week
or
two
ago
I
would
have
been
like
I
don't
know
how
fun
that's
going
to
be,
but
we've
just
landed
that
in
a
very
good
place
for
aws,
because
it
needed
it
for
various
pieces.
C
Gcp
doesn't,
but
we
definitely
want
to
bring
over
that
essentially
the
same
blueprint
where,
if
the
rest
the
function
currently
works
is
that
you
could
ever
use
the
default
or
you
can
ask
get
to
create
a
ppc
subway
subnet
stack,
which
it
does
or
you
can
pass
in
existing
stuff.
We
will
be
bringing
over
to
gcp,
although
there
is
no
strict
timeline
on
that.
But
if
you
look
at
this,
you
just
forget:
you'll
see
it's
quite
high
near
the
top
because
there's
recently
raised.
C
I
do
comment
on
that
and
let
me
know
timelines
and
stuff
that
you
really
need
it
for
and
we
can.
We
can
take
a
look.
A
A
C
But
we've
got
we've
got
it
working
for
the
rest,
so
the
blueprint
is
there.
You
just
need
to
essentially
translate
that
for
gcp,
but
it's
just
I
mean,
feel
free
to
contribute,
and
then
we
can
look
at
testing
and
collaborating
that's
no
problem,
but
we
will,
if
not
we
will
get
to
eventually
there
would
be.
There
was
less
of
an
impetus
for
gcp
because
it
has
built-in
separation
concerns
because
of
its
project,
setup,
design,
aws,.
A
B
C
Trust
talking
you
know,
whereas
in
gcp
you
could
just
have
a
project
for
each
thing,
but
it
depends
on
the
work
you're
doing.
Obviously
this
one
you're
doing
daily
stuff.
So
I
I'd
understand
if
you're
doing
stuff,
with
the
same
project
with
various
stuff,
so
we
will
look
to
add
it.
But
yeah
do
comment
on
the
issue
and
we'll
do
that.
We'll
keep
that
in
mind
as
we
try
and
support
yourself
as
well
as
project.
B
B
I
was
in
achomat's
parameter.
Okay,
so
I
think
if
I
would
have
killer
city
of
status
before
it
would
have
thrown
an
error
so
that
solves
that
mystery.
But
now
we
should
have
the
service
running
there.
It
is,
and
if
we
look
at
the
kit
level,
green.
B
C
B
B
What
you
can
do
later
is
destroy
this
sandbox
environment
and
stop
stress
again.
A
C
And
I
get
1.1.0
is
imminent,
it's
probably
everywhere
today
or
tomorrow
there.
It's
been
substantial
to
make
sure
that
you
break
anything.
But
if
you
see
your
images
update
or
take
the
latest
version
of
get
just
you
might
want
to
do
some
stuff
just
manually.
Try
terrifying
as
well
make
sure
that
nothing
is
crazily
off
base,
but
we've
we've
checked
and
hopefully
everything
should
be
fine,
but
yeah.