►
From YouTube: Dev Environments demo 2022 10 19
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
Hi,
my
name
is
rosalar
and
I'm,
going
to
give
you
a
short
presentation
about
the
fear,
then
development,
environments,
project
and
the
progress
that
was
made
on
the
screen
on
the
screen.
You
can
see
that
I
already
created
an
image
that
we
will
be
using
in
this
presentation.
The
creation
of
the
image
is
automated
up
to
a
point
of
having
a
CI
that
will
be
automatically
creating
a
images
on
every
push
to
the
repository
and
the
automation
is
done
by
ansible.
A
A
So
basically
we
only
provide
the
branch
that
for
backend
and
for
UI
that
the
virtual
machine
should
be
built
from
and
a
Zone
if
the
default
one
in
Europe
is
not
what
we
are
we're
after
so
generally,
we
should
try
to
minimize
the
latency,
so
the
closer,
the
VM,
the
better.
So
let's
create
a
VM
5.
A
A
So,
let's,
let's
try
to
log
in
oh,
it's
SSA
is
SSH,
is
not
yet
the
red
so
why
we
ate
why
we
equate
I
would
like
to
only
point
out
that
some
of
the
activities
here
will
take
a
long
time.
So
I
took
a
laboratory
to
add
10
to
post
process
the
video
and,
at
some
point
as
some
of
the
some
of
the
parts
of
the
video
will
be
sped
up.
A
So
we're
in
okay
and
now
the
more
TD
already
gives
the
developer
some
useful
information.
So,
first
of
all,
we
need
to
add
this
into
ATC
or
hosts
on
our
laptop
and
I've
created
a
tool
that
automate
that
gives
some
better
overview
for
developers.
What
exactly
is
happening
and
at
what
stage
the
machine
is
currently
when
it
comes
to
bootstrapping
the
environment
and
it's
adapt
to
that
is
step.
A
Two
cretino
is
divided
into
Stage,
like
executes
in
stages,
so
here
we
have
like
networking,
information,
addressation,
wireguide,
U,
AI,
bootstrapping,
verification
of
branches
and
etc,
etc.
So
these
are
all
important
informations.
That
developer
may
need
once
the
two
reports
that
the
machine
is
ready
to
level
bar
can
start
using
it,
but
more
about
it
later.
A
First,
and
so
why,
while
we
are
added,
it's
important
to
note
that
we
that
the
tool
itself
very
and
also
does
some
sanity
attacks
so
to
so
that
developer
does
not
have
to
debug
things
on
their
own.
So,
for
example,
the
bra
the
branches
that
we've
passed
to
The
Tool
during
creation
of
the
virtual
machines
are
verified
if
they
are
indeed
containers
built
for
these
branches.
If
they
are
not,
the
two
will
fail
and
we
refuse
to
Proto
continue.
A
So
this
prevents
a
situation
when
we
have
container
pull
back
off
and
we
can
be
sure
that
any
other
that
any
later
stages
are
are
can
succeed,
can
indeed
succeed.
So
apart
from
that,
just
also
tools
suggest
that
you
can
that
one
can
follow
the
bootstrap
process
more
closely
by
by
using
roon
on
CTL
tool.
So,
let's
login.
A
So
a
developer
machine
is
already
set
up
in
a
way
that
you
can
suit
out
to
any
user
and
you
can
log
in
to
developer
and
you
don't
need
to
manage
Keys
the
GC
does
it
for
you.
So
as
long
as
you
have
enough
privileges
on
egce
in
the
dev
in
our
upstrates
Dev
development,
environment,
you're
good
to
go,
you
don't
have
to
worry
about
anything.
That's
done
automatically!
So
let's
try.
A
The
service
is
called
Booter
and,
as
you
can
see,
it
does
various
things
like
G,
starting
GDK
warming,
a
GDK,
app
setting,
password,
etc,
etc.
The
two
is
written
in
go
and
you
can
see
it
in
the
repository,
so
it
takes
some
time.
So
maybe
I
will
show
you
the
repository
in
the
meantime
on
as
you
can,
then
here
you
will
be
able
to
see
our
VM,
but.
A
And
I
already
I
also
share
my
notes.
What's
still
to
do
what's
not,
and
it's
not
everything
is
polished
yet
so
there
are
two
bugs,
however,
and
or
bikes
for
to
do
if
you
prefer
that
I
still
need
to
take
care
of,
and
some
automation
left
more
about
it
at
the
end
of
the
presentation.
A
But
here
also
you
have
ansible
playbooks
and
the
Booter
itself.
The
butter
is
divided
into
like
the
system,
part
that
does
all
the
all
the
activities
like
bootstrapping
GDK,
creating
tenant
waiting
for
other
controllers
to
get
ready,
Etc
and
they
use
the
robs,
which
is
basically
the
presentation
layer
that
we
see
here.
As
you
can
see,
the
kind
cluster
is
creating
so
here
in
the
logs
and
here
in
in
the
two
in
the
Booter
tool
itself,
so
the
in
case
something
goes
wrong.
A
The
systemd
will
restart
the
Booter
and
the
Buddha
will
try
to
try
again.
The
Booter
is
indepotent.
So
if
Terrace
Wilson
was
transient,
error
like
Network
glitch
or
like
record
history
was
temporarily
and
available,
it
would
then
Booter
will
retry,
and
it
will
also
try
to
give
you
helpful
error
message.
What
went
wrong
and
what
which
one
exactly
place
to
work
on
you?
What
can
you
do
to
maybe
fix
it,
but
the
main
idea
in
with
which
this
system
was
designed
is
to
keep
it
simple.
A
So
if
you
break
it
just
create
a
new
one,
it's
meant
to
be
fixable
by
providing
an
a
new
machine.
Now.
A
The
machine
itself,
maybe
a
few
words
while
the
Boost
system
is
still
bootstrapping,
is
a
bit
over
provisioned.
So
in
here
we
could
fit
into
a
smaller
machine.
So
like
a
smaller
Russian
in
the
in
the
series
is
like
four
CPU
16
gigs
of
RAM,
but
this
is
like
a
very
tight
fit
and
so
I've
made
a
decision
to
pick
a
bigger
machine
so
that
we
have
some
spur
capacity
and
we
don't.
A
We
avoid
some
weird
timeouts
and
errors
and
have
some
space
for
our
developers
to
experiment
in
case
they
want
to
debug
or
maybe
launch
something
heavier
on
the
cluster.
The
drawback
of
this
approach
is
that
the
bigger
machine
costs
200
dollars
per
month.
If
we
wanted
to
learn
it
continuously,
the
cheaper
machine
is
up.
One
is
only
100,
it's
up
for
discussion,
just
pointing
it
out.
Now.
A
Let's
see,
maybe
something
already
is
available.
Oh,
why
would
the
putter
is
booting?
We
can
already
create
a
wire
guard.
We
can
access
the
wire
guide.
So
here
we
have
UI
address
sorry,
we
have
address
and
it's
worth
noting
that
the
tool
itself
randomizes
password.
So
every
time
the
bootstrap
VM
is
bootstrapped,
there
will
be
different
passwords
for
security.
So
there
is
no
such
thing
like
I've
read
all
the
VMS
have
the
same.
Password
is
late
where
and
we
have
a
problem
now.
A
Passwords
are
randomly
generated
and
another
nice
thing
about
the
system
is
that
one
moment
five
thousand.
A
Okay
certificates
are
safe,
signed
a
new
client.
A
I'm
not
sure
so
I
need
to
have
a
look
why
it
wasn't
why
I
wasn't
asked
to
log
in
I
need
to
verify
this,
but
we
said
another
session,
I
don't
know
but
anyway,
so
this
doesn't
work.
Maybe
this
is
a
problem
with
wire
guards.
Still
we
need
to
debug
it.
So
this
is
like
something
to
do,
but
anyway
new
client,
let's
call
it
P
Rose
lag.
A
So,
depending
on
the
platform
you're
on
Mac
Linux
and
what
kind
of
distribution
you're
using
it
may
be
a
different
way
to
import
wireguard
profile
on
Ubuntu.
This
is
the
command
it's
already
out.
The
profile
is
already
activated
and
we
can
already
try
to
login
to,
for
example,
gtk.
A
A
For
gtk
to
start
and
to
compile
webpacks
and
that's
one
and
whatnot,
so
we
get
a
bootstrapped
gtk.
Unfortunately,
there
is
also
a
problem
with
gtk
itself,
because
at
some
point
during
the
bootstrap
process
it
dies
and
I
need
to
debug
it.
Why?
But
again
another
thing
for
my
to-do
list,
but
this
is
unrelated
to
the
automation
tool.
This
is
like
the
problem
with
GDK
itself.
It
seems
now
again
randomized
password
sign
in.
A
Gtk
already
is
profit
pre-configured,
so
observability
feature
is
enabled
and
all
our
tokens
are
created
and
so
on
and
so
on
and
oh
cubeconfig
is
ready
to
be
downloaded.
So,
let's
log
into
the
machine,
oh
here
we
have
some
information
also
about
what
the
machine
is
where
the
machine
is
or
the
IPS
and
whatnot.
But
anyway,
and
in
order
to
download
Cube
CTL,
we
need
to.
A
To
a
remote
instance
and
using
kubernetes
cluster
as
if
we
it
was
locally,
so
we
no
longer
have
a
problem
or
with
a
different
architectures
arm,
X8
arm,
AMD
64.,
it
simply
works
and
you
you
can
use
telepresence
and
any
other
tool,
because
the
latency,
if
you
picked
machine
close
to
your
location,
low,
Zone,
to
close
your
location,
it's
really
small
and
it
works
really
great.
So
let's
get
an
overview.
A
It's
going
to
overview
what's
happening,
so
gatekeeper
is
bootstrapping,
so
it
would
take
some
time
before
it
starts
and
you
can
see
ensure
Gob
cluster
is
deployed
so
waiting
for
cluster
to
become
ready.
Two
is
waiting
for
us
for
cluster
to
get
ready
now.
The
wire
guard
also
makes
it
easy
to
share
with
when
people
you
just
need
to
create
a
new,
a
new
profile
and
it
works.
Anybody
can
just
download,
and
you
can.
A
You
can
just
give
the
password
and
username
for
wireguard
UI
to
product
manager
or
something
on
your
colleague,
and
they
can
create
a
profile
for
themselves
or
you
can
send
them
a
profile
guide
profile.
They
connect
and
they
have
us
at
the
same
access
as
you
do
to
gitlab
Cube,
kubernetes
and
Gob
backend.
Now.
A
So
we
need
to
wait
a
moment.
So,
let's
speed
up
a
bit
now,
action
auxiliary,
manifests,
are
deployed
so
in
order
to
make
Gob
tenant
accessible
I,
we
are
deploying
methanol,
B
and
making
and
VIP
I've
done
a
load
by
another
additional
load.
Creating
low
additional
load,
balancer
Service
with
VIP
address
that
is
accessible
from
the
workstation
from
the
developers
workstation
and
now
it's
being
deployed
so
D1
set,
is
getting
started.
A
Now
and
now
we
are
deploying
the
Gob
tenant.
I
think
this
is
the
last
stage
and
again
this
is
fully
automated
developer
doesn't
have
to
do
anything.
The
Gob
tenant
is
created
with
one
exception,
so
it
turned
out
to
be
so
I'm,
not
sure
we
should
be
automating.
A
But
again,
this
is
something
maybe
we
can
maybe
want
to
discuss
for
now.
There
is
one
very
simple
step
for
developer
that
they
need
to
do
once
their
bootstrap
process
is
done
in
order
to
finalize
the
provisioning
of
tenant.
We
will
get
to
this
in
the
moment.
Let's
have
a
look
where
we
are
also
it's
Jaeger
is
still
deploying.
A
Oh
Jager
is
running,
so,
let's
see
if
this
was
it.
No
so
Booter
is
created,
is
waiting
for
gitlab
observability
in
a
gitlab
namespace
to
get
ready,
and
let's
wait
a
moment
in
the
meantime.
Here
again,
we
have
of
tokens
printed
for
developers
convenience
some
additional
information
like
how
to
copy
Cube
CTL.
The
cube
CTL
is
already
prepared
in
a
way
that
allows
accessing
from
the
developers
workstation
so
export
it
from
kind
and
IP
addresses
are
adjusted
so
that
developer
doesn't
have
to
and.
A
Yeah,
oh
and
we're
done
so:
let's
we
need
to
visit
provision
provisioning
page
another.
We
need
to
visit
visit
this
URL
in
order
to
finalize
the
provisioning.
So,
as
I
said,
because
of
the
way
the
gatekeeper
works
automating,
this
this
part
was
pretty
difficult,
so
I
I
choose
to
have
once
more
manual
step
for
developer
left.
A
So
I'm
not
sure
why
it's
happening
like
gitlab
is
because
the
tool
verifies
after
starting
gtk.
The
GDK
is
running
some
somewhere
along
the
way.
Gtk
is
just
stopping
or
giving
up
and
I'm
not
sure.
Why.
A
While
we
wait
for
gitlab
to
start
another
thing
that
needs
polishing
is
that
we
then
there's
some
work
work
needed,
because
in
order
to
be
able
to
see
observability
UI
embedded
in
git
lab,
we
need
to
access
GDK
or
gitlab
gtk
using
IP
and
not
the
domain.
This
is
due
to
how
DNS
resolution
currently
works
in
the
cluster,
and
it's
on
my
to-do
list.
A
Just
quite
a
little,
and
while
we
wait
we
can
already
open.
The
two
are
also
provides
you
with
the
link
to
the
group
that
was
chosen
for
observability.
So
this
group
is
picked
every
time
during
the
bootstrap
and
there
are
then
groups
differ
between
machines,
but
the
for
every
machine.
The
same
group
is
about
for
each
machine.
The
same
group
is
always
the
same
group
is
chosen.
So
let's
open
this
group,
oh
as
we
can
see,
gitlab
observability
UI
is
already
working.
A
It
works
so
developer
gets
out
of
the
box
gtk
and
Gob
configured
together
with
embedding
working,
so
they
can
immediately
start
developing
and
working
on
it.
So
this
concludes
my
presentation.
I
hope
you
liked
it.
There
are
still
some
things
to
do,
but
I
think
it's
pretty
usable
by
now.
Let
me
know
what
you
think
and
feedback
is
very
welcome.
Thank
you.