►
From YouTube: CNCF CI WG Meeting - 2019-01-22
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
B
A
C
E
C
D
F
D
D
F
D
F
Think
it's
only
just
a
couple
of
minutes
because
there
had
been
some
previous
discussion
on
a
an
issue
in
github
in
the
cross
cloud.
Cia
repo,
the
cross
cloud,
repo
and
I
just
wanted
to
bring
it
back
up
because
they
kind
of
had
stopped
it
Wilton
pick
it
up.
On,
January,
22nd,
so
I
just
wanted
to
get
that
started
again.
Then
we
can
take
it
offline.
After
that,
probably.
D
A
D
Great
105
we
can
get
started
thanks
for
joining
us
fancy.
Fbi
working
group
today
is
January
22nd.
Just
a
quick
note.
This
meeting
is
being
recorded
and
will
be
shared
to
the
cloud
native
computing
foundation.
Youtube
channel
right
after
this
phone,
the
CNC
FCI
working
group
meetings
are
monthly
on
the
fourth
tuesdays
of
the
month.
At
this
time,
11:00
a.m.
Pacific
time.
D
The
recap:
we've
attended
the
Kubik
on
China
and
Shanghai
and
there's
a
link
here
to
the
presentation
that
was
presented.
If
you
would
like
to
take
a
look
at
the
slides,
the
MC
FEI
intro
presentation
was
given
by
watson.
We
also
have
discovering
the
untold
user
stories
of
kubernetes
with
applied
anthropology.
This
was
delivered
by
hippie
hacker
here,
welcome
to
click
through
and
see
that
talk.
D
We
also
attended
cucum
Seattle
and
the
co-located
event,
FBI
Oh
mini
summit,
where
a
talk
on
the
CMS
was
given
and
a
cube
con,
Seattle
and
intro
to
the
cross
club
CI
and
we've
got
a
youtube
link
here
for
the
presentation
and
intro
and
the
deep
dive
youtube
links
for
both
and
Andrew
from
VMware
gave
a
presentation
on
adding
support
for
new
platforms
and
you're.
Welcome
to
click
through
to
see
his
presentation.
There
I'm
upcoming
events
that
we
are
looking
forward
to
include
the
Mobile
World
Congress
for
Barcelona.
D
A
D
D
In
April
we'll
be
attending
the
open
networking
summit
in
San
Jose
California
we've
submitted
a
few
csps
and
are
crossing
our
fingers
and
toes
and
hoping
to
hear
back.
One
of
the
topics
for
cross
club
projects
will
be
regarding
cross
group
collaboration
and
how
and
why
we
added
the
Linux
Foundation
projects
called
own
app
to
the
CNCs
CI
dashboard
and
we'll
talk
a
bit
more
about
that
idea.
D
In
general,
when
we
take
a
look
at
the
next
iteration
of
PMC
FCI
planning
in
May
is
the
next
cube
quorum
cloud
native
Khan
in
Europe
in
Barcelona,
the
CSP
window
for
that
event
has
closed,
but
please
click
through.
If
you
are
interested
in
attending
that
pool
event
through
and
by
cube,
kubernetes
and
Club
native
computing
foundation.
D
D
Right,
the
next
iteration
of
San
CSCI
GFCI,
is
currently
a
status
dashboard
that
shows
multiple
projects
and
multiple
cloud
providers,
provisioning
on
kubernetes
and
then
running
on
the
cloud
providers.
Since
the
FCI
v2
will
have
a
different
focus
and
view
so.
I
will
pine
box
this,
probably
five
minutes
or
less
I'll
go
over
the
goals
for
the
next
iteration
of
the
stance.
The
FCI
dashboard
high
level
features
review
the
mocks
and
the
roadmap.
D
All
right
high-level
goals
for
the
fancy
FBI
dashboard-
these
are
in
line
with
the
CFCF
goals.
We
want
to
help
demonstrate
the
use
of
cloud
native
technologies
and
promotes
new
AMCs
projects,
attracts
more
interest
in
15
CS
and
provide
a
third
party
neutral
spot
to
validate
these
projects,
we'd
like
to
support
and
contribute
to
a
sustainable
and
scalable
project
ecosystem
and
allow
to
get
feedback
from
cloud
native
end-users
and
projects.
D
D
So
the
first
key
feature
of
the
new
iteration
of
the
dashboard
will
be
it's
a
highlight
and
validate
the
CNCs
graduated
and
incubating
projects.
Currently,
there
are
three
levels
of
maturity
for
CNCs
projects,
graduated
incubating
in
sandbox
and
we'd
like
to
start
by
really
highlighting
those
graduated
and
incubating
ones
and
we'll
start
by
validating
the
stable
and
head
releases
where
the
stable
and
head
commits
from
github
the
sandbox
projects
may
be
added
at
a
later
time.
We
will
start
with
those
top
maturity.
D
Projects
will
list
them
in
alphabetical
order
of
graduated
and
then
followed
by
alphabetical
order
of
incubated,
and
we
also
have
a
section
for
Linux
Foundation
projects
like
own
app.
We
plan
to
reuse
build
containers
that
are
provided
by
a
project
CI
system
which
is
different
than
what
the
current
dashboard
does.
Now
we
build
those
projects.
D
But
only
with
that,
we
want
to
increase
collaboration
with
the
project
maintainers.
So
we
will
be
reworking
the
dashboard
and
the
different
components
so
that
the
maintainer
can
update
up
the
project
details
through
a
github
PR
release
details
their
github
PR
we'd,
like
our
system
to
integrate
with
your
external
CI
system,
we're
currently
using
git
lab
as
the
base
CI
system,
and
we
want
it
to
be
a
flexible
system
that
can
use
if
you
use
gate
lab,
we'll
use
that
if
you
use
Travis
CI
will
integrate
with
that
Jenkins,
etc.
D
D
Currently
we're
showing
the
stable
in
the
head
releases
and
we
would
like
to
add
support
for
the
release
candidate.
The
new
UI
also
supports
more
release
versions.
If
we
would
like
to
go
back
one
or
two
versions
of
kubernetes,
for
example,
our
new
UI
will
allow
for
that
support
as
well
and
finally,
another
key
features
we'd
like
to
start
using
cube
ATM
for
bootstrapping
and
kubernetes
on
the
packet.
D
D
So
here
is
the
mock-up
for
the
next
iteration
for
the
CI
dashboard
overview
screen
at
the
top.
We've
got
the
test
environment
showing
kubernetes,
stable
release
running
on
bare
metal
packet,
and
that
initial
stage
is
a
success.
After
that
initial
stage
is
successful,
then
the
graduated
Sancia
projects
will
show
the
releases.
This
is
the
latest
stable
and
the
latest
TED
commit
from
github
the
build
status,
the
deploy
status,
and
then
this
would
be
the
end-to-end
test
status.
D
The
badges
indicate
a
success
or
a
fail,
and
if
the
build
stage
failed,
then
the
deploy
and
test
stage
would
show
a
grey
and
they
badged.
It
would
not
be
clickable.
We
would
not
run
any
action
if
that
initial
stage
failed.
Likewise,
if
we
build
and
deploy
the
build
brand
in
the
deploy
field,
then
we
would
not
show
the
end-to-end
test
and
we
may
see
in
the
beginning.
D
The
next
slides
show
the
kubernetes
release
selector.
So
here's
stable
view
113
one
has
a
down
arrow,
I
click
on
that
down
arrow
and
it
opens
up
a
selector
drop
down.
I
have
the
options
to
choose
the
latest
I'd
commit
or
the
release
candidate
should
be
a
new
feature.
If
I
highlight
over
release
candidate
Senate
switches
to
release
candidate.
D
D
D
Okay,
I'll
continue
the
roadmap.
How
are
you
going
to
get
there
January
here?
We
are.
We
are
planning
and
announcing
those
changes.
February
next
month,
we
plan
to
reveal
the
new
UI
of
the
project
focused
homes,
home
screen.
We
also
would
like
to
implement
the
smoke
tests
after
the
app
deployed
and
plan
for
integrations
and
cube
ATM
for
March,
we'll
be
preparing
for
the
open
networking
summit
in
San
Jose.
So
we
would
like
to
update
own
app
and
we'd
like
to
implement
the
external
integration
to
the
project's
CI
system.
A
D
Next
March
preparation
for
that
working
group
at
the
end
of
March
and
open
networking
summit
in
the
beginning
of
April
updating,
onap
Phileas
reliefs
are
adding
nzn
and
smoke
tests
and
start
updating
that
functionality
to
add
the
project.
Details,
release
details,
build
details
integrations
with
the
external
systems,
updating
each
component
so
that
we
can
collaborate
with
those
project
maintainers
and
creating
that
readme
as
well
and
then
later
on
in
the
year.
We
hope
to
add
that
release
candidate
for
kubernetes.
We
have
some
presentations
for
cube,
con,
tu
and
intro
to
the
stands.
D
C
Thanks
for
sinner,
so
this
is
part
of
complimenting
other
projects
and
efforts
that
are
going
on
like
the
conformance
or
congruent
sig
testing
and
we've
been
actively
talking
with
folks
about
Pesce
red
and
how
we
could
integrate
directly.
Maybe
pull
results,
help
with
different
views,
there's
a
dashboard
right
now.
That's
for
tester!
It
is
goes
into
lots
of
details
that
help
the
developers,
especially
kick
Nettie's
everything
and,
and
then
results
are
sent.
C
A
C
We're
trying
to
make
sure
that
what
we're
doing
is
complementing,
or
it
may
be,
exploring
some
areas
that
aren't
area
and
that's
what
this
is
about,
so
we're
hoping
to
get
feedback
going
forward
and
where,
where
we
can
help
best
from
like
a
cloud
provider,
standpoint
and
people
that
are
wanting
to
test
or
look
at
things
right
now,
it's
going
to
be
as
listening.
I
was
just
going
over
we're
moving
off
on
the
the
view,
so
that's
not
the
focus
and
then
we'll
be
helping.
C
G
C
E
C
So
the
the
next
iteration
that's
going
to
be
released
for
the
San
CFC,
I
dashboards,
so
I
think
that's
what
you're
referring
to
right
now.
Other
people
could
run
different
dashboards.
The
source
is
available
to
run
all
of
that,
but
the
actual
dashboard
that's
running
on
CN
CF
CI
right
now
will
not
have
cloud
providers
as
a
focus
at
some
future
date.
There
may
be
another
screen
or
a
view
that
could
show
that
don't
know
what
that's
going
to
be,
but
right
now
there
won't
be
cloud
providers
there.
So
there's
there
are
on
test
grid.
A
B
Sorry
this
is
Dan
conference
and
see,
if
maybe
we
could
just
provide
one
piece
of
context.
It's
that's
missing
from
this,
which
is
the
original
driver
for
making
this
change
to
to
that.
Oh,
is
that
we
want
the
responsibility
for
ensuring
that
the
clouds
are
working
correctly
on
the
clouds
that
we
don't
feel
like
were
the
the
right
body
to
be
ensuring
to
fix
things
and
such
and
in
many
cases
it's
required
coordination.
B
That's
that's
challenging
for
us
to
pull
off,
and
so,
if
each
project
is
there,
each
cloud
or
each
provider
is
responsible
for
it.
Then
they
could
provide
the
data
to
us
and
we
could
display
it.
But
the
question
then
is
well
how
what
are
we
going
to
do
that
with
the
data?
That's
different
from
test
grid,
and
so
I
guess
I
would
would
leave
open
the
idea
of
us
displaying
something
in
the
future.
It's
we're
not
ruling
it
out,
but
but
for
now
we
don't.
D
A
Maybe
that
cloud
having
a
bad
day
or
something
specific
to
the
cloud
or
whether
it
was
specific
to
the
project
just
test
grid
have
I
guess
views.
I
certainly
would
have
all
the
data,
but
does
it
currently
have
used?
That
would
allow
you
to
do
the
sort
of
cross
cloud
comparison
within
the
test
for
infrastructure
and.
C
They
don't,
as
far
as
I
know,
there's
nothing
in
test
grid.
That'll,
give
you
a
quick
overview
of
all
the
projects.
The
data
is
there,
so
you
could
go
through
and
look
at
the
health
of
say
three
or
four
different
cloud
providers,
you're
wanting
to
look
at
and
look
at
how
that
is,
but
there's
no
quick
overview
screen
and
I
think
tying
in
with
what
Dan
was
saying.
There's
been
requests
from
a
lot
of
folks
on
the
test
that
work
with
test
grid
and
from
different
projects.
C
That
would
like
a
view
that
does
that
that
may
be
a
completely
different
type
of
dashboard.
It
may
not
be
at
same
GFCI,
it
could
be
wherever,
but
there's
been
a
desire
to
do
that
and
that
that
could
happen.
There's
some
interest
we'll
be
talking
with
them
and
then,
as
far
as
something
directly
on
the
dashboard,
and
to
continue
with
what
Dan
was
saying.
C
If
we
can
have
cloud
providers
that
can
help
make
that
maintained,
I
want
to
say
help,
but
they
actually
maintain
running
the
tests
submitting
the
results,
and
we
know
we
already
have
a
home
for
those
that
other
people
are
doing
it
that's
test
grid.
We
could
potentially
have
a
view
of
the
test,
data
and
specific
parts
that
maybe
the
community
as
a
whole
says
we're
real
interested
in
this
space.
C
D
E
So
I
think
you
guys
should
be
able
to
see
my
screen
yeah
okay,
so
today,
I
will.
Let
me
share
a
very
simple
demo
about
how
we
be
running
a
very
something
very
similar.
True,
since,
if
that's
for
you
Alibaba
Group,
actually
the
background
is
we
have
a
lot
of
teams,
inaudible
group,
including
Alibaba
cloud,
including
the
unfinished
all.
We
have
a
lot
of
affiliate
company
single
above
a
group.
They
have
their
own
kubernetes
cluster
actually
and
we
notice
there's
some
of
our
teams.
E
They
actually,
you
know,
maybe
had
a
little
bit
about
on
the
kubernetes
code
and
they
began
to
maintain
their
own
version
and
they
began
to
divert
from
the
upstream
which
we
are
trying
to
avoid
this
situation.
So
the
last
year
we
created
a
cross
team,
CI
dashboard
in
Alibaba
Group,
and
we
asked
who
required
every
team
you
know
about
you
uploaded
your
end-to-end
test
result
I
mean
option.
E
Entrant
has
read
out
to
the
system,
so
we
can
know
that
came
is
began
to
divert
from
the
upstream
and
we
will
cooperate
with
them
to
make
sure
that
they
will
keep
up
with
the
action
and
we
will
see
anything
contributed.
Could
you
bring
back
to
an
option
or
anything
we
need
to
we
implement
or
refactor
into
having
something
that
that
is
why
we
have
a
close
team,
CI
dashboarding
on
up,
and
it
currently
works
very
well
and
the
UI
of
this
dark
for
a
very
simple.
E
E
We
have
kin
which
and
then
is
all
evening
which
dumplings
Alibaba
cloud
and
we
also
have
the
the
the
dead
table
for
all
the
other
teams
inside
and
Alibaba
I
have
very
small,
very
quick
demo
about
how
how
this
close
closely
I
works,
and
you
can
see
here
it
is
actually
a
very
simple
front-end
web
site
and
every
table.
Every
every
data
in
this
cockerel
crows
team
see
is
actually
is
the
rding
over
kubernetes
cluster.
E
So
but
number
we
can't
define
a
category
which
name
is
crew
bananas
and
we
can
defy
the
test
result
project
which
name
like
conformance
test
or
end-to-end
test.
So
after
that
we
just
created
these
CRTs
incriminated
cluster,
and
then
we
will
have
the
category
and
the
project
on
the
website
of
the
VI
of
the
site.
Dashboard,
it's
very
easy.
E
So
so,
as
you
can
see,
if
you
credits
the
our
division
and
conformance
test
as
the
Arabic
name
end-to-end
test,
you
will
have
a
true
grown
here
and
after
that
we
also
add
our
own
provider,
which
is
actually
a
different
teams.
For
example,
we
have
team,
which
name
is
Ali
Baba,
which
have
team
which
named
Ali
Ali
Ewing,
and
that
is
actually
so.
E
Every
team
being
in
inside
Alibaba
Group
will
go
and
themselves
and
the
patter
on
these
close
close
the
eye
and
after
you
create
this
Kristy's,
they
are
DS
and
you
can
see
that
we
have
more
providers
in
over
close
close
the
eye
and
as
long
as
we
have
all
the
teams
on
board
with
the
window
verse
they
are
dashboard
and
then
the
Loews
team
will
be
required
to
upload
their
test
result
and
and
again.
The
test
result
is
also
easy.
E
Rd
vicious
following
these
specifications
like
about
in
your
project
within
your
cluster
version
and
what
is
the
has
to
result
from
your
team,
and
we
also
require
them
to
link
a
URL
of
their
intern
or
CI
system.
Maybe
it's
jackings
or
Travis.
We
don't
care
about
initially
the
UI
of
the
build,
and
you
can
see
we
actually
added
as
a
field
which
named
detailed,
detailed
reference
and,
ultimately,
credit.
This
test
result
CRTs
in
over
kubernetes
cluster,
and
then
we
will
see
on
the
real
test
reload
uploaded
from
different
games.
D
E
E
So
this
is
basically
on
how
or
a
close
team
CI
dashboard
works
in
Alibaba
cloud,
and
you
can
see
it
actually
very
similar
to
to
the
same
safe,
CI
dashboard
and
that's
why
we
are
trying
to
see
if
their
cooperation
with
since
that's
the
I
work
group
and
we
have
over
one
of
the
over
primary
go
ahead.
We
want
to
add
on
a
bubble
cloud
at
Apple
water
using
close
closely
I,
but
at
via
already
discussed
all
fly
and
today
and
actually
we
can
see
the
seamstick
cross
class.
E
They
are
trying
to
use
test
grade
as
a
new
bedroom.
It
Hanako
Collider.
So
here
are
some
very
quick
questions.
You
may
be
lookin
discussed
later
in
this,
so
what
will
be
the
same?
Sex
toy
dashboard
looks
like
I
have
asked
his
question
actually
meeting
and
the
second
question
is
Hobbs
incident.
Ci
dashboard
click
data
from
text
grid,
or
we
just
you
know-
maybe
we
don't
care
about
that.
E
We
just
do
stay
Square
to
as
a
as
all
these
tests
without
dashboard
instead
and
the
second
goal
of
our
collaboration,
we're
going
to
trying
to
looking
at
is
that
we
want
to
install
since
they've
closed
clubs.
They
are
inside
Alibaba
to
serve
as
the
next
version
of
over
closed
teams.
They
are
dashboard
because
you
know
we
don't
want
to
maintain
something
which
is
basically
exactly
same.
This
means
that
all
the
sins
that
we're
doing-
and
we
can
see
that
we
already
have
open
source
project.
E
C
Let
me
add
me
here:
okay,
well,.
C
So
the
we
kind
of
went
over
I
guess
how
it
looks.
So
we
have
some
of
those
mocks
as
far
as
how
the
view
of
the
dashboard
is
the
current
view
that
we
have
that's
again
available
if
someone
wanted
to
for
can
use
that,
as
as
is
the
dashboard
itself,
is
pretty
flexible
as
far
as
adding
new
clouds.
But
the
new
view
is
what
we
were
just
showing
mocks,
I'm,
not
sure
exactly
what
they
look
like.
As
far
as
if
you
came
in
it'd
be
nice.
C
If
you
may
have
to
go
back
and
get
the
older
current
version,
if
you
wanted
to
be
able
to
have
what
we
have
I
think
either
way
the
new
view
or
the
other,
it
is
about
showing
status,
different
stages
that
could
be
projects
or
could
be
groups,
so
it's
still
probably
pretty
applicable
to
what
you're
doing
as
far
as
Alibaba
as
a
cloud
provider
I'm
happy
to
help
with
the
integration
into
test
grid
and
collecting
data
and
the
there
won't
be
any
dashboard
at
this
time
other
than
test
grids.
So
it
wouldn't
be.
C
E
E
Question
is,
and
I
said
we
want
to
install
the
sensor
called
CDI
inside
Alibaba,
so
that
means
every
every
every
part
in
this
pipeline
should
be
truly
open
source
that
we
can
install
that
inside
Alibaba,
but
an
L
close,
close
close
data
is
already
fully
open
sourced,
but
as
far
as
I
know
that
the
test
grid
itself
is
not
open
source.
Yet.
D
E
B
If
test
current
is
never
going
to
be
open
source
that
that
sort
of
came
out,
I
would
be
open
to
CNCs
funding
an
open
source
replacement
for
it,
but
but
having
spoken
to
Google
about
it
it
just
it
doesn't
seem
like
there's
anything,
proprietary
or
sensitive
or
anything
like
that.
It's
just
the
tedious
issue
of
it
being
tied
to
internal
systems
and
them
not
having
the
resources
to
cut
those
ties
and
make
it
portable,
but,
and
then,
as
we
mentioned
earlier,
I
am
also
open,
particularly.
B
We
had
help
from
from
some
of
you
on
designing
and
funding
a
third-party
interface
to
test
grid
that
would
be
pulling
the
data
from
it.
So
I
think
there's
a
lot
of
areas
for
collaboration
here.
My
hope,
though,
is
the
test
grid
or
open
source
and
then
you'll
feel
more
comfortable
using
that
as
the
repository
for
all
the
data.
Okay,.
C
F
Yeah
I
could
just
bring
up
what
I
wanted
to
and
then
maybe
a
chat
for
a
couple
of
minutes,
but
I
don't
want
to
derail
the
current
discussion.
That's
going
on
for
test
grid
right
now.
That
seems
to
be
more
broadly
applicable
to
the
attendees
of
this
meeting.
So
that's
you
know
we
could
take
this
particular
topic
that
I
wanted
offline
completely.
That's
okay,.
C
Okay,
well
I,
guess
I'd
jerod
on
on
yours
and
as
far
as
Rick
we're
looking
at
with
this
new
iteration
of
the
CNCs
CI
is
making
it
a
lot
easier
for
projects
to
help
adding
themselves
and
in
doing
the
integration
with
external
systems.
So
that's
part
of
what
we're
planning
and
as
far
as
the
roadmap,
we're
going
to
be
having
public
documentation
for
how
the
different
pieces
can
be
added
and
updated
on
the
screen
where
that's
going
to
come
from.
C
There
will
be
pieces
like
it
if
we
need
to
do
a
direct
integration
with
the
new
CI
system,
so
we
talked
with
Jenkins
right
now.
We're
gonna
be
adding
support
to
talk
with
you
know
different
ones
based
on
the
project.
So
if
it's
alright
to
take
that
offline,
we
can
talk
specifically
about
route,
because
we
are
interested
in
doing
that.
Yeah.
F
That's
fine
in
the
one
comment
I
would
make
right
here
in
this
forum.
Is
that
what
I
saw
from
what
Lucia
was
talking
about
with
the
2.0
effort?
It
looks
like
that's
going
in
the
direction
that
a
lot
of
the
hosted
projects
by
the
CNC
F,
the
you
know
the
incubating
projects
and
the
graduated
projects
would
probably
like
to
see
it
go.
It
looks
like
it'll,
be
you
know,
there's
an
effort
around
being
able
to
add
those
projects
and
integrate
more
easily
inside
environments.
F
So
we
have
all
the
integration
tests
running
for
all
the
CNC
F
projects,
and
so
that's
I
think
what
I
saw
today
is
is
actually
what
I
am
very
interested
in.
Seeing
in
helping
the
the
rook
project.
Is
you
know
just
like
any
of
the
other
CN
CF
projects
integrates
and
then
the
final
thing
is
that
it
was
entirely
clear.
You
know
if
it's
possible
for
the
CNC
F
to
be
hosting
the
CI
environment
completely,
because
you
know
we're
running
our
own
Jenkins
server
right
now
and
it's
it's.
D
F
To
date
and
babysitting
it
and
hosting
it
very
effectively,
so
if
the
CNC
F
has
the
ability
to
you
know,
host
the
environment,
we'd
be
okay
with
migrating
our
current
Jenkins
setup
over
to
what
works
better
for
the
cross
cloud
environment.
Are
the
effort
there
and
you're
doing
some
of
that
porting
migration
work
in
order
to
have
the
CNC
F,
and
you
know
the
cross
cloud,
CI
experts
they're
kind
of
being
able
to
host
the
integration
test
on
a
more
day-to-day
basis,
and
then
we
could
take
the
rest
of
the
discussion
online.
C
Heard
I
guess
from
several
different
projects,
similar
things
as
far
as
hosting
that's
a
pretty
big
effort.
I
guess
is
the
short
of
it
and
I
think
there
is
an
interest
from
different
folks
that
are
helping
provide,
see
I
environments,
including
on
the
linux
foundation,
side
figuring
out
a
way
to
do
that
where
it
doesn't
require
a
team
of
50
just
to
keep
that
running,
was
it
desired.
Ideally,
it's
more
of
a
self-serve.
E
C
Maybe
in
the
future
we
could,
what
I
would
I
would
say.
I
would
like
to
look
at
would
be.
How
do
we
have
something?
That's
more
of
like
a
template
or
a
skeleton
framework
for
the
CI
system
and
its
self
serve.
So
you
can
come
in
and
if
you
put
stuff
in
there
then
then
it
then
it
runs.
Ideally
it's
similar
to
any
project
where
you're
going
to
drop
your
circle,
CI
or
Travis,
and
you
go
configure
the
pieces
that
you
care
about
and
maybe
that's
the
clusters
you
didn't
have
to
worry
about
cluster.
C
B
You
know
I
mean
I,
wouldn't
mention
that
the
packet
hardware
is
available
to
projects
via
the
community
infrastructure
lab,
but
we're
CFCF
would
definitely
be
hesitant
on
taking
over
management
of
a
Jenkins
infrastructure.
If
anything
I'd
say
we're
trying
to
get
away
from
that
and
encouraging
folks
to
go
with
commercial
hosting
got.
C
C
C
C
G
G
We
had
initially
been
working
on
the
cnc
I
code
within
the
oracle
part
of
the
cnc
f
CI
stuff
and
we're
going
to
be
transitioning
that
over
to
a
different
team.
So
we
need
to
sort
that
out
internally
and
then
we'll
follow
up.
I
think
the
email
thread
has
already
been
started
with
with
lucena,
so
we'll
just
use
that
same
one.