►
From YouTube: CNCF CI Working Group - 2018-01-23
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.
C
B
All
right
1005,
we
can
get
started.
My
name
is
Lou
Cena,
stricka--
and
I've
been
doing
project
management
for
the
seei
working
group
and
the
cross
cloud.
Ci
team
I've
posted
the
meeting
agenda
and
notes
for
this
call
and
said
the
chats
and
also
a
copy
of
today's
slide
presentation
has
been
shared
in
the
chat
window
as
well.
I'll
pass
it
over
to
Taylor.
If
you'd
like
to
introduce
yourself
and
then
we
can
popcorn
introduce
everyone
on
the
call
and
get
started.
E
This
is
the
first
time
I'm
attending
this
bug.
Group
and
I
just
want
to
get
myself
updated
with
this
group.
Basically,
we
have
awesome
projects
who
use
CI,
which
is
more
or
less
based
on
kubernetes
testing
for
our
tools.
So
we
are
looking
for
some
alternatives
in
that
direction.
I
just
want
to
get
updated
myself
with
the
C&C
of
CI
working
good.
A
Dan,
your
audio
was
a
little
cut
out.
As
you
came
in
I
couldn't
quite
hear,
everything
is.
Was
there
something?
No
I
was
something.
A
Happy
to
have
anyone
joined
that
once
listen
and
participate
to
see
what's
going
on
also,
if
anyone
has
something
they
would
like
to
talk
about
a
topic
specifically
the
CI
working
group.
There's
a
shared
document
with
agenda
notes
so
feel
free
to
add
anything
on
here,
maybe
even
for
the
next
time
when
we
prepare
that
and
happy
to
have
you
join
in
on
that
otherwise
I'm
participating
on
some
of
the
things
that
we're
working
on
on
the
cross
cloud.
Ci
team,
so
I'll
jump
right
into
that.
D
D
D
E
A
A
Okay,
so
this
is
the
current
team,
Mike
Ross
cloud,
CI
development,
doing
development
so
Denver,
who
some
of
y'all
have
maybe
met
previously
Watson
has
been
doing
API
development
and
some
front-end
development
josh
is
doing
front-end,
dev
and
then
Lucena.
B
A
Myself
he's
not
down,
so
this
is
current
team
and
the
meeting
notes
I
had
talked
about
before
those
are
linked
off
of
the
CI
working
group,
github
page
so
cents.
Last
and
last
meeting
we
have
had
a
couple
of
demos
and
meetings
with
some
folks.
Camille
we
went
through
the
current
status.
Hadn't
had
an
update
with
her
and
nearly
a
year.
It
seems
like
it's
been
quite
a
while,
so
that
was
good
to
catch
up
with
her
we're
going
to
be
following
up
to
get
more
of
her
feedback
Lucas.
A
We
had
a
meeting
last
week
talking
about
cube
Edmond
and
how
a
DM,
how
we
could
add
that
in
as
a
potential
plugin
for
are
doing
kubernetes
provisioning.
We,
the
system
now
has
it
uses
custom
provisioning
on
all
the
clouds.
So
we
had
some
feedback
on
where
you
cube.
Atm
is
right
now
what
type
of
support
and
then
some
directions
that
are
going.
A
We
also
received
a
bunch
of
I
guess
more
detailed
specifications
and
what
would
you
look
into
to
see
if
it's
going
to
work
right
now
or
if
we
need
to
have
some
further
conversations?
So
that's
on
our
list
and
then
we'll
be
having
some
follow-up
conversations
with
Lukas
on
the
cross
cloud.
Software
stack
itself
from
the
CI
system.
The
pipeline
we've
as
we've
been
increasing
and
moving
towards
the
production
release
at
the
system
we've
been
working
through.
A
It's
started
getting
really
rapid
on
resource
usage,
so
we
actually
had
to
reach
out
to
the
cloud
providers,
get
a
bunch
of
that
increased
as
we're
pushing
through
all
of
the
different
environments
and
testing
and
seeing
that
that'll
Pinal
us.
Some
conversation
stand
with
some
of
the
folks
like
for
the
IBM
and
bluemix
stuff,
that
you're
aware
linker,
D
and
there's
as
we're
refactoring
to
work
with
the
new
system,
as
is
flit
out
and
fixing
some
issues
on
some
of
the
existing
projects.
A
We've
had
some
items
for
upstream
changes
like
core
DNS
and
there
was
I
guess
it
was
right
at
the
end
of
the
last
on
the
edge
of
the
last
meeting,
and
there
was
extra
kubernetes,
it
was
six
as
well
and
and
then
on
packet.
There
was
what
there's
been
limitations
with
resolving
resolution
on
the
clusters,
because
a
packet
doesn't
provide
any
type
of
dns
service
or
anything
else
internally.
A
The
part
of
the
3m
scheduling
is
the
client
for
triggering
and
controlling
the
backend
CI
system
and
handling
stuff
like
when
is
the
new
kubernetes
masterbuilt
done
and
complete
and
ready
to
provision
and
then
run
through
and
collect
all
the
status
and
stuff.
So
this
is
part
of
that,
so
that
your
client
for
doing
all
those
pieces
and
and
then
the
next
step
I'll
get
to
in
a
minute
on
the
3m
integration
tests,
we've
been
doing
a
lot
of
integration
tests
across
the
whole
system.
A
A
So
one
of
the
items
that
we
ran
into
was
with
when
you're
doing
a
lot
of
deploys,
app,
deploys
and
then
running
tests
on
top
of
each
other
and
that
the
state
of
the
dashboard
so
working
through
those
sort
of
things-
and
this
is
really
going
to
be
affected
more
when
we
start
increasing
the
number
of
times
the
dashboard
is
updated.
But
seeing
this
and
let's
see
so
then
we
get
to
in
progress
effluent
D
is
was
a
little
bit
higher
on
the
priority
list.
A
Previously
it's
been
lower,
but
it
was
partially
done
and
last
year
the
builds
were
working.
So
the
remaining
items
there's
a
couple
of
remaining
items
to
test,
but
the
big
thing
was
refactoring
it
to
support
the
new
after
place.
That's
been
completed
and
it's
ready
to
test
so
we'll
be
finishing
that
out
and
it'll
be
coming
in
the
next
couple
of
weeks
or
so
the
the
last
some
of
the
last
items
for
every
100
or
the
running
the
scheduled
job.
This
is
what
runs
at
3
a.m.
A
and
every
day
to
do,
builds
for
all
the
active
projects
through
provisioning
and
to
all
of
the
active
clouds
with
the
latest
stable
and
head
of
kubernetes
so
will
be.
This
will
be
using
the
new
trigger
client
and
stepping
through
and
running
for
each
of
the
pieces,
and
then
one
thing
that
we
need
to
update
and
work
on
is
the
related
to
all.
A
So
this
has
a
lot
of
the
parts
that
are
allow
us
to
do
an
integration
with
other
groups
like
own
app
for
the
build
system
itself,
and
it's
working
internally,
so
it'll
be
public
on
that,
and
then
we
can
start
working
with
other
folks
to
take
advantage
of
those
parts.
The
backend
API
system
integrates
that
and
then
the
projects
and
classes
up
planning
to
have
for
that
launch.
A
So
coming
in
the
future,
so
we
have
we're
going
to
we're
planning
on
being
that
cube
con
and
we
have
an
intro
that
we
are
would
like
to
do.
That's
pretty
close
to
what
we've
done
in
the
past
a
little
bit
of
updates
with
what's
production,
launch
the
deep
dive,
we're
hoping
to
focus
more
on
working
with
with
projects
as
far
as
integration
and
and
then
start
getting
feedback.
A
The
get
outside
we've
done
some
review
on
that
we're
trying
to
write
something
out
on
how
we're
actually
already
using
some
of
the
processes
and
and
ideas
that
are
being
talked
about
from
get-ups
and
we'd
love
to
talk
more
about
that,
and
then
it
would
be
nice
to
get
a
I
think
one
of
the
requests
is
and
to
have
someone
from
that
end
talk
as
well.
So,
let's
see
we
have
quite
a
few
other
demos
we
need
to
catch
up
with
on
the
storage
working
group.
A
The
packet
plus
arm
was
deferred,
so
try
to
follow
back
up
with
Ed
and
see
if
he's
available
yet
and
then,
as
I
mentioned,
OpenStack
will
be
falling
back
up
with
Chris
hi.
Once
we
retarget
integrating
the
code
that
he
wrote
so
he
wrote
most
of
the
OpenStack
provisioning
code
and
and
essentially
we
need
to
update
it
and
pull
it
into
the
new
release
and
then
we'll
follow
up
the
time.
C
A
He
could
I
think
most
of
it
was
pretty
close,
and
so
we
were
going
to
go
through
and
see.
I
think
it
would
be
as
if
there's
a
anything
major,
then
maybe
we
push
that
back
to
him.
It
could
be
pretty
minor.
We
merged
his
code
into
a
branch
that
was
pretty
close
to
the
current,
so
Denver
and
I
were
going
to
dig
through
that
and
see
if
it's
pretty
short
to
update
and
then
deploy.
If
it
is,
then
we'll
do
it.
If
not,
then
we'll
push
back
to
dress
and
allow
them
to
retarget.
A
Think
that
we
should
base
through
and
getting
all
the
I
guess,
the
production
bike
fixes
and
everything
else
that
we've
been
working
on
last
couple
of
weeks
this
week,
so
I
think
will
be
up
and
ready
by
end
of
week
as
far
as
those
parts
and
probably
want
to
check
in
and
you'll
we'll
have
it
running
at
3m
like
actually
by
tomorrow,
we'll
be
running
going
through
and
saying
what?
What's,
the
results
with
the
results.