►
Description
CNCF SIG Runtime Container Orchestrated Device Working Group Meeting 2021-01-12
A
D
D
E
E
D
D
F
F
Nope,
okay,
let's
start
so
in
2020,
I
think
we
kind
of
started
the
first
drafts
of
cdi,
and
I
presented
the
cod
working
group
at
cubecon,
which
were
actually
probably
the
two
big
points
we
also
kind
of
started
discussing.
I
think
the
different
projects,
whether
it's
through
the
nri
or
through
the
resource
management,
work
group,
that
kind
of
got
started
and
more
that
really
that's
related
on
the
pod
resources
api,
which
is
the
api
that
allows
that
allows
monitoring,
not
monitoring
device.
F
D
F
F
F
I
think
looking
at
2021,
one
of
the
kind
of
deadlines
that
I
was
hoping
for
us
to
achieve
is
to
have
maybe
enough
implementation
in
one
of
the
major
run
times
by
the
end
of
2020,
and
I
think,
unfortunately,
that
that's
something
that
that's
a
that's
a
more
or
less
a
milestone
that
we
kind
of
missed
here,
and
so
I
think,
going
forward.
It'd
be
it'd,
be
interesting
for
or
at
least
we
probably
need
to
figure
out
how
we're
gonna
move
on
this.
F
A
I
I
think
your
plan
of
you
know
getting
it
up
on.
Podman
makes
sense,
because
it'll
it'll
stretch
out
the
you
know
the
service
and
get
it
get
it
used
from
that
client
perspective
that
you're
focused
on
right
and
then,
whatever
demos
you
put
together,
we
can
probably
set
that
up
on
on
container
d
and
start
working
it
into
kubernetes.
We
will
need
to
do
a
presentation.
A
We
yeah,
I
mean
basically,
we
just
need
to
add
the
pre-create
right
and
then
once
that,
that's
just
an
injection
point
and
really
what
you're
going
to
be
doing
on
podman,
I
suspect,
is
adding
the
client
options
to
set
cryo
to
be
able
to
I'm
trying
to
cryo
library
to
be
able
to
to
to
use
those
pre-injection
points
at
the
same
place.
You'll,
of
course,
you'll
need
to
push
the
you
know
the
all
the
different
injection
points
into
into
the
cryo
code.
It's
it's
pretty
similar
code.
A
We
just
need
to
keep
the
links.
You
know
together
between
the
two
projects,
cryo
and
container
d,
so
that
we
can
make
sure
we're
putting
the
injection
points
at
the
same
place
right
in
roughly
the
same
manner
that
you're
wanting
to
you
know
to
see
making
sure
we
put
put
the
same
content
in,
for
example,
if
you
need
particular
annotations
to
be
injected,
you
know
we'll
need
to
be
doing
that
in
concert
right.
D
Yep,
so
so
my
line,
I
think
it
was
quite
similar
to
what
mike
mentioned
so
practically
like
have
all
the
cdi
code
as
a
separate
library
like
the
code
which
can
be
embedded
in
any
offer
project
to
render
it
have
one
entry
point
where
we
say
this
will
contain
this
container
description.
What
we
are
trying
to
create
and
the
results
should
be
returned
as
a
modified
content
of
wet
container.
D
I
think
I
think
right
now,
it's
a
bit
flucky
state.
We
don't.
We
don't
know
michael's
plans
on
when,
where
what
kind
of
functionality
he
will
be
doing
so,
I
would
say
if
we
want
to
achieve
something
soon
enough:
let's,
let's
do
it
by
just
directly
injecting
with
cdi
into
a
cryo
container
d
and
podband,
as
just
as
a
proof
of
concept
as
a
demos
and.
D
D
So,
in
short,
what
what
I
am
thinking
is
we
need.
We
need
to
have
a
discussion
with
kubernetes
folks
on
how
we
can
expose
entities
from
the
run
times
towards,
like,
like
two
upper
layers,
saying
like
this
is
where
object
would
can
be
attached
to
a
container
how
and
like
all
the
specialities
it
should
be
hidden
from
the
kubernetes.
But
when.
D
A
A
All
right,
as
soon
as
you
guys
get
some
kind
of
a
demo
level,
you
know
proof
of
concept
running
at
the
client
level.
I
think
in
podman
or
whatnot.
Then
then
we
can
pick
some
stakeholders
from
the
kubernetes
side
get
them
on
our
side,
and
then
you
know
to
put
together
a
demo,
maybe
dems-
maybe
you
know,
plus
mornell.
I
mean
he's
already
here,
so
he's
a
good
stakeholder
and
signal
and
with
the
together
with
those
two
guys
we
should
be
able
to.
You
know
present
something
to
just
to
the
signo
team.
A
So
yeah
that
I
think
I
think
at
that
I
agree.
I'm
just
saying
we
should
bring
together
a
few
stakeholders
from
a
few
areas
and
bring
them
here.
First,
you
know,
have
a
you
know,
casual
conversations,
get
them
on
our
side
and
then,
when
we
go
to
sig,
node
right
they'll
be
able
to
chime
in
and
say
yeah.
I
like
this,
maybe
bringing
derrick
in
at
some
point
as
well.
F
Got
you
but,
like
generally,
I
think
like
because
this
group
has
also
different
devices.
I'd
be
I'll,
also
add
access
to
a
melon
snake.
So
that's
not
completely
true.
That's
it's
the
only
device
I
have
on
my
machine,
but
I
think,
like
I'm
very
happy
to
kind
of
test
different
devices
and
show
them
if,
if
people
want
kind
of,
have
want
to
record
demos
around
that
that
that
it
would
also
be
kind
of
like
really
awesome.
D
F
D
G
D
A
D
G
Hey
guys,
hello,
yeah,
hello,
I
have
a
question
here
and
I'm
sorry
if
this
is
something
you
guys
already
cover,
I'm
trying
to
understand
why
you
guys
are
leading
towards
starting
with
bookman.
I
would
expect
that
changes
would
have
been
done
more
at
the
runtime
level.
I
would
expect
changes
to
be
done
at
container
d
or
cryo
level,
so
I'm
just
trying
to
get
what's
the
rational
to
start
in
higher
level
component,
like
botman.
A
Well,
we've
already
got
some
functionality
in
inside
the
you
know
the
container
runtimes
to
support
this.
We
just
have
to
add
the
injection
points
and
when,
when
you
want
to
do
a
demo,
you
need
a
client
and
container
d
and
cryo
and
themselves
don't
have
a
client
so
you're
stuck
with
well.
How
do
I
demonstrate
this
right?
Do
I
do
I
run
it
using
cryctl
or
podman,
or
you
know,
or
whatever
what
other
you
know
client?
Would
you
like
to
do?
There's
a
couple
of
container
d
client
proposals
out
there.
G
D
F
D
D
But
how
to
say
that
we
are
interested
to
make
sure
what
nri
interface
will
be
first
of
all
powerful
enough
to
do
a
lot
of
tasks
not
only
for
devices
but
about
our
resources,
but
initially
you
can
be
on
the
nodes.
Second
thing:
it
should
be
performant,
so,
like
yes,
exact
mechanism
is
fine
for
now,
but
I
hope
when
we
will
do
some
stress
testing
in
the
end
of
a
year
or
close
to
the
end
of
a
year,
we
might
think
about.
I
don't
know
like
tt
or
pc
grpc
or
some
some
other
interfaces.
D
I
have,
I
think,
continually,
have
good
experience
with
visible
scenarios
already.
So,
to
summarize,
I
think
one
of
the
goals.
What
I
see
for
this
year
is
to
make
sure
what
nri
will
be
powerful
interfaces
to
run
time
and
some
of
our
items.
What
we
want
to
do
is
written
and
we
issue
number
two
for
nri
project.
F
D
D
F
F
F
D
F
F
Okay,
I
mean,
I
think,
it's
important
to
kind
of
define
time
budgets
and
maybe
the
things
that
you
mentioned,
which
is
like
a
scaling
these,
like
these
make
more
sense
as
a
way
to
engage
rather
than
to
start
the
conversation.
By
saying,
I
would
like
to
explore
grpc
or
other
mechanisms,
they're
they're
kind
of
easier
to
communicate.
Why
you're
exploring
them.
F
F
A
F
A
F
C
No,
nothing
really,
I'm
just
looking
forward
to
getting
the
proof
of
concept
working
with
podman
and
eventually
and
crying
container.
I
feel
like
I
feel
like.
I
would
understand
it
much
better.
Once
we
have
code
and
all
going
on
as
well
as
the
discussions
that
we've
been
doing.
That's
all
make
sense.
Yeah.