►
From YouTube: Flatcar Container Linux release planning 2022-01-25
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
A
A
First
of
all,
we
have
a
bug
smashing
day
coming
up
and
there's
a
tracking
issue
for
the
bug
smashing
day
as
well,
which
you
can
check
in
the
issue.
Tracker
just
give
me
a
second.
A
The
bug
smashing
day
will
be
broadcast
on
youtube,
so
you
can
watch
the
stream
of
us
smashing
max
bugs
you're
invited
to
join
via
zoom
call
or
just
through
the
metrics
channel,
and
help
us
identify
bugs
and
help
us
smashbox.
A
So
the
whole
flat
commentators
team
will
just
spend
their
whole
day
on
friday,
smashing
bugs
from
the
issue
tracker
combing
issues
in
the
issue
tracker
and
so
on.
If
you
have
a
favorite
itch
that
you
need
scratched,
this
is
your
opportunity
to
make
your
voice
heard.
If
you've
always
wanted
to
start
smashing
box
in
flatcar
linux,
then
please
join
and
we'll
help
you
along.
A
We
have
a
number
of
talks
coming
up
at
fosdem.
It's
it's
five
talks
overall
and
handing
over
to
kai
to
introduce
his
talk.
B
Yeah,
I
submitted
a
talk
for
the
general
topic
of
how
to
use
immutable
infrastructure
with
flat
car
and
ignition,
and
it
will
touch
the
basic
principles
and
then
go
into
some
techniques
on
how
to
do
this
with
terraform
and
in
the
end,
I
will
also
show
how
you
can
reuse
your
instances,
while
still
updating
the
configuration
and
do
so
with
some
kind
of
proof
of
concept
hack
hack,
which
I
did
for
ignition
with
a
new
directive
where
you
can
reuse
the
root
for
fs
state
and
yeah,
avoid
having
to
redeploy
your
whole
instance.
C
Hi
everyone.
So
in
this
talk
we
cover
the
testing
process
of
flat
car
from
a
big
overview
and
we'll
dig
into
the
implementation
with
the
test
framework
we're
using
with
flat
pearl,
it's
called
color
and
we
see
a
tiny
example
of
how
to
write
test
for
flat
car
and
to
contribute
in
this
way
to
the
operating
system.
A
And
I
know
scion
has
a
talk
accepted
in
the
distributions
deaf
room,
which
is
about
hardening
container
hosts,
but
scion
is
battling
audio
issues.
A
So
these
are
our
foster
talks
and
that's
our
backsmashing
day.
The
final
noteworthy
news
is
that
we've
started
tracking
releases
in
issues
as
well,
giving
you
a
shoot
template
with
all
of
the
to
do's
that
we
go
through
until
something
finally
gets
released.
It's
currently
an
ongoing
release,
so
you
can
see
that
it's
live
in
action
and
here's
the
tracking
issue
for
that.
It's
just
in
the
issue
tracker.
It's
one
of
the
first
issues
there.
E
E
A
D
Yeah,
sorry
for
the
delay,
so
yeah
so
welcome
to
the
flat
car
real
estate
meeting.
Thank
you
either
for
taking
over
like
sorry
for
the
delay
and
so
yeah.
So
the
agenda
is,
we
will
be
discussing
the
current
release
and
doing
the
release
planning,
as
we
are
right
now
in
between
a
release.
So
we
are
not
doing
two
weeks
of
planning.
D
We
usually
do
two
weeks
of
planning
two
releases
of
planning,
but
this
time
we
are
just
focusing
on
the
next
one
as
it's
two
weeks
from
now
yeah.
So
I
see
peter
you
and
you
have
john,
but
yeah.
Would
you
like
to
introduce
once
more.
F
Yeah,
this
is
you're
talking
to
me,
hi
everybody.
This
is
peter
pullia
from
imperial
nice
to
nice
to
be
joining
you
again
for
those
unfamiliar
ampere
computing.
We
make
hyperscale
processors
that
are
aired,
64
architecture,
so
very
happy
to
be
joining
and
hearing
more
about
your
air
64
releases.
G
H
Okay,
good
yeah,
I'm
aryan,
ariane,
I've
been
running
a
flat
car
linux,
kubernetes
cluster
home
for
a
year
or
two.
I
think-
and
I
was
I've
been
at
the
first
meeting
of
this
months
ago
and
I
thought
I'd
join
again,
just
to
see
what's
what's
going
on
and
what's
up
and
I'm
going
to
be,
writing
a
blog
post
about
my
little
home
cluster
relatively
soon.
So
we'll
also
share
that
in
the
in
the
community.
Here
once
it's
out
awesome.
A
D
E
Hey
folks,
yeah
sorry,
I
was
having
some
trouble
connecting
I'm
joking,
I'm
part
of
the
kinfolk
team
at
microsoft
as
well,
though,
dealing
with
different
things
from
flat
car,
even
if
a
bit
related,
because
we
we
managed
the
and
we
developed
the
nebraska
project
that
manages
the
updates
for
flat
car,
I'm
I'm
actually
just
I
just
joined,
because
I
was
interested
in
in
learning
how
the
this
release
meeting
is
conducted.
E
I
Hi,
sorry,
I
get
my
camera
on
hi,
I'm
danielle,
I'm
a
program
manager
vladkar.
So
I
wanted
to
join
this
one
yeah
and
see
like
the
release
planning
into
a
couple
of
them,
but
like
interested
how
it
goes
now.
I
D
D
We
now
do
like
we
don't
do
all
the
introductions
we
just
do.
The
folks
are
joining
new,
so
yeah.
So
I
guess
that's
all.
So,
let's
move
on
to
the
release
planning
yeah
so
before
that,
let's,
let's
give
you
a
current
state,
so
we
are
doing
a
release
right
now.
We
are
in
between
a
release.
So
if
you
joined
the
matrix
channel,
you
would
be
seeing
the
status
that
we
are
doing.
D
The
the
progression
like
today
was
a
really
busy
day
throughout
the
through
the
day,
and
things
are
looking
good
and
we
should
be
having
releases
like
out
by
end
of
the
day
or
hopefully,
tomorrow
and
then
theodore
already
talked
about
the
fostering
talk
so
do
join.
We
have
four
talks.
If
I
recall
correctly
five,
we
have
five
five
talks:
yeah,
okay,
so
five
talks
we
have
and
oh
yeah.
This
is
doing
two
talks.
D
So,
yes,
we
have
five
talks,
so
yeah
do
join
the
to
join
the
dev
rooms
and
give
feedbacks
on
the
talks
and
yeah
would
love
to
see
you
there.
D
Then
we
have
the
bug
smashing
day,
which
is
coming.
It
would
be
happening
on
a
matrix
channel.
We
would
be
having
we're
trying
to
get
a
stream
as
well.
D
We
so
just
join
in
the
matrix
channel,
we'll
have
more
information
on
the
day
of
the
box
smashing
day,
and
the
plan
is
that
we
would
be
going
through
all
the
issues
and
a
good
a
good
day
to
cont
if
you
are
looking
to
contribute
a
good
day
to
contribute,
throw
in
ideas
open
up
even
open
up,
I
would
say
new
issues
if
you
have
and
closing
the
older
ones
which
are
either
fixed,
not
relevant
yeah
so
see,
do
remember.
D
The
date
is
this
friday,
which
is
20th
of
january
cool,
moving
on
to
the
planning
board.
So
is
the
planning
board
visible,
yeah
cool?
Okay?
So,
as
I
told
we
are
doing
so
just
for
the
new
folks,
how
I'll
just
let
you
know
how
we
plan
the
release.
So
we
have
a
plant
board.
We
have
a
long
term
board
and
then
we
have
in
progress
ready
to
review
ready
to
release,
and
so
what
planned
is?
D
Basically,
we
if
we
when
we
are
introducing
planning,
introducing
new,
bugs
or
sorry
introducing
new
bugs
that
needs
to
be
fixed,
so
we
introduce
it
to
the
planning
board
and
then
as
it
progresses,
we
move
it
through
the
issues.
Since
the
boards
are
connected
to
the
issues
we
directly
mark
them,
control
them
how
they
move
over
to
different
boards
through
the
issues
itself
and
then,
like
you,
can
see
the
planning
for
right
now,
the
planning
is
happening
for
the
current
release.
It's
not
done
yet.
D
So
it's
still
open
the
next
one
is
will
be
happening
on
7th
of
february.
So
we
will
be
planning
for
that
in
the
in
this
meeting
right
now,
and
then
we
have
ready
to
release
as
soon
as
they
are
released.
We
move
them
as
done
like
released
and
after
after
three
releases,
we
remove
the
whole
whole
board
together.
So
at
most
we
have
three
to
four
released
boards
and
then
ready
to
release
would
be
two
and
then
the
other
boards
are
just
for
planning.
D
Long
term
are
issues
which
ends
up
more
than
like.
We
end
up
spending
more
than
two
weeks,
so
we
usually
put
that
in
long
term
and
people
usually
give
status
updates.
We
don't
have
any
one
right
now,
so,
okay,
so
now
moving
on
to
the
release
planning.
So
in
this
release
we
are,
do
we
merged
a
couple
of
them
a
couple
of
the
packages,
but
a
lot
of
them
were
in
progress,
so
those
things
we
would
be
working
on
the
next
one.
D
So
right
now,
so
I
moved
this
particular
backlog
and
then
in
progress.
It
was
a
bunch,
so
I
just
moved
them
we,
I
did
not
add
any
new
packages
that
need
to
be
added,
because
this
is
a
good
amount
and
given
we
are
working
on
systemd
systemd,
we
planned
for
seven
february.
Thanks
to
questions
work.
We
have
done
a
good
progress
there,
so
yeah,
so
anything
other
than
this,
that
you
think
that
needs
attention
or
any
package
that
needs
to
be
added.
D
No
okay,
so
I
think
this
is
good
and
yeah,
so
we
are
working
on
the
we
are
working
on
the
systemd
updates
and
we'll
start
as
soon
as
we
complete
of
the
release
we'll
resume
the
work
on
the
in
progress
issues.
I
guess
so
and.
D
Any
issues
that
you
want
to
like
right
now
we
have
the
ipv6
one,
so
we
merged
the
changes
that
needed,
but
they
have
not
been
merged
into
the
like
core.
The
coreos
overlay
packages
has
not
been
updated
to
refer
to
the
boot
engine
and
it
changes
so
this
that
would
happen
this
week.
So
we
would
have
the
ipv6
fixes
in
and
yeah
this
bug
the
alpha
three
one,
the
excellent
spot.
This
can
be
moved
method
right
to.
C
B
B
D
This
entire
yeah,
so
I'm
putting
this
here
and
I
think
it
this
release-
would
be
very
package
heavy
like
we
would
be
pushing
a
lot
of
packages
and
the
update
so
other
than
that.
That
is
there
anything
that
you
want
to
talk
about.
G
Today
I
discovered
a
security
issue
in
geology
and
gentle
already
updated
to
listen
to
2033
that
are
nine.
So
I
added
that
in
to
the
board
of
release
february
7th.
D
G
We
have
two
options
we
can
just
bump
to
the
br9
of
2.33
or
we
can
just
jump
to
the
next
version,
2.34,
so
yeah.
Whoever
wants
to
work
on
julep
series,
so
you
can
choose
between
yeah.
A
Okay,
okay,
I
think
I
think
if
we
wanna
jump
to
34,
then
we
would
need
to
do
both
right.
If
it's
a
security
issue,
we
need
the
bump
to
33
to
the
latest
version,
at
least
for
beta
unstable,
because
we
don't
want
to
switch
glc's
in
in
a
pitch
level
release
and
for
the
next
alpha
major
release,
we
may
investigate
bumping
to
3.34,
which
can
be
an
exciting
job.
B
D
Thank
you.
Thank
you
rongsu,
so
yeah,
it's
like
we
are
approaching
the
same
way
for
systemd
as
well.
We
are
updating
this
249
in
the
other
branches,
but
250
would
be
in
alpha,
but
anyways
yeah.
Anything
else
matthew
was
saying
something.
A
D
Yeah
yeah,
hopefully
the
next
one
would
be
like
the
bigger
than
the
current
one
but
yeah.
So,
let's
see
and
if
no
question
then
I
can
return
back
to
the
slides.
D
Yes,
so
folks
we
are
like,
if
you
would
like
to
contribute,
do
like
spread.
The
word
tell
to
other
communities,
there's
a
lot
of
work
going
on
and
there's
a
lot
of
opportunities
for
contribution,
and
given
the
box
matching
days
coming
up,
it's
a
it's
a
good
way
to
start
contributing
and
we'll
try
to
do
a
stream
so
that,
if
you
are
not
a
matrix,
you
can
also
follow
through
the
screen.
Use
a
youtube
chat,
probably-
and
we
are
there
on
matrix,
also
bridge
to
irc.