►
From YouTube: CNCF CI Working Group Meeting - 2018-02-13
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
B
A
A
B
A
B
B
B
B
B
D
B
One
of
the
goals
here
so,
as
Lucy
said
this,
we
meet
on
this
CI
workgroup,
twice
monthly
belong
here,
and
some
of
the
folks
on
the
team
think
that
did
this
last
release.
So
why
are
we
here
and
CNCs
has
a
lot
of
projects
that
you'll
know
prometheus
it's
growing
every
month,
a
lot
of
projects
and
a
lot
of
clouds
coming
on
and
the
goal
is
to
test
the
interoperability
between
all
the
projects
and
get
the
results
on
how
they
work
on
as
many
cloud
providers
as
possible
so
cross.
B
Let's
G
I
project,
that's
the
goal
of
building
this
out.
We
have
a
few
people
that
family
that
kind
of
question
all
right
now
could
be
actor
and
Zinberg.
The
project
consists
of
a
testing
system,
so
this
would
include
some
of
the
sense
that
you
may
be
familiar
with
of
CI
the
status
repository
server
and
a
dashboard.
The
testing
system
has
the
built
components.
B
We
have
a
goal
in
the
cross
body,
I
project,
the
targeting
all
the
projects.
What's
life
right
now:
on-scene
CFC
I,
this
Q
kinetics
Prometheus
linker
game
14
s
will
be
releasing
fluently
as
soon
and
we
have
a
few
others
in
the
works.
Likewise,
for
clouds
we'd
like
to
target
all
public
or
metal
on
private
clouds,
we
have
AWS
Google,
gcgj
packet
for
bare
metal
and
a
sure.
We
have
bluemix
ready
in
testing
ready
to
go
real
soon
and
we're
working
on
OpenStack.
B
B
Let
me
know
if
y'all
aren't
able
to
see
anything
on
the
screen,
so
this
dashboard
is
showing
the
status
from
from
builds
from
app
deployments
e
to
e
tests
and
the
Q
committees
provisioning
on
all
clouds
based
on
the
upstream
commits
so
I
got
there
here
see
this
was
a
few
kinetics
one.
Eight
one
committed
for
a
Prometheus
commit
on
master,
so
the
head
release
and
then
we
take
the
builds
and
go
through
deploying
this
to
each
one
of
the
cloud
providers.
B
We
can
see
there's
right
now,
there's
some
upstream
issues
with
Google.
These
are
actually
some
account.
Issues
were
increasing
quota,
and
some
of
these,
though,
could
be
right
now
we
have
successful
builds.
But
if
we
had
a
maybe
an
upstream
core
DNS
issue,
then
we
would
see
that,
as
we
come
clear
here,
we've
one
of
the
recent
items-
I
guess
that
were
just
about
to
just
releasing
the
last
few
days-
would
be
this
litter.
So
a
small
thing,
but
something
been
asked
for
so
word
what's
that
project.
B
So
these
are
your
standard
things
going
to
the
get
across
class,
so
this
is
the
actual
org
or
the
cross
cloud
CI
project
and
then
all
the
different
components
that
make
that
a
for
how
the
whole
thing
works.
We
one
other
item
we
were
asked
for
to
add
with
a
prominent.
Where
do
we
report
bugs
on
all
of
these?
The
main
focus.
D
D
B
Let's
go
ahead
and
see
how
some
of
this
runs.
Normally,
this
is
running
every
daily
for
Santi
s,
the
CNCs
CI.
It
is
going
to
go
through
and
do
builds
and
check
the
status
of
whatever
is
currently
available.
We
actually
pushed
a
few
things
out
for
fixes
on
projects,
and
so
it
was
run
recently,
I'd
like
to
show
doing
an
actual
app
deployment.
So
what.
B
B
B
The
backend
system
I
had
all
these
tabs
ready
on
the
other
computer,
but
three
let'em
here,
so
we
can
see
on
cross
project
which
I
mentioned
earlier,
which
is
the
app
deployment
component
for
the
testing
system.
You
can
see
that
a
bunch
of
jobs
got
kicked
off.
These
are
pipelines
for
doing
the
app
deployments
and
if
we
go
back
and
look
at
the
dashboard,
we
can
see
here's
Prometheus
getting
deployed
on
some
of
these
routes.
It
may
not
work
on
some
of
these
where
there
were
failures.
B
This
is
it
testing
right
now,
but
as
these
go
through
we'll
see
some
more
so
let's
go
look
a
little
bit
more
on
what
these
parts
are
and
then
we'll
come
back
and
check
here
in
a
bed.
So
the
testing
system-
this
is
a
built
pipelines.
It's
per
project.
We
can
optionally
use
a
project's
build
artifacts.
So
if
Prometheus
has
a
CI
system
where
artifacts
are
stored
and
usable
by
the
public
for
potentially
PI
s,
we
could
pull
those
out
or
we
build
our
own.
So
that
was
something
we
were
looking
at
earlier.
B
Go
back
to
cloud
provisioning
pipeline,
that's
cross
cloud!
That's
true
burn
Eddie's
deployments.
Do
all
the
cloud
providers
app
deployment
pipeline,
that's
cross
project
which
we
were
just
looking
at
over
here
and
that's
deploying
the
Prometheus
and
any
other
application
onto
those
kubernetes
clusters
or
potentially
some
other
environment
the
built
pipeline.
So
let's
look
at
those
stages
and
your
traditional
set,
compiling
the
binaries
e
to
e
test
and
getting
all
of
those
things
ready.
D
B
Available
at
different
stages,
so
even
if
we're
using
an
external
system
for
the
artifacts
will
still
create
those
pinning
so
that
we
know
what
they
are
and
we
can
use
them
in
the
next
pipeline.
So
the
cloud
provisioning
again,
this
is
kubernetes
provisioning
will
collect
all
pinnings
from
the
builds
of
kubernetes
and
then
deploy
those
and
then
we'll
update
the
dashboard
status
patches
as
we're
going
along.
So
as
kubernetes
is
getting
deployed,
it
will
start
saying
running
and
we
can
look
at
the
provisioning
and
then
we'll
go
to
the
app
deployment
stage.
B
Once
kubernetes
provisioning
is
done.
Those
clusters
are
ready,
which
may
have
been
done
beforehand.
There
may
be
available
one.
Otherwise
these
can
go
consecutively.
We
use
helm,
charts
to
deplete
one
of
those
projects
and
then
we'll
deploy
the
e2e
test.
Containers
similarly
run
those
été
tests
and
then
based
on
the
results
of
each
one
of
those
stages,
we'll
be
updating
the
dashboard
status
batch.
So,
if
anything
fails
then
it'll
be
marked,
as
Wells
will
have
the
satisfying
to
the
appropriate
job
it
passes,
then
it.
B
B
B
Internet,
okay,
well,
each
one
of
these
jobs
will
be
similar
to
what
we
just
looked
at
on
the
this
again
was
the
app
deploy.
The
next
job
was
the
end-to-end
test
and,
as
we
saw
it,
it
went
all
the
way
through
and
past,
and
then,
if
we
go
back
here,
we
can
see
more
of
these
are
starting
to
complete,
like
Prometheus
on
a
sure,
looks
good
for
me.
Prometheus
version
200
on
AWS
looks
good.
We
go
through
each
of
those
any
failures.
We
could
similar
look
like
this
dire.
B
D
B
If
get
lab
is
one
of
the
main
components
right
now
that
we're
using
and
get
lab,
if
you're
not
familiar
with
a
unified,
CI
CD
platform,
it
provides
runners
ability
to
do,
builds
your
normal
jobs.
It
also
does
mirroring
of
the
git
repos
so
that
we
can
do
triggers
on
those
sort
of
things
for
the
provisioning,
we're
using
care
form
cloud
in
it.
B
And
then
we
do
custom
kubernetes
configuration
for
each
cloud
enabling
us
to
set
various
flags,
the
app
deployment
helm
as
well
as
e
to
e
test,
and
then
hopefully,
working
as
as
much
as
possible,
with
upstream
projects
like
for
meekness
to
build
those
IDI
tests
and
then
like
containerize
them
the
dashboard.
So
we
were
referring
to
that
as
two
parts.
There's
the
status
repository.
That's
where
we're
saying
the
backend
API,
that's
elixir
and
Erlang
allows
us
to
have
high
performance
for
any
clients.
D
B
B
Okay.
So
what's
next
and
we're
in
the
midst
of
adding
support
for
onap
right
now-
and
this
is
they're
specifically
their
service
Orchestrator
and
we're
doing
an
integration
with
our
CI
systems
are
actually
using
their
build
artifacts
and
using
their
test
results
from
their
CI
system
to
update
on
the
build
status
patch
and
then
we'll
be
doing,
deploy
ease
of
those
artifacts
to
kubernetes
and
that's
in
progress
right
now.
B
The
Google
side,
just
real
quick
I
mentioned
earlier
increasing
some
quota,
run
that
for
the
account
that
we
have
right
now,
so
that
can
be
renamed
and
we
have
IBM
cloud.
The
bluemix
side
is
clipping
release.
We
that
should
be
brill
soon
and
then
opens
a
current
development
finishing
that
out.
Lundi.
F
B
B
Quick
market
that
y'all
can
see
on
some
of
those
things
we're
adding
we're
going
to
be
continuing
collaboration.
This
is
an
app
integration,
so
we're
working,
let's
shake
from
clarify
that
Chris
hides
from
open
sack
for
me.
Yes,
you
know
with
the
ETH
s
happy
to
be
doing
that,
and
we
have
some
other
demos
coming
up.
We're
going
to
be
doing.
D
D
B
D
B
D
A
E
E
E
E
B
E
B
B
Absolutely
is
there
any
other
from
yes,
anyone
else
on
the
Prometheus
same
questions
or
comments
on
the
end-to-end
test,
I
guess
more
general
into
em
tests
right
now,
we're
looking
at
ensuring
functionality
on
kubernetes
and
each
build
essentially
works.
I
think
we'll
need
to
look
more
into
the
performance
since
we
have
they
we're
doing
a
large
set,
but
we
can
look
at
that
how
that
would
fit
into
this
right
now.
We
want
to
make
sure
we
cover
all
the
functionality
or
yeah.
B
B
Sure
so
in
the
cross
cloud,
CI
org
are
y'all
able
to
see
my
screen
yeah
coming
up
just
spinning
primeira.
B
Clicking
on
cross
yeah
there
we
go
okay,
so
the
two
primary
parts
would
be
on
bills
and
on.
How
do
we
build
and
making
sure
that
builds
are
working?
Fine,
if
you
don't
have
an
artifact
so
that
you
can
provide
and
then
the
next
would
be
88's.
So
the
builds?
How
we're
building
Prometheus
is
in
a
Prometheus
configuration
repository
and
is.
D
B
Configuration
there
we
go:
ok,
I'm,
not
sure
why
the
zoom
screens
delay,
but
ok,
so
this
repository
here
it
has
the
information
for
doing
the
bills
and
for
running
gitlab
and
pulling
in
all
the
different
parts
that
we're
using
for
the
tests.
So
we
have
these
get
lab
CI
ml
files.
This
would
be
like
Travis,
CI
or
circle
CI,
anything
else
describing
how
to
build
the
different
parts.
B
So
this
would
be
one
area
if,
if
this
is
something
where
Prometheus
team
says
hey,
we
can
help
with
making
sure
that
it
builds
successfully
or
we
we
should
really
add
another
component.
So
this
will
be
one
area
and
then
the
other
area
would
be
the
actual
into
end
test
and
the
end
end
test.
What
we
try
to
do
is
we'll
take
an
upstream
test,
so
an
example
would
be
and
Denver,
if
you
have
any
thoughts
on
this,
speak
of
it
for
DNS
or
kubernetes.
B
It's
taking
a
lot
of
the
load
for
some
reason
on
my
internet
here,
but
core
DNS
has
some
test
functionality
under
here,
and
we
have
instructions
on
here's
how
we
can
run
the
specific
end-to-end
test.
A
kubernetes
has
into
end
tests
as
well
that
they
could
run
specifically
for
testing
the
pies
besides
the
full
conformance
test.
So
if
we're
doing
like
an
app
test
or
something
they
also
have
a
there's
cube
the
cube
DSS.
B
So,
if
we're
looking
on,
maybe
you
have
a
Prometheus
test
or
Eco,
or
maybe
you
say
we
want
to
put
it
inside
of
the
main,
prometheus
Prometheus
repo,
and
you
have
something
in
here
and
then
here's
how
we
would
run
those
specific
tests,
not
the
unit
tests
for
builds
but
actual
and
then
tests
that
are
doing
that
and
we've
sometimes
built
some
smoke
tests
that
will
run
for
a
project.
You
know
the
tests,
you
know
what
should
how
it
should
be
working
for
Prometheus.
So
we
we
don't
want
to
spend
a
whole
lot
of
time.
B
D
Yeah,
thank
you
well
Connor,
who
color
is
on
the
cold
and
he's
on
the
call
as
well,
and
he
started
working
on
some
n2
s.
End-To-End
tests
for
the
service
discovery.
So
maybe
this
will
be
a
good
test
run
to
see
if
this
can
be
added
to
the
tests
that
permit
use
us
I
think
he
wanted.
He
wanted
to
show
a
short
demo,
but
I'm
not
sure.
If
he's
he
had
time
to
prepare
it
for
today,
hey
hello,
yeah.
F
D
F
Sorry
I
got
back
from
Paris
last
night
like
to
my
yeah
yeah,
so
I've
been
working
on
and
I
stood
up,
a
Jenkins
server
dot
basically
set
up
for
these
service
discovery
tests
were
Prometheus,
so
I've
set
up
a
few
examples
like
what
ec2.
So
we
try
to
slave
out
there
on
ec2
and
see
if
Prometheus
service
discovery
is
working
with
that
for
a
P
or
that
comes
in
on
prometheus,
and
things
like
that
and
I
wasn't
actually
aware
to
be
honest
stuff.
F
The
CNC
I've
had
this
continuous
integration
set
up
so
I'm,
not
sure
if
it
is
worth
continuing
down.
The
road
I
was
genuine
book.
Maybe
some
of
those
tests,
I've
written,
could
be
integrated
with
what
you
guys
have,
because
we
are
laughing
service
discovery
tests
and
it's
an
area
we
want
to
cover.
Yeah
I
can
drop
links
in
yet
yeah
Jenkins
server,
the
fastest
into
the
job,
actually
might
be
a
Busey
yeah.
B
That
sounds
like
a
good
match
for
this
ticket
and
I'm
seven,
so
the
end-to-end
test
that
we're
trying
to
run
two
shows
just
by
the
results.
Four
scenes.
Yes,
it
seems
like
service
prometheus,
a
good
choice.
F
D
F
B
Exactly
what
we
want
to
do,
and
it
sounds
like
the
service,
every
test
will
work.
So
what
what
I
think
would
be
a
good
idea
is
to
if,
if
y'all
want
to
look
at
something
that
would
be
a
standard
way
of
where
you
could
put
it
in
increments
for
running
this
test
outside
of
the
system.
So
what
are
the
requirements
to
run
the
test?
What
are
you
expecting
and
then
the
instructions
for
running
this?
B
F
Yeah
I
can
definitely,
if
you
give
me
those
questions,
I
can
definitely
talk
about
system.
I,
guess
it
depends
on
each
test.
What
what's
required,
because
the
requirements
will
be
different
for,
say
your
chest
and
your
ec2
and
then,
if
your
testing
says
something
like
zookeeper
it'll
be
different
for
them:
yeah,
basically,
your
buff
suck
and
the
container
does
go
and
that
can
build
Prometheus
and
reach
out
to
those
services
for
them.
Yeah
I
can
like
write
up
for
more
details
or
a
documents
on
what
we
need.
D
B
Ok,
so
right
now
what
we're
targeting
is
and
what
you're
we're
seeing
with
Prometheus
here
and
I'll.
Just
go
back
to
that.
So
this
is
Prometheus
deployed
on
kubernetes,
which
is
so
right
here
we
have
kubernetes
a
cluster,
that's
running
on
AWS
and
then
Prometheus
was
deployed
on
to
kubernetes,
that's
on
AWS
and
that's
what
this
was.
So
we
actually
deployed
the
different
prometheus
components
into
the
kubernetes
cluster
they're
up
and
running,
and
then
we
will
run
the
end-to-end
test.
That's
actually
going
against
Prometheus
running
on
topics,
written
X,
I.