►
From YouTube: CNCF CNF WG Meeting - 2023-05-15
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).
B
A
That's
right,
he
said
something
about
like
the
a
conference
right.
C
C
D
C
I'm,
just
looking
for
the
meeting
notes
here
just
to
kind
of
chug,
my
memory
as
well
I
can
stick
it
in
there
for
anyone
just
to
quick
access.
I
know
it's
in
the
it's
in
the
meeting
invitation,
but
it
just.
D
E
C
A
C
Yeah
I
can
actually
and
I'll
I
I
mean
I,
guess
I
guess
you
want
to
add.
I
can
add
something
to
the
agenda.
Peace.
E
A
Okay,
our
it
is
on
six
after
the
hour
and
apparently
also
Tom,
can
also
join
so
yeah
I,
guess
that
we
can
start
so
well,
apparently,
Taylor
and
others
are
attending
the
5G
event,
so
hopefully
they
can
share
something
after
the
event.
So
the
next
thing
is
like
I,
don't
know
if
you
have
plans
to
to
submit
some
papers
for
for
the
other
fan
developer,
the
same
forum
is
a
virtual
event.
So
let's
see
it's
a
great
opportunity
to
share
ideas
or
best
practices.
A
In
this
case,
do
you
have
plans
to
submit
something.
A
D
A
Actually,
if
someone
wants
to
submit
something
yeah,
we
can
maybe
to
meet
together
or
like.
C
Yeah
I
mean
I
would
be
interested
if
you
know
Victor.
If
you
were
interested,
I
I
mean
I.
If
you
want
to
set
like
I
would
be
happy
to
just
you
know,
maybe
shut
up
a
short
call
and
just
discuss
it.
A
little
bit
more
I'm
I'm
working
in
lfn
in
the
in
the
Anakin
assured
program
and
we've
had
long
had
conversations
about
you
know,
cnfs.
C
You
know
they're
sort
of
people,
there's
work
going
on
and
sort
of
cnfs
over
on
this
in
the
CNC
app
and
there's
a
very
of
course,
infrastructure
that
should
support
cnfs
and
there's
some
requirements
for
those
within
lfn
I've
been
working
in
the
past
with
Taylor.
Of
course,
trying
to
get
you
know,
strengthen
the
collaboration
between
both
organizations
and
so
that
there's
a
less
fragmentation.
If
you
will.
D
C
So
you
know
I
I,
don't
have
the
answer,
I
think
there's
some
things.
I'm
thinking
and
I'd
be
happy
to
maybe
discuss
it
a
little
bit
more,
maybe
not
on
this
call
here.
But
you
know
if
you're
interested
I
could
I
can
reach
out
to
you,
and
maybe
we
can
have
a
first
pass
and
then
see
if
there's
anything
that
we
might
want
to
bring
up
to
the
to
the
group.
A
No,
that's
awesome,
actually
very
interesting
and
also
well.
You
have
been
also
in
a
few
discussions.
Yeah.
C
A
So
aware,
like
now,
we
are
like
considering
like
I.
Don't
know
that
is
the
first
pillar
of
the
provisioning
like
to
consider
like
not
only
the
the
workloads
also
the
point
through
nephew
like
the
whole
infrastructure,
so
I
guess,
if
we
can
I
I,
think
that
we
can
combine
all
these
areas
like
a
as
you
said
like
to
unify
and
try
to
make
all
these
things
like
online,
so
yeah
but
yeah
definitely
yeah
quite
interesting
to
do
that.
So.
C
Yeah
I
mean
I.
Have
you
know
that
I'll
just
throw
it
out?
As
another
example
I
mean
that
you
know
we
for
those
for
those
of
you
who
were
with
silver?
You
know
it's
a
I
believe
that
there
are
plans
at
some
point
to
offer.
You
know
to
do
CNF
sort
of
validations
there
and
using
the
test
Suite
from
cncf
and
I.
C
You
know
I,
it's
great
I,
just
my
my
concern
is
always
about
these
slightly
variation
variations
and
different
views
and
and
sort
of
how
do
we
I
I,
use
the
term
a
line
where
we
can
and
only
diverge
where
you
have
to
because
otherwise
it's
just
you
know
it
creates
so
many
different
views
of
what
it.
What
are
the
best
practices
at
you
know
specifically
for
cnf's.
It
can
get
you
get
different.
You.
C
Answers
if
you
go
to
different
places
and
I
think
that's
a
that
is
of
course
a
little
bit
of
a
challenge,
so
the
more
we
can
do
to
collaborate
I
think
is
the
is
my
main.
The
main
thing
that
I
would
be
interested
in
trying
to
form
some
kind
of
session
around.
You
know
how
do
you,
how
do
you
bring?
How
do
you
bring
those
closer
into
alignment
while
still
allowing
the
flexibility
to
have
different
opinions?
You
know
have
an
opinionated
view
in
different
places.
C
If
you
look
at
lfn,
for
example,
within
aniket
I
mean
we've
managed
with
some
of
the
work
we've
been
doing,
to
align
on
the
first
sort
of
essential
and
I
know,
I'm
mixing
between
the
CNF
test
suite
and
the
working
group
here,
but
I
think
some
of
the
work
we
do
here
does
transfer
translate
into
tests
in
the
test.
Suite
and
there
today
exists.
C
I
think
it's
around
15
essential
tests,
we've
managed
on
anikit
to
align
on
on
14
out
of
the
15,
which
I
think
is
actually
you
know
it
was
very
encouraging
and
that
that
that's
those
are
the
small
steps.
I
think
we
can
do
to
help
you
know
to
contribute
if
we
have
new
ideas
to
bring
them
back
and
sort
of
say,
are
these
applicable
for
everyone,
or
are
they
really
an
opinionated
view
that
it
should
be
only
in
one
place?
I,
don't
know
if
that
makes
sense.
C
If
it
doesn't
sorry
guys,
it's
still
Monday.
A
C
Yeah,
maybe
something
like
a
call
for
action:
an
open
discussion,
yeah,
let
let's
let
me
do
this.
Okay,
I
can
I'll
reach
out
to
you
and
see
if
we
can
maybe
just
set
aside
30
minutes
and
just
discuss
some
ideas
and
see
if
we
can
come
up
with
something
that
would
make
sense,
because
I
don't
have
a
clear
view
on
it.
Right
now
and
I
I
can
probably
share
why
if
we
meet.
B
A
E
Hi,
thank
you,
hi
I'm,
not
sure.
If
it's
already
discussed,
I
would
also
like
to
have
a
discussion
on
between
horizontal
and
vertical
Cloud,
these
vendors,
bringing
their
own
cloud
Solutions
versus
building
one
big
cloud
where
all
these
cnfs
can
be
on
board.
That's
different
tenants,
not
sure.
If
it's
already
discussed
in
this
working
group.
A
I
mean
yeah,
this
is
I,
mean
I,
guess
history
like
with
CNN,
apps
and
I.
Guess
it's
a
valid
topic
to
discuss
here
as
well,
so
yeah
I
don't
know
like
do
you
want
to
discuss
right
now,
like
as
part
of
the
agenda
items
or
like
what
is
here.
A
Yeah
I
think
so
I
I
don't
have
to.
We
don't
have
too
much
items
in
the
agenda.
So
let's
put
it
like
please
here
in
agenda,
and
maybe
what
do
you
think
like
cooking
I
mean
the
the
rest?
Actually
the
rest
of
the
topics
that
we
have?
It's
not
too
much
time.
I,
don't
think
that
we're
going
to
take
us
too
much
time,
and
definitely
we
can
save
some
time
for
for
discussing
this
particular
topic.
A
All
right,
so
the
next
quite
events
is
like
the
open
run.
Summit
if
I
understand
this
is
a
virtual
event.
So
and
after
that
we
have
the
open
source,
Summit,
so
yeah,
also
I,
guess
like
there's
going
to
be
a
one
one
Regional
Summit
as
we
we
had
in
Vancouver
yeah,
the
other
teams.
Two
events
are
like
mwc
and
kubecon.
So
Taylor
did
you
mentioned
something
about
like
a
kubecon
or
like
the
cloud
native
taco
day
during
classical
event
or
like
you,
don't
have
information
yet.
F
Still
not
confirmed
we're
wanting
to
get
sponsors
for
the
event
and
I'm
gonna
try
to
make
it
happen.
We
have
I
mean
it
seems
like
it's
been
well
received
every
time,
so
that's
I
think
we
need
to
keep
doing
it
and
if
we
don't
have,
if
we
have
a
enough
sponsorship,
then
we'll
probably
end
up
with
potentially
a
full
day,
and
if
we
get
a
half
day
only
then
we'll
probably
do
the
community
Gathering,
like
we
did
in
cubeconi.
F
A
F
I
would
just
use
it
as
a
I.
Don't
I,
don't
know
that
it's
covers
an
egg
I'd
have
to
like,
but
you
could
use
it
just
kind
of
as
a
a
general
idea
basis
and
we'll
can
and
get
a
new
one.
E
A
All
right,
I
think
those
are
the
all
events
that
we
have
so
there's
any
anyone
missing,
please
feel
free
to
to
add
it
as
part
of
the
list
given.
D
B
To
tell
her,
you
probably
are
connecting
from
a
phone
or
something
I
have
opened
the
the
prospectus.
It's
a
relevant
information
for
any
of
foreign
North
America,
so
yeah,
it's
it's!
Okay,.
A
Okay,
so
that
gave
us
time
I
don't
know
we
have
PR
to
review
like
or
something
but
I
guess
much
better.
To
start,
like
checking
the
the
items
that
we
have
here
in
the
agenda,
so.
A
Okay,
so
basically
the
the
point
that
you
want
to
discuss
is
like
having
a
CNF
which
is
applied
among
multiple
data
centers,
like
how
can
what
is
the
best
practices
to
to
the
boy.cnf
is,
if
they
understand
correctly
or
like.
E
No,
mostly
infrastructure
perspective,
I
mean
I,
don't
want
to
name
any
vendor.
Let's
say
there
is
a
vendor
who
is
providing
5G
solution.
There
is
a
vendor
who's
providing
Grant,
so
they
all
have
their
own
kubernetes
distribution.
Assuming
it's
a
cloud
native
Network
function
versus
the
operator
having
a
unified
Cloud,
let's
say
from
openshift
Doc,
VMware
or
Ranger.
E
So
this
will
create
silos
right,
I
mean
as
a
operator
the
each
of
these
products
have
its
own
life
cycle
management.
It
will
be
difficult
to
manage
again.
So
how
is
the
industry
addressing
this?
Let's
say
the
same
CNF
can
be,
might
be
certified
on
both
openshift
and
VMS.
So,
instead
of
having
their
own
Cloud
solution
from
each
of
the
vendors,
isn't
it
possible
to
or
consider
it
as
a
good
practice
to
have
one
unified
Cloud,
where
all
these
CNS
can
be
onboarded
instead
of
having
so
many
different
deployments,
the
different
versions.
A
Okay,
I
guess:
that's
reminding
me
a
little
bit
the
the
topic
which
was
discussed
during
the
The
Guiding
event.
So
we're
like
his
name.
It
was
presented
that
were,
let's
take
the
case
for
455
free
fight
for
5G
deployments
like
where
you
have
like
a
multiple
cnfs
and
every
single
CNF
is
using
different
vendors,
which
has
different
infrastructure
requirements.
A
So
I
don't
think
that
I
don't
know
like
maybe
I'm,
not
lacking
up
knowledge,
but
I
guess
like
I,
just
assuming
that,
mostly
like
the
industry,
has
been
using
a
single
infrastructure
vendor.
Maybe
I
could
be
wrong
like
someone
who
has.
D
A
A
A
So
so,
when
you
express
your
desire
like
what
is
your
your
5G
deployment
desire,
so
you
consider
like
the
infrastructure
as
part
of
the
requirements
So
eventually,
in
this
case,
nephew
is
going
to
take
the
decisions
and
it's
going
to
try
to
make
the
deployments
one
of
the
the
key
tools
that
we
are
considering
for,
for
that
particular
exercise
is
cluster
API.
A
So
this
idea
is
to
consider,
as
part
of
the
package,
a
certain
custom
resources
of
cluster
API
and
deployed
the
application
try
to
solving
the
the
the
the
the
the
requirements
on
the
the
the
the
CNF.
In
this
particular
case,
it
is
something
that
we're
like
still
experimenting
and
and
certain
things
that
we
haven't
reached
that
point.
Obviously
this
is
very
new
and
I
haven't
explored
yet,
but
I
don't
know
like
someone
has
another
experiences
or
like
ways
that
the
industry
has
been
mitigated.
This
particular
case.
E
A
Yeah
exactly
so
so,
basically,
cluster
API
has
different
providers
so,
and-
and
in
that
way
you
can
Express
those
requirements
based
on
the
application,
but
yeah
I
mean
now
we
have
like
a
I
mean
closer
API
has
been
there
for
a
while.
So
now
the
major
differences
we
are
trying
to
do
is
like
we
are
trying
to
integrate,
like
that
particular
tool
with
the
nephew
ecosystem
Express.
The
5G
deployment,
like
as
a
as
I,
knew
I
wanted
like
resource
like
where
you
express
your
intent.
A
Yeah
I,
don't
know
if
that
makes
sense,
but
for
now
I
mean
we're
working
on
that
and
he's
showing
like
a
good
results.
The
only
problem
that
we
have
is
like
right
now:
cluster
API
only
focus
on
deploying
kubernetes,
so
and-
and
there
are
some
cases
where
we
need
to
interconnect
those
clusters
like
so
for
now,
I
don't
know
if
we
have
like
a
a
tool
which
can
help
us
to
interconnect
those
clusters
using
the
same
model
that
we
use
like
a
for
the
name
carium
given
as
resource
model,
so,
okay.
E
Okay,
I
think
I
think
nephew
would
try
to
address
the
current
challenges,
because
I
heard
from
different
operators
that
we
have
one
chromatic
Center
one
from
Nokia,
and
they
also
have
their
own
based
on
openshift,
and
it's
really
hard
to
convince,
let's
say
at
xnr
other
players
to
move
from
their
own
kubernetes
distribution
to
openshift
they'll
come
up
with
so
many
and
I'm
saying
that
it's
not
good
for
that's
not
tested
all
these
things
that
would
come
up
with
so
hopefully
with
nephew
and
with
standardized
cluster
API
I
mean
with
cluster
iPad.
A
Yeah,
exactly
and
also
now,
like
a
kubernetes,
has
these
LDS
Concepts.
So
not
only
you
depends
of
the
the
the
cluster
vendor
like
you
also
depends
on
the
cycles
that
they
have
so
if,
for
some
reason
they
don't
want
to
move
forward,
they
haven't
apply
all
the
patches
because
they
are
like
a
cumulative
distribution,
so
you
have
to
heavily
depend
on
them
like
that
on
their
own
Cycles.
E
E
I'm
not
really
really
sure,
because
I've
read
that
that
at
some
stage
there
is
left
here
is
slightly
overlapping.
The
domain,
orchestrator
or
or
vnfm.
A
I
I
think
if
I
have
to
Define
nepheum
few
words
I
could
say
like
a
nephew
is
so
it's
like
the
tool
which
is
bringing
the
the
get
UPS
best
practices
or
like
for
for
cnfs,
so
I
mean
obviously
I'm
trying
to
quit
a
lot
of
fun.
So
so
in
that
way,
like
he's
he's
not
pretending
to
be
like
a
replacement
like
or
like.
A
Probably
it's
trying
to
connect
a
lot
of
the
things
that
they
are
there
like
I
mean,
and
there
are
people
who
are
like
connecting
with
owner
so
with
all
our
existing
ecosystem
in
open
source
ecosystem,
so
yeah,
but.
D
A
Bnfs,
it
was
like
a
very
can
be
a
manual
thing,
so
it
needs
like
a
lot
of
interaction
between
different
operators.
In
these
cases,
the
the
interaction
is
more
like
a
using
github's
best
practices
like
and
the
GitHub
or
GitHub
or
any
Instagram
source
of
true.
F
There
there
are
some
parts
that
they're
looking
at
orchestrating
deployment
of
kubernetes
it's
at
least
in
the
the
Future
Part
of
nephea
they're,
focusing
on
onboarding
and
management
of
the
CNF
life
cycle,
including
any
type
of
capabilities
needed
for
the
networking
and
anything
that
may
require
the
CNF
and
attributes
and
needs
in
the
cluster.
F
A
Yeah,
so
that's
true,
like
also
well
nephew
and
in
in
two
weeks,
I
guess
we're
going
to
have
the
first
release
so
that
it's
a
long,
a
long
things
to
do
a
lot.
A
lot
of
things
to
implement
in
that
particular
project
so
also
move
a
lot
of
moving
parts.
So
it's
promising
a
lot
of
things
so,
but
yeah,
it's
also
a
good
place
where
we
can
like
bring
these
kind
of
concerns
and
say
like
well.
A
A
Okay,
well
Taylor
I
I
couldn't
attend
the
previous
meeting,
so
I
don't
know
if
you
have
something
or
I
don't
know.
If
you
discuss
something
from
the
previous
meeting
that
you
want
to
bring
in
this
particular.
F
No
all
right
so
that
this
would
be
some
relation
to
thinking
about,
like
what
is
nephio
covering
and
other
projects
that
are
dealing
with
when
you're
looking
at
get
Ops
how
to
use
the
patterns
and
stuff
with
get
Ops
for
doing
deployments.
You're
going
to
start
thinking
of
things
that
are
not
just
deploy
the
application
onto
kubernetes
with.
F
Without
thinking
about
the
platform,
so
there's
some
parts
that
end
up
thinking
about
what
is
what
are
you,
configuring
on
the
platform
and
stuff
like
that?
And
then
you
start
looking
at
things
like
extensions
to
kubernetes
and
everything
else.
So
there's
Nikolai
had
brought
up
cni
plug-ins
like
psyllium
and
there's
other
ones
that
I
think
would
come
in.
F
How
do
we
talk
about
projects
like
that
and
best
practices
that
we
think
would
be
good
for
the
community
to
adopt
in
general,
so
we
kind
of
and
Victor
a
few
months
ago,
but
we
were
talking
about
maybe
highlighting
best
practices
from
nephio,
so
that
could
be
some
areas,
things
related
to
maybe
that
the
boundary
between
ran
and
and
then
core
core
components,
and
how
do
we?
What
what
would
we
think
would
be
practices
and.
F
Maybe
technology
to
look
at
that
are
on
those
edges
and
even
we
could
even
think
about
like
Stefan
on
Rand,
because
now
there's
more
and
more
adoption
of
running
kubernetes
on
the
edge
and
everything.
Well,
how
are
you
going
to
do
it
on
radio
Iran
is
digging
into
that,
but
I
think
that
would
be
something
to
explore.
A
lot
of
the
practices
we've
been
focused
on
are
more
General
practices
that
would
be
for
any
type
of
workload,
not
even
specific
to
cnfs.
F
D
F
True
and
then,
if
we're
going
to
have
projects
like
psyllium
that
are
going
to
go
through
and
say,
hey
we're
following
best
practices
like
Community,
agrees
on
and
running
in
the
kubernetes
environment
and
what
are
those
so
that
you
know
that
they
could
be
written
up,
and
maybe
they
become
part
of
the
CNF
certification,
so
that
potentially
profiles.
So
maybe
we
have
workload
application
like
profiles
and
then
something
that
would
cover
projects
like
psyllium.
A
A
Well
and
another
topic
that
I
was
thinking
around
like
maybe
it's
not
related
with
a
little
bit
more
cnfs
and
all
these
things
it's
just
about
the
how
to
manage
the
I
mean
a
few
years
ago.
We
didn't
have
configuration
tools
like
ansible
puppet
Jeff,
all
of
these
things.
So
that's
why
those
things
work
right
like
because
we
have
to
manage
all
the
hosts
operation
tasks.
A
So
so
you
were
those
were
great
and
and-
and
we
have
a
great
progress
on
them,
but
now
that,
assuming
that
most
of
the
deployments
are
using
kubernetes
as
a
standard
like
the
new
Cloud
operations
operating
system,
so
I
I
just
think
about
it.
A
Like
still,
is
it
still
making
sense
to
to
do
certain
operations
with
ansible
and
all
of
these
configuration
tools
or
makes
more
sense
to
take
advantage
of
kubernetes
talking
about,
for
example,
you
can,
if
you
need
like
a
to
install
like
a
kernel
module
for
example,
so
there
are
ways
to
do
it.
The
same
task
using
massive
or
you
can
take
advantage
of
kubernetes
and
do
the
same
operation
same
thing
for
installing
things
on
the
host.
A
I
know
that
definitely
that
somehow
my
biolets,
the
the
principle
that
we
are
saying,
I'm
not
not
trying
to
use
privileged
containers,
but
it's
possible
to
do
it
so
I,
don't
know
if
you
want
to
talk
about
this
particular
topic
or
it
could
be
the
a
good
practice
or
bad
practice
to
use
kubernetes
is
a
as
a
configuration
tool
or
keep
using
the
same,
the
same
tools
like
traditional
tools
like
ansible.
What
do
you
think
Maybe,
Taylor
or
someone
you
want
to
mention
something
about
this
topic.
F
F
The
reason
why
you're
using
them
and
patterns
that
I
think
could
be
applied
with
different
tools,
so
get
Ops
doesn't
require
flux.
Cd,
for
instance,
get
the
patterns
behind
get
Ops
are
older
than
the
term
get
Ops
you.
F
You
could
see
people
using
the
same
type
of
principles
that
you're,
seeing
with
those
type
of
deployments
and
management
for
the
configuration
and
all
of
that
for
a
long
time
before,
probably
before
kubernetes,
I,
I
would
say
and
I
think
those
are
more
important
to
really
understand,
then
looking
at
the
technology
or
tools
or
whatever
has
to
do
with,
does
the
tool.
Let
you
follow
the
patterns
and
practices
that
you
want
to
utilize
that
you
think
are
going
to
be
good,
I,
guess
stepping
back.
F
What
is
the
problem
that
you're
going
to
solve
and
then
do
these?
Does
this
technology
help
you,
or
is
it
going
to
be
harder
because
there's
definitely
some
technology?
Where
you
could
say
you
can
use
it
following
any
pattern,
but
it
may
fight
you
or
it
may
it
may
not
be
designed
to
follow
those
patterns.
So
when
we
talk
about
kubernetes
and
Cloud
native
kubernetes
is
an
implementation
of
the
principles
and
practices
that
existed
before
kubernetes
but
they're
baked
in.
F
It's
going
to
just
help
you
along.
So
when
you're
looking
at
configuration
management
deployments
whatever
else.
Well,
then
you
know
ansible
would
just
be
one
tool
and
you
go.
How
does
it
follow
those
so
ansible
and
and
many
of
similar
ones
can
be
potentially
simple
enough
and
they
allow
you
to
have
a
domain.
It
has
a
domains.
E
F
A
Yeah
also,
like
I,
mean
yeah.
Definitely
that's
true,
like
all
the
things
that
you're
saying,
but,
for
example,
like
I,
think
the
naming
was
a
puppet
agent.
If
you
compare
some
of
the
functionality
that
this
particular
agent
is
doing
in
the
the
servers,
it's
quite
similar
like
what
Cuba
does
in
in
the
working
modes,
like
a
I
mean
it's
constantly
checking.
A
If
there
is
something
new
to
do,
and
once
it
receives
instruction
applies
the
the
operation,
obviously
more
things
to
do
like
a
cube,
letting
this
is
connecting
containers
and
doing
a
lot
of
stuff
and
probably
agent
definitely
manage
files
and
sell
packages,
and
things
like
that,
but
again
I
guess
in
a
sense
the
financiality
that
she's
particular
these
two
things
are
like
doing.
Is
it's
pretty
much
similar?
A
It's
sharing
a
lot
of
things
so
yeah,
so
maybe
the
major
difference
is
like
the
level
of
adoption
that
kubernetes
has
so
so,
probably
not
probably
a
few
years
ago
there
there
were
just
few
people
reducing
kubernetes
in
their
own
deployments,
but
now
that
the
the
it
must
mess
up
the
deployments
are
using
kubernetes.
Probably
it's
not
the
case
like
most
of
them
has
kubernetes
on
it.
So
it's
not
a
problem,
doesn't
have
that
particular
agent
or
behavior
in
the
server
but
yeah,
probably
yeah.
A
The
the
is,
is
better
to
have
like
a
choices
and
tools,
I'm,
not
saying
that
we
don't
have
to
stop
using
Nancy
or
any
configuration
tool.
Of
course
there
is
Leon
use
cases,
but
I
guess
I,
don't
know
if
we
we
should
start
like
relying
more
in
in
in
having
the
fact
that
maybe
we
have
kubernetes
as
a
deployment
and
take
advantage
of
those
tools
there
and
try
to
minimize
the
the
the
corner
cases
like.
A
I,
don't
know
like
really
is
is,
as
you
said,
it
all
depends
of
on
the
use
case,
every
single
use
case
and
everything
probably
has
different
scenarios.
A
All
right,
we
don't
have
any
other
topic
in
the
agenda.
I,
don't
know
if
someone
wants
to
bring
something.
C
I
had
I
did
actually
have
a
and
I
think
it's
it
feels
like.
The
timing
is
kind
of
good
I
have
a
there's
a
discussion
item
there
at
the
bottom,
which
I
just
had
put
into
the
agenda.
C
Yeah,
so
basically
what
I,
I
I
shared
this
with
Taylor
a
week
or
so
ago,
just
and
I
I
don't
know
if
anyone
else
has
if
this
is
just
me
or
if
there's
others
who
might
think
this
could
be
a
good
idea.
So
this
is
really
just
a
discussion
item
having
participated
here
in
the
CNF
working
group
and
also
the
test
suite
for
that
matter.
C
One
of
the
things
you
know,
I
I
feel
like
I,
have
a
pretty
good
view
on
what
we're
what
our,
what
our
goal
is,
of
course,
identifying
best
practices
and
I
think
I
ran
into
I
was
looking
at
our
repo
today
and
I.
Just
I
found
a
nice
little
reminder
if
I
would
almost
in
fact
I'll
do
this
I'll
just
take
a
picture
and
share
it
in
this
in
the
chat,
so
I
don't
have
to
share
my
screen,
but
it
it
was
a
little
bit
along
the
topic
of
what
we.
C
What
you
were
just
discussing
now
partially
give
me
a
second
here:
I'm
gonna
put
this
in
chat,
I.
C
Yeah,
if
I'll
do
that,
that's
fine
bear
with
me
for
a
second.
C
C
Yeah
so
I,
just
I
was
just
noting
when
you
were
talking
I,
think
maybe
there's
some
relevance
to
this
as
well.
This
is
from
our
this
is
from
our
repo
here.
This
is
some
documentation.
We
have
on
sort
of
how
we
work
with
the
communities
and
also
the
scope
right
and
so
I
think
I
I.
We
were
talking
a
little
bit
about
infrastructure
and
we're
talking
about.
You
know
what
this
group
is
focusing
on.
How
do
I
build
cnfs?
How
do
I
run
cnf's,
deploy,
manage
lifecycle?
C
We've
been
talking
a
little
bit
about
nephew,
and
so
the
what
I
wrote
in
the
notes
or
in
the
agenda
today
was
really
just
question
about.
Would
it
make
sense,
or
would
it
be
a
value
to
this
group
to
somehow
try
and
build
a
view
of
what
we
you
know?
We
have
categories
and
I'm
just
going
to
go
to
that
for
a
second
here,
so
bear
with
me,
I
think
it's
here
too
yeah.
So
we
have
these
different
categories.
C
Where
we
are,
we've
been
working
with
identifying
best
best
practices
and
I'm
wondering
if
it
would
make
sense
to
somehow
try
to
summarize
what
are
the
areas
where
we
feel
that
you
know
if
we
were
to
sort
of
put
a
a
judgment.
Call
on
this
area
is
fairly
well
understood.
It's
green.
There
are
best
practices,
you
know
they're
they're
versus
other
areas.
That
may
be
underdeveloped,
in
other
words,
just
a
tool
to
try
to
help
us
understand
where
our
best
practices
needed,
because
I
think
sometimes
for
at
least
for
myself.
C
It
feels
like
we're
looking
for
Best,
Practices
and
and
I
just
like
to
have
an
organized
way
of
seeing.
Where
are
the
challenging
areas
you
know
and
I
think
you
were
touching
on
a
little
bit
Victor
about
life
cycle
management,
there's
no
tools
that
are
being
that
are
coming
and
I
know
that
we're
not
lesser
looking
at
the
tools
but
we're
looking
at
the
patterns
and
the
best
practices.
D
C
Just
a
thought:
if
someone
would
be
interested
I,
think
that
would
create
some
value
to
identify
the
you
know.
What
are
the
areas
in
terms
of
cnfs
that
are
underdeveloped
needs?
More
work
needs
more
best
practices
to
address
some
issues
and
I
don't
know
if
anyone
else
feels
the
same
way
very
curious
to
hear
your
thoughts.
A
To
be
honest,
I
never
think
about
it,
but
now
that
you
present
this,
so
so
what
could
be
from
from
your
opinion
like
what
could
be
the
the
best
way
too,
the
criteria
that
we
can
use
like
a
a
number
of
best
practices
or
the
quality
of
the
best
practice
or
yeah.
C
That's
a
good,
that's
a
good
point:
I
I,
don't
have
the
full
view,
but
I
think
maybe
starting
with
simply
I
mean
it's
really
simple:
to
identify
what
we
have
and
you
know
we've.
We
have
categorized
things
already
so
I
think
just
having
a
reflection
on
that
and
then
certainly
maybe
looking
at
you
know
from
a
community
I
think
we
need
to
sort
of
rely
on
ourselves
to
say.
So.
What
are
the
areas
where
we
feel
you
know
there's
only
two,
but
let's
just
use
an
example.
Hypothetical.
This
category
only
has
two
best
practices.
C
Is
there
a
reason?
Is
it
because
we're
not
having?
Is
there
any
challenges
there
or
are
there
challenges
that
remain,
and
even
if
we
don't
have
the
best
practice,
we
can
identify
some
of
those
challenges.
I
just
I
can't
help,
but
think
this
might
help
us.
You
know
identify
areas
where
we
need
to
solicit
you
know
and
whether
that's
from
csps
or
vendors,
you
know
trying
to
understand
what
are
the
challenges
or
that
you're
having.
How
do
we,
you
know,
so
that
we
can
reflect
on
on
possible
best
practices
for
that?
C
It's
just
it's
just
an
idea,
otherwise
it
feels
like
it's.
Does
anyone
have
any
best
practices?
You
know
it's
a
it's
great
and
I
think
we
have
identified
them.
We've
identified
some
I'm
just
trying
to
think
from
a
more
maybe
structured
approach
to
you
know
where,
where
are
the
biggest
challenges
that
remain
and
maybe
identify
new
new
categories
that
we
haven't
really
touched
on.
B
I
have
some
some
kind
of
quick
comment
here.
My
I
mean
earlier
earlier
in
this.
In
this
call,
they
don't
remember
who
brought
up
the
topic
of
okay,
but
vendor
X
is
delivering
their
CNS
only
certified
against
their
own
kubernetes
in
this
clear
is
a
sign
of
not
following
any
best
practices
right,
because
essentially
this
means
that
their
distribution
is
fine-tuned
and
the
CNF
is
fine-tuned
for
there's
a.
D
B
Between
the
kubernetes
distribution,
with
whatever
plugins
and
whatever
it
comes
there
and
the
the
CNF
so
I
mean
I'm,
not
saying
that
we
shouldn't
invest
into
the
best
practices.
I.
Just
somehow
feel
that
I
mean
the
real
world
is
not
really
following
them
and
then
the
question
is:
are
we
I
mean?
Is
anyone
practicing
these
practices?
I?
Guess
that's!
That's
the
the
the
the
the
question
in
reality.
I
would
I
would
love
to
to
have
all
of
this.
B
You
know
being
followed
and
so
on
and
so
forth,
and
we
have
examples
of
CNS
being
certified,
which
obviously
are
following
best,
but
I
mean
you,
you
cannot
pass
the
certification,
but
the
yeah
I
mean
this
is
more
like
a
observation,
not
not
that
it
doesn't
say
anything
good
to
the
discussion
anyway.
E
D
C
Some
ways
this
was
again
back
for
at
least
in
my
thinking,
was
that
we,
you
know
it's
almost
like
you
can
see.
This
is
another
way
to
think
about
what
I
was
was,
was
kind
of
suggesting
there
or
trying
to
discuss,
is
almost
a
maturity,
maybe
model
right
some
somehow
trying
to
come
to,
because
if
why
aren't
they
following
those
those
best
practices,
then
and
I'm
sure
there's
many
different
reasons.
B
Yeah
exactly
I
I
agree
is
there?
Is
there
any
disconnect
between
like
Whoever
has
to
implement
them
and
what
we?
What
we
think
because
I
mean
I,
haven't
been
to
each
and
every
discussion
here,
but
more
or
less
know
and
understand
what
we
mean
when
we
say
best
practices
and
it's
somehow
kind
of
I.
Don't
know
Ideal
World,
where
you
know
we
have
stateless
services
and
everything
according
to
the
theory,
but
that
then,
in
the
end,
maybe
in
reality
is
just
not
feasible.
B
Don't
know,
but
it's
yeah
something
that
probably
we
have
to
to
somehow
try
to
to
go
and
listen
to
real
world
vendors
of
the
CNA
site.
D
F
Ideally
we're
solving
someone's
we're
helping
to
solve
problems
or
pains
when
someone's
saying
I'm
having
a
hard
time
with
this,
but
we're
trying
to
help
with
that.
So
a
lot
of
problems
in
the
past
well
relating
to
what
is
kubernetes
doing
or
what
is
cloud
computing.
One
of
the
main
topics
is
interoperability
between
multiple
clouds
at
this
or
start
of
this
call
talking
about
different
vendor
clouds,
and
then
how
do
you
ensure
that
things
are
going
to
work
between
them
if
someone's
providing
their
own
environment
whatever
so
the
the
interoperability?
F
There
is
part
of
it,
interoperability
between
the
different
applications
or
cnfs
that
are
going
to
work
together
and
that's
going
to
go
at
all
different
layers.
I
mean
we
have
it
split
in
different
ways.
This
these
actors
and
okay,
the
interoperability
I,
think-
can
be
applied
at
different
layers,
including
the
how
the
CNF
in
for
operator,
how
do
I
run
and
for
a
deploy
and
manage,
and
then
you
have
well,
my
infra
actually
has
extensions
and
stuff
because
the
workloads.
F
F
Now,
it's
just
CNF
developers
there's
a
another
document,
that's
best
practice
for
CNF
developers,
so
this
is
only
one
actor
and
then
some
CNF
developers
they
actually
care
about
how
to
run
and
operate
it
because
they're
the
ones
building
it
and
they
need
to
know
how
is
it
working
so
they
actually
start
thinking
of
this.
So
in
some
some
ways
they
could
be.
The
actor
is
also
a
CNF
operator
and
then
how
do
I
consume
it?
F
Okay,
well,
you
may
have
CNF
developers
that
are
also
thinking
about
that,
and
so
these
areas
this
this
is
kind
of
to
split
and
think
about
the
practices
that
may
overlap.
You
may
have
a
microservice
that
also
needs
to
think.
Okay,
what
is
a
configuration
life
cycle
or
upgradability
of
a
microservice?
Why
don't
we
have
these
just
an
area
to
really
think
about
the
best
practice,
but
the
best
practice
may
actually
be
in
multiple
areas.
D
C
Yeah
I
agree
with
you
and
that's
the
categories
is
great,
I
mean
it's
just
you
know
it's
categorization,
but
I.
Think
to
your
point.
It
comes
back
to
so.
What
are
the
I
I
hate
to
use
the
word
life
cycle,
but
it's
it's
everything
from
I
mean
as
a
as
if
I
start
with
just
myself,
I
mean
as
a
representative
of
a
CNF
vendor
I
mean
the
challenge.
Is
there
if
we
were
to
sit
in
a
room
and
just
start
to
say?
So
what
are
the
challenges?
C
Well,
the
challenges
someone
already
mentioned
that
there's
many
different
opinionated
versions
of
kubernetes.
So
every
time
we're
going
to
show
that
we're,
actually
you
know,
can
can
be
deployed
there
and
and
and
and
it
works
you
know,
there's
a
lot
of
certification
work
that
has
to
go
on
some
of
it's
overlapping,
very
similar,
some
of
it's
different.
C
What
about
orchestration
so
is
the
end
customer
looking
to
orchestrate
the
CNF
using
own
app
or
using
nephew
or
using
something
else.
That's
that
those
are
so
there
I
think.
My
point
is
trying
to
understand
what
some
of
those
categories
in
terms
of
the
areas
of
a
CNF
that
not
as
not
only
the
CNF
vendor
who's,
creating
it
they're,
creating
it
for
the
purpose
of
to
be
used
by
someone,
and
so
what
are
the?
What
are
the
challenges
of
those
different
environments?
C
You're
going
into
and
I
guess,
I
was
trying
to
think
about
what
are
those
areas
if
we
can
sort
of
massage
out
some
of
those
areas
and
try
to
understand?
Where
are
the
challenges,
because
then
you
could
start
to
look
at
what
you
know
what
best
practices
do
we
have?
What
do
we
not
have.
F
An
effort
to
get
a
list
of
challenges
would
probably
be
a
good
place.
I'm
actually
headed
towards
the
Big
5
G
event.
Today,
so
I'll
try
to
listen
and
and
write
some
up,
I.
F
Think
a
lot
of
the
stuff
that
I've
been
hearing
are
from
the
cons
consumer
side,
this
service
providers
themselves
and
looking
at
how
are
they
managing
so
some
of
those
are
going
to
be
overlapping
down
here,
but
writing
up
the
challenges
if
we
can
have
wherever
they
are
I'm,
not
really
worried
at
what
layer
just
who's
having
a
challenge,
if
you're
in
a
kubernetes
environment,
what
type
of
challenges
are
you
having
and
if,
if
you're,
a
vendor
and
you're
having
challenges
deploying
or
you're
having
a
challenge
is
integrating
and
working
with
another
vendor
or
running
on
kubernetes
is
problematic,
with
some
other
hard
requirement
that
you
have
somewhere
else.