►
From YouTube: Ansible Provisioning Sync
Description
https://docs.google.com/document/d/1O-ykLHFybv-JapZRRNy0FNqr-WXwP58aWiAMgLiegq8 (internal only)
A
B
A
A
Able
to
focus
on
this
awesome,
so
I
spent
some
time
yesterday
getting
the
sandbox
environment
to
work
with
ansible,
that's
working
now
and
it's
running
in
ci.
What
I'm
able
to
do
is
I'm
able
to
configure
the
console
cluster
and
that
it
doesn't
yet
write
out
the
gitlab
rb,
but
what
it
does
is
it
installs
the
omnibus
package
and
it
starts
console.
So
it's
just
like
very,
very
basic.
A
I
realize
with
the
addition
of
both
of
you
on
this,
like
we're
not
going
to
be
able
to
share
a
project,
it's
just
going
to
be
too
chaotic,
so
I
created
three
projects
alpha
beta
and
gamma,
we'll
each
take
one
and
that
will
allow
us
to
work
independently
of
each
other.
As
we
start
like
building
out
the
roles
and
infrastructure,
I
expect
the
sandbox
projects
will
go
away
like
after
we're.
After
we're
done,
we'll
go
probably
go
back
to
one.
A
What,
for
now,
we
still
have
the
project
named
sandbox
as
well.
Maybe
if
what
you
guys
could
try
today
is
to
get
everything
working
locally,
I
did
update
the
readme
you'll
just
need
to
asdf
install
the
dependencies
decided
to
use
pipen
for
python,
so
make
sure
you
can
do
like
a
pip
bam.
Shell
and
pip
have
installed
to
install
ansible
and
its
dependencies
make
sure
you
can
run
terraform
using
the
gitlab
state
file
because
we're
using
terraform
integration
for
gitlab.
A
C
C
A
A
Okay,
okay,
well
yeah!
This
was
put
together
fairly
hastily,
so
I
apologize
for
any
problems.
Let
me
know
if
you
hit
any
roadblocks
today,
I
can
walk
you
through
and
once
we
have
the
separate
environments,
I
think
it's
going
to
be
a
lot
better
too,
because
we
can
just
you
know
we
can
work
independently
of
each
other
for
number
three.
A
We
don't
yet
have
a
bastion
figured
out.
Maybe
we
can
push
this
off
till
later
and
just
use
public
ips
just
to
make
things
simpler
for
running
locally,
because
most
of
the
work
now
is
going
to
be
done
locally
anyway,
once
we
have
the
bastion
set
up,
you
can
do
forwarding
through
it.
I
guess
and
run
ansible
through
the
bastion,
but
it'll
be
easier.
I
think
what
I
don't
know
yet
is
so
you
probably
saw
like
we're
using
send
links
to
sim
link
to
get
and
to
symbolic
for
both
ansible
and
terraform.
A
A
So
if
you
look
at
the
get
roll
right
it,
it
inherits
the
inherits
the
common
role.
So
I'm
just
doing
the
same
in
the
role
I
created
for
console
in
our
project
and
then
this
thing
writes
out
the
gitlab
rb
we
could.
We
could
try
to
use
the
get
roll,
but
I'm
worried
like
when
it
comes
to
petroni
like
for
console.
Maybe
this
will
work,
but
for
patrony
it's
gonna
be
like
we're,
probably
gonna
diverge
or
you
know
need
some
way
to
inject
our
own
config.
So
I'm
not
sure.
A
A
A
C
C
A
A
C
D
C
D
D
A
So
what
do
you
guys
think
if
we
just
create
issues
for
more
aligned
with
the
cookbooks
like
exports,
mtail
server
fluentd
says
ctl.
They
create
a
bunch
of
issues
for
that
and
you
can
just
take
them
up
like
whoever
whoever
wants
to
work
on
stuff
can
just
take
them
and
assign
them
to
themselves
and
and
then
we
each
take
a
component
like
I'll.
Just
keep
console
if
I'll
create
an
issue
for
pg
bouncer
petroni.
We
need
to
create
the
kind
of
like
the
base
role
for
that.
A
So
someone
can
do
that
as
well,
so
I'll
create
a
trendy
issue.
Pg
bouncer
issue
I'll
also
create
issue
for
like
bastion
secrets
that
I
think
like.
Maybe
maybe
we
just
kind
of
avoid
dealing
with
secrets
for
now
as
best
we
can,
until
we
figure
that
out
and
then
and
then
I'll
create
issues
for
the
other
cookbooks,
and
we
probably
still
need
to
do
like
an
audit
as
well
to
make
sure
we're
not
missing
anything.
A
C
A
Yeah,
that
would
be
great
so
for
the
demo
tomorrow,
it's
gonna
do
like
showing
showing
console
configured
and
ansible,
but
it
won't
be.
It
will
just
be
running
right
now,
like
it's
not.
I
can
yeah
I'll
I'll
continue
to
try
to
demo
that,
and
maybe
we
can,
we
can
also
demo.
I
don't
know
if
we'll
be
able
to
demo
petroni
like
we
have
to.