►
From YouTube: CNCF CI WG Meeting - 2019-08-27
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
A
A
B
C
C
A
Saying
thank
you.
So
much
I'll
take
a
look
at
the
email
and
see
what
we
can
pull
together
and
then,
let's
see
there
was
the
CFP,
the
joint
CFP
that
we
put
together
for
QQ,
North,
America
and
I
haven't
heard
back
if
it
has
been
accepted.
I
think
that
the
team
is
planning
to
give
CFP
announcements
the
first
week
of
September,
so
maybe
a
week
from
now
we'll
know
if
that's
been
accepted
or
not.
A
And
open-source
summit
in
France
it
looks
like
priyanka
from
gate
lab
is
doing
a
keynote
and
I
haven't
heard
I'll
check
in
to
see
if
any
of
the
work
done
with
get
Leben
stance,
the
FCI
may
be
highlighted
at
all,
so
I'll
be
available
to
help
with
that.
There
are
some
co-located
events
at
cube:
con
North
America
in
November,
there's
a
new
network
service
mesh
con
that
has
opened
up
it's
sponsored
by
the
network
service
mesh
community
and
they
have
a
CFP
window
open
until
February
13th.
A
C
A
A
So
the
scenes
the
FCI
team
is
working
on
a
few
initiatives
here
and
we're
nearing
the
finish
line
on
many
of
them.
So
the
first
one
we're
working
on
is
the
C
IRA
factor.
We
want
to
move
towards
a
more
kubernetes
way
of
doing
things,
and
so
we
are
implementing
support
to
use
cube
spray
to
provision
kubernetes
on
the
scene,
CFC,
I,
dashboard
and
we've
decoupled.
A
The
hardware
provisioning
stage
with
the
kubernetes
provisioning
stage,
which
were
previously
in
one
step,
lives
a
couple
bat
so
that
they're
now
modular
two
steps
and
we're
working
on
a
CLI
tool
to
help
support
using
both
cube
spray
now
and
using
kind
later,
as
we
feel
there
are
use
cases
that
would
support
either
one
and
we're
going
to
start
with
cube
spray.
So
that's
what
we
have
going
on
now
is
creating
a
CLI
provisioning
wrapper
and
creating
a
plugin
for
cube
spray
to
provision
kubernetes
onto
the
CNC
FCI
system.
A
After
we
have
cube
spray
in
place,
we'll
be
able
to
update
the
kubernetes
release
version
on
the
dashboard
to
the
latest
version
and
it'll
be
easier,
going
forward
to
keep
that
in
line.
Keep
it
up
to
date
with
the
latest
and
we're
also
going
to
be
discontinuing
use
of
the
quote:
unquote,
cross
cloud,
kubernetes
provisioning
tool
so
we'll
be
using
the
new
way
of
provisioning
in
place
of
the
cross
cloud
way
and
then
later
we'll
be
kinds
plug
in,
so
that
we
can
support
those
use
cases.
That
would
be
beneficial
for
use
in
kind.
A
A
C
D
Either
Hardware
provisioning
is
working
as
expected
right
now
and
I
think
we're
going
to
be
able
to
put
that
in
place
and
that
the
kubernetes
in
for
provisioning
portion
is
also
pretty
close.
D
At
this
point,
we
have
the
different
components
for
how
we
want
to
run
cube
spray,
and
now
it's
the
the
part,
that's
going
to
integrate
between
the
hardware
infrastructure
and
then
run
cube
spray
and
specifically
run
it
as
a
plugin,
so
that
we
can
add
kind
another
stuff
later
and
the
interface
for
provisioning
looks
the
same
as
far
as
like
I
did
declarative
configuration,
but
well.
We
should
like
loosing
a
set
in
the
next
couple
of
weeks.
I
think
we'll
be
done
and
have
that
in
production
replacing
cross
Club.
C
A
Thank
you
so
much.
The
other
large
effort
we
are
working
on
for
the
CNC
API
dashboard
is
to
add
support
for
external
contributions
so
that
it
can
be
easier
for
more
people
to
maintain
and
add
new
stands
to
hosted
projects
onto
the
San
CFC
I
dashboard.
We've
started
with
linker
d2
as
the
new
project
to
add
it's
an
incubating
project
and
it
uses
Travis
CI
and
we've
refactored.
D
Right
now
we're
trying
to
make
it
language
independent
for
the
plugins
as
where
we're
going
for
this
iteration.
So
potentially,
if
someone
wanted
to
write
a
plug-in
and
any
language
as
long
as
you
follow
the
the
API
that
we
have
to
integrate
with
the
CI
proxy,
it
wouldn't
matter,
and
ideally
we
can
have
contributions
for
the
not
only
adding
projects
but
the
plugins
themselves.
It
probably
would
be
to
add
a
specific
project,
but
I
know:
we've
had
some
conversations
about
drone
being
used
as
a
one
of
the
CI
systems.
A
Thank
you.
We're
also
iterating
on
an
idea
to
expand
our
current
test
environment
drop-down,
which
is
currently
one
drop
down.
That
shows
the
kubernetes
releases,
as
well
as
the
architecture
options,
and
we
have
this
mock
that
we're
going
to
move
forward
on
that
uses,
radio
buttons
to
show
all
the
possible
configuration
options
at
a
glance,
so
we're
putting
kubernetes
stable
and
head
on
the
screen
and
we're
also
putting
x86
and
arm
on
the
screen.
Since
we
have
two
options
per
choice,
it
it
makes
sense
to
show
it
all
on
the
screen.
A
The
stable
will
be
the
default
and
x86
will
be
the
default.
So
when
you
first
load
CNC
fci,
this
is
the
view
that
you'll
see
and
then
someone
will
be
able
to
change
it
from
staples
ahead
and
then
the
content
on
the
screen
will
change
depending
on
the
configuration
that's
been
selected
in
the
test
environment
section.
A
B
A
That
is
definitely
they'll
hand
in
hand,
so
this
UI
will
make
it
pretty
obvious
how
we
should
implement
the
stateful
URLs,
whereas
the
drop-down
things
were
hidden,
and
so
they
were
a
little
bit
more
complicated.
So
I
think
that
the
stateful
URL
enhancement
and
this
UI
enhancement
will
make
a
big
difference.
A
A
Software
updates
I'm,
making
this
ongoing
and
what's
next
so
after
we
get
link
32x
with
the
build
status,
badges
then
we'll
start
on
the
deploy
status.
Badges
will
retrieve
the
build
artifacts
from
their
Travis
CI
system
and
use
those
to
deploy
linker
t2
to
the
selected
test
environment.
Configuration
we'll
also
make
an
enhancement
for
the
MVP
of
the
build
status
badge
for
linker
D
to
the
badge.
When
you
click
on
it
will
go
to
an
internal
build
on
get
lab
on
the
scene.
A
Cfc
I
get
lab
platform,
and
what
we
want
to
do
in
the
next
iteration
is
to
take
the
user
to
the
project's
Travis
CI
build.
So
instead
of
coming
to
C&C
FCI,
it
would
go
out
to
Travis
CI
dot
org
for
linker
t2
and
show
that
job
that
either
passed
or
failed
or
is
running
we'll
also
be
able
to
add
more
projects.
A
A
In
the
future,
we'll
be
adding
plugins
to
other
CI
systems,
I
believe
circle,
CI
will
be
the
next
one
that
we
target
we
currently
do.
Support
Jenkins
for
onap
will
want
to
iterate
on
that.
If
any
other
incubating
scenes
the
FCI
hosted
projects
around
Jenkins,
then
we'll
take
a
look
at
updating
that
plugin
as
well.
A
A
You
so
you
can
find
us
on
github,
it's
the
cross
club
CI
repo,
around
slack
since
the
FBI.
You
can
also
join
the
mailing
list,
the
CNCs
CI
public
mailing
list,
and
these
calls
are
usually
every
fourth
Tuesday.
It
will
be
not
meeting
in
September
and
any
questions
feedback
suggestions
for
soon
CFC
I.
At
this
time.
D
D
D
We're
in
the
middle
of
a
pretty
big
refactor
on
the
CNF
test
bed,
while
also
trying
to
continue
adding
use
cases,
we're
trying
to
take
advantage
of
the
efforts
on
the
CNC
FCI
side
for
splitting
that
hardware
and
Kuban
any
clustered
provisioning
and
that's
a
good
fit
for
what
we're
doing
specifically
being
able
to
have
hardware.
That's
ready
and
reuse
that
same
hardware
for
the
tests
that
are
run
on
the
same
CNF
test
bed.
D
Ideally,
we
can
get
some
help
around
the
open,
sac
deployment
itself
and
the
chef's
deployment,
as
originally
used
as
pretty
brittle
it's
broken
and
quite
a
bit
and
we've
had
to
keep
updating
little
bits
over
and
over
and
so
there's
a
desire
to
move
to
something
like
open,
sac,
Helmer,
Cola,
and
so
if
it
can
get
the
right
help.
Iran.
That
will
probably
be
thanking
that
migration
and
I
think
that's
going
to
be
a
better
fit
for
what
people
are
wanting
at.
D
The
bigger
effort
is
around
the
use
cases
and
the
setup
that
runs
on
top
of
the
platform
and
that's
consisting
of
the
network
functions
themselves,
which
should
be
in
VMs
or
containers.
Some
of
them
may
be
old-school,
big
monolithic
or
we're
moving
towards
using
cloud
native
principles
and
actually
being
CNS
and
then
any
type
of
workload.
D
The
plot,
the
cluster,
open,
sac
communities,
the
workload,
infra
extensions
or
changes.
If
you
want
to
swap
out
OBS
for
OpenStack
with
BPPV
switch
or
whatever
you're
wanting
to
do
there,
NSM
has
components
for
doing
the
networking.
Dan
M
has
different
pieces.
So
there's
all
these
different
parts
and
we
want
to
make
it
where
that's
part
of
the
configuration
that's
easier
for
folks
to
use.
One
of
the
events
mentioned
was
and
talked
a
tutorials
and
stuff.
D
D
What
we're
looking
at
is,
we
haven't
been
doing
this
primarily
because
of
the
resource
utilization
running
the
eyes
on
cunning
test
on
commits,
but
as
we're
creating
these
specific
use
cases
that
people
are
interested
in
and
knowing
like
what
are
the
metrics.
And
what
are
we
seeing
over
long-running
cycles
of
doing
this
again
and
again,
we'd
like
to
have
a
set
of
use
cases
that
are
of
the
MIS
interests
and
have
them
running
either
on
commit
for
any
changes
in
those
areas
or
on
some
type
of
regular
scheduled
basis.
D
D
Yeah
and
I
appreciate
that
y'all
have
been
a
great
help
on
the
specific
failures
and
stuff
I.
Think
a
lot
of
the
tear
down
time
may
have
to
do
with
the
Machine
types
when
we're
using
those
larger
machines,
they
take
a
lot
longer
than
say
the
excellent
smalls
or
any
of
the
smaller
instances.
The
new
networking,
the
Intel
networking
into
extra-large
and
stuff.