►
From YouTube: Cloud Foundry Community Advisory Board Call [March 2021]
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
I'll
kick
things
off
big
news
from
the
foundation.
Of
course
we
announced
dates
for
cf
summit,
so
that's
gonna
be
july.
21St
and
22nd
it'll
be
in
north
america
time
zones
and
the
call
for
proposals
is
now
open.
So
I
believe
that
ends
may
21st,
so
you
should
check
it
out.
It's
it's
on
the
website.
You
can
register
for
the
event.
There
is
a
sponsorship
prospectus
and,
but
most
importantly,
the
call
for
proposals
is
open.
A
So
for
you
know,
cloud
foundry,
committers
and
everyone
else
in
the
community
now
is
a
great
time
to
put
in
proposals
for
cloud.
Foundry
summit
should
be
fun
another
virtual
event.
A
I
I
am
very
much
cautiously
hoping
there
will
be
in-person
events
in
2022,
but
you
know
it
is
what
it
is
still
so,
but
but
it
should
be
fun
to
get
together
again
and
yeah.
Just
one
event
this
year,
so
hopefully
be
a
bit
bigger
turn
out,
but
yeah
looking
forward
to
that,
but
call
for
proposals
is
open.
Please
spread
the
word
on
that
to
all
the
project
teams
and
folks
in
your
respective
companies.
A
Other
than
that,
I
just
wanted
to
say:
keep
us
informed
of
interesting
project
updates,
we're
always
looking
for
blog
posts
for
the
cloud,
foundry,
blog
ids
for
ideas
for
live
streams
or
tutorials
ram
and
shedrack
I've
been
doing
a
lot
of
cool
cool
work
there.
So
if
there's,
you
know
a
project
that
you
feel
like
could
use
a
little
bit
more
visibility
or
you
know
you'd
like
a
tutorial
written
for
which
can
probably
help
with
that
so
just
reach
out
to
the
cff.
A
A
Okay
with
that
eric
do
you
want
to
give
us
some
updates
on
the
application,
runtime
pmc.
B
Yeah
I'm
happy
to
so
I
made
some
notes
in
the
doc,
but
I'll
run
over
those
real
quick
across
the
integration
projects.
I've
had
kind
of
regular
releases
for
both
cf
deployment
and
tia
for
cates
from
release
integration.
I
think
the
latest
see
if
kate's
minor
version
has
a
nice
improvement
to
cf
apps.
B
So
if
you
have
some
some
missing
apps
or
some
apps,
even
with
zero
instances,
those
will
actually
return
in
a
reasonable
amount
of
time
when
you
run
that
command
and
then
folks
from
early
integration
have
also
been
working
with
some
other
folks
from
sap
and
ibm
outside
the
team
to
be
testing
cf
deployment
against
the
bionic
stem
cells
and
getting
some
mileage
on
those
and
driving
out
a
few
bugs
and
then
qcf
is
continuing
to
release
some
patch
versions
on
the
2.7
line,
with
some
cf
operator
fixes
and
some
other
dependency
updates.
B
I
think
there's
a
pretty
big
cf
operator,
update
that
resolves
some
outstanding
bugs
there
and
then
on
some
of
the
component
teams.
B
I'm
pretty
sure
that
cappy
is
done
with
all
the
v3
endpoints
at
this
point,
but
I'm
still
waiting
on
independent
confirmation
of
that,
but
so
pretty
sure
that's
done
so
they've
been
focusing
on
a
few
other
things
as
well.
I
know
there's
been
a
few
edge
cases
that
they
have
realized
around
some
of
the
state
transitions
for
apps
and
how
they
affect
rolling
app
deployments,
or
you
could
end
up
with
an
unexpected
app
restart.
B
If
you
change
one
of
the
parameters
on
an
app,
so
they've
been
fixing
up
some
of
those
cases
so
that
they're
all
much
more
consistent
and
predictable,
and
I
think
they're
restarting
some
work
on
app
manifest
diffs
with
the
server-side
manifest
apply
pretty
soon
and
then
irini's
also
been
working
with
the
capi
team
to
transition
over
to
a
crd
interface
for
their
lrp
abstraction
inside
of
cloud
controller.
B
On
the
networking
side,
I
know
they've
started
to
look
at
what
it
would
take
to
support
http
2
as
a
protocol
and
the
go
router
and
some
of
the
other
changes
around
that,
and
so
I
think,
they're
they're
working
on
an
initial
problem
statement
and
proposal
for
that
that
they'd
like
to
get
feedback
on
so
keep
an
eye
out
for
that
soon
and
then
a
couple
other
improvements,
a
while
back
diego
had
taken
in
some
work
that
was
contributed
to
alaskan
refinements
to
some
of
the
bin,
packing
that
it
does
in
order
to
favor
the
lower
indexed
cells,
to
try
to
get
some
more
efficient
packing
on
those
and
so
they're
working
on
some
additional
indexing
refinements
to
support
that
in
a
few
edge
cases.
B
And
then
the
logging
and
metrics
team
also
had
some
releases
again
to
address
some
of
the
bionic
stem
cell
compatibility
issues
that
had
come
up
in
earlier.
Testing
and
they've
also
had
some
component
logging
improvements
trying
to
get
everyone
aligned
on
those
human
readable
time
stamps
for
component
logs.
B
So
those
are
just
some
of
the
highlights
across
those
pmc
teams
for
the
past
month
or
so.
A
C
Yeah,
I
maybe
don't
have
anything
as
polished
as
eric,
but
I'll
just
run
through
my
points.
I
guess
so.
We
have
some
tweaks
to
memory
task
cleanup
right
now
when
you
run
the
scheduled
task,
cleanup
it
loads
all
those
fast
enough
memory,
so
we're
getting
some
reports
that
customers
are
having
to
inflate
their
director
size.
So
hopefully
that
fix
will
come
out
soon
right
now,
the
postgres
director
ships
with
postgres9
and
postgres10.
C
We
also
shipped
bosch
dns
last
month
because
we
bumped
to
go
115
go
115
now
enforces
sands
on
cert,
so
people
that
bump
to
washington
s128
might
run
into
deployment
failures
if
they
don't
have
sands
on
their
certs.
So
I
think
we've
documented
that
in
bosch
deployment,
but
that's
something
to
keep
your
eye
out
for
and
then
bionic
is
still
moving
along.
C
A
Great
yeah
awesome
any
questions
for
eric
or
maya
about
those
updates.
A
Okay,
the
extensions
pmc
as
troy,
left
I've
been
just
doing
some
housekeeping
and
whatnot
for
the
extensions
pmc.
We
didn't
think
it
necessarily
made
sense
to
find
a
new
extension
pmc
lead,
given
the
technical
governance
changes
coming
up,
presumably
in
a
couple
of
months,
so
I've
just
been
sort
of
place
holding
for
that.
I
did
formally
retire
a
few
projects,
a
couple
that
had
been
long
dormant,
sql
server
and
brooklyn
broker-
probably
could
have
been
retired
a
couple
years
ago
and
then
also
cf
swagger,
which
is
also
long
dormant.
A
But
I
thought
perhaps
there
might
be
some
community
interest
there,
because
it's
kind
of
a
worthwhile
thing
and
then
cf
dev,
which
is
more
current,
but
that's
also
no
longer
being
maintained.
A
So
we
moved
back
the
or
I
haven't
moved
to
the
attic
yet,
but
I
will
this
week
so
those
four
projects
formally
retired
a
few
more
coming,
probably
cfcr
in
the
next
couple
months
and
cf
local
once
once
a
few
other
things
have
happened
to
replace
that
and
yeah
lots
of
other
projects
are
still
you
know,
jumping
along.
I
know
service
fabric
at
a
major
release
or
not
a
major
release,
but
you
know
it's
a
0.13,
but
but
still
like
lots
of
new
bug.
A
We
will
get
some
significant
updates
from
the
build
packs
crew
at
the
next
cap
call
meeting.
So
current
state
of
cloud
native
build
packs,
picketto
build
packs,
last
generation,
cf
bold
packs,
all
that
stuff.
How
c
cloud
native
bill
pax
are
playing
with
cfr
cates
things
like
that,
so
that
should
be
a
nice
deep
dive
into
build
packs
at
the
next
cab
call.
But
we
do
not
have
a
presentation
for
this
cap
call.
A
So
unless
there
are
any
other
orders
of
business,
I
think
that's
probably
a
wrap.
Anyone
have
anything
they
want
to
talk
about
or
okay.
Well.
Thank
you
all
very
much
for
joining
maya
thanks
for
coming
from
the
bosch
pmc
eric
thanks
for
the
updates.
Thank
you
all
for
coming.
Chris.
D
Yeah,
steve
sorry,
can
I
try
to
put
people
in
the
spot
a
little
bit
sure,
probably
maya
and
eric
I
apologize,
but
with
the
bionic
stem
cells
is
given
the
the
april
kind
of
deadline.
We
have
to
make
a
decision
on
cloud.gov
whether
or
not
we
open
related
things.
D
If
we
can't
get
patches
and
so
do,
we
have
any
idea
of
of
how
hard
that
timeline
actually
is
for
for
bionic
and
if
that's
going
to
work,
because
we
have
to
unfortunately
start
a
compliance
process
and
a
whole
slew
of
paperwork
and
figure
out
a
remediation
plan,
and
we
don't
want
to
do
that
if
you're
all
really
confident
that
we're
going
to
hit
april
30th
or
whatever.
C
D
No,
I
mean
so
part
of
our
sorry.
Part
of
our
ssp
says
our
system
security
plan
says
that
we
get
regular,
updates
and
patches
the
operating
systems,
and
if
that
can't
happen,
because
the
existing
stem
cells
are
no
longer
going
to
be
patched
and
bionics
not
ready
and
proven
with
cf
deployment,
then
that
puts
us
in
a
position
where
we
have
to
address
that
with
the
compliance
folks
and
have
a
remediation
plan
and
that's
actually
a
lot
of
work
and
from
the
communications
we've
seen.
You
know
they
all
say
hey.
D
We
might
hit
this.
We
might
not
hit
this
deadline
of
april
30th
and
I'm
just
trying
to
get
an
understanding
of
you
know
how
close
we
think
that
would
be
because
of
the
the
amount
of
work
we'd
have
to
do
like.
Let's
say
it's
not
ready,
not
proven
not
tested
for
cf
deployment
by
april
30th
is
it
may
5th?
Is
it
july,
like
those
are
very
different
targets?
If
that
makes
sense,
I
know
that's
a
hard
question
answer.
I
apologize
yeah.
B
I
I
think
that
that
makes
sense
steve.
I
I
think
there's
still
some
risk
that
there
are
operational
unknowns
with
how
some
of
the
deeper
components
of
cf
deployment
things
like
garden,
especially
are
going
to
work.
B
So
I
know
there's
been
a
couple
of
fixes
that
have
gone
into
garden
already
for
some
issues
that
were
discovered
on
previous
rounds,
but
I,
like
I
couldn't
say
you
know
for
100
certain
that,
like
there
will
be
a
lot
of
mileage
with
cf
deployment,
in
particular
on
on
bionic
stem
cells
by
that
the
end
of
april,
and
so
I
do.
I
do
see
some
risk
of
of
running
past
that
I
don't
think
it
would
be
much
like.
I
doubt
it
would
be
into
july
to
take
us
to
resolve
any
of
those
issues.
B
You
know
certainly
a
lot
of
the
other
big
vendors.
You
know
especially
sap
and
ibm.
If
they've
really
been
stepping
up
to
drive
this
effort,
they
have
some
of
those
same
concerns
security
concerns
and
want
to
make
that
transition
for
their
large
cf
environments
over
to
bionic
very
quickly.
So
if
it
does
go
past
april
I
I
would
hope
that
there'd
be
kind
of
increased
urgency
to
getting
that
resolved.
Say
sometime
in
may,
but
you
know
I
wouldn't
say
april.
30Th
is
a
lock
at
all.
A
A
C
A
A
We
just
we're
just
wrapping
up
the
meeting,
but
welcome
if
you
have
any
questions
or
anything
you'd
like
to
bring
up.
You
have
made
it
at
the
buzzer,
but
if
you're
just
popping
in
the
recording
for
this
will
be
up
in
you
know
a
couple
of
hours,
so
I
believe
that's
a
wrap
for
today
happy
st
patrick's
day.
Thank
you
all
for
joining
and
we'll
talk
to
you
all
soon.
Beyond
slack.