►
From YouTube: Kubernetes SIG Scheduling Meeting - 2019-05-09
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
As
you
know,
this
meeting
is
recorded
and
will
be
uploaded
to
public
internet,
so
chances
are
whatever
you
say
in
this
meeting
will
last
for
a
very
long
time.
With
that,
let's
start
the
meeting
you
know
I,
there
are
a
couple
of
bigger
projects
that
we
were
working
on
for
1:15
one
is
even
hotter
spreading.
The
idea
is
that
we
are
spreading
pods
among
certain
failure,
domains
or
ecology
domains.
If
you
will
way,
is
working
on
that,
it's
actually
getting
closer
I
guess
to
see
a
PR
for
that.
B
C
A
A
Because
he
wants,
he
wants
to
review
them,
but
maybe
he
forgot-
or
he
had
other
things
to
do,
but
to
review
it.
So
that's
one
of
the
items,
one
of
the
big
items
that
we
have
for
1:15,
the
second
one
is
building
the
scheduling
framework.
Some
of
you
folks
are
helping
helping
me
with
building
that
Abdullah
is
here.
He
is,
or
at
least
and
epi
are
for
implementing
pyramid
plugin.
It
has
one
of
the
most
important
extension
points
of
the
schedule
and
is
probably
one
of
the
more
complex
ones
permit.
B
A
Allows
us
to
build
more
advanced
features
such
as
gang
scheduling,
and
so
so
there
are
a
few
other
PRS
for
for
the
scheduling
framework,
one
is
PR
to
add,
unreserved.
Basically,
unreserve
is
an
informational
extension
point
that
allows
allows
other
plugins
to
register
and
get
notified
in
case
a
part
that
was
supposed
to
be
reserved
or
has
passed.
A
Of
course,
there
is
a
high
level
one
for
twitch
scheduler
consumes
and
that's
just
the
plugins
that
are
enabled
and
the
plugins
that
should
be
called
at
each
extension
point
that
PR
for
the
configuration
is
also
sent
out.
So
it's
on
a
review
I
believe
it's
getting
closer
to
the
final
version,
and
hopefully
we
can
match
it
soon.
A
Among
other
plugins
that
we
were
working
on
is
a
if
I'm,
not
mistaken,
is
livia.
We
were
working
on,
also
post
bind
and
we
should
probably
start
I
mean
you
sort
I
have
already
also
filed
an
issue
for
I,
think
Q
sort
of
in
fact
archers.
One
of
our
contributors
have
ordered
also
file
the
same
issue
almost
in
parallel.
So
anyway,
Hugh
sort,
plugin
is
also
being
worked
on
and
a
PR
is
out
that
one
is
under
review
as
well.
A
There
are
a
few
other
ones
for
light,
filter,
possible,
temporary
filter
and
also
for
scoring
extension
points.
We
will
add
those
as
well,
but
the
reason
that
I
didn't
find
those
right
away
was
that
I
wanted
to
get
these
more
important
or
sort
of
more
critical
ones,
which
some
of
them
didn't
exist
in
the
original
scheduler
logic
finalized,
and
then
we
could
basic
cope.
I
can
add
some
of
the
other
extension
points
we
will
see.
A
My
hope
is
that
we
can
get
more
extension
points
in
115,
but
given
that
we
are
getting
closer
to
the
code
freeze,
we
may
not
be
able
to
add
all
of
them.
It's
there
is
a
high
chance
that
we
will
postpone
some
of
those
extension
points
to
1
116.
In
fact
that
was
the
original
plan,
but
we
thought
if,
if
we
get
lucky,
we
might
get
more
of
these
extension
points
in
150.
A
There
is
another
effort
to
add
less-than
and
greater-than
operators
for
for,
inter
pod
affinity,
the
PR
for
that,
for
that
is
also
out.
We
are
working
with
the
API,
reviewers
and
other
folks
and
contributors
to
get
that
merged
as
well.
One
other
update
that
I
have
for
you
is
that
during
the
week
of
Q
Khan
and
the
week
after
that,
we
are
not
going
to
have
any
sick
meetings.
A
Of
course
we're
gonna
have,
as
you
may
already
know,
we
are
gonna,
have
a
face-to-face
meeting
at
the
Q
point
contributor
summit,
which
is
one
day
before
the
start
of
the
conference,
and
also
we're
gonna,
have
sick,
intro
and
sick
deep
dive
sessions
during
the
conference.
If
you
happen
to
attend
a
conference,
you
are
more
than
welcome
to
join
us
in
any
of
those
events,
so
these
are
all
the
updates
that
I
have.
A
C
A
I
believe
more
specifically,
we
are
talking
about
gang
scheduling
or
cause
yeah
yeah,
so
basically,
that
entity
will
be
a
plugin
that
is
gonna,
be
written
for
that
that
is
gonna
get
caught
at
that
extension
point.
So
so
we,
you
know,
I,
believe
you
are
not
aware
of
this
effort
that
we
have
in
an
incubator
project
which
is
called
Cubase
as
a
product
queue
patch.
We
are
introducing
new
API
as
a
as
a
CRD
for
now
that
basically
tells
us
what
is
what
a
gang
is.
A
A
A
A
C
A
It's
yeah,
so
so,
assuming
that
a
plugin
is
well
behaving,
there
are
two
scenarios
that
is
possible.
One
one
scenario
plug-in
detects
that
these
the
number
of
paths
never
reaches
five.
Let's
say
all
right
for
some
for
some
reason
or
has
some
logic
that
under
certain
conditions,
it
goes
ahead
and
rejects
all
those
paths.
So
that
is
one
scenario:
either
plugin
detects
that
this
is
not
gonna
happen,
happen
or
or
some
you
know,
some
condition
happens
on
a
plugin
decides
to
reject
all
of
them.
A
So
that's
one
one
possibility
just
goes
down
and
rejects
all
of
those
in
the
waiting
second
scenario:
the
plugin
does
not
detect
and
there
is
no
logic
that
checks
certain
conditions
or
the
condition
is
complex.
We
cannot
really
easily
detect
it,
but
we
never
detect,
but
the
reason
that
we
have
a
timeout
is
exactly
to
cover
this
kind
of
situations.
So,
after
five
minutes,
all
of
those
parts
will
get
rejected
automatically
or
you
know
whatever.
The
timeout
is
right.
C
B
A
In
the
original
design,
I,
don't
remember
exactly
because
we
have.
We
had
gone
back
and
forth
among
a
few
options.
I
believe
the
latest
version
was
that
there
is
a
concept
of
group,
odd
groups
right.
The
park
has
a
minimum
mean
available
and
it
it
either
has
a
label
selector
or
that
basically
tells
which
parts
are
in
this
group
or
it's
I,
don't
remember
which
option
we
eventually
chose,
but
anyways
I.
Either
it
has
a
label
sector
or
it
has
a
name,
and
the
name
is
specified
in
the
pod
spec.
A
So
each
individual
part,
which
is
a
part
of
this
group,
puts
the
name
of
the
group
in
its
pod
spec,
so
that
when
the
scheduler
sees
apart,
it
knows
that
it's
a
part
of
this
group.
It
goes
and
fetches.
The
group
looks
at
it
sees
how
many
is
them
in
available
and
basically
runs
the
logic
based
on
that
by
the
way
this
permit
plugin
is
not
used
only
for
gang
scheduling
to
be
good.
C
A
So
yes,
why
I
think,
based
on
what
we
had
in
mind,
the
plugin
has
all
the
logic
to
figure
out
whether
the
number
of
paths
are
available
for
getting
rescheduled
or
can
be
scheduled
or
not.
But
in
the
case
that
we
have
missed
something
we
can
add
the
added
later.
Of
course,
there
is
a
reason
that
we
call
all
of
these
like
alpha
version
and
that's
exactly
to
cover
these
scenarios.
We
might
have
missed
something.
There
might
be
some
parts
here
and
there
we
can
change
anything
later,
thanks,
yeah.