►
From YouTube: Kubernetes SIG Scheduling Weekly Meeting for 20230223
Description
Kubernetes SIG Scheduling Weekly Meeting 2023-02-23T18:00:07Z
A
A
A
Today
is
February
23rd
and
a
quick
reminder
that
this
is
being
recorded
and
it's
going
to
be
uploaded
to
YouTube,
so
be
mindful
of
what
you
say
and
if
respect
each
other.
A
Okay,
let
me
give
you
co-host
capabilities.
B
Okay,
I'm
trying
to
present
all
of
my
screen
here
so
last
time
we
met
by
the
way.
Could
somebody
verify
that
they
can
actually
see
my
screen.
A
Yes,
we're
seeing
code.
B
Okay,
yeah
yeah.
This
is
vs
code.
So
last
time
we
met,
I
was
telling
about
this
need
to
have
a
plug-in
into
the
scheduler,
which
would
do
topology
scoring
and
as
a
recap
of
that,
the
idea
was
to
you
know
basically
do
resource
scoring
similar
to
what
no
resource
feed
is
doing,
but
now
for
topologies.
B
So
suppose
you
have
like
four
topologies,
where
there
are
nodes
and
in
this
example
here
one
of
the
topologies
has
two
machines,
and
assuming
that
you
know
the
machines
are
relatively
unloaded
or
have
a
similar
note.
Then
this
bottom
topology
here
would
have
like
significantly
more
resources
than
the
others.
B
So
the
intention
with
this
new
plugin
was
that
to
be
able
to
give
a
score
for
the
entire
topology,
so
that
the
best
topology
would
nodes
would
get
like
a
hundred
each
and
then
the
worst
topology
could
be
like
this
would
get
a
zero,
and
you
know
those
topologies
that
that
would
have
resources
somewhere
in
between
the
worst
and
the
best
would
get
something
linearly
as
they
score.
So
that
was
the
the
idea
and
I
was
suggested
to
do
an
entirely
new
plugin.
B
Instead
of
fiddling
with
the
no
resources
fit
itself,
so
that's
where
it
started
from,
and
the
thing
is
that
to
do
this
kind
of
topology
scoring
I
would
actually
need
the
score
values
from
the
node
resource
fit,
which
is
doing
things
quite
nicely,
and
it's
nicely
configurable
and
so
forth.
So
I
was
thinking
that
okay,
if
I,
do
a
new
plugin.
What
are
my
Alternatives
do
I
like
copy
the
code
of
no
resources,
fit
that
wouldn't
make
much
sense.
B
I
don't
want
to
do
a
copy
paste
code,
so
is
that
I
first
created
an
implementation
with
composition,
and
that
was
fairly
fairly
simple
but
and
actually
I
could
I
could
show
that
what
it
looks
like
it
was
a
little
84
lines
for
the
basically
the
wrapper
part
of
it
and
the
main
idea
there
was
just
to
have
a
score
plugging
interface
in
a
new
plugin.
This
composition
example,
and
basically
just
instantiate
a
node
resources
fit
into
there
and
place
it
there,
and
at
that
point
it's
already
like
ready
pretty
much.
B
It
can
run
if
you
just
have
the
rest
of
the
boilerplate
there,
and
so
it
did,
and
that
was
kind
of
fine
and
to
get
the
basically
the
score
back
to
this
new
plugin.
All
I
had
to
do
was
to
basically
add
the
score
extension
return,
something
else
than
nil
and
the
framework
delivers.
The
calculations
from
this
included.
B
Node
resources
fit
to
the
normal
last
score
function
then,
and
I
can
do
my
magic,
then
calculating
those
topology
scores,
which
is
not
that
interesting,
probably
for
anybody,
but
but
this
was
my
first
take
at
you
know
how
to
reduce
this
existing
plugin
and
to
get
and
in
terms
of
how
much
code
we
went
there
not
much
so
it
became
pretty
look
pretty
nice,
okay,
at
least
in
my
opinion.
What
do
you
guys
think
not
big.
A
B
I
actually
want
them
both
to
be
running
because
I
I,
like
the
node
resources,
fit
like
I,
said
and
it
kind
of
like
it
gives
a
good
score
for
the
individual
nodes.
Okay,.
A
A
B
I
want
the
full
score,
so
the
drawback
with
this
design
here
is
that
it
actually
runs
the
same
node
resources
fit
calculations
twice,
so
that's
not
ideal.
It
could
have
been
ideal
to
get
just
the
score
from
node
resources
fit
and
continue
from
there.
So
I
didn't
like
this
too
much
and
the
other.
Basically,
let's
say
drawback.
That
I
saw
was
related
to
the
actual
configuring
of
this
thing,
because
I
need
to
have
the
node
resources
fit
arguments.
B
How
can
I
make
this
work
so
that
the
no
resources
fit
scores
would
be
provided
through
the
cycle
state
to
some
new
plugin
of
mine
and
that's
what
I
went
after
so
after
fiddling
around
with
the
framework
side,
a
little
bit
I
came
up
with
something
that
shoot.
B
Unfortunately,
this
is
not
updating
properly,
but
let's
see
if
it
now
it
does.
Okay,
so
I
came
up
with
this
so,
and
this
is
by
the
way
in
this
it's
a
little
bit
more
complicated
than
is
necessary,
so
only
the
top
right
corner
is
actually
necessary
for
my
use
case,
but
for
the
sake
of
doing
a
demo
to
you
guys,
I
went
a
little
bit
over
the
top
and
created
a
little
bit
more
of
this
example.
B
Plugins
then
so
in
the
demo
that
you
will
be
seeing,
there's
a
node
resource
of
fit
is
going
to
be
the
source
for
the
the
other
plugins
below
it,
and
the
framework
is
going
to
know
based
on
the
arguments
of
these
two
plugins
over
here
invert
example
and
topology
scoring
that
they
actually
want
to
have
the
scores
from
node
resources
fit
and
the
framework
is
going
to
do
a
little
bit
of
a
magic
can
write
score
channels
as
I
call
them
into
the
cycle
state,
and
these
guys,
then,
will
read
the
scores
channels
and
receive
the
scores
from
there
and
then
I
have
another
one
over
here,
which
is
some
example
plugin,
and
it's
requesting
this
course.
B
B
So
that's
going
to
be
the
demo
of
the
day,
basically,
and
even
though
you're
probably
not
that
much
curious,
but
this
shows
how
the
the
connections
were
configured
down
here.
So
there's
a
plot,
a
bunch
of
plugin
arcs,
which
say
pipe
score
plugins
and
the
name
where
they
want
to
have
the
score
from
so,
for
instance,
there's
some
example
at
the
bottom.
It
wants
to
have
the
score
from
topology
scoring
and
the
invert
examples
of
these
guys
and
similarly
others
so
pretty
trivial
stuff
actually,
and
these
go
to
a
schedule.
B
A
profile
called
notebook,
topological
spread
scheduler
and
I've
disabled
a
few
plugins
just
because
there
would
be
too
much
prints
in
the
look
and
my
demo
is
just
about
lock
prints,
it's
not
going
to
be
overly
overly
fantasy,
but
let's
see
the
demo.
So
there's
the
port
and,
like
I
said
all
I'm
gonna
show
is
like
lock
prints,
so
I'm
gripping
through,
basically
the
scoring
and
the
scheduler
config
is
the
log
level
is
Max
to
spinal
tap
levels,
so
it'll
be
printing,
all
the
scores.
B
So,
let's
see
do
we
get
a
demo
effect
here?
No,
we
didn't
so,
let's
go
and
see
so
the
node
resources
fit
was
where
things
were
supposed
to
start,
so
it
gave
the
nodes
which,
by
the
way,
were
present
in
those
topologies
that
I
presented
earlier
this
kind
of
a
scores
so
they're
pretty
fairly
similar
to
each
other,
and
then
we
have
several
plugins
going
on
here.
B
So
we
have
the
topology
scoring
thing,
which
should
be
giving
the
best
score
to
the
one
topology
which
had
two
nodes
in
it,
and
it
is,
if
you
remember
the
names
of
those
they
were
dglh2
and
CML
S2.
So
since
node
resources
fit,
if
you
calculate
the
sum
of
those
that
topology
had
like
way
more
than
the
other
topologies,
which
only
had
one
node
in
them.
So
this
is
the
best
topology,
so
they're
getting
100
and
the
the
rest
of
the
topologies
only
had
a
single
node.
B
So
among
the
rest
of
them,
this
is
the
worst.
So
it's
getting
a
zero.
The
CFLs
and
the
rest
are
then
linearly
pretty
close
to
the
worst
because
they
only
had
one
node.
So
that
kind
of
like
proves
that
the
topology
scoring
works,
but
at
the
same
time
there's
this
composition
example
actually
running
so
the
code
that
I
was
showing
you
and
it
has
the
exact
same
score
as
the
topology
scoring.
B
So
yeah
no
surprises
there,
so
these
guys
exact
same
score
as
a
composition
so
functionally
it's
the
same
in
terms
of
you
know
getting
my
use
case
where
I
wanted
to
get,
but
conceptually
this
pipeline
is
totally
different
and
it's
worth
mentioning
Maybe,
the
other
plugins
as
well,
so
the
invert,
the
example.
What
is
that
so?
B
Basically,
the
invert
example
is
a
very
simple
scoring
plugin,
which
takes
the
input
score
from
basically
any
configured
other
scoring
plugin
and
calculates
a
100
minus
the
input,
so
it
inverts
the
logic
which
is
well,
maybe
not
so
useful,
as
just
you
know,
as
a
demo
here.
But
if
you
start
to
think
about
you
know
the
potential
of
such
a
thing,
you
could
invert
any
scoring
logic
with
that
kind
of
a
concept
which
could
be
handy,
although
it's
not
overly
useful.
B
If
you
have
the
same
weight
for
you,
know
the
input
and
this
guy,
because
they
will
be
canceling
each
other
out,
but
which
is
by
the
way
happening
in
this
demo,
but
anyway
putting
that
aside.
So
the
the
last
one
was
the
sum
example.
So
this
is
like,
if
I
show
the
graph
again.
So
what
was
the
topology
again?
B
So
no,
actually
it's
the
demo
is
probably
the
one.
So
this
is
summing.
The
invert
example
of
the
topology
scoring
okay.
So
those
were
the
configured
things,
so
it
should
be
summing.
The
inversion
and
the
topology
scoring
so,
for
instance,
CFLs
has
a
score
of
26
okay,
so
invert
has
26
and
the
topology
Series.
So
that
adds
up
correctly,
but
let's
see
something
CFL
S5
well,
that
was
17
and
the
topology
score
was
10.
B
So
again,
yeah
adds
up
correctly,
so
kind
of
like
proves
the
point
it's
calculating
correctly
and
that
kind
of
ends
the
demo
so
yeah.
These
were
the
let's
say:
plugin
we're
using
Alternatives
that
I
could
come
up
with
I
kind
of
like
the
the
pipelining
idea
myself,
because
it
has
lots
lots
of
more
potential
to
it.
But
unfortunately,
that's
of
course,
a
framework
site
change,
although
not
a
big
one.
I
only
spent
less
than
80
lines
of
code
there,
but
yeah
anyway.
It
is
what
it
is.
B
The
the
sources
by
the
way
are
available
at
my
Fork
of
of
the
scheduler
so
and
it's
actually
at
the
at
the
meeting
agenda,
there's
a
link
to
there.
So
if
anybody
is
interested
in
taking
a
look,
please
do
and
I
think
it's
time
for
questions.
Does
anybody
want
to
see
anything
like
from
the
sources?
Oh
I
could
maybe
show
what
the
one
of
those
let's
say-
the
invert
for
instance,
what.
A
A
I
might
be
more
interested
in
the
framework
side
of
changes,
and
also
there
is
I
was
wondering
how
you
configure
them
the
pipeline,
because
it
looks
like
these
Arguments
for
the
plugins
are
like
each
of
them
has
a
different.
B
That's
visible
in
the
framework
side
like
you,
if
you
wanted
to
see
that
so,
okay,
so
let's
close
the
plugins
and
let's
go
in.
A
I'm
not
sure
if
you
have
time
to
go
through
all
of
that,
but
so
unless
we
have
more
time
later,
but
I
have
other
questions
such
as.
Where
do
you
want
to
go
from
here.
B
Well,
it's
that's
a
good
question,
but
basically
what
I
started
with
was
you
know
the
desire
to
have
a
new
plugin,
because
we
have
a
use
case
for
that
now.
This
pipelining
thing
that
I
showed
you
know
it's
nice
to
have,
but
it's
I'm
not
going
to
die
if
I
don't
get
it,
but
there's
potential
in
that
one.
So
I
mean
it's
open
for
debate
whether
it
would
be
beneficial-
and
you
know,
ideas
are
welcome.
I'm
just.
A
Presenting
anything
from
from
my
point
of
view,
it's
kind
of
an
Overkill
for
to
have
this
complexity
in
the
scheduler.
If
we
don't
have
other
use
cases,
so
maybe
you
could
start
by
sending
an
email
to
the
mailing
list
to
gather
feedback
from
other
developers
to
see
if
anybody
sees
value
on
this.
A
C
So
I
joined
late,
but
I
guess
I
gave
the
idea
of
the
framework
changes
that
so
can
it
set
some
music
scenarios
that
some
users
want
to
do
some
run
time,
pretty
elastic
debugging
on
some
particular
path.
We
don't
know
the
rules.
We
cannot
set
that
statically
in
the
Upstream.
So
maybe
this
framework
can
be
useful
for
before
you
scanning
those
kind
of
mechanisms
in
there
like
their
input,
runtime
production,
environment
and
some
past
guests.
C
B
It's
not
not
a
thing
so
yeah,
it's
a
it's!
This
pipelining
idea
actually
gives
more
like
flexibility
to
add
things
after
another
plugin,
for
instance.
Now
we
have
this
pretty
much
hard-coded
normalization
functions
and
things
like
that.
You
could
take
this
further
and
you
know
pipeline
another
plugin
doing
normalization
functions
or
whatever
you
want
after
one
or
the
other
and
like
I,
said
this
inversion
logic
or
anything
that
can
be
quickly
calculated
and
alter
the
scores
of
one
Plugin
or
the
other.
B
B
Yeah
so
in
my
particular
case,
I
want
to
have
both
the
node
resource
of
feed,
resource
results
and
I
want
to
have
them
summed
into
the
actual
end
score
as
well,
and
I
want
to
have
this
topology
score
for
for
the
topologies,
so
I
want
to
have
them
both,
but
there
could
be
situations
where
you
know
you'd
like
to
tweak
the
results
from
some
plugin
with
some
kind
of
a
mathematic
function
like
I
was
explaining
earlier,
but
you
wouldn't
really
want
to
anymore.
Have
the
original
Source
plugin
score
as
such?
B
You
would
just
want
to
have
the
end
result
after
you
know
pipelining
it,
so
that
would
be
require
a
little
bit
more
work
instead
of
the
current
logic,
which
is
summing.
Everything
up
to
the
final
score
of
the
nodes.
You'll
probably
need
to
have
something
similar
to
the
summing
plugin.
That
I
was
showing
doing
things
instead
of
the
current
logic,
which
is
summing
everything
up
but
yeah.
It's
more
of
a
flexibility
thing
allowing
for
tweaking
the
scores.
C
C
Yeah
so
I
mean
we
used
frequent
change
that
you're
crafted
so
that
you
can
introduce
the
final
plugin
for
information
purposes
to
adapt
all
the
score
for
one.
You
know
for
each
now,
I
mean.
B
B
On
it
was
based
on
basically
looking
at
the
arguments
of
the
the
plugins,
so
there
was
a
special
meeting
given
to
one
special
argument
of
the
plugins,
so
that's
the
way
that
it
works.
It's
it's
a
really
small
patch.
Actually,
so
it
won't
take
a
long
time
for
anybody
to
look
into
it's
less
than
80
lines,
and
that's
all
that
is
okay.
A
So,
for
once,
the
no
resources
fit
plugging
is
one
of
the
fastest
plugins
we
have
so
that
by
itself,
like
being
able
to
you
know,
reduce
calculation
might
not
be
as
important
both
depending
on
the
use
case
right
now,
if
you're
thinking
of
thousands
of
posts
per
second-
maybe
it
is
important,
but
yeah
back
back
to
my
original
point.
He,
if
you
see
value
on
having
this
Upstream,
it
would
be
good
to
gather
feedback
from
others
to
see
where
it
is
worth
to
to
Upstream.
A
B
A
Okay,
so
for
that
we
actually
have
a
separate
blog
targeting
kubernetes
Developers,
which
we
would
make
more
sense
for
this
kind
of
content,
because
this
does
this.
This
is
not.
This
doesn't
face
Upstream
users
right
so.
B
Now
it's
developers
yeah.
This
is
definitely
Developers.
A
Right
so
there
is
a
yeah.
There
is
a
repository
for
that
I.
Don't
have
it
at
hand
if
you
don't
find
it.
Let
me
know
in
this
slack
and
I
can
look
it
up,
but
yeah.
That
would
be
a
better
location
for
this
kind
of
content
on
his
I
guess
a
bit
more
free
form,
and
you
know
the
audience,
is
it
fits
better,
the
audience?
Okay,
so
you
could
consider
that
and.
A
And
I
suppose
oh
yeah
you're
your
entire,
for
this
is
public
right,
yeah
Okay,
so
yeah
useful
for
others
to
find
those
links.
If
if
they
are
available
and
I,
think
we
can
go
from
there
yeah
in
in
in
Practical
matters,
we
are
too
late
in
the
127
release.
A
So,
or
even
the
blog
post
for
the
developer,
the
developer
blog
blog
does
anybody
else
in
the
community?
Have
other
questions.
A
B
It's
it's
kind
of
like
it
is
very
much
topology
related
and
this
latter
one
that
I
was
demonstrating.
It's
a
generic
topology
score,
so
basically
you
can
hook
it
up
with
anything.
It
doesn't
have
to
be
the
node
resources
fit
any
score.
Plugin
can
be
hooked
up
to
that
thing,
I'm,
not
sure
if
they
are
really
useful.
But
if
you
wanted
to
calculate
topology
scores
based
on
something
else
you
could.
This
won't
allows
it.
B
B
That's
the
flexibility
in
there
and
with
this
pipelining
approach,
anything
can
be
connected
to
anything
as
long
as
it's
a
score.
Plugin.
A
A
Okay,
so
yeah
I
guess
compose
topology
scoring
or
something
like
that.
But
that's
those
are
fine
details.
If
there
are
no
other
questions,
I,
don't
think
I
see
vinayak
here.
A
A
Okay,
thank
you
so
for
vinay,
XPR
I
believe
this.
It
was
way
that
was
reviewing
this
PR.
C
Yes,
I
was
but
Ernest
was
a
long
time
ago.
Yeah
have
I
tried
to
refreshing
my
memory
and
yeah.
The
beginning
says:
there's
nothing
to
significant
change.
Since
I
lost
a
review
there,
I
will
yeah
check
that
I.
Think
I
did
do
some
live
debugging
with
some
with
chain
on
the
internet,
but
I
just
need
to
refresh
the
memory.
I
will
take
a
look
yeah,
but
if
you
are
interested,
you
can
take
a
look
I
believe
yeah.
This
has
been
postponed
by
more
than
one
release,
so
yeah
it's
good
to
have
exercise
on
it.
C
A
Okay,
I
actually
lost
my
audio
when
sharing
the
screen,
so
it
looks
like
there
most
of
the
changes
were
in
the
in
the
cubelet
side
right
since
the
last
time.
C
Sorry
I
had
it
got
distracted.
It.
A
Okay
sounds
good:
I'll
I
cannot
commit
to
review.
This
I
really
have
a
lot
of
PRS
Abdullah.
Do
you
have
a
chance
to
also
take
a
look.
A
C
A
Can
now
please
like
tag
me
away
on
the
pr.
A
Okay,
so
we
that
we
don't
have
any
other
topics
so,
but
we
still
have
a
few
minutes
left
if
anybody
else
has
any
other
questions.
C
A
D
E
Yeah,
if
you
want
to
talk
about
descheduler,
this
meeting
is
good
for
that.
We
also
have
a
a
recurring
meeting
for
the
D
scheduler
itself
that
we
do
on
every
other
Tuesday,
because
that
should
be
on
the
calendar.
D
Excellent
yeah
I'll
try
to
find
that.
Thank
you.
Mike
is
the
K5
Rochelle
directly
to
you
just
just
to
kind
of
get
some
clarification,
so
I
don't
want
to
spam
and
waste
everybody's
time
on
it.
E
Yep
yep
come
on
clack
you're,
just
ask
in
there
perfect.
Thank
you.
D
A
You
can
always
ask
in
the
antique
scaling,
Channel
and
you
know,
start
a
thread
yeah.
That
should
be
enough
because
some
other
there
there
are
multiple
developers
in
the
descendor
project.
So
maybe.
E
A
C
Might
just
maybe
one
option
is
that
you
can
create
a
dedicated
this
schedule,
a
stack
channel
because,
like
Coke,
just
create
a
dedicated
code
channel,
so
you
can
do
also
do
that
for
this
schedule.
E
C
A
Okay,
I
think
there
are
no
other
questions.
You
can
give
five
minutes
back
to
everybody.