►
From YouTube: Kubernetes SIG Service Catalog 20161215
Description
SIG service catalog discusses plan for release milestones
Agenda - https://docs.google.com/document/d/10VsJjstYfnqeQKCgXGgI43kQWnWFSx8JTH7wFh8CmPA/edit
A
All
right,
can
you
all
see
my
screen
yep,
alright.
So,
as
has
been
previously
discussed
in
sig
meetings,
the
sig
is
going
to
make
an
official
CFP
response
for
q
con
EU,
which
is
in
Berlin
on
the
twenty-ninth
and
30th
of
2017,
and
part
of
that
CFP
response
includes
a
demo,
and
so
it
would
be
really
nice
if
we
were
accepted
that
we
actually
had
something
to
demo.
A
So,
let's
I'm
going
to
put
the
cart
before
the
horse
here
a
little
bit
and
we'll
talk
about
what
we
want
to
be
able
to
show,
and
since
I
would
really
prefer
not
to
have
this
land
on
a
march
27th,
let's
say
or
28th.
We
need
some
time
to
allow
for
shake
down.
Some
time
to
allow
for
slip,
I
think
that
some
of
you
in
the
audience
may
be
familiar
with
the
concept
of
things
not
being
done
when
you
plan
for
them
to
be,
and
so
we're
going
to
give
ourselves
a
little
safety
room.
A
So
the
tentative
target
date
that
I
just
us
with
the
sig,
leads
that
we'd
like
to
be
in
this
MVP
one
state
by
is
march
first
of
2017,
and
the
content
of
that
is
pretty
much
the
barest
skeleton
of
an
MVP
like
thing
that
has
the
right
architecture.
So,
let's
talk
about
functional
requirements
for
this.
A
A
If
people
are
familiar
with
that,
it
is
a
going
API
client
that
provides
a
an
interface
in
terms
of
the
go
API
types
that
hits
the
rest
interface.
There
is
infrastructure
already
to
to
generate
this
thing
and
we
want
to
be
able
to
use
that
to
generate
our
own
client.
Third
is
there
should
be
a
native
Pernetti
style,
CLI
experience,
so
what
that
means
is.
We
should
have
a
cube
CPL
like
thing
that
you
can
do
cube
or
but
I
think
Brennan.
You
called
a
catalog
CTL.
A
It's
called
that
for
now
in
this
meeting,
khattak
catalog
CTL
get
brokers
and
you
get
a
formatted
list
of
brokers.
You
can
do
described
on
one
of
these
resources
list
and
describe
on
these
resources
and
get
formatted
output
and
then
integration
with
the
open
service
broker.
Api,
you
should
be
able
to
add
a
broker.
A
Yet,
and
going
back
to
the
barest
skeleton
of
MVP
I
think
just
getting
a
secret
is
in
keeping
with
that
with
that
mindset,
so
the
high
level
architectural
requirements
to
go
along
with
this
is
that
we
have
moved
off
third-party
resource
and
fully
on
to
service
catalog
V
1
alpha
1
API.
We
have
code
generators
in
place
for
deep
copy
defaults,
conversions,
yellow
parsers
in
the
API
client.
The
controller
or
controllers
is
the
case
may
be
by
the
time
we
actually
build
this
stuff
use
the
Cooper
Nettie's
controller
infrastructure,
meaning
the
the
list.
A
Watchers
informers
generic
controller
and
the
CLI
interface
is
implemented
as
something
that
vendors
in
the
guts
of
cube
CTL,
but
adds
Lister's
and
describers
for
the
API
resources.
I
will
talk
a
little
bit
about
a
future
things
with
CLI,
but
I
want
to
know.
If
there
are
any
questions
about
this
before
we
continue
I.
B
A
That's
a
really
good
question
off
the
top
of
my
head.
I
would
say
that,
like
the
one
of
the
brokers
that
is
currently
in
the
incubator,
repo
might
be
a
good
candidate,
but
I
think
that
is
something
that
bears
some
consideration
by
the
group.
You
know,
especially
in
light
of
the
fact
that
we
plan
to
have
a
demo
of
the
stuff.
We
need
to
have
a
broker
to
demo
right.
B
A
C
Yes,
I
would,
I
would
probably
nominate
the
s3
broker
in
the
cloud
foundry
samples,
repo
we've
used,
that
with
pretty
good
success,
and
I
will
primary
reason
I'd
vote
for
this.
Is
it
doesn't
have
it's
not
a
sink
and
it
doesn't
have
a
long
lag
time
between
synchronous
provision
and
by
end
calls
okay.
Well,
that's
demo,
I'm,
not
suggesting
that's
like
the
official
MVP
one
support,
but.
C
D
D
A
B
A
B
A
So
I
agree,
unshaded
I
think
should
and
will
are
dramatically
different
things
in
terms
of
messaging
and
expectation
creation.
So
I
would
like
to
have
a
more
detailed
discussion
about
the
degree
to
which
we
expect
interoperability.
I
completely
agree
that
it
is
a
it
is
a
goal
and
the
as
as
Aaron
was
just
suggesting
we
seem
like.
We
are
not
were
considering
strongly
using
a
cloud
foundry
brooker
as
part
of
the
demo.
B
B
E
A
I'm
hearing
a
no
so,
let's
see
to
get
there,
we
have
another
milestone
that
we've
just
discussed
called
Legos
one,
and
it
is
the
first
couple
functionals
where
distinction
between
functional
and
architecture
is
not
made
in
a
first-class
way,
because
we
finished
assembling
this
right
before
the
sig
meeting
started.
So
the
requirements
there
are
Service
Catalog,
V,
1,
alpha
1
API
is
complete
and
functional
a
broker
service
class
instance.
Binding
integration
should
be
possible
with
the
rest.
Api
and
api
server
serves
this
to
enable
one
to
item
on
this
list
and
then
generated
going
client.
D
Well,
so
this
is
great,
but
it
leaves
all
of
the
logistics
as
an
exercise
to
the
user.
I
think
this
is
a
good
first
step,
I'm
interested
now
in
like
how
we
get
in
February
one
and
who's
doing
what
and
how
we
can
start
breaking
out
the
work
items
and
parallelizing
and
all
that
magical
stuff.
That
makes
for
a
good
success.
Yeah.
D
A
A
Sweet,
so
that
really
was
all
that
we
had
had
on
the
agenda
for
today.
I
personally
am
extremely
over
scheduled
have
quite
a
bit
of
stuff
to
get
done
before
the
end
of
the
week.
So
if
there
are
no
discussion,
topics
related
to
this
I'd
like
to
adjourn
the
meeting,
and
perhaps
we
can,
we
can
talk
amongst
the
leads
a
little
bit
more
on
some
of
the
details
on
this
everybody.
Okay,
with
that
I.
B
Hey
I
won't
mind.
Ending
early
I
did
have
one
comment
to
make
to
the
group
just
to
get
their
owns
pulse
on
the
matter.
Okay
want
to
have
any
user
experience
for
the
MVP
one.
Do
we
want
it
to
be
all
see
alive?
The
reason
I
ask
is
I'm
trying
to
see
if
I
can
find
a
developer
here
that
can
help
build
a
VPS,
catalog
browse
experience
or
see
if
anyone
can
help
but
alone
in
the
communities.
Dashboard
said
I.
B
A
Okay,
well,
thank
you,
everybody
for
joining,
I'm
going
to
end
the
meeting
here
and
since
I
believe
this
is
the
last
cig,
Service
Catalog,
a
scheduled
meeting
of
2016
I,
want
to
just
say
thank
you
to
everybody
that
has
been
participating.
Everybody
that's
been
attending
hello
to
anybody
watching
on
youtube
that
has
not
yet
joined
a
meeting.
We'd
love
to
have
you
and
everybody
have
a
wonderful
holiday
season
and
new
year
take
care
bye.