►
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
We
want
to
discuss
fips
right.
Let's
start
with
dates.
B
A
Today's
agenda
items
tips,
so
we
got
a
permission
from
canonical
to
start
creating
VIPs
stem
cells
for
internal
use
within
the
foundation,
which
means
we
can
produce
stem
cells
that
cannot
go
on
Porsche
IO,
but
we
can
put
them
in
a
private
bucket
and
then
use
them
in
say
CF
deployment,
but
also
component
pipelines
for
testing
purposes.
A
So
we
can
find
issues
with
components
that
are
incompatible
with
fips
and
I
have
a
way
to
fix
those
issues,
Upstream
and
then
it's
up
to
the
different
vendors
to
negotiate
their
own
contracts
with
canonical
and
build
or
figure
out
their
own
ways
of
producing
a
Vib
stem
cell.
But
at
least
we
know
that
the
functionality
in
the
stem
cell
Builder
forfeit,
producing
Vib
stem
cell
FIB,
stem
cells
has
been
tested
and
that
the
stem
cells
produced
by
that
are
compatible
with
CF
deployment.
At
least
that's
the
goal.
A
There's
a
few
few
steps
that
need
to
happen.
First
off.
We
need
to
go
and
build
a
VIPs
Jammy
stem
cell.
That's
quite
a
big
one
and
that
work
I
believe
there
are
some
interest
from
sap
and
contributing
and
I
know
that
from
the
VMware
side
we
have
some
pressure
to
take
on
that
work
and
I
believe
that
Ramon
potentially
maybe
wants
to
be
involved.
You
need
to
figure
that
one
out
it's.
C
A
A
Yeah
so
the
foundation
so
like
we
would
the
the
so
we
want
a
pipeline,
a
public
pipeline,
I
guess,
but
the
end
result
of
it
is
not
going
to
be
public
right.
So
we
have
the
I,
don't
know
CI
dot
bar.
What's
its
borscht.ci.
We
have
this
instant
Concourse
instance,
which
is
owned
by
the
foundation,
and
this
is
where
we
already
have
bionic
fips
right.
So
we
have
a
stem
a
pipeline
here
to
create
a
bionic
whip
stem
cell.
You
want
something
like
that.
D
A
I
I
will
continue
and
I
can
recap
if
he
joins
back
I.
Don't
know
it's
awkward.
If
we
wait
here,
10
minutes
for
his
internet
issues
to
go
away
so
yeah.
We
want
a
version
of
this
pipeline,
but
then
for
Jimmy,
and
we
probably
have
to
figure
some
things
out
or
backboard.
Some
of
the
features
that
were
on
this
Branch
to
be
able
to
Stefan
is
coming
back.
A
Yeah
no
problem,
so
we
need
a
a
Jimmy
version
as
a
first
step
of
this
pipeline
and
I
will
need
some
backboarding
of
the
the
stuff
that
was
done
on
the
bionic
Branch
to
the
gme
branch.
A
But
yeah
it's
just
work
that
needs
to
happen
and
I
I
feel
like
we
need
to.
This
is
the
first
step
and
we
as
a
group,
need
to
figure
out
how
we
want
to
collaborate
basically,
because
there's
probably
multiple
people
that
want
to
or
want
to
help
in
this,
but
yeah
I
think.
Last
time
we
did
this
cross-cutting
collaboration.
It
was
just
mainly
driving
the
work
so
yeah
I'm
I'm,
open
to
IDs.
A
C
And
because
of
at
sap,
we
had
an
agreement
with
with
canonical
that
they
built
the
trips
themselves,
I
know,
but
when
they
provide
it
within
repository,
where
we
get
access
to
where
we
can
download
it
and
we'll
handle
the
license.
So
yeah
University
also
solution
for
the
for
the
community
or.
A
Yeah,
but
they
are
Downstream
of
this
pipeline,
so
canonical
helped
us
build
this
Pipeline
and
then,
if
this
pipeline
goes
green,
this
is
basically
the
stem
cell
Builder
right,
there's
code
that
goes
into
the
stem
cell
Builder.
If
they
make
changes
to
the
stem
cell
Builder,
we
want
to
validate
that
the
stem
cell
Builder
still
still
works.
That's
why
why
we
have
this
Pipeline
and
then
they
have
their
internal
Downstream
process
to
republish
it.
A
So
we
want
that,
but
this
time
around
we
we
are
actually
allowed
to
use
the
stem
cell
that
we
create
right.
First,
it
was
just
this
pipeline
was
just
for
validating
that
the
stem
cell
Builder
worked
now
we're
going
to
be
able
to
also
use
the
stem
cell
in
at
least
the
other
pipelines
to
validate
further
VIPs
compatibility,
but.
F
C
C
So
but
let's
say
just
try
to
understand,
okay,
but
that's
fine
to
to
hear
that
plan
by
the
community,
but
makes
a
lot
of
sense.
B
At
sap,
so
so
it
means
the
the.
C
Stem
cell
is
now
as
time,
so
it's
not
available
because
of
the
bill
does
not
exist,
but
the
license
issue
is
resolved
and
canonical
mean
time
has
also
confirmed
that
the
chemi
operating
system
can
get
the
flip
support.
When
you
build
it.
A
Or
maybe
it's
still
in
progress
like,
but
it
should
be
lending
like
somewhere
this
month,
so
we
we
are
basically
clear,
like
there's
no
blockers
from
canonical
to
start
his
work
right.
It's
now
just
up
to
us
to
build
that
pipeline,
got
it
yeah
and
and
start
creating
this,
the
stem
cell.
A
C
C
What
I
think
we
should
step
on
it
yeah
and
once
now
to
you
use
fips
themselves?
What
would,
when
the
recommended
Day
by
the
community?
Would
it
be
just
go
to
canonical
just
buy
it
and
deploy
the
platform
tree?
That's
it.
E
So
what
I
think
we
should
do
is
like
once
we
have
the
whole
pipeline
built
up
and
then
once
we
test
it
like
with
CF
deployment
and
everything,
we
will
just
do
a
release
of
that
of
that
branch,
and
basically,
what
people
can
do
is
basically
use
that
release
and
then
they
can
have
their
own
pipeline
or
whatever
set
up
where
they,
where
they
use
their
licensing
code,
were
to
create
the
tarball,
the
stem
cell
turbo
that
they
actually
need.
I.
Think
that's
the
proper.
E
It's
the
same
is
what
we're
doing
now.
We
just
all.
We
also
now
do
a
stem
cell
release,
but
now
we
put
up,
we
create
all
the
tar
balls
and
we
put
them
in
a
blob
store,
but
we
can
also
now
do
it
like,
basically
also
in
a
we
can
set
up
a
release
in
a
GitHub
page
or
whatever,
where
we
can
say.
This
tag
has
been
tested
and
you
can
now
build
this
and.
A
We
can
figure
out
all
the
details
yeah,
so
if
we
want
to
do
it
properly,
we
should
find
a
way
to
pin
our
our
apps
packages
yeah,
because
those
are
floating
right.
So
there's
this
time
aspect
to
it.
So
you
can
check
out
attack
tag,
but
you
you
will
not
be
able
to
reproduce
the
same.
You
you
are
not
able
to
get
the
same.
Stem
cell
I
mean
this
is
a
broader
yeah.
I
know
it
is
currently
a
problem.
A
What
we
we
are
not
as
affected,
because
we
are
all
consuming
the
same
artifacts
right.
So
that's
why
it's
not
that
visible,
but
stem
cell
reproducibility,
like
from
a
checked
out,
commit,
would
greatly
help.
E
A
F
That
data
is
so
late
in
the
build
process.
It
really
feels
like
there's
two
separate
there's
like
building
the
initial
stem
cell
and
then
there's
a
totally
different
process
for
rebuilding
that
stem
cell,
that
we
don't
currently
have
that
we
need
to
build
like
I,
don't
see
any
other
way
of
doing
it.
Yeah.
E
A
Is
we
could
like
to
improve
our
reproducibility
of
our
stem
cell
in
general
right,
like
that's,
even
a
useful
thing
to
have
for
the
non-fip
stem
cells
so
yeah?
You
could
do
that
by
decoupling,
like
the
the
package
snapshot
generation,
like
moving
that
really
in
the
front
of
the
stem
cell,
so
like
on
a
I,
don't
know
whatever
on
an
interval
or
something
it
would
run
a
job
just
get
a
snapshot
of
the
packages
it
would
install.
A
F
E
A
Could
be
a
thing
where
we
like
rewrite?
Do
the
mapping
of
like
oh
you're
asking
for
this
thing
or
then
you
actually
mean
this
particular
version
of
this
thing,
but
yeah
that
would
be
a
separate
track
of
work
that
would
greatly
help
with
the
I.
Don't
know
at
least
the
I
mean
it
becomes
more
relevant
if
people
want
to
start
rebuilding
a
VIP
stem
cell
right.
A
So
it's
basically,
we
need
a
VIP
stem
cell
first
then
we
want
to
get
all
the
components
to
be
compatible
and
then
the
vendors
want
to
have
a
reproducible
way
of
producing
that
stem
cell
internally.
A
A
Don't
know,
like
that's
I,
think
a
third
work
stream,
where
we
we
as
individual
vendors,
need
to
have
a
talk
with
canonical,
maybe
again
to
discuss
if
we
can
actually
just
redistribute
the
stem
cell
like
if
they
have
ideas
on
how
we
want
to
do
that.
That
would
be
the
best
outcome,
but
we
cannot
count
on
that
right,
so
I
think
the
reproducible
stem
cell
work
is
also
valuable.
A
Yeah
I
mean
it's
valuable
in
itself
and
it
would
help
with
the
reduced
or
not
reduced,
using
rebuilding
a
stem
cell
internally.
Smaller.
F
B
A
That
case
we
already
solved
that
problem
yeah.
We
solved
that
for
the
bionic
one.
A
F
Presumably,
the
target
would
be
anything
that
canonaco
can.
Support
seems
like
if
we
currently
cut
a
stem.
If,
if
the
foundation
currently
cuts
a
stem
cell
for
it
they're
well,
do
we
we
don't
cut.
That's
not
true.
We
cut
some
weird
ones,
but
most
likely
one
of
the
vendors
is
going
to
want
to
ship
that
as
a
fips
version.
E
So
yeah
I
think
AWS
gcp
Azure
would
probably
the
most
like
yeah,
probably.
E
Yeah,
well,
we
don't
support
it
anyway,
so
and
Ali
cloud
is
probably
also
going
to
be
a.
B
G
C
And
do
you
have
also
some
timeline
in
mind
that
in
such
an
flip.
A
Stencil
could
be
available.
We
we
hope
end
of
the
year.
Okay,
no,
not
like
that.
That's
when
we
want
to
have
everything
that,
like
we
needed
earlier,
we
want
the
this
is
like
for
everything
being
at
least
compatible-ish,
as
in
CF
deployment
deploys
with
VIPs
that
some
somewhere
close
to
the
end
of
the
year.
C
Yeah
I'm
just
asking
for
the
for
the
stem
cell
itself,
not
not
for
the
CF
deployment.
So
for
me
it
sure
CF
deployment
is
something
that
comes
later
and
end
of
the
year
would
be
fine,
yeah,
so
yeah
it
would
be
perfect,
but
nobody
knows
what
the
problems
are
now
in
CF
deployment.
C
No,
we
tried
already
the
bionic
FIB
stem
cell
so
and
had
already
a
working
Bosch
and
a
working
great
top,
so
some
components
could
show
that
some
components
support
fips,
and
this
is
a
state
we
would
like
to
reach
as
soon
as
possible,
also
with
the
Chinese
them.
So
this
is
why
I'm
interested
just
in
getting
the
FIB
stem
cell
and
not
expecting
that
it
is
already
validated
for
the
CF
deployment.
So
we
take
it.
A
C
A
Internally,
so
you
as
an
as
a
Target,
you
have
using
it
with
for
the
voice
director
right.
C
And
let's
say
so
so
this
is
just
sap
internal,
but
we
say
it
would
be
cool
to
get
the
stem
cell
itself
as
a
kind
of
Milestone
where
in
use,
because
of
it's
not
trust
what
we
are
waiting
for
on
the
final
CF
deployment.
We
have
also
the
demonstrate
when
we
get
progress
on
on
the
topic
here.
A
Yeah
the
the
problem
is
that
for
the
internal
validation,
you
will
have
to
work
with
canonical
to
get
the
stem
cell
yeah
right,
because
the
the
stem
cell
that
were
like
we
could
try
to
like
as
an
intermediate
goal,
also
try
to
use
the
VIP
stem
cell
with
the
in
the
Bosch
directors
pipeline
Upstream
right.
That
could
be
a
thing
we
do
before
going
for
CF
deployment.
No.
A
That's
that's
the
same.
It
requires
less
Hoops.
If
we
do
it
in
the
Upstream,
because
we
have
full,
we
have
the
the
stem,
the
the
license.
Yeah.
C
Yeah
so
because
of
let's
say
when
we
were
together
with
canonical,
the
Assumption
was
already
can
only
deliver
the
stem
cell,
so
this
is
what
we
had
with
with
the
bionic
version,
so
it
was
built
by
a
canonical.
We
try
to
deploy
it,
so
that
was
a
delivery.
Channel
I
would
say
it
also
resolve
the
license
problem.
C
Now
now,
I
just
see
that,
let's
say
when,
when
it's
now
the
case
with
the
stem
cells
built
by
the
community,
it
doesn't,
it
means
it's
not
coming
from
canonical
anymore.
No.
A
C
It's
complicated
so
but
let's
say
for
us,
so
we
have
to
ask
so
so
what
I
understand
is
or
what
I'm
interested
in-
and
this
is
some
answer
economic
lab
to
give.
When
can
we
get
the
stem
cell.
A
Yes
and
then
you're
gonna
put
pressure
on
canonical
and
then
they
are
going
to
come
to
us
again
right
to
help
with
the
stem
cell
Builder
to
actually
add
Jimmy
support,
I
mean
that
and
then
we're
going
to
build
this
pipeline.
So
that's
what
I
mean
like
there's,
probably
going
to
be
people
from
VMware,
fap
and
canonical
that
all
want
to
have
make
this
pipeline
happen
because
we're
all
interested
in
it.
D
A
Yeah
so
I
think
the
good
first
step
is
to
create
a
channel
like
we
did
with
bionic
invite
the
people
that
want
to
help,
and
then
we
go
from
there.
But
at
least
we
have
a
a
plan.
I
guess.
Maybe
it
would
be
good
if
we
write
some
of
this
down,
but
I
mean
this
college
recorders,
which
also
counts
as.
D
A
I
think
we
should
so
first,
we
need
to
start
to
work
on
the
the
pipeline,
because
that's
just
our
working
group
and
if
we
feel
like
we're
getting
close
to
making
something
work,
I
mean
it
also
depends
right.
Do
we
need
an
RFC
if,
like
the,
if
it's
just
the
CF
deployment
right,
we
just
want
to
work
with
the
deployment
working
group,
which
is
probably
mostly
influenced
by
what
SMP
wants,
because
it's
staffed
by
sap?
So
if
sap
wants
fits
testing,
I
mean
sure
we
can
have
an
RFC.
A
D
A
D
Validation,
whether
the
validation
will
happen
finally,
yeah,
we
can
discuss
this
in
the
Tuesday,
maybe
maybe
just
on
CF
deployment.
A
Side
yeah
like
as
a
first
step
right
and
then
it
is
like
up
to
the
working
groups
to
also
like
if
they
feel
like
they
want
faster
feedback
right
and
they
want
to
incorporate
VIPs
in
their,
but
that's
optional
right.
That
would
be
a
logical,
Next
Step,
but
I
wouldn't
want
to
make
that
a
requirement
before
like
say
the
end
of
the
year
right
like
if
we
can
have
CF
deployment.
Do
the
final
validation,
that's
good
enough
for
now.
A
Good
point:
yeah:
don't
we
at
least
have
like
some
Central
agreement
on
that
this?
This
is
a
thing
that
we're
all
going
to
be
working
on
yeah
but
I
mean
to
be
honest,
I
think
it
will
be
pretty
easy,
given
that
there's
some
pressure
on
the
VMware
side,
at
least
to
make
this
happen,
so
that
should
help
prioritize
getting
these
fixes
through,
but
I
mean
still
it's
good
to
on.
The
yeah
also
create
an
RFC
so
that
we
have
some
visibility,
public
visibility
and
into
this
as
well
yeah.
A
I
think
next
step
is
create
a
channel
and
then
invite
people
and
start
working
on
this.
The
pipeline
yeah.
Okay,
so
we
can
close
the
VIPs
topic
and
continue
with
reviewing
PRS.
H
A
Yeah
I
think
Benjamin
I
took
you
out
of
the
rotation
for
stem
cell
or
for
pull
request,
reviews
I'm,
happy
to
add
you
back
but
yeah
just
say.
If
you
have
availability
to
look
at
these
things
yeah,
you
can
add
me
back.
Okay,
yeah
you're
back
I
will
add
you
back
to
the
rotation
after
the
call.
B
B
A
F
A
A
F
Speaking
speaking
of
Branch
protection,
there's
the
discussion
topic
around
switching
from
deploy,
keys
to
bots
and
I
had
to
make
a
fine-grained
access
token
the
other
day,
and
it
did
not.
Let
me
select
which
repos
it
has
access
to.
You
can
only
select
repos.
It
seems
like
in
that
user's
GitHub
account,
not
things
they
have
access
to.
Just
like
the
Bosch
admin
bot,
its
own
personal
repos
are
the
only
things
that
can
grit
that
token
access
to
or
everything
which
doesn't
seem
fine-grained.
If
you
ask
me,
no
that's,
but.
F
E
For
this
one
I
wanted
to
add
my
review,
but
I
I
cannot
test
it
locally
because
I
don't
have
windows.
So
I
did
this
in
BBL
and
it
seems
perfectly
fine.
D
D
F
A
F
Well,
no,
it's
that
the
windows
team
had
some
sort
of
transitional
period
and,
like
the
make
file
in
stem,
build,
isn't
the
one
that's
actually
used
to
build
stem
cells,
there's
that
one
in
that
other
repo
that
gets
copied
in
and
replaced
the
the
old
makefell
gets
copied
and
that
one
gets
used
and
said
nobody's
quite
sure
why
or
when
or
how
it
changes
things
and
nobody's
bothered
looking
at
it,
because
Windows
stem
cells
generally
just
work.
So
it's
this
thorn
in
our
side
that
we've
not
looked
at.
E
Yeah,
this
also
seems
like
no
brainerds
like
go
change,
something
and
I
would
say
local
seems
the
same
thing
to
do,
because
we
use
it.
We
have
set
a
specific
Go
versions
in
our
sea
ice
anyways.
F
E
F
So
that'll
apply
to
all
of
the
current
go
packages,
but
it
just
doesn't
do
anything
on
the
other
ones.
Presumably,.
E
E
F
It's
probably
harmless
to
set
it
and
go
120
and
119.
It
probably
doesn't
do
anything
or
it
doesn't
cause
harm.
At
least
yeah
and
I
would
assume
that
if
somebody
actually
doesn't
want
this,
you
have
a
release
that
actually
doesn't
include
the
vendored
files,
because
it's
not
doesn't
work
in
an
air,
gapped
environment.
You
could
just
source
that
and
then
unset
this
afterwards.
If
you
wanted
to
so,
yes
seems
good.
E
B
H
A
No,
but
your
internet
is
lagging
oh
wait.
It
happens.
B
E
F
I,
don't
think
it's
your
internet.
Mine
came
up
blank
today,
too
I
think
github's
having
some
weird
things.
E
F
All
the
code
I've
ever
seen
also
says
that
I
wonder
if
this
could
be
a
false
unresponsive
agent,
like
in
large
deployments
when
you
do
a
Bosch
VMS.
It
gives
them
like
five
seconds
to
respond.
So
if
you
have
like
600
VMS
somebody's
not
coming
back
in
time
and
the
CLI
says
that
one's
unresponsive,
even
if
it's
still
heart,
beating
just
fine,
so
normal
health
monitor,
gives
VMS
like
45
seconds,
whereas
Bosch
VMS
only
gives
him
like
five
seconds
so
that
could
be
what's
going
on
here.
We've
definitely
seen
that
before.
D
What
what
is
when
look
it
looks
like
he
has
only
one
instance.
Is
it
then.
D
So
somewhere
in
the
Bosch.
D
B
A
A
A
I
mean
we
can't
point
to
stop
agents,
let's
call
them
right.
Our
school
for
lease
has
a
stop
agent
script.
H
H
A
A
A
E
H
Because
it's
documented
that
we
are
metrics,
you
receive
basically
some
some
yeah
metrics
about
the
excess
on
different
endpoints
right,
but
this
is
only
true
for
the
Matrix
endpoint
itself.
D
Yeah
it
says
that
you
get
genetic
metrics
about
the
Bosch.
Apis
parameters
provides
but
yeah,
it's
not
the
case.
So
if
you're
yeah,
if
you're
done
yeah,
want
to
improve
this,
then
we
have
to
fix
the
toxin.
F
D
But
there
are
different
processes:
I
I,
don't
remember
that
the
architecture
changed
so
that
so
we
have
a
Matrix
Service
process
and
the
Bosch
director
and.
F
B
E
D
A
Well,
oh
yeah!
This
is
something
that
you
are
doing.
E
Spot
prices
instead
of
the
and
with
the
provisioning
model,
and
so
they
now
have
two
ways
how
to
create
spot
VMS,
basically
same
as
in
AWS.
F
E
You
have
it,
but
B
is
just
I,
want
the
cheapest
the
cheapest
option
in
this
data
center,
and
do
you
have
it
yes
or
no,
and
then
basically
the
only
thing
you
have
is
like
like
when
it's
shut
down,
so
you
have
a
fighter
for
the
current
behavior
is
like
you,
can
only
have
it
for
Max
24
hours
and
the
new
behavior
is
you
can
have
it
as
long
as
we
don't
need
it.
F
I
thought
that
first
link
says
something
about
like
bidding
or
something
or
you
have
to
specify
a
price.
F
F
E
E
F
By
the
way,
AWS
advertises
theirs
as
up
to
a
90
discount,
which
I
suspect
is
why
it
says
up
to
a
91
discount,
probably.
E
E
It's
also
pretty
hard
to
find
the
pricing
prices
for
for
each
region
and.
A
E
E
A
Yeah
I
think
we
we
just
set
this
to
created
the
story.
This
issue,
which
is,
did
we
put
yeah?
We
put
it
on
the
wish
list.
Okay,
it's
important
because
it's
yeah,
it's
not
so
safe
to
do
that.
Now,
in
this
time
itself,
we
want
to
do
that.
The
next
stem
cell.
F
F
Stacks,
just
you
just
hope
that
it
lines
up
right
now,
so
we
want
to
redo
the
logic,
but
we
don't
want
to
do
that
in
Jammy
right
now,
because
it
would
be
a
big
change.
C
G
G
F
Yeah
and
once
we
do
the
2404
work,
we
should
be
easier
to
make
a
config
in
the
stem
cell
Builder
that
the
the
CPI
is
able
to
provide
an
ID
that
will
actually
work
for
that
right.
Now,
it's
very
very
difficult
to
know
exactly
what's
going
to
happen
in
it
all
the
is.