►
From YouTube: 2022-11-16 Delivery:System Sync and Demo
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
A
Welcome
everybody:
this
is
16th
of
November,
2022
delivery
system,
sync
and
demo.
Thank
you.
Everybody
for
joining.
We
have
few
discussion
points
nothing
to
demo
today,
but
I
guess
very
important
discussion.
Point
I
should
review
Ahmad.
Do
you
want
to
start
to
verbalize
yours.
B
Here,
quick
update
about
the
clusteric
construction.
Today
we
merge
the
drumbook.
Finally,
so
it's
all
good
I
think
one
one
thing
that
comes
next
is
I
also
created
the
fourth
cluster
yesterday
to
prove
that
we
can
do
N1
Mr
using
terraform
that
we
can
create
the
cluster
and
the
DNS
and
everything
just
works.
B
B
So
I'm
not
entirely
sure
actually,
if
we
can
achieve
this
Swedish
to
rebuild
other
cluster
and
I,
think
this
somehow
collides
with
a
point
that
Kelly
added
that
we
can
drop
the
cluster
rebuild.
Okay
are
entirely
I'm,
not
sure
so.
A
Okay,
maybe
then,
let's,
if
you
I,
mean
add
whatever
you
need
to
add,
maybe
we
can
revisit
back
your
point
after
we
discuss
Point
C
true.
B
So
just
another
thing
is
yeah
like
destroying
and
creating
cluster
automatically
using
terraform
locally
got
some
comments
and
some
discussion
items
on
the
issue,
but
still
there's
also
I'm,
not
sure,
if
it's
impacted
but
by
the
foundation
team
awning
kubernetes
next,
so
it
seems
like
the
some
of
the
issues
are
already
like
somehow
dissolving
on
on
their
own,
somehow
I'm,
not
sure
so.
B
A
Perfect,
thank
you.
I
I'm
I
will
try
to
speak
with.
I
spoke
with
Alan
today
about
also
foundation's
team
and
I'm
gonna
have
the
next
week
when
I
come
back
since
I'm
Asia,
Asia,
Pacific
friendly
right
now,
it's
time
zone
with
Pierre
and
Felipe
also
to
understand
where
they
stand
with
that
and
with
Analisa,
that
is,
their
manager.
A
I
know
that
there
would
be
you
know
a
bit
of
a
shuffle
in
all
of
it
in
general,
you
know
like
people
moving
around
and
maybe
team
gets
bigger,
other
teams
get
smaller
and
so
on
so
I'm
not
sure
what
he's
actually
right
now
the
remit
of
all
these
quotes
and
everything.
Definitely
there
is
some
overlapping
with
foundations
team,
but
it's
not
yet
clear
to
me,
which
is
the
overlap,
something
that
probably
will
be
a
bit
clearer
in
q1,
so
I
am
not
I
mean
I'm
more
than
welcome.
A
If
we
have
Solutions
already
in
place
for
some
of
the
problem
we
need
to,
we
need
to
tackle,
but
I
think
we
shouldn't
stop.
We
shouldn't
stop
here
with
what
we
are
trying
to
achieve
right.
So,
let's,
let's
move
to,
let's
discuss
team
Point
c
a
bit
better,
so
we
can,
you
know
also
align
with
the
and
also
has
been
but
I
I'm
working
to
keep
it
and
just
progress
on
that.
Then
then
dropping
it.
B
One
one
thing
is
the
cluster:
rebuild:
is
Swedish,
Jenny
are
going
to
be
the
release
manager,
so
I'm,
not
sure,
as
I
said,
like
who's
going
to
take
care
of
this
part,
we
can
do
it
this
week,
but
I'm
not
sure
if
we
can
shrink
it
this
week.
Taking
in
consideration,
Friday
is
friends
and
family
day
were
found
in
friends
day,
so
I'm
not
sure.
C
So
what
of
our
goals
after
we
created
the
rum
bug,
was
to
go
through
that
run
book
and
determine
all
the
paints
or
paints
and
determine
all
the
points
of
contention
and
I.
Think
this
revolves
around
you
know
creating
another
cluster
rebuild
and
just
verifying
that
our
runbook
works
as
desired,
but
also
identifying
creating
issues
for
all
the
stuff
that
we
simply
don't
like
in
the
procedure.
You
know
like
I,
don't
like
the
fact
that
we
need
to
do
some
manual
work
inside
of
tarot
form,
for
example.
C
C
And
I
say
this:
thinking
that
being
able
to
rebuild
a
cluster
should
be,
you
know
just
one
day's
worth
of
work.
So
really
there
shouldn't
be
a
lot
of
impact
and
that's
something
I
could
probably
tackle
now
that
we've
got
some
release
major
swaps
happening
and
then,
after
we've
identified
all
the
issues
that
we
want
to
work
on,
we
could
prioritize
it
and
then
hypothetically
it'll
be
small
enough
chunk.
A
A
D
A
D
Quebec
and
McKelly
were
sort
of
cutting
out
in
between.
A
I
I
guess
we.
We
still
need
to
go
back
to
the
last
point
that
you
made
John
I
totally
missed
that
part.
C
D
C
A
Okay,
I
was
saying
that
we
lost
your
your
last
point
that
you
were
making
so
I'm,
not
sure
if
you
can
go
back
to
that.
C
I
vaguely
recall
I
was
saying
I'm
thinking
with
the
flip
of
release.
Managers
I
could
tackle
the
work
of
like
maybe
doing
a
rebuild
cluster
testing
session,
and
then
I
could
write
down
all
the
stuff
that
you
know,
I
think
is
painful.
I
think
it'd
be
wise
if
more
than
one
of
us
was
able
to
be
a
part
of
that
process.
Just
to
you
know
two
people
going
through
it.
Those
two
people
provide
input
as
to
the
pain
points
that
we
identify
and
stuff
that
we
think
are
valuable
to
fix.
C
We
could
go
through
as
a
team
to
prioritize
set
issues
and
then,
as
it
doesn't
matter,
who's
release
major,
hopefully,
we've
got.
The
bits
of
work
is
slimmed
down
enough
where
it
doesn't
matter
if
your
release
manager,
hopefully
time,
can
be
spent
that
way.
You're
not
suffering,
is
release
major
but
still
contributing
to
our
okrs
as
well.
A
Okay
sounds
good:
who
wants
to
take
the
action
of
clarifying
a
bit
more
the
memory
explicit
about
the
work
we
want
to
do
next?
What
you
were
mentioning
before
John.
C
I
would
like
to
nominate
agma
to
tackle
that
clarification,
just
because
he's
been
closer
to
that
work
at
the
moment
and
he
could
kind
of
provide
guidance
as
to
what
clearly
should
the
next
steps
be,
and
then
you
know
one
of
us
could
pull
that
work
in.
A
A
Perfect,
shall
we
move
to
point
B
onus
to
yours,
foreign.
C
After
learning
that
the
reliability
team
is
creating
a
team
called
foundations,
I
feel
like
we
need
to
better
understand
what
their
ultimate
goals
are,
because
if
they're
going
to
be
the
team
that
wants
to
own
the
kubernetes
infrastructure,
I
think
this
is
fine.
It
just
kind
of
shifts
the
style
of
work
that
we
end
up.
Working
on.
C
C
There
is
a
not
necessarily
contention,
but
there
are
some
conflicting
objectives
with
how
that
team
may
want
to
manage
clusters
with
the
way
that
we're
currently
testing
our
capabilities,
and
if
those
opinions
are
going
to
remain
strong
enough
where
it's
impeding
work,
then
we
really
want
to
figure
this
out.
You
know
soon,
whereas
if
it's
more
like
a
situation
where
we
could
keep
chugging
on
with
the
work
that
we
are
working
on,
and
then
we
could
maybe
toss
off
this
responsibility
later.
That's
probably
okay
as
well.
I,
guess,
I'm!
C
A
A
Understand
you're
right
is
what
I'm
trying
to
figure
it
out
with
today.
What
I
was
speaking
with
dalan
and
I?
Guess
I
would
figure
it
out
a
bit
more
also
who
are
speaking
with
Analisa
as
well.
Alan
right
now
doesn't
seem
that
that
he
doesn't
want
to
say
okay,
zoning
like
kubernetes.
A
If
we
need
to
step
some
boundaries,
I
think
probably
core
infrastructure,
maybe
should
own
everything
that
is
like
you
know,
gcp
cluster
itself,
until
the
apis
and
from
the
API
is
on.
It
should
be
something
that
where
we
plug
ourselves
in
this
is
not
a
clear
it's
not
clear,
at
least
where
Audis
is
going
to
be
structured.
They
are
working
on
that
and
when
I
ask
for
timelines.
Definitely
this
is
not
something
it's
going
to
come
in.
Q4.
A
Is
this
something
that
we
can
probably
hope
to
have
a
bit
more
clarity
in
q1,
you
said
that
I
will
also
try
to
understand
where
Analisa
Philippe
and
here
and
everybody
is
in
on
on
this,
and
if
there's
something
in
mind
that
would
work
on,
especially
in
the
next
quarter,
but
from
what
I
found
in
a
lie
for
their
okrs.
A
A
So
I'm
I
don't
see
anything
that
is
going
in
the
direction
of
what
we
want
to
achieve.
Okay,
on
the
other
end,
I
can
totally
see
that,
maybe
later
on,
the
work
we
are
doing
now
will
probably
be
kind
of
say,
change
ownership
and
go
a
bit
more
on
their
side
right.
A
The
part
that
I'm
trying
to
not
so
I
would
like
to
do
two
things
right
now.
There
is
not
I
want
to
understand
what
they
want
to
do
strategically.
Where
is
their
Vision,
at
least
in
the
legs,
in
the
next
two
three
quarters
where
they
want
to
go
when
we
know
that
we
can
understand
where,
if
we
can
align
our
roadmaps?
A
Because
if
right
now,
we
are
just
like
hoping
for
them
to
take
this
work
and
complete
it
in
in
the
way.
We
want
I'm
afraid
that
we
are
gonna
like
end
up
in
a
in
a
waiting
Loop,
and
we
is
gonna,
probably
postpone
the
Direction
Where
We
want
to
go
with
with
this
right,
because
we
are
not
simply
building
the
capabilities
of
rebuilding
clusters
just
for
the
sake
of
rebuilding
them,
but
we
are
actually
trying
to
build
this
functionality
because
we
want
to
actually
to
go
somewhere
else.
Next
right.
A
We
want
to
build
on
top
of
these
functionalities,
maybe
like
maybe
enable
us
to
do
Google,
looking
deployment
enable
us
to
to
have
to
have
the
company
to
deploy
risky
changes
and,
and
so
on.
A
So
for
the
this
is
also
going
to
point
c
a
bit
for
this
quarter.
I
I
would
say
that
we
should
still
like
keep
iterating
on
what
we
built.
A
Maybe,
since
we
are
pretty
busy
with
the
scope
over
release
measurement
as
well,
because
we
have
an
exploitations
where
we're
gen
in
Ahmad
are
in
full
rotation
is
also
having
the
rotation.
After
that
plus,
we
have
a
Vladimir
joining
us
in
13
days
from
now
where
it
will
have
to
ramp
up
and
we'll
also
to
support
him
in
his
onboarding.
So
there
will
be
definitely
less
Firepower
to
tackle
our
hairs.
So
maybe
is
the
reason
why
I
also
had
the
point
C
to
understand
what
we
want
to
do
with
that.
A
But
going
back
to
your
point,
Scarborough
Israel
I
really
want
to
do
that.
I'm,
not
sure
this
is
in
their
roadmap
or
at
least
not
in
this
shape
and
the
form
you
want
it.
For
the
next
couple
of
quarters,
foreign.
C
I
think
that's
fine,
the
I
guess.
The
thing
that
I
want
to
point
out
is
that
you
know
if
we
I'm
not
trying
to
push
this
work
on
other
people
yeah.
If
we
want
to
maintain
this
I,
think
that's
fine.
It's
probably
just
it's
just
not
in
alignment
with
the
delivery
team
goals.
You
know
our
primary
goal
is
mtdp
and
making
sure
we
deploy
wherever
as
quickly
as
possible
in
closer
ownership
kind
of
takes
us
away
from
being
able
to
achieve
that
goal.
To
some
extent.
C
We
certainly
want
to
be
involved
and
we
certainly
want
to
be
part
of
driving.
You
know
what
we
want
to
see
and
be
able
to
integrate
or
tooling
with
it.
But
if
that
team
is
has
a
desire
to
take
over
cluster
usage,
we
could
focus
our
efforts,
like
you
mentioned
on
stuff,
like
blue
green
deployments
and
other
fun
things
that
we've
had
ideas
for
in
the
past,
which
I
think
would
be
a
good
benefit
to
us.
C
But
with
that
mind,
maybe
we
should
just
keep
going
with
our
current
okr,
which
I
think.
At
that
point,
we
should
discuss
more
of
your
point,
C,
primarily
because
what
I
just
proposed
after
the
discussion
for
the
first
point,
we're
kind
of
contradicting
each
other
in
terms
of
what
we
want
to
accomplish
in
the
next
few
weeks.
Yeah.
A
So
I'm
I
told
you
I'm
going
to
keep
investigating
on
that
and
whatever
we
are
doing
now
is
not
going
to
be
wasted.
We're
still
like
contributing
anyway
to
infrastructure
goals
and
everything.
I
will
try
to
build
some
extra
Clarity
around
that
part
and
so
on,
just
to
be
sure
for
the
time
being,
maybe
let's
discuss
Point
c,
as
you
said,
and
trying
to
understand.
A
Okay
with
the
current
like
think
capacity,
let's
review
our
key
results
that
we
set
for
ourselves
for
the
foreign
and
understand
how
we
can
maybe
reduce
the
scope
slightly
to
still
keep
it
like
achievable,
but
also
aspirational
and
challenging.
At
the
same
time,.
A
So,
currently,
our
okrs
O'hare
was
like
in
increasing
the
what
it
is,
the
reliability
of
and
repeatability
of,
cluster
rebuilds.
A
The
first
key
result
that
we
added
there
is
to
have
a
foolproof
run
book
that
can
be
like
executed
with
not
so
much
like
step
by
step,
not
so
much
brain
power
just
like
something
that
is
really
proof
that
we
can
repeat
continuously
the
other
key
result.
We
added
was
to
rebuild
an
additional
Rebuilder
staging
cluster.
A
So
say
that
we
are
We
Are,
One,
Step
Closer
to
the
first
key
result,
because
I
mean
just
today
we
merged
them
book,
and
we
know
that
we
have
some
some
parts
that
we
need
to
optimize
right
to
execute
that
as
a
single
match
request
and
a
lot
of
parts
that
we
want
to
surface,
identify
the
gaps
and
trying
to
improve
the
experience
around
the
execution
of
that
runbook.
A
What
about
do
you
think
that
only
keeping
these
key
results
will
be
something
feasible
to
achieve
in
Q4,
seeing
their
current
team
capacity
for
the
next
three
months.
C
In
that
cluster
rebuild
should
take
less
than
a
day.
It
took
akbud
Lake
his
entire
day,
but
like
it
should
take
less
than
a
day
from
the
result
of
that
work,
we
should
have
a
bunch
of
issues
that
contribute
to
the
second
akr,
which
is
trying
to
figure
out
how
to
make
it
more
a
more
friendly
operation.
C
A
That
is
like
his
work
to
do.
We
have
limited
capacity,
is
being
some
value
if,
for
whatever
reason,
we
are
able
to
do
all
the
work
done,
no
one
is
preventing
us
to
continue,
and
you
know
I'll
do
the
rebuild
this.
This
staging
cluster,
the
Epic
that
we
put
in
place
is
already
clear
enough
also
to
establish
like
the
the
next
Milestone
or
the
one
of
rebuilding
the
decision.
A
Cluster,
so
I
would
say,
let's
put
ourselves
in
a
situation
of
having
the
first
result
as
a
achievable
and
then
anything
guys
that
come
on
top
of
that
is
added
value
again
the
value
we
are
building
up
here.
Maybe
it's
not
going
to
stay
in
the
increment
of
our
team,
but
it's
still
gonna
something
that
we're
gonna
benefit
from
for
where
we
want
to
go.
So,
let's
try
to
also
see
that,
because
I
mean
it
doesn't
mean
that
a
lot
of
things
that
we
are
building
right
now
as
well.
A
If
we
are
looking
at
the
pipeline,
Foundation,
stuff
and
so
on,
we
are
also
Ruben.
Is
the
dri
I'm
quite
sure
that
some
of
this
part
soonerly
they
will
end
up
on
observability
group
capabilities
right
because
they
will
also
have
to
probably
monitor
pipelines,
and
this
is
what
we're
trying
to
do
right
now
is
actually
building
this
functionality
that
will
be
sooner
or
later,
I'm
quite
sure
we
will
end
up
in
the
product.
A
Do
you
think
that
only
the
first
key
result
is
a
allow
me
the
word
to
ease
to
achieve
or
is
still
like
challenging
enough
for
us?
Thank
you
for.
A
C
A
A
A
Actually,
he
takes
a
step
about
being
the
infrastructure
doing
that
so
I.
Actually
you
know
we
are
the
objective
and
then
the
heat
results
are
actually
part
that
you
see
you
link
in
the
Epic,
but
they're
not
really
added
there.
A
I
will
try
to
be
a
bit
more
clear
on
the
objective.
We
are
in
a
lie
trying
to
to
say
where
we
want
to
go
and
everything
and
everything
that
it
comes
on
top
of
that
is
going
to
be
extra
value
that
we
we
add
to
this.
A
Anything
that's
as
to
what
previous
discussion
for
today.
C
A
Okay,
Ruben,
since
we
are
speaking
about
okay,
Arts,.