►
From YouTube: CNCF CI WG Meeting - 2019-06-25
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
Great
11:05
Pacific
time,
Tuesday,
June
25th
and
welcome
to
the
CNC
FCI
working
group.
The
call
on
the
agenda
today
we'll
take
a
look
at
some
in
progress
and
upcoming
events
on
our
radar.
We
will
take
a
look
at
some
updates
to
the
scenes:
the
F
dot
CI
status
dashboard,
as
well
as
some
work
in
progress,
some
tickets
in
progress
and
possibly
discuss
moving.
This
call
to
one
our
leader
from
11:00
a.m.
Pacific
time
to
12:00
noon.
A
A
B
A
Great
well
no
worries
if
anything
comes
to
mind,
please
feel
free
to
add
to
the
meeting
notes,
magenta
or
in
the
zoom
chat
or
just
verbalize.
If
you
have
anything
you'd
like
to
add,
including
upcoming
events.
So
as
we
speak
cubic
on
cloud
native
cone
open
source
summit,
China
2019
is
happening
in
Shanghai
thanks
for
all
attending.
If
you
are
in
Shanghai,
it
is
2:00.
In
the
morning
there
so
I
appreciate
your
your
time
and
attention
for
the
CI
working
group
call.
Earlier.
A
C
It's
great:
we
had
a
lot
of
participation
from
both
telecom
providers,
as
well
as
vendors
and
some
interest
from
I
would
say
more
like
kubernetes
developers
and
stuff.
There
are
a
few
people.
There
are
interested
in
I
guess
the
CI
side
of
things
in
general,
besides
all
of
the
networking
aspects,
so
it's
a
good
session
good
conference
so
far.
A
A
All
right,
well,
I,
hope
it's
going
well
coming
soon
in
the
end
of
September.
Is
the
open
networking
summit
in
Europe?
It
is
an
answer
at
Belgium,
just
a
train
ride
from
Brussels.
The
CFP
has
closed,
so
those
who
have
submitted
CFPs
to
ons
will
receive
your
notifications
on
Friday
July
5th,
with
the
scheduled
announcement
on
July
10th.
A
The
end
of
October
is
open
source
summit
Europe
and
France,
and
it
looks
like
the
CFP
window
is
still
open.
You
have
until
Monday
July
1st
to
get
your
CFP
in
for
OSS
Europe
in
November
will
be
the
next
cube
con
cloud
native
con
in
North,
America
and
San
Diego.
The
CFP
window
is
open
until
July
12th
and
there
are
several
co-located
events,
one
with
the
CFP
window
open
that
I'm
aware
of
is
envoy
con
and
the
SE
p
window
closes
on
July
12.
For
that
co-located
event
as
well.
A
A
A
A
So
the
test
environment
here
at
the
top
of
the
page
is
your
kubernetes
test
environment.
You
can
select
if
you
would
like
to
look
at
the
stable
kubernetes
or
the
head
commit
of
kubernetes
on
x86
or
arm,
and
so
when
I
select,
kubernetes
stable
on
arm
the
provisioning
was
a
success.
The
bare
metal
packet
and
the
build
and
deploy
stages
for
core
D
and
s
envoy,
fluency
and
Prometheus
are
active.
A
Received
a
fun
fun
bit
of
press
on
adding
arm
to
fancy
up
CI
cloud
native
computing
foundation,
arms
itself
with
graduated
project
support
that
was
fun
and
2:41.
We
added
arm
support
to
envoy
and
we
also
updated
the
hardware
provisioning
code
to
use
the
reserved
our
machines.
Thank
you
so
much
packet
for
providing
reserved
machines
for
both
x86
and
arm.
A
This
really
helps
with
the
I
guess
percentage
of
times
we
see
success.
Sometimes
it
would
be
failed
because
in
that
moment,
in
time,
at
3
a.m.
Eastern
time
when
we
were
provisioning,
these
machines,
maybe
another
customer-
was
also
provisioning
machines,
and
so
there
wasn't
one
available
for
the
scene
CFC
guy.
Now
the
machines
are
reserved
just
for
CNC
FCI
and
we
say
the
successful
provisioning
much
more
often
now
so.
Thank
you
very
much.
D
A
B
D
Okay,
nowhere
I
was
just
taking.
E
D
A
A
Currently,
we
are
working
on
our
three
oh
release
that
will
include
we're
adding
sub-header
to
display
the
scene
co-hosted
projects
by
Stan's
day
off
maturity
level.
This
is
to
get
120
in
the
cross
cloud
repo
and
we
will
be
as
we're
adding
more
projects
to
the
dashboard,
we'll
be
showing
all
of
the
graduated
projects
together
right
under
the
test
environment
and
then
we'll
show
the
incubating
CN
CF
projects
followed
by
currently
the
Linux
Foundation
project
of
onap.
A
F
F
Okay,
I
believe
this
is
it
and
so
we've
got
a
essentially
where
we
have
the
three
CN
CF
relation
stages
right
now,
to
start
with,
graduated
projects
incubating
projects
and
foundation
projects
they're
all
points
we'll
organized
through
a
young
fellow
with
the
labeled
project,
CNC
appellation,
so
pair
of
sections
as
well
as
order,
and
so
it's
coming
along.
It's
nearly
ready
to
be
released.
A
That
looks
great
and
yes,
there
are
mock
is
a
little
bit
out
of
date,
so
our
mock
had
I,
believe
linker
D
in
or
know
it
had
fluency
in
the
incubating,
but
it
has
since
graduated.
So
thank
you
so
much
for
updating
that,
looking
forward
to
seeing
it
on
production
coming
soon,
I'll
jump
back
onto
the
screen
share
the
next
item.
A
So
that's
one
of
our
main
goals
for
doing
the
CI
refactoring
and
so
far,
we've
broken
it
down
to
several
parts
for
the
main
epic
of
support
and
cube
ATM
for
bootstrapping,
the
kubernetes
cluster
Zhaan's
packet,
and
so
far
we
have
made
good
progress
on
updating.
How
hardware
is
provisioning
so
dumper
if
you'd
like
to
talk
a
little
bit
about
it,
I've
dropped
in
our
visual
representation
of
the
CI
infrastructure
refactor
as
well,
and
if
you'd
like
to
share
your
screen
for
anything
or
want
me
to
go
to
any
link.
Please
let
me
know.
B
So
we've
finished
the
first
component
of
this,
which
was
separating
out
the
hardware
provisioning
verse,
the
Kuban
eighties
bootstrapping,
because
in
the
past,
with
Kross
cloud
they
were
one
of
the
same.
But
as
a
CI
system
we
want
to
have
both
Asst
parts
be
composable,
so
the
provisioning
fails.
You
know
that
failed
and
have
better
terraform
logging,
so
we
didn't
tell
why
it
failed
and
then
be
able
to
run
retries
and
roll
back.
B
So
it's
not
just
fair
on
the
jobs
over
and
that
involved
adding
some
additional
scripts
to
be
able
to
go
to
check
inventory
at
packet
when
we're
not
using
reserve
service.
So
do
we
have
we're
asking
five
nodes?
Are
there
as
their
capacity
for
that?
So
we've
added
things
like
that,
which
will
else
okay
check
the
facility?
B
So
we
we
know
what
version
of
kubernetes
we're
versioning
at
running
and
if
we're
doing
a
head
a
few
banana
bits,
we
need
to
know
what
commit
so
we
can
show
them
the
dashboard.
So
that's
in
progress
and
then
the
next
ticket
we
have
after
that
also
is
to
support
container,
because
content
is
a
project
under
CNCs.
But
at
the
moment
a
tube
spray
is
only
supporting
doherty
directly
and
that
covers
everything
and
progressed
on
that's
our
thing.
Sina.
C
C
I
dropped
a
link
to
a
question
I
had
on
the
packet
slack
I,
don't
know
Edie.
If
you
saw
that
thread.
This
is
on
the
integration
thread,
so
anybody
that
has,
if
you've
already
joined
the
packet
slack
and
go
to
that
it's
in
an
integration
channel,
but
I
can
speak
to
her
fast.
So
when
Denver
was
working
on
the
capacity
checks,
there's
a
API
which
actually
I
can
drop
that.
So
there's
a
API
call
in
the
packet
API
that
lets
you
do
capacity
checks
for
non
reserves,
the
on-demand
instances
and
it's
it
doesn't
say
that.
C
C
C
B
We're
looking
at
a
in
a
facility
based
by
base,
so
first
try
history
see:
do
we
have
the
reserve
capacity
to
to
provision?
That's
these
amount
of
resources
and
the
trick
with
the
reserved
ones
is
the
D
provision
times
quite
a
lot.
So
we
make
the
provision,
but
the
entry
run
again,
but
it's
still
15
minutes
until
they're
available
again
right.
E
E
C
Yeah,
ideally,
it
would
work
at
the
higher
level
just
like
the
the
other
capacity
check,
and
if
you
don't
specify
specific
instance
IDs
whenever
you're
using
the
reserved,
then
the
Machine
creation
API
acts
pretty
similar.
So
it
would
do
next
available
from
the
pool
of
reserved
similar
to
next
available
from
the
pool
of
on-demand.
C
Ideally,
the
capacity
check
from
a
high
level
would
do
the
same.
Do
you
have
enough
capacity
in
your
reserve?
Pool
yes
go
forward,
and
if
not
that's
you
know,
we
can
get
more
specific,
but
ideally
you
can
at
least
do
the
minimum
of
that
I.
Don't
know
if
there's,
if
you
can
provide
information
on
does
or
D
provisioning,
that's
would
be
great,
but
that's,
that's
probably
would
be
the
next
level
of
details.
E
C
G
E
C
E
E
C
E
C
A
minimum,
if
there's
going
to
be
deep
provisioning
or
that
we
could
say
what
is
the
state
of
the
system
and
if
we
know
it's
in
a
deep
provisioning
state
and
there's
some
type
of
timestamp
related,
then,
ideally,
we
can
at
least
derive
that.
Oh,
it
shouldn't
be
in
the
d
provisioning
state
for
two
hours
right.
E
G
Is
Watson
I
had
a
comment
too.
If
we're
talking
about
checking
capacity,
I
guess
Denver
mentioned
this.
What
I
would
call
it
an
atomic
way
so
saying
are
three
servers
available
because
I
need
three.
Otherwise
is
not
useful
to
me.
I
guess:
I
didn't
don't
remember
the
API
says:
can
you
reserve
three
at
a
time
that
also
you're
still
going
to
run
into
problems?
If
you
can't
also
reserved.
C
E
C
So
it's
almost
like
it's
not
a
capacity
check,
it
would
be.
This
is
a
actual
request
to
allocate
those
machines
as
an
entire
set,
and
then
you,
when
you
say,
allocate
them
all
whatever
you
do
for
implementation.
On
the
back
side,
you
mark
those
where
they're
going
to
be
provisioned,
even
if
or
they're
available
to,
whoever
asked
great.
C
C
A
Great
thank
you
and
we're
also
working
on
the
epic
to
add
support
for
external
contributions
and
currently
we've
completed
one
step
which
is
changing
where
the
project
details,
the
display
name,
logo
and
caption
are
retrieved
for
the
dashboard
and
in
progress.
We
are
working
on
the
release,
details
and
so
that
corresponds
to
the
visual
combs.
You
can
see
on-scene
CFC
I,
so
anything
under
the
project
column
has
a
new
repo
per
project
where
those
details
can
be
updated
and
currently
we're
working
on
things
within
the
release,
column
and
I'll
take
a
look
at
the.
A
G
So
the
release
details,
what
we're
trying
to
do
is
have
it
so
that
the
the
project
owners
maintainer
can
have
more
control,
fine-grained
control
when
they
add
the
project
so
release
details
are
there
in
the
mo
file
on
the
bottom.
This
file
is
something
that
the
project
maintainers
would
eventually
control.
G
So
stable
ref
is
and
give
a
little
bit
of
history
of
the
stable
ref,
and
what
a
ref
is.
A
ref
is
really
a
semantic
version
or
we
hope
a
semantic
version.
That's
really
anything
that
project
maintainer
decides
as
a
tag
for
their
release.
Name,
we,
you
know,
talked
previously
about
trying
to
do
this.
Programmatically
on
our
end
or
something
and
just
doesn't
work.
Some
people
don't
use
semantic
versioning.
Some
people
do
different
themes,
so
we
it's
best
for
us.
C
G
Maintainers
do
that
and
then,
of
course,
they
head.
Ref
is
a
branch
name,
so
you've
got
a
tag
or
a
branch
is
both
of
those
either.
Those
can
be
in
gitlab.
Carl
answers
a
ref,
so
we
allow
for
the
project
contributors
now
to
they
can
do
a
pull
request
against
their
respective
project
configuration
file.
G
That's
under
the
cross
cloud
project,
I'm,
not
CNCs,
CI,
that,
oh
and
in
future,
we're
going
to
have
it
to
where
that's
yet
CN
CF
CI
animals
I
actually
in
the
projects
repo,
so
that
they
can
maintain
it
kind
of
like
a
try
to
see
how
I
or
circle
CI
style,
and
so
that's
the
direction
we're
going
and
that's
on
des
now
so
you're,
looking
at
how
that'll
and
on
prod.
Sometimes
we.
A
Thanks
Watson
and
yes
well-
also
update
the
contributing
guide
we've
got
under
a
cross
called
CI
repo,
the
contributing
markdown
file,
which
will
be
updated
incrementally
as
each
one
of
these
steps
are
updated.
So
currently,
you
can
update
the
release,
details
and
follow
the
steps
here
and
once
we
have
the
stable
ref
and
the
head
ref
promoted
through
will
update
this
contributing
guide
to
add
those
steps
as
well.
A
So
we
currently
do
an
external
integration
with
one
of
the
projects
that
are
on
the
dashboard
and
that
is
own
app
and
own
app
uses
Jenkins.
So
we're
connected
to
that
external
CI
system
and
we'll
take
a
look
at
the
graduated
projects
first
and
see
if
they're,
using
Travis,
CI
or
circle
CI
or
drone,
but
IO
and
Desai,
and
and
pick
one
integration
to
start
with.
A
After
that,
we'll
work
on
the
app
deploy
phase
so
we'll
use
the
container
artifacts
that
were
published
by
the
CNCs
projects
to
inform
the
deploy,
step
and
update
the
documentation
and
then
we'll
be
able
to
start
collaborating
with
scene.
Cf,
hosted
projects
for
more
interaction
and
having
them
add
and
maintain
their
projects.
And
after
that,
we'll
work
on
the
end-to-end
tests
with
the
projects.
A
C
So
drone
I/o
was
one
of
the
ones
that
looks
promising
for
people
who
want
multiple
architectures
and
something
it's
real
portable
and
we
were
discussing
how
number
one
we
could
help
the
project's
directly
by
saying
here's
a
easier
way
to
run
or
do
builds
on
different
architectures.
Maybe
for
every
pull
request
was
something
that
Matt
was
saying
arm
is
focused
on
and
then
we're
interested
in
being
able
to
support
those
external
systems.
C
C
Think
it's
promising
for
the
effort
that
we've
been
working
on,
because
we
do
want
external
folks
that
are
actually
creating
some
of
those
see
eyes
right
now,
we've
been
doing
most
of
the
work
like
that.
Oh
now,
integration,
the
Jenkins.
We
did
get
some
input
on
the
status,
but
if
there's
someone
actually
building
it
for
project
that
nothing.
A
D
No
I
think
you've
captured
it
all
mostly
I
think
matt
has
been
working
more
active.
We
had
to
think
that
Andrew
and
seemed
quite
promising.
We
are
well
in
gauging
more
actively
with
some
of
the
other
CI
system.
Companies
behind
it,
but
Drona
currently
seem
to
be
quite
well
set
up
to
actually
get
this
not
get
this
running
so
that
song
that's
a
reason
why
I
might
actually
discuss
the
weight
with
you
on
that.
Okay.
C
And
I
guess
a
related
item
was
there
was
another
was
maybe
a
need
for
help
on
get
arm
builds
on
get
lab,
so
arm
builds
of
projects
using
get
lab,
and
we've
approached
in
full
ways,
including
using
VMs
for
the
arm
to
build
the
projects
or
arm,
as
well
as
using
at
the
physical
packet
machines
and
deploying
runners
and
and
actually
building
the
the
various
projects.
The
their
arm
side
on
packet
machines
and
I.
C
C
C
And
Philip
it
would
be
good
to
get
on
that
from
your
side.
I.
D
E
This
is
Edie.
I
am
aware
of
a
set
of
patches
that
were
put
together
to
support,
get
lab
runner
on
arm
and
that
got
pulled
into
a
broader
discussion
of
get
lab
runner
on
multiple
architectures
and
I
will
I
know
that
there
are
some.
There
are
some
open
issues
that
might
be
worth
reviewing
for
that
which
all
which
all
identify.
C
H
Yeah,
if
you
have
the
issue,
if
you
can,
if
you
can
put
it
that
would
be
great,
otherwise
I
can
lower
search
to
okay.
C
So
we
do
have
runners
on
arm,
so
I
definitely
want
to
get
Denver
and
our
site
involved.
So
if
you
can
put
just
get
us
all
in
that
list
and
we
can
at
least
contribute
to
knowledge
about
how
we're
doing
it,
which
may
may
not
be
the
best
way-
but
at
least
you
can
show
here
is
a
working
example.
A
Thanks
everyone,
alright
great,
so
we
welcome
feedback.
We've
got
the
crust
on
see,
I,
see
a
dashboard
github
tracker
you're
welcome
to
join
slack
D&C
up
slack
at
scene.
Cf,
dosh,
CI
email
join
the
mailing
list,
and
this
call
is
a
fourth
Tuesday
of
the
month,
currently
11
a.m.
Pacific
time.
The
next
item
on
the
agenda
was
maybe
having
a
lazy
consensus
of
Plus
Ones
thumbs
ups.
H
H
America,
yes
and
I
was
just
wondering
if
anyone
here
is
interested
in
collaborating
on
some
proposals.
I
really
want
to
submit
some
talks
around
see,
I,
see,
I,
see,
D
and
just
not
not
like
a
keep
lab
CI
story,
but
more
like
I.
Think.
This
group
here
has
a
lot
of
the
CI
brain
trust
and
we
could
put
together
something
that
is
educational
for
a
lot
of
folks.
C
It
sounds
like
a
good
idea:
why
didn't
maybe
paying
off
offline
okay,
yeah.
H
H
H
A
That
sounds
great
all
right,
so
we
will
see
you
again
on
the
fourth
Tuesday
of
July.
Continue
a
conversation
on
the
slack
in
the
mailing
list
and
I
will
ask
the
CNC
F
CI
team
to
update
the
community
calendar
for
this
call
to
start
at
12:00
noon.
Pacific
time
for
next
time.
These
meeting
notes
are
available
any
time.
So
if
you
have
any
demo
or
news
or
updates
or
questions
that
you
would
like
to
address
in
next
month's
call,
please
feel
free
to
add
them
at
any
time.