►
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).
B
C
C
A
C
A
I
heard
that
apparently
the
people
in
the
cry
in
cryogenics
that
sounds
horrible-
the
people
in
the
team
that
is
called
cryogenics.
A
They
were
experimenting
with
some
like
heavy
GitHub
actions
based
workflows
where
they
were
like
Fanning
out
and
doing
like
dirty
things
at
the
same
time.
Something
so
that's
probably
why
we
were
encountering
those
limits.
A
E
B
A
A
B
A
Me
I
mean
I
can
look
at
it.
It's
fine,
but
I
think
that's
the
best
way
forward.
C
Yeah
I
won't
have
planned
this
week
next
week.
Okay,
I'll
scrolling.
E
Wait
yeah,
so
you
reviewed
it.
C
So
basically,
this
brings
the
option
to
set
the
local
OS
disk
of.
B
A
Yeah
ironic
should
like
it
it's,
it
looks
like
Aaron
hasn't
looked
at
it.
Maybe
you
should
just
add
a
review.
D
D
C
D
A
What
you
could
do
is
what
sometimes
works
is,
if
you
have
an
authorized
key
that
you
put
in
the
Bosch
EMV
settings,
because
that
usually
gets
picked
up
pretty
quickly.
I
mean
there
are
cases
where
it
fails
before
that
and
you
it.
C
A
Work
right,
but
since
that
key
gets
injected
through
the
I
mean
if
the
whole
OS
crashes,
that
doesn't
help
80
of
cicadas,
you
could
still
ssh
in.
If
you
have
no
running
ages,.
D
D
A
B
C
A
A
A
E
A
A
Yeah
I
discussed
this
with
with
the
the
VMware
folks
and
they
are
gonna
take
over
this
pull
request
because
there's
like
one
bit,
that's
missing
related
to
the
final.
What's
it
final
packages.
A
C
A
It
has
been
tested
right,
so
if
you
just
rename
it
so,
you
use
this
code
that
is
here
and
then
rename
the
final
bills
package
manually.
Then
it
works.
If
you
also
have
the
Ruby
release
changes
so
there's
because
there's
in
the
Ruby
release,
there
are
some
things
that
are
hard-coded
some
parts
and
they
should
just
use
the
Bosch
compile
Target
and
that's
the
change
that
Ramon
made
and
so
yeah
and
basically
there
has
been.
A
We
have
had
a
proof
of
concept
or
remote
has
a
proof
of
concept
which
works
and
should
fix
this.
Now
it
just
needs
to
be
I.
A
Partial
life
stuff
needs
to
be
fixed
by
the
by
the
VMware
team
and
rumor
needs
to
create
his
pull
request
for
the
Ruby
release,
and
then
we
need
to
roll
it
out
to
all
the
cpis
and
all
the
what
else.
The
Voice
director
also
needs
to
do
the
same
thing.
So
we're
gonna,
prefix
everything.
A
C
B
B
A
B
E
A
C
Yeah,
what
I
understood
from
the
pr
100
discussion,
pension
in
Benjamin
I,
was
wondering
why
this
is
done
in
the
stem
cell.
Something
for
syswalk
is
done
in
the
stem,
so
maybe.
A
The
own
logging
of
of
our
own
stuff,
what's
their
own
stuff,
I
mean
the
RCs
log
releases,
also
for,
like
our
system
releases,
just
to
configure
this,
everything
is
Rector,
basically
for
the
normal
syslog
kernel
logs
and
all
the
other
stuff,
that's
being
sent.
A
A
A
A
E
A
A
Syslog
release
is
just
configuring.
The
rsys
lock
demon
right
differently,
I
I
think
it
hooks
it
into
it.
Instead
of
configuring,
no
I
think
it's
just
writing
config
files,
since
when
are
you
allowed
to
come
with
to
override
direct
yeah?
It's
a
dirty
thing,
yeah!
That's
why
I'm
like
say
that's
what
I'm
saying
like
we
should
like
align
with
them
because
they
are.
This
is
like
they're,
it's
not
a
typical
boss
release
because
they
are
just
changing
config
files.
A
A
Rc's
law
itself
says:
use
openssl,
don't
use
the
umrael
anymore
sure,
but
if
you're
not
for,
if
you're,
not
supporting,
if
you're,
not
forwarding
logs
anywhere
again.
Why
is
this?
Why
is
this
so
difficult?
I,
don't
understand
it's
not
difficult!
It's
more
of
like
this.
The
only
thing
I'm
concerned
about
or
I
think
we
can
do
without
this.
These
lines
right.
A
E
A
E
A
Because
then,
if
you
added
line
here,
you're
affecting
everybody,
that's
using
the
stem
cell,
if
you
add
this
line
only
to
the
artist
lock
release,
is
the
responsibility
of
the
RCs
lock
release
right,
it's,
but
it's
basically
about
responsibilities
like
from
a
board
side
of
I
found
it
hard
to
reason
about
how
we
use
this
thing
from
a
bush
perspective,
because
I'm
not
maintaining
the
RC
slog
release,
so
I
can
reason
about.
Oh,
yes,
we
added
additional
package
because
it's
a
dependency.
E
A
A
So
we
configure
it
so
that
we
do
store
logs
in
a
central
place
locally
on
the
machine
we
don't.
We
are
not
concerned
with
shipping
the
logs.
If
you
want
to
ship
the
logs,
you
use
rsys,
lock,
release
and
that
happens
to
use,
configure
the
same
Daemon
I.
Think
that
that's
like
the
API
boundary,
but
there
is
a
syslog,
forwarder
and
RCS
log
already
configured
by
default
within
the
stem
cell
because
it
needs
to
handle
the
defaults,
the
default
logs,
the
kernel,
the
current
logs,
that
all.
A
A
Anyway,
so,
let's
just
if
the,
if
they
have
some
other
creepy
tool,
that
they
use
in
a
different
thing
and
they
want
to
use
the
default
logs,
I
don't
want
to
override
anything.
Let
me
put
it
differently.
Is
this
line
required
for
sap
to
have
it
work
or
how?
How
are
how
is
sap
configuring?
Our
syslog?
Are
you?
Are
you
all
using
the
RCs
lock
release,
or
is
there
a
different
way
to?
Are
you
using
a
different
mechanism
to
configure
the
the
forwarding
I
think
they
use
the
syslog
release.
C
Yes,
I
also
think
that,
and
my
understanding
is
that
this
line
here
makes
it
more
resilient.
Otherwise
you
have
when
the
connection
is
not
stable
for,
but
so
when
we
follow
the
works
in
the
connect
network
connection
is
not
stable
opponents,
so
it's
more
resilient
for
the.
A
Yeah
I
understand
I,
understand
that
piece
of
the
argument.
So
no
no
I'm,
not
I'm,
not
concerned
about
the
line
itself,
I'm
just
concerned
about
putting
this
line
in
the
stem
cell
there
first
of
putting
it
in
the
our
syslog
release.
So
you
want
to
remove
this
complete
line
in
the
maybe
it
will
break
some
Edge
case
for
someone
I.
C
You
we
make
a
change
here.
Now
is
the
time
with
Jamie,
because
everyone's
validating
I
think
it's.
If
we
don't
see
an
issue
adding
this
to
those
chain
stem
cell
this
anyway,
configured
here
also.
A
A
Yeah
like
this,
this
file
is
the
same,
is
why
is
it
still
using
variable
mod
loads.
E
In
well
Upstream
in
Ubuntu
packages
it
still
uses
mod
load,
but
in
the
official
package
packages
they
don't
you
they
don't
use.
They
use
modules
that
from
model
over
bars.
A
So
there
is
a
lot
to
clean
up
only
in
only
in
RC
slogan
for
in
the
syslog
stuff,
so
yeah,
because
we
aren't
doing
that
many
things
here.
Okay,
we
have
this.
A
lot
has
commented
out:
yes,
because.
E
A
A
E
A
No,
because
our
sysl.
E
A
E
B
E
A
A
A
Yeah
and
you
don't
want
to
remove
no
G
new
TLS,
because.
A
Is
a
default
a
default
thing
yeah
also
like
that,
would
make
it
really
ugly
to
roll
out
the
syslog
for
release
right
people
would
it
would
be
a
breaking
change?
Yes,
that's
not
a
good
thing.
Yeah,
okay,.
E
C
C
A
I
know
some
working
groups
have
already
started
merging
these
types
of
things.
My
concern
is
a
bit
that
if
everybody
starts
doing
that,
we
run
out
of
GitHub
workers
quite
quickly,
Maybe.
A
So
I
would
rather
wait
for
the
the
discussion
we
have
on
entity.
You
see
around
that
the
external
workers.
A
E
B
A
C
C
A
A
A
C
E
A
A
A
Sure
someone
wants
to
review
this.
C
A
Okay,
if
you
have
contacts
I
mean
this
just
looks
like
a
search
for
the
place,
feel
free
to
merge
foreign.
C
C
E
E
A
Because,
like
most
of
the
things
are
actually
just
put
in
the
in
GitHub
I
believe
like
a
lot
of
things,
we
just
we
have
a
few
things
that
we
fetched
using.
Thank
you,
those
those
meta
links.
C
E
Well,
the
the
Ruby
install
the
Ruby
installer
from
postmodern.
We
use
that
from
get
reused
with
GitHub.
A
E
B
A
A
E
E
A
A
C
E
A
D
D
There
are
multiple
questions
that
that
are
interesting
for
me,
because
currently
we
are
starting
or
we
started
with
the
implementation
of
the
SR
storage
CLI,
similar
to
the
three
CLI
right
and
there
I
would
have
some
questions
with
regards
to
integration
later
on,
because
currently
we
are
doing
that
in
the
report
on
my
own
honor
and
in
in
GitHub
here,
but
as
soon
as
we
are
integrating
into
Bosch
some
at
some
point
in
time,
I
guess
we
have
to
switch
to
a
different
repository.
Otherwise
we
cannot
merge
required
PRS
right,
yeah.
A
D
Yeah,
okay,
so
so
currently
we're
I
mean
we
just
can
go
ahead
for
next
two
weeks,
I
guess,
but
then
we
are
probably
done,
which
is
here
iPad,
so
with
some
major
parts,
and
then
I
would
like
to
to
integrate
it
early
right.
A
Maybe
maybe
it
makes
sense
to
because
I
mean
yeah
I
would
start
to
maybe
create
a
PR
to
the
community
repo
to
ask
to
to
create
the
Repository
and
also
to
add
it
to
the
foundational
infrastructure
working
group.
Because
then
we
can
get
the
repo
set
up
and
then
it's
just
a
matter
of
pushing
to
it
and
then
it's
it's
there
right
and
then
we
can
have
the
full
review
thing
once
we're
gonna
integrated
into
to
Bosch.
A
But
then
it's
already
in
the
right
place
and
you
don't
have
to
block
your
development
now,
because
you
can
just
work
against
the
private
thing
and
then,
but
we
can
already
start
getting
that.
D
A
It's
always
this
nice
language
of
saying
I'm,
not
gonna.
Do
it
right,
it's
a
polite
way
of
saying
I'm,
not
gonna.
Do
it?
No,
no
I
like
I,
think
it's
good.
If
you
create
a
PR
and
then
like
Ben
and
I
can
approve
it
basically
created
because
there's
some
information
where
I
need
to
I
will
show
you.
So
it's
okay,
this
repo
Community,
the.
D
A
D
D
A
A
Have
ownership
as
a
Porsche
group,
so,
okay
here
add
it
to
this
list.
D
Then,
today,
in
the
days
before,
we
had
a
look
into
the
integration
of
S3
CLI
into
the
boss
director
and
somehow
we
are
utils
into
the
agent
code
as
well
and
at
some
point
we
always
get
stuck
in
the
agents,
because
it's
really
confusing.
What's
going
on
there,
somebody
knowing
the
agent
code
in
that
way
and
who
can
be
contacted,
do
we
know
somebody.
E
A
If
every
anyone
has
some
I
I
believe
that
probably
all
the
people
also
on
the
VMware
side
will
have
to
build
up
context
to
start
working
on
this
so
yeah,
that's
unfortunate
I
think
Aaron
has
recently
at
least
looked
at,
but
I
think
that
was
mostly
around
bumping.
Auto
bumping
the
different
clis
into
because
we
were
not.
We
were
building
all
these
clis.
All
these
blobs
or
cli's.
A
We
have
pipelines
to
to
cut
new
releases
with
new
versions
of
go,
but
then
we
weren't
bumping
them
in
the
the
stem
cell,
Builder
and
and
stuff
like
that,
and
the
Porsche
director
release.
A
E
But
okay.
A
E
A
E
A
E
Then
delegates
to
the
http,
HTTP,
client
and
then
downloads
designed
URLs
as.
A
D
It's
really
strange
that
it's
some
at
some
point
in
time.
It's
somehow
delegating
to
the
to
the
CLI
right,
which
is
yeah.
A
C
Yes,
if
you
don't,
there
is
a
con,
the
agent
settings
they
have
the
Bob
Store
I'm,
not
mistake.
If
you
use
the
old
way
without
signing,
you
don't
know.
E
Like
unsigned
URLs,
which
was
the
majority
of
people,
is
using,
you
get
the
access
log
in
wire
feed
cap
director
mobstor.
They
have
these
access
logs,
but
these
don't
work
for
signed
URLs,
because
this
happens
on
the
VM
with
the
agent
itself.
So
there.
A
A
But
I
mean,
like
there's:
I
mean
more
that
we
Pace,
like
not
the
whole
complete
URL,
but
we
did.
We
just
say:
hey
this
fails
or
whatever
or.
B
E
A
A
E
A
E
A
A
E
D
E
D
E
D
You
enable
A3,
then
you
want
to
see
oh,
how
often
did
it
retry
to
fetch
blobs
and
so
on,
right,
okay-
and
this
seems
to
be
difficult
currently.
E
And
you
try
to
get
the
voice
from
the
The
Voice
DNS
blobs,
basically,
and
that
failed,
because
S3
used
a
different
certificate,
it
was
not
signed
and
it
was.
It
was
annoying.
But.