►
From YouTube: 2022-11-30 - 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
Vladimir,
this
probably
isn't
the
right
Zoom.
If
you've
got
this
from
the
delivery
group
call,
you
probably
want
to
be
in
the
system
one.
Let
me
just
ping
you
a.
C
D
A
A
Yeah
so
welcome.
This
is
30th
November.
This
is
our
email,
America's
timed
orchestration
demo,
and
we
are
a
little
bit
light
on
people
today,
but
we
do
have
some
stuff
on
the
agenda,
so
we
will
see
how
we
go
so
I
didn't
remember
to
ask
Graham
this
before
he
signed
off
for
the
rest
for
the
day,
but
I
know
it's
sort
of
in
progress.
A
I
don't
know
if
you've
got
an
answer
yet
on
the
packages,
but
hopefully
we'll
hear
tomorrow
whether
we
need
to
really
that
one's
just
interesting
on
her
is
there
going
to
be
more
work
uncovered
versus
it's
not
blocking
us
right
now,
but
it
would
be
nice
to
know
if
we
we're
going
to
need
to
do
more
work.
So
we'll
see
what
Graham
comes
back
with
there.
A
Steve
was
also
planning
to
give
us
a
demo,
but
he
is
out
sick.
So
that's
a
shame,
but
we
can
catch
up
on
that.
Another
time
was
there
anything
else.
Was
there
anything
you
wanted
to
demo
today,
Matt.
D
D
So
so,
essentially,
the
I've
got
an
MR
up
at
the
moment
that
has
all
the
terraform
set
to
spin
up
the
actual
kubernetes
cluster
itself
to
spin
up
the
environment
in
which
is
all
relatively
Bare
Bones.
It
was
going
to
be
a
little
bit
Fuller
to
begin
with,
but
I
took
these
stance
to
keep
it
slimmed
down,
essentially
because
the
environment
is
going
to
be
long-standing
and
not
just
an
ephemeral
up
and
down
up
and
down
kind
of
thing.
D
The
Bastion
host,
therefore
also
requires
additional
Chef
roles
in
the
release
environment
itself,
like
a
base
role,
as
well
as
the
role
for
the
Bastion
hosts,
Scott
and
I,
were
having
a
little
bit
of
back
and
forth
on
draft
error
that
I
have
up
in
the
chef
repo
and
that
we're
not
entirely
sure
that
we're
going
to
stick
with
like
a
generic
base
role,
because
the
environment
itself
is
going
to
be
very
paired
down.
D
So
we're
kind
of
kind
of
discussing
on
what
the
best
option
is
going
to
be
there.
In
all
likelihood,
we
might
scrap
having
a
base
roll,
because
the
whole
idea
of
the
base
role
is
really
just
to
you
know,
sort
of
keep
things
dry
and
can
sure
we
don't
repeat
ourselves
over
and
over
in
sort
of
roles
that
build
on
top
of
the
base
right.
It's
like
it's
a
very
generic
sort
of
concept,
but
we've
actually
already
got
like
a
bit
of
a
Singleton
role
in
there
already
for
the
release.
D
Instance
that
is
running
inside
the
existing
release
environment.
So
we
might
just
repurpose
that
a
little
bit
it
depends
on
kind
of
the
effort
involved,
but
at
any
rate
the
terraform
itself
is
therefore
a
lot.
Simpler.
Doesn't
include
the
Bastion
at
this
point,
because
we
kind
of
want
to
work
on
getting
the
chef
rolls
ironed
out
to
make
sure
you
know,
because
if
we
stand
up
the
Bastion
without
the
roll
nothing's
going
to
happen,
it
just
won't
provision
it'll
just
sit
there
empty
and
useless.
A
Do
you
do
you
know
what
next
steps
look
like.
D
Yeah,
so
the
next
steps
is
Graham
and
scarbeck
are
adders
reviewers
on
the
terraform
Emma
I
already
had
some
of
their
input
earlier
on.
D
Whilst
it
was
still
in
work
in
progress
phase,
so
as
it
exists
right
now,
they're
I'm
not
expecting
there
to
be
any
drastic
revisions,
so
that
Mr
should
hopefully
go
in
by
the
end
of
the
week,
which
means
we
should
have
the
terraform
and
the
infrastructure
stood
up
by
the
end
of
the
week,
which
is
good
because
then
there's
now
a
usable
environment
that
you'll
be
able
to
access
via
the
Ops
Bastion
in
lieu
of
having
like
a
dedicated
Bastion
for
release.
So
you
know
the
public
IP
is
is
whitelisted
for
Ops.
D
Basically,
so
you
can
still
actually
get
in
and
interact
with
the
cluster
and
then
we're
going
to
be
working
on
so
I'm
working
on
the
chef
side
of
things
so
that
we
can
send
up
a
Bastion
one.
Other
thing
that
I
need
to
verify
as
well
as
the
next
step
is
making
sure
that
we
are
peered.
We
have
EPC
peering
with
the
Ops
account.
D
It
looks
like
we
do
in
One
Direction,
but
I
need
to
verify
that
it's
also
good
back
in
the
opposite
direction,
because
that
would
enable
it's
not
like
a
super
important
thing.
It's
mostly
to
enable
the
use
of
what
we
have
running
in
Ops.
So
if
we
wanted
to
hook
in
monitoring
or
Sentry
or
just
any
of
those
things,
but
the
main
next
steps
is
infrastructure
goes
in
Chef
rolls
gets
ironed
out
to
spin
up
the
Bastion,
but
in
the
meantime,
it's
a
it's.
A
usable
cluster
and
a
usable
environment.
A
C
Do
so
I
was
catching
up
on
the
blog
post
generation,
for
the
policy
extension
wanted
to
see
how
it
ended
up
being
implemented.
If
we
could
leverage
this
Logic
for
the
the
the
extension
of
bug
fixes
into
the
security
release
itself,
so
I
was
trying
to
I
was
testing
it
basically
right.
So
the
the
feature
itself
is
designed
as
a
standalone
rig
Tusk,
which
is
great,
because
this
will
allow
us
to
easily
integrate
that
into
the
patch
release
as
well.
While
I
was
looking,
something
came
to
my
mind.
C
That's
why
I'm
a
little
digressing
here
with
Point
3B,
because
I
something
that
I
noticed.
So
when
we
generate
the
blog
post,
even
the
regular
one
that
we
already
have
there
is
this
I
find
a
super
annoying
task
to
change
the
author
to
the
name
of
the
release
manager
that
is
generating
this
and
then
someone
puts
his
own
Twitter
handle
someone
don't
and
then
you
have
to
put
your
gitlab
username
and
then
there
are
all
the
situations
where
this
is
this
counts,
as
an
extra
CI
run,
it
takes
time
to
change.
C
That's
it
then
there's
an
extra
CI
run,
but
then
it
also
happens
when
we
go
over
which
day,
for
any
reason,
we
don't
release.
So
we
move
to
the
next
day.
Maybe
the
release
manager
in
the
other
time
zone
is
going
to
change
it
as
well
and
I
was
thinking
I,
don't
take
any
real
benefit
or
credit
for
having
my
name.
Next
to
that
blog
post
items,
I,
don't
I,
don't
even
care
partly,
but
maybe
someone
does
right,
but
I
was
thinking.
C
Is
there
a
way
to
just
not
have
to
touch
the
blog
post
and
just
merge
it?
So
the
screenshot
here
is
from
the
link
below,
because
basically
it's
it's
a
three-line
change
in
release
tools
in
the
template
and
by
the
way
the
those
URL
are
built.
We
can
simply
say
that
the
author
is
delivery
group
release
manager,
whatever
we
like
linking
to.
C
We
need
to
have
a
link
on
gitlab.com,
so
I've
put
the
our
delivery
group,
the
group
itself,
so
it
links
to
the
group
page
because
you
can't
put
the
full
URL
just
what
goes
after
gitlab.com.
So
we
may
put
something
there
that
it
would
be
the
the
URL
on
github.com
and
the
Twitter
one.
The
default
is
using
the
gitlab
account,
so
I
was
thinking.
Maybe
this
is
a
simple
change
and
it
will
make
one
merge
request.
Last
one
CLS.
A
I
think
the
Twitter
one
we
could
absolutely
just
standardize.
I,
never
put
my
own
Twitter
account
on
there.
I
always
use
the
getlab
one.
So
I
think
that
bit
we
could
just
lock
in
the
actual
author
name
is
an
interesting
one.
I,
don't
really
know
the
history
behind
this,
but
from
looking
at
the
at
the
at
the
releases,
like
even
the
monthly
release,
goes
with
a
an
individual's
names.
So
you
know
it
seems
very
intentional,
but
I
don't
know
I,
don't
know
that
anyone's
ever
gone
back
and
reviewed
it.
When.
C
C
I'm
just
surrounding
a
sea
ice
creeper,
so
when
it
was
manual
and
I
had
to
go,
I
mean
that's
the
point
also
it
has.
This
was
manual
a
point
in
time,
so
I
had
to
scan
through
all
the
things
that
I
emerged,
that
I
picked
and
take
links
and
review
formatting
editing,
so
I'll
gladly
take
the
credit
for
spending
time
in
doing
this
right.
This
is
just
extra
time
for
no
reason
so
I
don't
want
to
go
there
and
put
my
name
and
just
for
yeah
I
see
no
value.
C
So
that's
why
I
was
these
are
very
aseptic,
so
there's
there's
nothing
really
there
right.
So
it's
all
generated
if
we
have
to
change
it.
I'm
fully
supportive
of
people
just
saying
changing
and
putting
their
name.
I
have
no
problem
with
this.
Just
want
to
have
a
frictionless
default
approach
to
this
when
things
goes,
how
say?
Fine
and
we
are
in
the
happy
part.
A
Yeah
all
right
fully
fully
okay,
yeah,
absolutely
great
and
I-
think
it's
perfect
timing,
because
the
reason
we've
never
really
had
answers
on
this
before
is
we
don't
have
a
product
manager,
but
now
we
do
so
I
would
suggest
that
Fabian
is
the
the
person
to
ask
about
whether,
like
is
anyone
going
to
care
about
this
like?
A
Is
there
someone
we
need
to
run
this
by
and
maybe
marketing
or
you
know
somewhere
like
that,
but
otherwise,
if
not
then
yeah
I
think
this
sounds
like
a
great
idea
like
I
would
love
to
remove
as
many
of
these
manual
steps
for
all
the
reasons
you
mentioned
so
yeah.
C
A
I,
just
don't
like
context
around
Verma
and
also
for
this
recording
around
where
we
are
sort
of
roughly
in
in
sort
of
timeline
of
these
things,
so
we're
right
now,
focusing
only
on
bug,
fixes
and
Patch
releases,
but
we
are
also
thinking.
I
mean
right,
we're
also
sort
of
thinking
about
improvements
for
the
security
release,
and
so
with
a
bit
of
luck.
If
we
get
this
process
working
well,
we
get
all
the
environments
in
place.
A
We
get
all
the
tools
in
place,
then
then
those
sort
of
logical
next
step
to
follow
up
will
be
to
see
how
much
of
this
process
we
can
add
on
to
security
releases,
to
reduce
release
manager,
overhead,
so
that's
kind
of
where
we're
it
won't
happen
until
we've
finished
our
current
okrs,
but
I
think
it
would
be
a
very
nice
addition.
A
Awesome
C
is
a
little
bit
of
an
FYI,
so
I'm
just
sharing
Myra
put
together.
This
super
issue
kind
of
running
through
the
experience,
the
user
experience
for
different
users
on
different
points
around
this
process
have
a
look.
Please
take
a
little
bit
of
time,
have
a
read
through
it
and
add
any
questions
or
comments
for
well
for
all
of
us,
but
on
that
issue,
because
I
think,
if
we
could
get
the
user
experience
right,
then
lots
of
other
stuff
will
just
fall
into
place.
A
A
Excellent
is
there
any
other
stuff
that
we
should
talk
about.
A
No,
it
will
be
a
little
bit
slower
on
progress
over
the
next
say
week
or
so
so
Steve
is
looking
at
the
managed
versioning
issue
for
pages.
Myra
is
out
until
sort
of
this
time.
Next
week,
Matt,
you
have
some
time
out
coming
up
next
week,
so
you
know
things
won't
necessarily
progress
at
the
pace
they
have
been,
but
we
can
hopefully
keep
things
moving
along,
keep
each
other
unblocked
so
that
we
we
can
still
still
keep
pushing
through
through
December
excellent.