►
From YouTube: Foundational Infrastructure Working Group [May11, 2023]
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
Infrastructure
working
group
meeting-
let's
see
I,
was
already
one
PR
just
merged
in
the
beginning.
That
was
related
to
Bosch
brute
letter
change,
an
oversight
in
the
CI
yeah.
We
have
this
one,
that's
open.
Some
changes
were
made
a
few
hours
ago
two
hours
ago,
so
I've
asked
again
to
take
another
look
because
he
had
some
initial
concerns.
A
I've
already
approved
it.
Let's
wait
for
Kenneth
I
expect
him
to
come
back
to
later.
Today,
it's
beginning
of
beginning
of
his
working
day
at
the
moment
returned
evenings.
A
Yeah,
there's
not
I,
don't
see
any
other
PRS.
So
is
there
anything
else
people
want
to
discuss
before
we
go
to
open
issues.
B
Yeah
great
thanks
for
that.
No
problem.
C
Some
old
Legacy,
you
know,
libraries
that
bootloader
is
still
using
and
then
we
can
also
deploy
Arm
based
releases.
C
A
A
What's
the
but
it's
outside
of
our
realm
of
yes,
it's.
C
A
C
A
A
Yeah,
let's
go
over
the
issues.
C
A
Yeah
I
liked
I,
like
the
changes
it's
much
clearer,
now,
I
like
the
fact
that
it's
now
I
mean
like
it
is
a
bit
of
like
a
a
trigger
or
a
red
flag.
If
you,
if
tests,
are
changed
that
aren't
like
if,
if
it's
not
immediately
clear,
why
they
just
that's.
Where
claim
changed
right,
and
here
it's,
it
is
changing
something,
but
then
just
from
dashes
to
lowercase
or
to
underscore
and
I
think
that
I,
don't
know
should
be
easier
to
review.
B
A
Thanks
for
that,
yeah
I've,
already
I
already
told
but
I
have
been
kind
of
to
take
another
look
at
the.
So
we.
B
Tried
to
find
documentation
about
these
ideas,
but
we
couldn't
find
Felix
wanted
to
add
some
context
from
the
CPI
I
think
about
the
CPI
is
to
deal
with
this.
Apparently
they
do
the
same.
D
Behind
what
exactly
you
mean
with
how
the
CPI
handles,
because
what
we
saw
this,
this
disk
is
either
resolved
by
ID
or
directly
from
the
path
so
both
time
it
really
the
agent
more
or
less
relies
on
what
comes
back
from
the
CPI
for
both
cases.
D
E
Is
that
it's
never
worked
with
ID
for
AWS
and
Ali,
and
the
aim
of
all
the
time
fall
back
to
the
past,
but
yeah.
We
have
sometimes
the
issue
that
on
Ali
Cloud
the
pass
is
also
not
working,
and
then
we
rerun
into
an
issue
and
with
the
change.
It
will
also
now
work
for
AWS
and
Harley
Cloud
directly
with
the
ID,
and
they
must
not
fall
back
to
the
path
anymore.
Yeah.
D
A
Yeah,
it's
good.
Let's
see
how
to
put
other
review
goes,
release
notes
missing.
A
It's
nice
addressing
someone
by
name,
not
mentioning
them.
You
know
long
actually
saw
this.
Did
it
change
released?
Now
it's.
A
C
A
B
If
no
permissions
BPM,
somehow
that
doesn't
have
permissions
to
do
that
anymore,.
A
B
The
default
and
you
know
1000,
and
they
want
to
change
it
to
one
hundred
thousand
one
million
one
million
yeah.
But.
A
B
A
C
C
B
A
A
A
Yeah
I,
don't
know
I,
don't
think
we're
gonna
get
to
the
bottom
of
this,
but
I
probably
want
to
have
to
be
people
that
got
that
release.
Look
into
this.
C
D
A
Okay,
I
will
ask
who
did
this
after
the
call
foreign.
A
B
I
wanted
just
to
check
on
that
long
discussion
regarding
openstack
and.
B
C
Yeah,
no
that's
something
else
so
I
proposed.
Should
we
should
we
look
into
the
IR
specific
kernels
and
then
his
problem
was
that
the
the
hardware
enables
kernels
that
we
are
using
is
not
working
for
him
on
openstack,
because
he
has
older
Hardware
that
that
that's,
that
doesn't
work
in
in
a
specific
in
his
specific
case
and
the
ga
kernel.
So
that's
basically
the
generic
that
is
I,
think
four
or
five
hundred
MBS
bigger,
which
has
everything
in
it
works
for
him.
A
A
It's
this
is
not
the
first
time
like
that.
Basically,
we
are
always
trying
to
use
that
kernel,
which
was
just
not
there
to
begin
with
so
yeah.
It
could
be
seen
as
a
bit
of
a
breaking
change,
but
I
think
it
is
what
we
want
and
there
seems
to
be
an
upstream
issue
like
it's
economical.
She
just
tried
to
fix
it
and
also
bis.
Specific
kernels
are
also
shipping.
The
same
version
of
the
kernel
as
the
hardware
enablement
Journal.
C
But
openstack
does
not
have.
Openstack
is
a
weird
case
because
with
openstack
you
can
basically
add
every
Hardware
behind
it.
Whatever
you
want
so.
A
But
it
shouldn't
matter
it
shouldn't
matter,
because
this
is
like
it's
about
the
hypervisor
right,
you're
running
a
VM.
C
C
Yes,
but
I
looked
in
so
for
the
is
specific
Cloud,
the
cloud
kernels.
Basically,
what
they're
calling
they
know,
which.
A
It's
not
about
Hardware,
it's
about
virtualized
Hardware,
it's
about
the
hypervisor.
They
are
optimized
for
a
hypervisor.
A
C
And
you
you,
like
the
same
as
when
you
do
on
your
lap
in
your
bios,
when
you
enable
a
specific
that
you.
C
Your
virtual
machine
can
incorporate
some
processor
power
directly
on
the
hardware
itself.
A
C
And
for
so
for
AWS,
gcp
and
and
sometimes
Ali,
we
know
what
kind
of
hard
they
know
what
kind
of
Hardware
and
CPUs
they
have
so
the
they
are
better
at
choosing
which
stuff
we
have
and
with
Hardware
enable
with
GA
kernels.
You
basically
have
here.
You
have
everything
we
can
do
everything
we
can.
D
C
All
modules,
whatever
you
want
and
for
for
age,
the
hardware
enabled
kernels
is
basically
for
the
newer
Hardware.
So
it
could
be
like
it's
Hardware
like
for
that.
That's
like
10
years
old
or
eight
years.
D
C
A
C
Yes,
it's
it's
especially
specifically
canonical,
but
for
open,
I,
think
they're,
the
major
ones,
people
who
are
using
openstack,
so
I
I,
would
more
say
like
let's
the
people
who
uses
the
openstack
stem
cell,
let
them
decide
which
Colonel
they
probably
want.
It's
just
a
bigger
footprint.
A
B
A
Yeah
and
and
the
is
specific
kernels
are
also
based
on
a
1.19,
so
like
the
the
only
one
with
the
old,
the
only
all
the
kernel
is
the
ga
one,
all
the
other
ones
are
1.19
and
on
different
patch
levels
because
of
back
parts
and
stuff
security
fixes,
but
yeah
I
I'll
briefly
looked
into
it
and
I
saw
that
the
so
so
one
problem
is
that,
like
going
to
an
hour
an
open
sex
or
the
KVM
specific
is
Kernel
that
wouldn't
probably
help,
because
it
is
still
based
on
1.19.
C
Built
their
own
stem
cell
with
the
new
with
the
older
kernel,
they
they.
D
A
A
Yeah,
it's
gonna
be
horrible,
like
yeah,
just
having
to,
because
I
noticed
that
some
of
these,
like,
although
they
are
all
one
like
the
oh
yeah
specific
ones
in
the
hardware.
Enablement,
are
all
like
1.19
so
like
for,
like
really
recent
CVS
from
like
say
a
week
ago
or
something
then
it's
fixed
in
hardware
enablement
and
but
not
for
the
gcp
one
right
so
that
these
all
get
their
own
patches
at
a
different
time
right.
So
you
would
be
lagging
behind
and
they
would
have
to
you.
A
You
think
you
have
a
CV
fixed
in
a
certain
stem
cell,
but
then
it
turns
out.
You
haven't
fixed
it
for
gcp
right,
because
you
still
need
another
patch
there
and
that
that
sounds
horrible
to
manage
basically
could
mean
that
we
have
to
cut
like
five
or
I.
Don't
know
four
releases
of
a
stem
cell
just
to
address
one
CV,
because
they
are
all.
B
C
I
know
there
is
some
the
only
thing
I
know
there
are
some
performance
improvements.
A
Yeah
sure
that
could
be-
and
that
would
be
nice
but
I,
don't
think
it's
worth
the
the
complexity
of
dealing
with
the
CVS
I
mean
I.
I
just
did
like
a
a
I
looked
up
recent
a
recent
CV
and
then
I
noticed
that
it
was
not
fixed
on
Aldi
kernels
kernel
lines.
Basically,
okay.
A
Well,
then
we
let
it
go.
I
I
did
the
sport
check.
Basically,
this
is
not
so
it's
not
like
published
that
they
have
so
yeah
we're
always
lagging
behind
such
and
such
on
these
kernels.
But
it's
more
like
a
it
to
me.
It
demonstrated
that
it's
not
like
that
I
have
one
Pipeline
and
then
have
all
the
different
types
of
kernels
come
out
at
the
end
right.
So
there's
apparently
some
manuals,
cherry
picking
between
different
branches
or
something
for
the
different
lines
which
makes
sense.
A
If
there's
nothing
else,
Let's
call
it
I.
E
Have
one
topic
I'm
a
little
surprised?
It's
not
here
we
reopened
the
back
regarding
the
queue
tasks
in
the
Bosch
Repository
and
it's
an
open,
but
I
don't
see
it
here.
A
Maybe
it's
not
an
inbox.
Maybe
it's
in
discussion.
E
So
maybe
you
can,
someone
can
have
a
look.
We
we
saw
again
some
cute
tasks
and
I'm,
not
sure
why
we
get
them
again.
A
A
B
A
Was
the
this
one
discussion.
A
Okay,
then,
let's
see
all
next
week
and
don't
forget
to
register
for
our
CF
day.