►
From YouTube: Foundational Infrastructure Working Group [Jan 6, 2022]
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
Okay:
let's
look
at
the
agenda.
A
A
A
B
A
Okay,
yeah,
there
are
some
agenda
items
I
saw
that
were
brought
in
someone
from
the
uaa
in
here.
In
that
call.
B
B
A
D
I
we
were
looking
into
this
project.
We
saw
that
event,
log
forwarders
on
our
login
list
and
the
two
things
we
I
noticed
is
one
I
have
no
permissions
on
it.
The
other
thing
is,
we
were
looking
into
it
to
try
and
figure
out
whether
or
not
we
should
continue
it
as
a
project
or
whether
we
should
try
and
plan
some
sort
of
way
to
integrate
it
with
windows
dislike
release,
but
I
don't
know
I
was
just
reaching
out
to
see
if
anyone
had
any
thoughts.
D
A
I
also
don't
know
I
I
think
david
stevenson
put
your
name
there
and
put
all
this
together,
so
we're
we're
still
trying
to
navigate
like
how
we
are
supposed
to
collaborate
with
the
different
areas.
So,
like
last
call
before
the
holiday
break,
we
had
the
uaa
folks
and
credit
folks
join.
A
A
But
it's
not
like.
We
can
say
we're
gonna,
do
a
bunch
of
engineering
work.
That's
up
to
the
foundation
members.
A
A
Yeah,
so
if
you're
looking
to
do
like
a
bigger
effort,
I
would
try
to
to
find
support
within
maybe
vmware.
Maybe
ask
david
stevenson.
A
If
that's
something
or
I
don't
know
who
else
to
ask
but
yeah,
and
then
we
could
have
like
support
to
do
that
type
of
work
and
then
there
would
be
a
pull
request
to
do
the
work
and
that
would
be
reviewed
by
the
people
in
this
call
or
there's
actually
more
people,
but
on
that
list
so
and
in
these
skill
calls
we
typically
just
go
over
the
different,
so
we
have
a
getup
project
and
then
in
there
we
have
different
tabs
for
the
different
areas.
C
A
D
It's
so
my
understanding
is
it's
it's
a
thing
that
forwards
the
windows
event
logs
the
assist
log
kind
of
the
like
os
level
logs,
but
as
far
as
I
understand,
if
it
exists,
possibly
a
it
could
be
brought
into
windows
log
release
and
if
it
was
brought
into
windows
system
release,
then
it
would
support
tls,
which
it
currently
doesn't
and
then
b.
A
That's
that
let's
go
to
the
true
the
bosch
yard
and
then
feel
free
to
drop
off.
If
you
don't
find
this
interesting.
A
Oh
yeah,
this
is
blocked
on
the
pr
that
needs
this
one
has
been
approved.
We
are
just
waiting
for
the
dependent,
the
actual
implementation
to
be
merged.
This
is
the
docs
vr.
A
So
I
would
like
the
author
of
the
pr
to
address
the
comment
from.
C
No
because
he
said
at
the
bottom,
he
says,
as
is
so
for
now
I
strongly
merging
these
prs.
Is
it's
just
a
notification
from
please
do
this
in
the
next
time?
A
C
A
But
it
could
also,
if
it's
like,
I'm
not
okay
with
I
strongly
I'm
strongly.
I
strongly
okay,
but
I
I
don't
know
okay,
I
will
ask
him
and
then
we
can.
If
he's
okay
with
it,
we
can
merge
it.
E
E
C
A
A
B
A
I
expect
him
to
respond
on
this
quickly
so
and
we
can
will
be
merged.
Okay,
so
that's
good,
and
then
we
can
merge
this
one
as
well.
A
F
So
I
have
pushed
new
code
here
today.
Okay-
and
hopefully
this
should
fix
the
issue-
well
so
donatello
from
ibm
to
I
we
had
a
meeting
one
month
ago.
Nearly
four
weeks
ago,
he
told
me
software
was.
F
Due
to
be
retired
sometime
in
the
future
so-
and
he
could
not
provide
me
any
thought
on
any
implementation,
so
I
just
implemented
a
small
in-memory
cache
for
already
seen
disk
ids
and
already
resolved
device
path
in
slash
dev,
and
this
solves
the
the
issue
basically
so
that
the
resolving
can
be
equal
many
times
reaching
out
the
same
result.
F
And
the
cache
holds
ten
entries
and
removed
the
oldest
one,
whenever
going
over
over
that,
but
few
people
are
mounting
more
than
10
days
like
yes,
10
percent.
A
No,
that's
super
fun,
okay,
so
we
should
we
already
reached
out
six
hours
ago
right
so
that
we
just
wait
for
that.
And
then
this
needs
to
be
reviewed
and
we
can
merge
it.
A
A
There's
some
comments.
I
also
will
look
into
that
because
I
think
it's
we
could
do
with
some
structural
changes.
A
A
I
think
we
should
be
really
explicit
about
it
being
a
vip
stem
cell,
so
maybe
like
even
the
name
of
the
stem
cell,
so
it
should
be
like
ubuntu-fibs
or
something
right
in
the
deployment
manifest
so
yeah.
I
think
it
should
be
more
of
like
an
argument
in
the
the
rape
task
to
build
the
stem
cell,
but,
like
that's
just,
I
need
to
dig
in
to
how
I
think
that
should
what
that
should
look
like
we'll
do
that.
A
But
apart
from
that,
the
changes
themselves
are
seem.
Okay
and
ramon
has
been
working
on
setting
up
ci
to
actually
test
the
fib
stem
cell
and
that's
a
broader
discussion.
We
are
currently
having
with
canonical
to
see
if
we
can
bring
this
support
in
a
more
supported
way
to
the
broader
community.
But
that's
still
an
ongoing
discussion.
A
A
No,
it's
not
much.
No,
this
is
an
ongoing
or
I
think
it's
waiting
for
on
a
review
from
you
as
well.
I
guess.
A
A
But
it
would
be
good
if
constantly,
but
I
think
constantine
is.
F
Yeah-
and
it
also
means
that,
if
we
remove
registry,
we
are
dropping
support
for
v1
contract
with
cpi,
yes,
all
together,
and
it
has
quite
a
lot
of
other
impacts.
I
guess
possibly
document
that.
F
And
there
is
also
relation
with
contract
with
stem
cells.
If
I
remember
correctly,
I'm
I'm
not
sure.
F
E
A
That's
the
the
best
thing
to
do,
because
it's
this
is
more
of
a
like.
This
was
a
story
in
the
backlog
vmware,
it's
just
like
cleanup
of
technical
depth,
something
we
haven't
like.
We
have
had
this
v2
cpi
for
a
long
long
time
right.
So
it's
about
time
to
start
actually
remove
all
codes
or
not,
and
also
it's
like
an
a
security
type
issue
right
where
you
have
this
key
value
store
basically
and
you're
putting
stuff
in
there
with
secrets,
I
mean,
if
you're
not
using
it.
A
Maybe
just
don't
have
those
secrets
right,
so
you
don't
have
to
explain
them
security.
Folks.
I
think
that
was
the
main
driver
to
have
less
attack
surface.
I
mean
I
don't
know
what
what
a
potential
attack
would
look
like,
but
it's
just
easier
to
explain
if
you
don't
have
to
explain
credentials
right
if
there's
no
credentials,
that's
always
the
easier
I'm
talking
to
security.
F
E
A
One
last
thing
I
think
constantine
is
on
vacation.
So
that's
why
he
didn't
respond
yet.
B
B
A
Like
that
yeah
test
coverage
yeah,
that
would
also
be
a
good
option,
so
this
is
basically
pending
review.
This
is
actually
waiting
for
changes.
A
B
A
Yeah
it
says
here
we
have
some
customers
that
are
using
threat
up
where
they
have
like
a
lot
of
credentials,
a
lot
of
certificates
on
their
go
routers
like
a
thousand
or
something,
and
then
it
loads
all
those
certificates
individually.
A
A
A
A
Shall
we
take
a
look
at
some
issues?
F
Oh
yes,
this
one
yeah,
I
submitted
that
last
sunday
and
it
looks
like
a
pretty
bad
one.
I
had
to
patch
my
bush
director's
life
to
get
them
actually
be
able
to
do
something
yeah.
Why
seems
that
the
vervic
app
store
tmp
is
required
by
the
blob
store
client
used
by
the
director,
the
the
ruby
code
of
the
pop
star
clients,
but
the
temporary
fires
into
a
pests
and
disks?
F
What
does
it
mean?
Why
is
it
putting
it
in
a
persistent
disk?
That's
weird,
yeah,
really
weird
that
that's
the
first
question
to
ask
and
the
workout
is
to
allow
bpm
to
right
there
to
mount
this
as
a
right,
writable
directory,
but
it's
just
to
work
around
right
now,
yeah.
The
question
is:
why
write
anything
there?
F
It's
it's.
Definitely
not
the
the
right
place
where
to
to
do
some
something
temporary,
so
yeah.
I've
just
commented
that
this
afternoon
and
yeah
we
see
who
has
time
to
spend
some
time
on
it,
but
it
looks
I
couldn't
deploy
anything
with
the
latest
version
of
bush
director.
F
F
A
F
I
I
have
specificities
in
in
my
bush
deployment,
I'm
I'm
using
an
old
version
of
push
deployment
from
2000
up
april
2020.
F
F
A
B
F
I
was
in
hurry
when
I
submitted
that
issue,
because
I
I
had
to
finish
preparing
a
training
for
for
monday
and
but
yeah.
I
realized
this
should
have
never.
This
could
not
possibly
pass
any
ci
on
your
side.
No.
B
B
F
A
Yeah
just
test
and
follow
up.
F
Yes,
don't
hesitate
too.
A
C
A
C
Because
we
didn't
have
any
entity
in
china,
so
we
could
not.
C
A
Yeah
that
was
like,
I
think,
pivotal,
had
an
entity
in
china,
so
they
were
able
to
have
an
account
there
and
be
able
to
publish,
but
now
with
the
acquisition
by
vmware
that
entity
at
some
point
was
yeah,
stops
or
demolished.
I
don't
know
the
right
word
for
what
do
you.
B
A
Yeah
something
like
that,
those
clothes
are
gone
so
yeah
there
was
no
legal
entity
anymore
to
and
that
there's
apparently
some
certificate
or
something
that
you
need
to
be
able
to
publish
amis
in
a
china
region.
B
A
A
Wow
yeah,
this
is
painful
to
watch.
People
tie.
B
A
B
A
A
F
Oh,
this
is
it's
jean-clay
stuff.
B
F
F
Maybe
it's
ready
to
escaping
improper
escaping,
while
writing
the
logs.
F
But
the
ac
definition
is
really
weird
shouldn't:
it
be
dash
name,
a
name
z3,
then
cloud
properties,
yeah.
A
B
B
F
Christopher
is
not
very
keen
on
markdown
syntax.
Well,
I
see.
A
B
A
I
don't
know
for
now:
let's
continue,
because
I
don't
don't
want
to
unless
someone
else
has
anything
else
they
want
to
add,
because
I
don't
like
I
don't
want
to
spend
too
much
time
on.
One
issue,
like
maybe
there's
other
issues
that
we
can
make
progress
on.
A
A
Yeah,
that
should
be
a
story
in
the
pivotal
backlog,
but
I
will
check
on
that
or
vmware.
That's
it
for
today,
guys
is
there
anything
else
we
should
discuss.