►
From YouTube: CentOS Automotive SIG - July 12, 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
And
getting
started
with
the
July
meeting
of
the
Centos
Automotive
Sig.
We
are
about
a
week
late
because
of
holidays
and
such
but
I'm
glad
to
see
everybody.
Let's
see,
we've
actually
got
quite
a
quite
a
bigger.
A
I
thought
we
were
going
to
in
the
middle
of
the
summer
time
remember
that
last
year
we
actually
put
meetings
on
Hiatus
for
a
few
months,
because
there
was
simply
nobody
around
but
glad
to
see
that
we
do
have
some
folks
around
this
time.
A
Introduction
I
think
we
just
did
while
we're
waiting
for
Leo
to
do
some
technical
status.
Stuff
I
was
going
to
see
if
anybody
had
any
remaining
questions
for
iot.bz,
because
Philip
gave
a
great
talk
last
time
and
talked
all
about
how
iotwh
is
using
the
automotive
Sig
Assets
in
particular
to
produce
a
red
pesk
as
a
product.
So
I
wanted
to
give
give
a
chance
for
anybody
who
had
any
remaining
questions
that
didn't
come
up
in
the
call
while
Philip
is
here.
A
Okay,
well,
we
can
go
ahead
and
move
on
then
for
joining
Leo.
Sorry
to
drag
you
away
from
so
technical
status
update.
We've
got
a
couple
of
different
things.
We
did.
There
is
an
updated
here
to
documentation
that
I
will
go
over
toward
the
end,
but
in
the
first
part,
I
wanted
to
hand
it
over
to
Leo
to
talk
about
container
images.
C
C
Container
image
and
starts
a
container
in
a
very
opinionated
way,
so
we
created
one
a
very
early
stage.
C
Alt
SD
toolbox
concept
for
people
to
be
able
to
either
build
packages
for
provide
it,
provided
it
right
comes
with
enabled
autosd
repository,
so
it
allow
people
to
easily
back
to
their
crate
RPM
packages
for
the
software
for
ltsd.
Using
the
package
driver
available,
no
repositories
and
also
should
be,
should
be
useful
for
people
developing
things
that
do
not
fit
in
a
containers
or
no
packages
or
anything
else
that
needs
to
integrate
with
the
hosts
and
there
are
directions
they
open,
not
and
not
fit
for
the
container
workloads.
C
C
And
the
other
thing
is
that
a
you
know
up
actually
give
me
a
second
I
have
to
go
back
to
this.
C
But,
but
did
one
of
the
place,
the
other
ones
that
we
have
early
stage
developer
image
should
be
pushed
to
AWS,
and
if
you
you,
if
you
looked
at
for
L
plus
d,
OS
build
in
a
in
Amis
when
creating
a
new
machine,
you
should
be
able
to
see
the
idea
of
chosen
of
those
images
that
can
bootstrap
a
new
ecq
server.
C
They
are
published
day
nightly,
so
there's
a
new
image.
If
there
are
changed
to
chose
the
images
there
are,
they
are
nightly
being
published
to
AWS
for
people
to
use.
They
are
mostly
useful
for
if
one
either
asked
test
the
autosity
operating
system-
or
you
can
hook
it
up
to
your
CI
pipeline
by
using
something
like
kubernetes,
you
can
convert
or
other
virtualization
orchestration
technology
to
test
your
application
in
the
CI
manner,
using
the
center.motor
Sig.
D
C
A
C
No,
that's
a
simple
developer
image.
That
was
the
only
we
can.
We
could
post
the
software,
but
itself
that'll
be
a
different
image
of
overall
I.
A
Okay
I
haven't
been
asked
about
that.
I
was
just
curious
myself,
oh
great
well,
thank
you.
Leo
I
really
appreciate
that.
That's
some
some
interesting
stuff
going
on
for
container
images.
If
you
are
the
kind
of
person
who
fires
up
container
images,
definitely
take
a
look
at
this,
especially
with
the
toolbox
and
we'd
love
to
hear
your
your
opinions
on
the
AWS
image.
A
We
are
we're
always
open
for
feedback
and
I
know
that
there
will
be
some
documentation
being
developed.
Yes,
Volker.
E
If
you
don't
mind,
we
sometimes
run
containers
on
machines
which
have
gpus,
so
it
would
be
interesting
if
you
have
a
little
test
if
it
works
for
you
running
or
accessing
gpus
from
inside
your
con,
a
safe
OS
container.
That
would
be
interesting
for
us.
I
think.
E
It's
for
for
rendering
we
are
using
dedicated
servers,
which
is
provided
by
Nvidia
and
for
our
Machinery.
We
have
embedded
devices
like
you
would
expect
these
typical
machine
iot
stuff,
which
is
having
additional
gpus
for
video,
analyzers
and
stuff
like
that.
A
E
A
I
see
okay,
the
Centos
Automotive,
the
auto
SD
image
is,
is
not
actually
going
through
a
safety
process,
so
it
does
share
a
great
deal
of
code
with
what
will
eventually
become
the
red
hat
in
vehicle
OS,
which
is
intended
to
towards
safety.
E
A
So
but
you
know
that
doesn't
necessarily
mean
that
it
can't
be
used
for
development,
so
I
think
that
you
know
as
it
as
you're
developing
towards
a
safe
OS
to
run
with
these
gpus.
This
might
be
a
very
good
way
to
do
it.
A
A
To
the
chat
here,
for
those
who
are
new,
Herta
is
a
lightweight
container.
Orchestration
system
based
on
dbus
and
system
d
is,
is
very
fast
and
efficient,
and
one
thing
that
we
I
should
also
mention
is
I
have
been
told
that
the
name
may
change.
A
You
can
take
a
look
at
the
at
the
source
for
it.
Here's
all
the
all
the
documentation
about
how
to
use
that
it
is
intended
for
multi-node
environments,
and
it
is
very
quick
uses
uses
quadlets
here
you
can
find
out
more
information
about
quadlets
with
podman.
A
A
I
think
we
should
have
stuck
I
really
liked
that
name.
In
fact,
you
know
I'm,
not
convinced
that
we
can't
go
back
to
that,
but
that
one's
unfortunately
you
know
not
within
my
not
within
my
sphere
of
influence.
A
F
I
said
Philip,
just
just
one
thing:
I
would
like
to
to
make
sure
I
understand
correctly
in
what
you're
presenting
today
with
the
auto
SD
toolbox.
F
Now
is
this
going
to
help
people
moving
to
a
custom
Hardware
especially
running
an
arm?
So
how
do
we
do
the
cross
development?
F
You
know
because
I
had
a
quick
check
and
in
fact,
if
I
understand
correctly,
which
this
is
it's
it's
it's
a
tool
to
manage
software
without
using
dnf
and
having
a
different
model
to
install
software
on
containers,
but
I'm
still
wondering
how
I
can
read
my
can-
and
you
know,
I
have
very
basic
issues
that
I
I
want
to
address.
G
I
I
can
answer
this
because
I've
I've
been
using
a
very
similar
environment
to
this
toolbox
for
about
a
year
now,
but
but
say
you're
in
the
process
of
hardware
enablement
and
all
that
Hardware
enablement
work
didn't
go
into
the
the
automotive
kernel
yet
on
on.
G
Basically
any
piece
of
Hardware
running
Linux
you
can
you
can
spin
up
this
toolbox
to
develop
on
and
in
and
out
of
OST
user
space
and
that's
not
necessarily
on
an
arm
board.
You
could
spin
up
this
toolbox
on
on
an
Intel,
laptop,
etc.
For
example,
one
use
case
I
use
this
for
is
I,
have
Linux
running
on
my
Mac
Mini
M1.
G
That's
that's!
Never
gonna
run
Red
Hat
Automotive
Linux
really,
but
what
I
can
do
is
spin
up
this
Rost
toolbox,
so
I
basically
have
an
auto
SD
environment
on
my
Apple
machine.
F
G
G
The
changes
are
minor
at
the
moment,
but
the
differences
are
minor
between
central
stream
and
the
automotive
string
distribution
at
the
moment,
but
it's
always
growing
so
purchase
an
example
of
that,
but
there
may
be
more
in
future.
Okay,.
G
Sometimes,
if
you
build,
if
you
build
an
RPM
on
sentos
stream,
9
versus
Auto
SD,
you
get
slightly
different
results
because
sometimes
to
to
build
an
automotive
correctly,
it
expects
like
the
ETC
OS
release
file
and
some
of
that
sort
of
stuff
to
have
the
automotive
labels
on
it.
So.
B
F
G
That's
a
valid
use
case,
yeah.
A
Any
any
further
questions
for
around:
oh
there
we
go.
F
I
have
a
last
one:
okay,
if
I
this
is
helping
me
to
build
images
for
my
specific
operating
system.
What's
about
cross,
build,
do
I
need
to
run
that
on
the
same
on
a
harm,
server
or
I
can
write
it
on
my
desktop
to
produce
home
binary.
F
F
To
be
honest
with
you
today,
most
of
the
business
is
on
arm.
I.
Think
everyone
agree
on
that.
We
see
some
demand
coming
on
risk.
F5
people
show
some
interest,
but
no
one
is
ready
to
pay
enough
money
for
us
to
work
on
it,
but
we
get
impressions
that
also
risk
fi
is
going
to
come
in
Dubai
pretty
soon
yeah
agreed.
H
I'll
just
raise
it
on
the
the
the
automotive
Sig
chat,
chat,
Channel
or
support
channel
John
Humphreys
from
TI
who's
here
today
has
been
reporting
some
issues,
interacting
with
some
red
Hatters
and
others
to
try
to
resolve
them.
H
I
admit
that
I
haven't
read
the
thread
carefully
enough
to
know
the
current
state
so
John.
If
you
could
share
that,
and
we
would
be
aware
if
there
was
any
urgency
in
in
helping
you
further.
D
Well,
so
I'm
really
kind
of
addressing
I
guess
what
what
Philip
is
talking
about
and
I
first
set
out
to
establish
a
good
development
environment
running
on
an
arm
device
itself.
So
there
was
no
cross
compilation
needed
no
qmu
or
anything
like
that
to
kind
of
emulate
that,
and
so
a
lot
of
the
the
so
I
have
so
so
TI
Texas
Instruments
has
a
a
nice
device
that
has
eight
a72
cores
and
the
board
that
we
sell
fairly
cheaply.
D
Yeah,
so
it's
got
32
gig
of
RAM,
so
it's
actually
a
nice,
powerful
environment
for
doing
builds
and-
and
so
that's
what
I've
been
working
on.
Is
it's
really
a
a
combination
of
getting
up
to
speed
in
the
Red
Hat
ecosystem,
as
well
as
getting
the
the
kernel
support
running
correctly
on
that
board,
with
right
now,
I'm
running
Fedora,
workstation
38
on
that
device
and
and
doing
bills
and
I
think
the
thing
that
I'm
running
into
right
now
is
is
won
a
few
specific.
D
How
I
built
kernel
and
working
through
that
now,
but
also
I
think
that
what
I
discovered
is
that
the
the
builds
for
Auto
se
have
been
with
rail
releases,
not
door
releases,
so
I
probably
made
that
mistake.
Early
on
should
have
picked
Cintas
rather
than
Fedora,
but.
H
D
So
so
what
what
I've
done
is
there's
this
nice
utility
called
mock
that
kind
of
like
emulates,
another
user
space
for
like
a
container
and
so
I've
been
running
that
with
a
a
a
a
Rel
image
or
a
rail
environment
to
get
around
that
so
I
I'm
making
good
progress.
But
it's
just
working
through
these
little
things
that
you
run
into
yeah.
H
Well,
I
think
that
your
comments
on
the
you
know
on
the
message
board
are
very
positive
right.
They
show
some
things
that
we
haven't
tested
that
you
know
some.
You
know
your
mileage
may
vary
and
some
work
is
left
to
the
reader
and
we
should
clean
that
up.
B
B
H
Think
that
you
know
Alberto
and
his
team
do
have
one
right
Sandra.
We.