►
From YouTube: Kubernetes Community Meeting 20160204
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Summary --
CoreOS rkt + K8s Demo [Shaya Potter]
Ebay k8s on Openstack and Openstack on k8s [Ashwin Raveendran]
SIG Openstack
Launch SIG Cluster Ops
Testing update [Jeff, Joe, and Erick]
1.2 Release Watch
A
And
say
this:
is
a
public
and
recorded
a
community
meeting
for
Cooper
Nettie's
and
today
is
februari.
Fourth,
so
for
those
of
you
who
haven't
taken
a
peek
at
the
agenda,
yet
we
have
quite
a
few
things
on
here.
We
have
a
demo
from
core
OS
and
I.
Don't
know
if
the
core
OS
team
is
on
here.
Yet,
if
you
are,
can
you
guys
pipe
up
SIA.
C
A
A
So
we
will
have
the
rocket
demo.
We
also
have
a
assmann
from
ebay
who
is
joining
us.
Is
he
on
the
call
or
the
video
yeah
perfect
awesome,
so
you're
going
to
get
to
you,
get
to
tell
us
a
little
bit
about
what
eBay
is
doing
with
OpenStack
and
Cooper
Nettie's,
and
also
the
special
interest
group
around
OpenStack.
A
There
we
go.
Thank
you.
I
want
to
touch
on
the
code
of
conduct
and
the
potential
for
us
participating
in
the
google
Summer
of
Code.
Those
are
things
get
totally
bumped
to
next
week.
If
we
need
to,
we
do
have
some
of
the
testing
infrastructure
team
from
the
inside
Google,
here
Jeff,
Joe
and
Eric-
to
talk
about
this.
Sadly
they're,
not
on
cameras,
unless
they
also
avail.
We
do
have
a
cameras
over
there,
awesome,
ok
and
then
PFC,
Jeff,
Joe
and
Eric,
and
then
we
can
touch
on
the
1.2
release.
A
E
Yeah,
we
do
we're
really
excited
to
announce
that
as
I'm
about
an
hour
ago,
we
can't
rock
at
one
point
0,
which
is
a
really
important
milestone
for
us.
So
this
is,
you
know
what
we're
considering
like
on
disk
format
of
the
CLI
it
stable
and
we're
really
encouraging
people
to.
If
you
get
out,
try
rocket
or
run
in
production
and
we're
gonna
do
we're
going
to
provide.
E
Then
you
have
also
been
doing
a
little
work
on
integration
with
coop
attorneys
and
try
is
going
to
do
a
bit
of
a
demo
of
where
that's
at
it's
not
fight
at
a
finalized
stay
yet,
but
now
that
we've
sort
of
hit
this
big
pompano
milestone.
That's
something
we're
really
going
to
be
focused
on
over
the
next
couple
of
months,
and
so.
H
E
H
E
Yeah
we're
not
expecting
that
we're
going
to
reach
like
what
we
calling
so
we're
going
in
sort
of
rocket
Nettie's,
as
so
the
integration
of
the
two
projects
we're
not
expecting
reach
my
kind
of
a
rocket
Nettie's
one
point
O
with
the
given
x,
1.2.
Realistically,
that's
going
to
be
in
1.3
and
there's
still
a
few
issues
around
getting
the
two
integrated
so
yeah.
It
was
sort
of
looking
a
bit
kind
of
different
different
release.
Kids.
H
E
B
B
B
D
B
B
H
B
There's
no
there's
a
lot
and
shrunk,
but
there's
a
bunch
that's
still
in
sort
of
our
personal
for
public
branches,
but
that
has
not
been
integrated.
Integer
gift
like
we
like,
as
we
run
into
issues
we
fix
them
and
try
to
put
everything.
We're
doing,
is
against
trunk.
To
answer
your
question:
we're
just
some
of
its
not
merged
into
drunk.
Yet.
A
B
E
H
I'm
actually
asking
you
guys
leading
questions.
One
of
the
folks
on
my
team
has
been
working
with
quite
a
bit
and
we're
very
excited
about
it
and
I'm
sort
of
asking
questions
that
I
think
are
maybe
on
other
people's
minds,
but
yeah
we're
very
excited
about
this
and
then
Michael
Nelson
who's
on
my
team
has
been
doing
a
lot
of
work
with
us
and
comes
to
the
sig
note
regularly,
as
well.
So
good
job
guys
it's
exciting
to
see
if
progress.
E
M
I
can
help
answer
this
question
and
remain
most
of
helpful
issue
with
integration.
Racket
with
Cuban
ideas
is
the
state
of
weather
and
Athena's
and
I
think
the
deal
is
the
pis
is
merged
should
be,
should
be
merged
today
or
if
it's
not
math
light,
and
the
said
whether
there
have
some
remaining
issue
and
then
most
those
things.
We
need
to
understand
and
thumb
like
the
master,
node
issue
and
also
the
also
the
e2e
finir
test
issue.
That's
all,
but
all
the
feature
actually
para
que
it
is
we
pretty
much
everything
should
be
chicken.
M
Yeah,
yes
and
the
knocking
have
some
that
the
issue
we
need
to
figure
out.
What's
going
on
that's
character,
there's
that
has
to
be
Nate,
hitter
logging
actually
Daphne's
feel.
So
that's
why
we
try
to
you
but
shouldn't.
You
know
different
from
the
other
other
format
in
Agra
trustee
support
is
Pat.
Okay,.
L
A
A
Share
that
and
share
information
about
integrated
with
Cooper
Nettie's
or
how
we're
working
to
integrate
it
so
something
we
can.
We
as
a
community
can
do
as
well.
Alright,
a
next
thing
on
the
agenda.
Thank
you
guys
from
the
forest.
You
next
thing
on.
The
agenda
is
hearing
about
ebay
and
OpenStack
on
Cooper
Nettie's
versus
Cooper
Nettie's
on
OpenStack.
If
I,
remember
correctly,
you
guys
are
at
least
looking
at
both
at
the
moment,
and
one
is
one
you
are
doing
already.
I'll
just
go
ahead
and
hand
this
off
and
you
can
check.
F
A
E
F
So
so
one
of
the
things
we
want
to
try
to
manage
with
our
Cuban
Eddie's
cluster
is
the
control
plane
which
manages
OpenStack
itself
so
like
em
I'm,
the
part
of
the
cloud
engineering
group,
and
so
that
this
particular
problem
is
pretty
hard,
because
OpenStack
has
different
versions
like
'no,
which
comes
out
quite
frequently
and
Before
we
jump
in
and
like
song,
you
know
all
of
a
base
problem
using
Cuban
at
ease
without
liking.
It
may
be.
F
The
one
of
the
first
thing
which
we
want
to
address
is,
like
you
know,
solving
every
internal
problem
is
you
see
like
if
we
can
use
cube
to
solve
open
stack,
the
crates
of
the
OpenStack,
and
you
know
all
the
necessary
components?
I'm,
not
necessarily
the
part
of
the
OpenStack
group,
but
I.
Think,
like
you
know,
since
we
are
pitching
this
container
management
solution
using
Cuban
at
ease.
There's
a
lot
of
interest
in
seeing
like
how
our
existing
problems
can
be
solved
using
the
same
format
which
we
are
witch.
F
We
are
preaching
to
the
rest
of
the
organization
so
and
this
it's
actually
chicken
egg
situation,
because
right
now,
Cuban
ADIZ
is
using
OpenStack
as
the
cloud
provider
internally
to
get
the
compute
and
the
required
resources,
including
load
balancers,
and
you
know
some
basic
networking
and
things
like
that.
But
if
you
have
to
manage
that
those
control
plane
components
using
Cuban,
it
is,
you
know
how
effectively
we
can
manage.
So
that
is
where
there
is
like
two
aspects
of
it.
F
F
It
is
so
on
that
side
of
the
world
we
have,
you
know,
started
this
little
POC
at
our
end,
to
see
if
we
can
run
OpenStack
Cola
components
using
Cuban
readies
itself,
so
that
is
the
that
is
a
discussion
which
we,
which
we
are
having
with
the
OpenStack
community
and
in
a
few
folks
from
brand.
Isn't
red
hat,
and
you
know
us
so
he'll
see
more
me
is
coming
out
of
from
that
front
pretty
soon.
F
It's
not
we'll
manage.
For
example,
we
are
using
salt
and
the
related
orchestration
which
cube
has,
but
I
think
it
is
proving
to
be
a
challenge
to
keep
it
up
with
the
scale
we
want
to
go,
you
know
and
reach,
so
we
are
actually
trying
to
develop
a
solution
which
allows
declarative
management
of
the
cube
clusters
itself.
So
that
is
another
angle
we
are
looking
at
so
here
we
are.
We
had
few
meetings
with
cutin
and
others
to
see.
F
If
we
can,
you
know,
have
something
done
generically
in
the
community,
but
I
think
the
the
the
option
there
was
to
try
it
out
internally,
like
you
know,
or
on
a
using
a
third-party
resource,
or
you
know
our
own
private
objects
and
then
you
know
circle
back
when
there
is
some
some
sort
of
tangible
outcomes
from
that.
So
those
are
the
two
aspects
we
are
working
on
papers
peculiar
does.
A
I
A
Well,
you
can
always
have
an
opportunity
to
ask
at
the
sig
openstack
group
we're
with
the
egg
open
stacker.
That
group
is
meeting
on
Tuesday
afternoons
every
other
week
and
we
just
met
this
week,
so
it
will
be
two
weeks
for
the
next
one.
You
can
join
the
google
group
for
some
cougar
knit
ecig
OpenStack
and
that
will
get
you
added
to
the
invite
if
you
have
interest
in
either
following
the
conversation
or
participating
in
the
meeting
I
just.
G
Want
to
give
a
shout
out
here,
I
went
and
reorganized
the
the
wiki
page
for
the
cigs
to
try
and
create
a
little
bit
more
readable.
So,
as
you
guys
add
cigs,
you
know
please
fill
on
some
of
the
blanks
there
and
you
know
and
as
you
get
a
slack
channel
created,
you
have
to
actually
invite
the
slack
archive
bot
there
and
then
it'll
start
archiving
all
your
conversations
that
has
to
be
done
once
yep.
A
A
Whole
thing,
but
thank
you
for
the
update
that
you
did
do
you
took
a
google
doc
that
I
had
created
just
to
try
and
keep
my
own
sanity
and
turned
it
into
a
useful,
wiki
artifact,
which
of
course
we
want
to
do
more
of
so.
Thank
you,
alright.
So
next
up
since
I
did
my
little
plug
for
the
sig
OpenStack.
Are
you
gay
Rob
to
talk
about
what
is
currently
being
bounced
between
stickups
and
cig,
deploy.
I
I'd
be
happy
to
shoe
voice,
oh
I'm,
so
rhyme
with
racking
and
we're
working
on
a
couple
of
different,
really
one
approach
to
standardize
operations
around
Cooper,
Nettie's,
ops
and
I
have
a
lot
of
experience
from
OpenStack.
You
all
might
know
my
OpenStack
pedigree,
where
I
was
really
involved
in
interoperability
in
ops
and
helping
people.
Thank
you
for
taking
notes
for
me
for
ops
and
so
thought
it
was
appropriate
to
try
and
build
a
cig.
I
Originally,
that
said,
sig
deployment
for
Cooper
Nettie's,
where
we
could
talk
about
what
deployments
were
and
I
took
down
for
last
week
to
talk
about
this
week's
put
together
a
draft
charter
for
that
it
and
it's
before
I
jump
to
the
Charter.
How
much
time
do
you
want
me
to
Spencer,
because
I
could
just
basically
announced
and
then
we'll
have
a
meeting
and
talk
about
it.
I
think.
A
C
I
So
I
put
together
a
charter
with
the
idea
of
looking
backwards
on
some
of
the
things
that
that
drove
OpenStack
into
less
operability
and
interoperability
challenges,
and
so
the
I
it.
Please
look
at
the
Charter
and
look
at
it
from
the
perspective
of
how
do
we
want
to
start
this
conversation?
It's
really
hard
to
go
back
and
reach
harder
things.
I
The
goal
here
is
to
really
collect
a
group
of
people
who
want
to
operate
Cooper
Nettie's
in
a
scalable,
secure,
repeatable
way
right
and
what
I've
learned.
It's
really
important
to
be
able
to
give
those
beck
group
of
voice
so
that
they
can.
You
can
go
to
one
place
in
sorry:
let's
pull
the
operators
and
see
what
they
want
to
do.
I
Let's
build
a
reference
architecture
and
collect
those
things,
so
the
Charter
is
about
establishing
that
as
a
baseline
I,
don't
want
to
spend
a
lot
of
time
building
a
charter
but
I
think
it's
important
to
start
that
and
then
pull
in
the
things
that
we've
been
working
on
already.
I
know
there
were
some
people
in
google
who
drafted
a
document
about
goals
and
objectives
for
what
a
deployment
should
be.
You
know
we
have,
we've
certainly
been
doing
some
work
and
have
opinions
their
salt
there's
at
least
two
workable
ansible
playbooks
at
all.
That's
great
yeah!
I
That's
how
things
get
set
up
to
an
extent.
We
need
to
agree
on
what
you
know
how
we're
going
to
do
it,
make
it
work.
So
that's
what
the
Charter
is
about.
I
haven't
set
a
time
yet
for
the
deployment
to
kick
things
off,
I'd,
probably
do
it
weekly
and
then,
if
we
get
some
some
motion,
then
we'll
will
slow
things
down
if
it's
necessary
and
I
expect.
My
expectation
is
that
we'd
actually
want
to
ultimate
going
to
have
face-to-face
meetings
or
meet
ups
or
things
like
that.
A
I
will
get
you
set
up
with
a
group
and
select
channel
and
all
of
that
and
I'll
finish,
setting
up
the
open
sex
like
channel
today,
yeah,
so
that
should
get
us
started
and
I.
Think
that,
because
naming
is
hard,
do
we
want
to
call
it
sig
off
sourcing
deploy
because
that
will
gave
cradle
groups
and
deployment
was
confusing,
because
six
config
is
handling
a
lot
of
the
app
deployment
stuff
yeah.
L
L
I
To
keep
the
Charter
discussion
going
but
dive
in
to
meet
pretty
quickly.
So
when
I,
when
we
put
together
the
sig
meetings,
we
will
we
will
time
box
charter
discussions
with
meet
discussions.
I've
done
that
done
way
too
much
of
this,
and
so
will
you
know
we'll
let
this
charter
be
via
a
long
roll.
Please
do
not
be
afraid
to
join
in.
If
you
have
specific
ops
things
we're
going
to
discuss
those
immediately.
I
don't
want
to
do
delays.
We
have
enough
ops
discussions
about
cluster
ops,
I,
like
cluster
ops.
C
C
A
Welcome
thank
you,
rob
and
thank
you
for
doing
the
note
taking
this
week
again.
So,
let's
talk
testing
now,
since
you
guys
I
suspect,
will
be
the
meat
of
the
discussion
today.
So
maybe
introductions
first
and
then
we
can.
You
had
some
things
Eric
that
you
were
going
to
have
done
specifically
and
then
we
can
open
up
some
questions.
Yeah.
N
N
Tuesday
and
early,
please
come
to
that
and
a
snob
of
the
puffy
fact
that
we
have
gotten
from
those
I
think
they're.
A
few
nokomis
fear
about
one
is
talking
about
for
making
it
easier
to
understand.
When
I
am,
you
know,
trying
to
commit
a
change
in
corona
use
like
what
is
a
republic
used
to
have
when
with
esteem,
where's,
Carruth,
clean
and
so
Jeff
work
documents
to
make
that
process
here
to
understand.
I've
also
gone
back
that
there's
not
a
clear
it.
This
way
to
run
tests
without
mom.
N
You
know
hacking
up
a
bunch
of
shell
scripts
to
trying
to
pretend
let
you
are
agent
assistance
and
we
much
to
make
that
be
better
process,
and
then
no
we've
also
been
trying
to
spend
a
lot
of
efforts.
Absolutely
getting
beat
me
easier
to
urge
consistently.
We've
had
a
lot
of
issues
with
test
leaking
on
it.
So
we
are,
you
know
one
latina
generals
going
to
use
the
place.
Then
we
are
going
to
work
basically
easier
to
detect
what
it's
like
him
and
get
into
a
better
state
about
that.
O
If
you've
done
any
committing
to
Cooper,
nettings
or
maple
request,
and
probably
be
his
first
time,
you're-
probably
going
to
get
a
little
bit
confused
by
all
the
box,
spamming
things
on
ER
what
goes
on
here?
How
does
how
does
it
actually
get
for
up?
How
do
you
actually
get
from
the
bull
request
to
nothing?
It's
though
save
I
can
screen
share
the
green
button
at
the
bottom.
In
the.
A
C
O
All
right,
so
we
have
it.
We
actually
had
in
the
developer
Docs
a
while
ago,
but
document
about
PR
west
and
what
that
life
cycle
looks
like
that's
it
improve,
or
that
is
being
what
so.
You
can
actually
see
like
what
goes
on
like
what
the
end,
what
the
actual
steps
are
and
what
the
different
robots
are
doing.
N
Can
keep
let's
see
so
another
interesting
thing
is
on.
We
don't
have
anything
to
show
for
the
making
it
easier
to
run
tests
yet,
but
the
basic
principle
is
that
we
want
there
to
be
a
consistent,
clear
way
to
run
a
single
test
or
on
all
the
tests
in
a
job
or
on
you
know
the
same
job
opportunity
and
to
have
the
fergie
more
right
now
in
our
e.t.b
scripts.
N
There's
a
bunch
of
you
know
tight
tight
colleagues
with
chickens
and
we
sort
of
want
to
do
couple
that
so
that,
if
you
are
not
chickens,
there's
a
clear
way
to
do
specify
like
I
just
want
to
run.
You
know
all
the
tests
of
this
sweet
and
how
that
works
well,
and
so
these
are
working
on
figuring
out
if
you
just
need
to
make
for
that,
and
I
will
extend
testing
thick.
N
So
if
you
have,
you
know
sponsor
opinion
on
I
know,
some
people
have
our
theory
on
us
interesting
little
script,
baby
sort
of
put
in
all
the
necessary
environment
variables
to
pretend
that
you're
vikans
on.
Oh,
not,
you
know
this
fairly
good
to
go,
but
but
yes,
we
would
the
appreciate
feedback
there
I'm,
starting
that
we're
trying
to
spend.
O
O
A
N
At
disability
to
what
tests
are
actually
having
problems
or
not
it's
a
bogus
missed
evening.
Are
you
know
whoever
trying
to
figure
out
the
best
late
again
available
to
you
guys,
as
opposed
to
our
personal
losses
on
so
pack?
Is
that
is
coming
less
urges
want
to
show
you
something?
That's
a
joke.
I've
been
working
on,
and,
and
yes,
this
or
just
you
know,
I
hit
you
in
a
sweet
little
boost.
N
All
the
tests
today
well
show
know
what
is
create,
was
not
running
and
and
can
toggle
something
that's
failing
all
the
time
or
two
you
know,
is
it
being
run
for
various
concerns
or
is
blinky?
This
is
a
quick
summary
of
going
on
like
this
to
be
available
to
people,
so
you
can
foresee
like
if
there
is
a
test,
its
failing
is
that,
as
you
know,
is
it.
H
N
Voters
basically
trying
to
get
all
of
our
test
results
and
historical
test
results
into
a
grid
so
like
we
can
see
if
something
is
flaky
and
of
this,
you
know
filter
down
to
specific
tests
that
I
am
interested
in
an
essentially
you
know.
Each
job
is
going
to
be
a
tab
up
on
the
top
and
then
the
various
results
and
their
historical
things
will
show
up
there
and
think
examples
is
a
exciting,
sometimes.
H
N
N
Yeah,
so
yes,
sir,
the
three
parts
is
one:
you
know
just
getting
a
UI
that
I
think
is
useful
for
people
to
consume.
The
second
thing
would
be
to
make
it
so
that
you
know
you
guys
who
are
outside
of
Google
can
view
all
this
data,
which
is
obviously
super
important,
and
another
important
thing
is
to
make
it
so
that
you
know
anyone
who
is
contributing
me.
Full
test
runs
and
I
pray
that
they
can
export
that
to
us
in
a
way
you're
sort
of
doing
we
were
they
bring
all
this.
N
N
On
so
we're
working
in
so
that,
like
the
test
grid,
so
this
one
here
that
I
assume
you
can
see
the
screen
the
the
summary
on
this
probably
is
just
an
HTML
page.
So
that
will
probably
be
you
know,
order
you
know
days
or
weeks
and
then
the
this
is
sort
of
a
more
complicated
app
and
so
there's
a
another
team
inside
of
Google.
That's
sort
of
working
on
this,
and
we
use
this
for
a
lot
of
our
internal
projects
and
so
there's
sort
of
a
bunch
of
it's.
Not.
N
It
wasn't
originally
designed
to
be
external,
and
so
we
are
working
with
that
team
to
try
and
figure
out
the
most
efficient
way
to
sort
of
you
know,
make
it
usable
and
not
have
a
bunch
of
pointless
links
that
you
know
assumptions
about
what
we
are
using
to
track
issues
or
Paul.
You
know
how
we
store
test
data,
there's
still
decoupling
like
after
the
apartment,
yeah.
H
This
is
the
sort
of
thing
that
I
would
really
love
to
see,
show
up
on
the
priority
list
for
release
13
and
actually
be
a
blocker
for
release,
1
3,
so
something
stuff
like
this
is
not
actually
done.
The
release
doesn't
ship
we
and-
and
so
this
is
I-
think
very
you
know
very
typical
of
the
kinds
of
things
that
need
to
be
prioritized
in
terms
of
the
overall
project
and
treated
as
blockers.
Not
in
that
sense,
so
this
is
really
great
stuff.
Glad
to
see
it
I'm.
A
H
Oh,
this
is
such
a
long.
This
is
such
a
long
topic
and
I
think
you
were
on.
You
were
on
the
six
the
Essex
scale
meeting
this
morning
and
I
mean
most
of
the
meeting
was
taken
up
by
us
discussing
like
what's
the
conformance
test.
How
do
we
know
whether
the
cluster
is
actually
working
lots
of
stuff
about
lots
of
issues
around
like
deploy,
flakes
versus
non
flakes
performance,
regressions
and
there's
an
awful
lot
here,
rather
than
try
to
wing
it
here?
H
I
think
I
would
like
to
try
to
create
some
kind
of
document
which
is
like
a
point
of
view
and
try
to
get
some
feedback
feedback
from
some
folks
on
this,
so
but
I
mean
I.
Think
getting
this
kind
of
this
kind
of
exposure
and
better
tooling
around
this
kind
of
thing
is
going
to
do
nothing
but
help
going
forward,
which
is
why
I
really
really
want
to
see
this
kind
of
tooling
make
it
on
to
the
like
top
10
feature
list
for
13
or
I
mean
there's,
probably
some
other
things
as
well
I.
H
I
think
I
have
a
kind
of
related
question
and
we're
seeing
maybe
we're
seeing
the
tip
of
the
iceberg,
but
it's
very
hard
to
tell
I
think
it's
been
it's
kind
of
a
known
thing
in
the
community
that
when
Google
puts
the
release
tag
on
a
release,
but
that
means
and
they've
deployed
it
into
gke
that
there's
belief
that
that's
a
that's
a
much
better
quality
bar
and
I.
Think
there's
also
some
ministry
about
additional
testing
and
QA
things.
H
A
Time
I
asked
about
that.
They
had
converge
to
a
single
set
of
tests
and
we
were
going
to
not
have.
We
were
going
to
move
the
release
release
label
when
we
actually
cut
a
release,
as
opposed
to
waiting
until
that
rolled
in
DGK,
which
was
its
original
use
case
some
time
in
eons
ago.
You
know
last
year
I'm.
H
A
P
Projects
is
specifically
implementation
of
Coober
Nettie's,
ng
ke,
that
we're
validating
that's
working
in
the
g
environment.
But
the
goal
is
at
the
Cougar
Nettie's
test
tests
that
are
in
the
open
source
that
are
run
as
part
of
the
video
/
source,
Cooper
Nettie's
validation
that
they
are
complete
and
and
give
everybody
the
confidence
that
fee
product
is
component
and
stable.
So.
O
O
H
You
know
showing
me
problems,
Cooper
Nettie's
problems
deploying
on
AWS,
so
it
may
be
that
that's
kind
of
the
a
little
bit
of
the
disconnect
between
the
email.
I
was
sending
and
I'll
say
the
perspective
of
the
Google
team
on
stability,
certainly
I
think
in
terms
of
performance,
regressions
and
performance
issues.
I
think
that
the
state
is
considerably
more
complex,
but
I
don't
know
perhaps
I've
said
I'll
set
enough
for
today.
Thank
thanks
for
the
opening,
though
Sarah
yeah.
A
A
N
I
mean
you
know.
Definitely
if
there
are,
you
know
if
anyone
is
running
continuous
testing
or
is
interested
in
running
continuous
testing
and
you
know
wants
to
like
definitely
the
ideal
goal
right
would
get
to
a
state
where
you
know
we
are
doing
testing
on
a
bunch
of
different
platforms,
and
then
we
have
a
great
way
to
could
you
know
collate
all
that
data
so
like
it
I
think
it's
more
yeah.
N
P
Q
Q
But
I
think
if
we
can
at
least
see
like
publicly
accessible
historical
results
of
the
AWS
performance
testing
and
then
start
to
see
that
flesh
out
for
other
providers
as
we
go
down,
the
line
that'll
really
help
people
sort
of
sanity
check.
Like
is
this
a
known
issue
on
my
platform.
Did
I
deploy
my
thing
incorrectly,
or
is
this
the
software
not
working
correctly
right.
M
Okay
I
to
something
here
here:
this
is
dong
from
google
and
actually
the
nola
team.
We
try
to
either
note
the
line
were
confirmed
highest,
and
so
this
is
not
a
cover
next
AWS,
as
the
cloud
provider
or
other
car
either.
If
you,
but
at
least
the
color,
I
will
earlier
mentioned
something
like
the
different
OSD
straw
and
a
different
kernel
and
know
the
config
configurations.
So
we
also
asked
the
huawei
folks
and
helped
you
provide
the
content
now
runtime
level
of
the
validation
test.
M
So
all
those
kind
of
together
will
be
as
the
package
they'll
confirm
test.
So
you
could
read
eventually
the
situation,
but
it's
not
completely
done
yet.
Eventually,
you
can
run
those
know.
The
level
confirm
ties
to
learn
against
you
note,
and
the
figure
out
is
maybe
is
your
configuration
issue
or
it
the
colonel
config
issue
or
other
configuration
issues.
So
hopefully
we
can
get
there
eventually.
H
Where
we're
having
these
kinds
of
issues
and
I
I,
think
I
mean
we
will
try
to
work
on
this
as
well.
But
I
think
this
is
another
one
of
those
things
where
contributing
the
quality
and
testing
for
the
community
is
not
just
like
going
in
writing
test
cases.
It's
helping
out
on
some
of
these
systemic
things
that
will
make
aight
I'll,
say.
The
total
life
cycle
of
tests
have
a
problem
record
over
the
ticket,
have
great
information
in
the
ticket
that
helps
everybody.
Help
with
that
problem
is
really
part
of
part
of
the
mission
here.
H
A
A
C
C
A
A
That
is
things
that
might
make
1.2
at
this
point,
we're
getting
pretty
close
to
be
won't
meet
1.2
if
it
hasn't
been
committed
committed
in
defense
of
the
call
request
and
such,
but
but
that
is
another
list
that
you
could
take
a
peek
at.
So
we're
still
targeting
last
I
heard
a
march
seven
for
a
release
date.
C
Q
Q
A
A
A
I
will
start
with
the
one
the
cooper
Nettie's
already
has
and
see
what
that
what
that
looks
like
and
if
that's
enough
for
us
to
just
pitch
it
up
to
the
cloud
native
compute
foundation,
so
that's
super
straightforward,
then
google,
Summer
of
Code
I'm,
going
to
punt
that
to
next
week,
if
we'd
like
to
participate
in
it,
we
need
to
get
mentors
so
think
about
that.
Over
the
next
week
we
need
to
have
people
commit
to
being
mentors
for
our
students
all
right.
Any
other
questions
in
our
last
four
minutes.
A
Doesn't
sound
like
it
well
then
have
a
great
week.
I
will
see
you
all
online
next
week.
I
will
post
the
video
of
this
community
meeting
today
and
then
the
notes
will
go
up
early
next
week
on
the
Cooper
Nettie's
blog.
If
you
want
to
share
the
Cooper
Nettie's
community,
chats
video,
a
playlist
with
people
feel
free.
That's
out
there,
it's
public,
it's
not
the
most
efficient
way
to
consume
these
events
other
than
participating,
but
it
is
certainly
available
if
somebody
wants
to
go
figure
out
what
we
said
during
this
chunk
of
conversation.