►
From YouTube: 2022-09-21 - Delivery:Orchestration demo - EMEA/AMER
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
Awesome
so
welcome
to
another
delivery,
orchestration
demo.
This
is
our
emir
america's
scheduled
one,
hey
myra,
just
getting
going
so
alessia
you've
got
the
first
item.
B
C
A
Yeah,
I
think
I've
done
this.
Let
me
just
quickly
show
you
what
I
did
because
I
think
I've.
A
Cool,
so
I
just
like,
I
think
we
had
it
pretty
much
on
here.
We
already
had
this
step,
which
was
create
the
git
tag.
I've
just
added
in
here.
This
was
the
pretty
much
the
sort
of
essential
part
of
the
of
the
other
issue
that
I
have
closed
out
and
moved
into
here,
which
was
to.
A
To
update
to
basically
specifically
update
the
tag
in
the
getlab
pages
repo,
and
we
want
that
to
be
the
sha.
A
A
C
Was
right,
yeah?
Now
what
I'm
thinking
I
mean
it's
fine!
What
I'm
thinking
is
that
this
one
kind
of
these
are
the
steps
in
in
the
to-do
and
then
the
definition
of
them
was
more
about
it.
Are
those
things
completed,
part
of
the
of
what
we've
done.
B
C
A
C
That's
supposed
to
be
there:
that's!
Okay!
Okay,
that's
in
the
right
position
in
the
right
spot.
This
is
basically
the
all
the
things
that
we
have
right
now
are
things
we
do
in
pages,
and
this
is
one
part
of
it.
Then.
The
second
part
is
that,
as
we
reach
the
the
gitlab
repo
which
we
do
after
the
components,
we
should
make
sure
that
the
things
we
did
above
are
reflected
in
the
yeah.
A
Does
this
overlap
with
the
rollout
plan,
because
some
of
these
things
like,
for
example,
like
we
got
like
tagging
up
actually
sagging
a
security
release
like
they
feel
very
much
like?
A
C
So
when
we
switch
from
version
1.6.7
to
15.3.4?
How
do
we
make
sure
that
the
next
security
release
will
act
correctly
on
on
the
previous
one
that
we're
not
in
the
thing.
B
Go
ahead,
mara,
yeah
thanks.
I
was
checking
the
list
of
the
definition
of
dawn
and
I
didn't
see
tracking
on
the
environments,
and
that
is
something
that
we
also
do
when
we
talk
a
patch
release
or
a
monthly
release
or
a
security
release,
and
the
tracking
is
also
like
spread
for
italy,
for
example,
is
that
something
that
we
are
also
thinking
of
doing
for
pages?
B
B
Is
it
this
one
2582?
A
C
This
is
the
original
one
that
graeme
wrote.
A
B
A
C
A
So
it
sounds
like
that
issue
that
we
were
just
talking
about
is
fine,
and
that
is
the
issue
which
basically
does
all
the
changes
to
the
tagging,
and
we
also
do
all
the
testing
that
those
tagging
changes
are
working
correctly.
C
Yeah
I
mean
I
I
didn't.
I
was
in
grimm's
mind
when
he
wrote
that,
but
I
was
my
idea
of
reading.
That
is
something
like
we
can
call
this
done
when
we
actually
have
gone
through
all
those
type
of
releases
and
are
sure
that
they
are
working,
which
is
a
way
of
looking
at
this.
The
other
one
could
be
just
we've
done
the
work
we
say
it's
done,
and
then
we
open
follow-up
issues
for
bug
if
they
don't
work
with
a
certain.
A
Time,
I
think
it's
worse.
I
agree
and
I
chatted
about
it,
and
I
think
I
mean
the
only
downside
is
we
potentially
have
an
issue
open
for
a
month,
but
I
think
getting
it
all
in
one
go
and
making
sure
we
have.
The
test
done
is
probably
worth
that
overhead
cool.
Okay,
great.
Do
you
want
me
to
have
another
guy
editing
that
alessio
or
is
it
quicker
future.
C
Thank
you.
You're
welcome
no
problem.
So
there
was
a
action
item
b,
I'm
not
sure
what
what
was
that.
So
I
think-
and
this
is
why
I
mentioned
before
about
rollout-
that
this
is
2601
but
yeah.
There
was
no
description,
just
our
title
and
I
wrote
this.
C
A
Yeah,
so
this
was
about
the
discussion
we
had
around.
What
do
we
want
to
do
specifically
around
security
releases,
but
also
back
ports
around
the
fact
that
I
think
I
think,
there's
a
fairly
bigger
sum.
Well,
I
think
there's
an
assumption.
At
least
in
my
head
of
versions,
will
change.
C
A
A
A
B
A
C
Okay
down
item
c
issue:
35
pages
can
be
built
from
sha
it's
there
and
then
I
had
an
action
item
for
myself,
which
was
writing
an
overview
of
the
process
for
developers.
I've
done
this
I'm
guilty
because
I
didn't
check.
I
just
asked
graham
to
review
it
and
forget
about
it
so
today
I
say
I
did
something
about
this:
where
is
it
and
so
I'm
guilty
of
not
following
up
with
my
own
actions,
so
thank
you.
Amy
for
fixing
the
diapers.
A
Yes,
all
right,
that's
right!
Well,
listen!
Games
out!
So
I'm
like
super
keen
on
this
one.
What
I
wanted
to
check
in
it
like,
I
think
it
looks
perfectly.
I
think
it
looks
definitely
good
enough
to
be
putting
in
front
of
developers.
So
am
I
right,
then,
if
you've
got
all
the
contacts
on
this,
we
are
at
the
point
where
we
want
to
double
check
that
the
pages
maintainers
are
happy
with
the
changes
that
will
happen
as
a
result
of
us
making
this
change.
A
So
there
are
some
benefits,
but
there
are
also
some
slight
downsides
or
changes
that
will
come
when
we
do
this,
so
we
discussed
just
making
sure
they
were
fully
aware
of
like
this
is
what's
actually
going
to
change,
and
so
that's
what
this
mr
is
about,
but
one
question
I
had
for
you
let's
see
is
I
see
I
recall
well,
at
least
in
my
mind,
it
felt
like
we
had
quite
a
big
conversation
about
what
they
would
potentially
lose.
A
Is
it
really
just
that
you
like
the
changelog
must
be
to
get
like
format.
The
the
version
must
be
the
gitlab
format
and
was
there
also
something
we
talked
about
like
potentially
developers?
Maybe
not?
A
C
C
What
is
that
yeah
that
maybe
is
not
called
out
explicitly
but
because
it
say
everywhere,
it's
it
tells
you
that
the
you
can't
you
cut
release.
When
I
mean
you
don't
cut
release,
we
cut
a
release
when
we
cut
a
global
release,
so
there's
no
room
for
you
for
cutting
out
your
own
releases.
A
C
C
C
Yeah,
I
will
not
so
yeah
this
given
we're
talking
about
this.
I
I
think
we
should
not
spend
words
here
on
explaining
that,
eventually,
you
may
be
able
to
run
your
owners.
A
Project
needs
yeah,
agreed.
Okay,
I
think
for
this,
for
certainly
for
the
sake
of
what
we're
trying
to
do
this
quarter
with
pages
and
cars
like
that
yeah,
let's
focus
on
just
what
we
need
and
add
in
stuff
later.
A
Okay,
stuff
awesome,
but
otherwise
I
think
it
looks
good.
Do
you
want
to
kick
off,
but
let's
go
and
get
that
in
front
of
the
pages
maintainers
and
actually
just
see
if
we
can
get
the
the
kind
of
thumbs
up
to
go
ahead
on
on
making
this
change.
Do.
A
A
Okay,
but
yeah,
I
would
say,
go
ahead
and
merge
this
in
and
then
we
can.
We
can
use
it
for
multiple
approval
things.
B
A
Yes,
thank
you.
I
am
going
to
do
something
similar
with
the
configure
team.
I
want
to
just
make
sure
that
they
are
also
aware
of
the
changes
that
will
come
their
way
from
auto
deploys
before
I
post
this.
I
was
going
to
just
stick
a
comment
on
the
epic
and
then
ping
them
on
there.
I
just
wanted
to
check.
I
had
all
the
pieces
correct
before
I
wrote
something
so
just
to
just
double
check
my
my
understanding
when
they
switch
over
to
autodeploy.
A
I
really
hope
we've
got
our
diagram
right,
so
we're
basically
saying
that
all
of
these
steps
down
here
where
they
currently
open
an
mr
to
change
the
version
image
on
on
pre-staging
and
in
production
that
will
all
just
get
automated
through
our
auto
deploys.
C
C
Now,
what
I
mean
is
that
now
they
have,
they
have
a
manual
process
right,
so
they
are
not
into
managed
versioning,
which
means
that
they
start
by
cutting
a
release
they
cut
release.
Then
they
do
pre,
they
do
some
tests,
then
they
do
staging
and
etc,
etc,
etc.
Right
what.
A
C
C
B
C
A
If
they
test
on
pre,
so
I
might
actually
leave
that
as
a
separate
option
and
then
add
that
as
a
follow-up
of
do
they
use
pre.
I
I
don't
think
they
do.
That's
where
my
money
is.
I
don't
know
this,
but
that's
my
gut
just
because
the
pre
and
staging
come
together
and
I
think
people
more
commonly
test
on
staging
when
they
have
those
things
together.
C
A
It's
essentially
a
a
reorder
right,
so
manual,
mr
bump,
for
pre
needed
what
happens
if
they
don't
do
it
on
pre?
Does
that
matter
that
pre
ends
up
on
a
different
version.
B
C
C
A
C
A
B
C
B
A
Okay,
awesome,
cool.
Okay,
I
will,
I
would
give
them
a
ping
on
the
on
the
issue,
sorry
on
the
epic
and
actually
double
check.
They
are
aware
of
what
will
happen
and
check
they're
good
to
go.
We're
still
waiting
on
the
canary
for
cats,
so
this
isn't
a
straightaway
to
get
going,
but
it'd
be
good
to
get
everyone
kind
of
agreed
for
when
we're
ready.
C
A
Yes,
no,
that's
a
really
good
point,
so
we
have
two
pieces
that
we
need
their
input
in
before
we
can
switch
on
auto
deploys
for
cars.
One
is
we
need
their
input
into
what
metrics
we
should
be.
Tracking
skabeck
has
sort
of
identified
the
gaps
and
has
made
a
suggestion,
but
ultimately
it's
up
to
the
stage
group
to
say
what
we
should
measure
the
other
one
yeah
you're
right
is
the
we.
A
C
C
Yeah!
That's
why
I'm
not
sure
if
I'm
just
thinking
registry
but
we're
talking
about
cats
or
if
because
it's
this
or
if
they
have
the
same
approach,
which
is
still
possible.
A
Yeah,
that's
a
good
point
so
that
one
of
the
issues
on
this
epic
is
your
right
is
to
figure
out
what
that
test
is
I'll,
get
that
kicked
off,
because
actually,
I
have
no
idea
how
big
that
might
be
nothing
or
it
could
be
months
of
work.
I
have
no
idea.
A
Okay,
great
so
three,
we
touched
this
a
little
earlier,
which
is
about.
We've
got
two
issues
which
are
sort
of
for
the
same
problem.
I
wanted
to
just
discuss
these
a
little
bit
and
see
like
do.
We
know
enough
to
be
able
to
pick
one
over
the
other
or
how
do
we
wanna
progress?
These
I'm
things
I
was
really.
B
Introduced
to
those
issues-
and
I
understand
the
one
from
graham's,
which
is
basically
reusing
what
we
have
on
gitlab
page
repository,
but
I'm
not
clear
on
yours
one
unless
you
do
you
mind
like
explaining
that
a
little
bit
please.
C
I
was
going
actually
to
ask
if
the
description
is
understandable,
so
yeah.
So
the
thing
is
that
we
do
track
deployments
for
some
components.
Now
I
would
say
projects
right,
because
compo
not
only
components
we
track
packages,
we
track
the
rails
applications,
so
some
project
are
tracked.
So
when
we
do.
C
Yeah,
but
it's
not
because
they
are
part
of
auto
deploy,
but
because
we
went
we
went
there
and
implemented
so
yeah.
So
that's
the
thing
right
so,
for
instance,
pages
is
part
of
how
to
deploy,
in
the
sense
that
when
we
installed
an
auto
reply
package,
we
installed
the
pages
version
that
is
in
there,
but
we
don't
track
the
deployment
on
the
pages
project.
C
Okay,
this
is
the
other
one.
Is
that
when
we
track
deployments
at
the
same
time,
we
also
do
a
central
tracking
on
release
metadata
when
we
track
a
deployment
for
the
commit
that
introduced
the
the
the
version
description.
So
the
metadata
itself
is
on
a
single
commit
and
that
commit
got
tracked
so
that
we
know
what
which
this
is,
what
we
call
the
product
version.
So
there
are
many
classes
on
release
tools
all
related
to
how
to
deploy
that
works
on
product
version.
C
So,
given
a
coordinated
pipeline
tag,
it
can
tell
you,
what's
inside
on
every
component,
also
those
that
we
are
not
yet
tracking
with
the
other
information
right,
because
it
it
goes
from
release
metadata,
fetches
the
metadata
itself
and
can
inspect
the
content
of
the
file.
So
that
thing
already
can
give
us
can
tell
us
which
version
of
pages
is
inside
of
an
auto
deploy
package.
C
C
My
proposal
here
is
that
we
remove
that
thing
and
we
just
stick
with
the
with
the
component
version
so
up
front.
When
we
target
release,
we
say:
release
metadata.
Tell
me
the
last
production
deployment
we
get
that
single
description
file
and
with
from
that,
we
can
infer
the
version
of
everything.
That's
inside.
A
C
C
C
A
C
So
the
the
this
was
my
yeah,
my
idea
on
that,
because
there
is
the
base
level,
which
is
the
one
that
is
already
documented
in
our
documentation.
Just
tell
you
if
we
would,
if
release
tools
needs
to
be
aware
of
a
component,
there
are
certain
things
that
you
have
to
implement,
and
one
of
this
is
making
sure
that
when
we
tag
out
deploy,
we
are
aware
that
you
have
a
version
file
inside
gitlab
itself
and
we
track
this
on
release
metadata.
C
A
Oh,
I
think
I
made
some
son,
so
if
we,
if
we
are
focusing
on
the
fine
last
component
deployment
from
release
metadata,
is
this:
is
this
something
that.
C
Be
yeah,
that's
a
refactoring,
I'm
saying
new
features
versus
refactoring
right,
so
this
is
something
we
can
do
right
before
and
we
can
also
run
some
comparison.
Okay,
just
dry
run
of
the
tagging
with
say,
feature
flag.
This
new
implementation
and
see
will
the
new
and
the
old
one
have
generated
the
same
stable
branches.
A
Cool
okay,
great,
so,
are
there
any
other
discussion
things
people
want
to
go
through
or
should
we?
A
A
Okay,
awesome,
so
I
know
I
have
an
action
first
off,
which
is
to
I
guess
like
spend
some
time
with
configure
working
out.
A
Deploy
and
let's
see,
I'm
going
to
give
you
the
super
important
project-
a
lot
of
tasks.
Hopefully
it's
not
a
project
of
of
check
in
something
with
pages
maintainer
about.
A
We've
got
a
bunch
of
other.
I
think
we've
got
a
bunch
of
issues
that
look
like
they
are
ready
to
go
in
fact,
myra.
I
know
you've
got
an
outstanding
task.
Do
you
want
to
just
like
as
your
first
task
as
you
come
out
of
release
management,
just
wrap
up
the
getaly
analysis
issue
and
then
I
think
we're
in
a
pretty
good
state
with
that
one.
C
Tasks
called
them
easy,
which
are
just
the
one
verifying
that
we
can
build
pages
for
for
shop.
So
this
is
something
that
is
kind
of
easy
to
do.
We
just
need
to
figure
out
how
to
do
with
the
documentation
of
what
omnibus
and
cng,
but
then,
if,
if
the
answer
is
no,
then
there
is
something
that
we
need
to
put
on
the
roadmap.
A
Yeah
yeah,
it
would
be
really
good
to
know
the
answer,
so
it
certainly
seems
like
the
the
can.
We
build
pages
from
cher
and
this
metadata
stuff.
These
two
feel
like
the
two
kind
of
really
useful
things
as
next
steps,
in
my
view
at
least
yeah
cool
myra.
I
know
you've
got
quite
limited
time
before
you
head
out
in
october.
A
Do
you
want
to
like,
like
phil,
please
do
time
box
a
getaway
analysis
issue
like
get
it
to
the
stage
where
we
have
enough,
but
it
doesn't
need
to
be
perfect,
so
they
get
it
good
enough,
and
then
we
can
just
say
it's
done,
but
is
there
like?
Do
you
want
to
have
a
go
at
doing
the
the
testing
pages
building
from
shah
like,
hopefully
that's
something
that
fits
with
the
time
you
have
next
week,
and
then
we
kind
of
have
the
answer
and
we
can
go
from
there.
C
C
So
it's
just
a
matter
of
doing
this
and
if
they
and
then
checking
the
the
gives
you
an
image
at
the
end,
so
you
download
the
image
you
run
it
on
docker
and
if
there
is
the
right
thing
inside
down,
so
it's
just,
we
can
close
it
and
say
it's
done.
If
not,
then
it
will
be
another
starter,
but
there's
no.
I
mean
unless
at
least
we
know
that
we
have
to
to
schedule
these
things
in
it
would.
A
A
We
have
another
like
that.
One
feels
bigger,
which
is
why
I'm
kind
of
not
sending
it
your
way.
Myra
like
that,
does
feel
like
more
than
four
days
of
work
unless,
unless
you
disagree
and
you'd
rather
tackle
that
one
and
then
graham
could
test
the
the
build
from
shah.
A
Okay
cause
it
feels
like
those
are
two
super
useful
pieces
and
then
hopefully,
we'll
get
a
thumbs
up
from
configure
and
from
page
maintainers,
and
then
we
can
kick
off.
I
think
it
gives
us
a
bunch
of
other
issues
that
we
can
kick
off.
Then
I'm
also
hopeful
that
the
cause
canary
isn't
too
far
away
jenny's,
making
great
progress
there.
A
So
there
are,
but
there
will
be
some
delays
on
the
cars
auto
deploy,
because
the
next
step,
once
we
have
a
canary
is
we
do
need
configure
to
make
some
changes
in
order
to
support
the
canary
inside
cars.
So
there
will
be
some
tasks
that
they
will
need
to
find
time
to
schedule.
So
I
don't
know
I
don't
know
what
their
capacity
looks
like
right
now,.
A
Thank
you
very
much
for
the
discussions
and
yeah
shout
if
you
need
stuff,
we
can
continue
async
and
we'll
see
we'll
see
how
things
go.