►
From YouTube: Service Catalog Basics
Description
Paul walks through the basics of the Service Catalog project and API.
A
Hey
everybody:
this
is
Paul
from
sig
service
catalog.
It
is
February,
2nd
2017
and,
despite
the
numerous
recordings
that
we
have
of
sig
meetings,
I
realized
that
we
don't
actually
have
an
introduction
to
what
Service
Catalog
is
and
how
the
API
works.
So
I'm
going
to
just
record
something
about
that
now
with
nobody
watching
me,
except
one
vallejo,
that's
how
you
say:
name
right
all
right,
excellent,
so
far,
I'm
one
for
one
one:
it
works
on
the
user.
Experience
came
to
Oakland
shift
and
he
wanted
to
know
about
this.
A
So
we're
going
to
record
it
all
right.
Everybody
say
thank
you!
You
want
okay.
So
when
we
talk
about
Service
Catalog,
what
we're
really
talking
about
is
a
way
in
the
kubernetes
world
to
use
this
concept
of
a
service
broker
in
order
to
provision
new
instances
of
services
and
bind
to
them
in
our
applications.
So
let
me
just
define
a
service
broker
as
something
that
manages
a
set
of
services
where
a
service
could
be
something
like
a
Postgres
database,
Mario
DB
database.
It
could
be
an
SPD,
it
could
be
a
message
broker
whatever.
A
So
when
we
say
provision,
what
we're
talking
about
is
like
make
a
new
instance,
somehow
whether
that's
actually
starting
up
a
new
process,
or
maybe
we
have
like
a
multi-tenant
fast
that
we're
exposing
via
service
broker,
and
we
just
want
to
make
a
new
tenant
and
when
we
say
find
what
that
means
is
creating
possibly
new
but
anyway
giving
us
back.
A
set
of
credentials
coordinates
big
items
that
we
need
to
use
the
service.
A
A
It's
ground
breaking
stuff
that
we're
not
the
only
folks
that
are
doing
it
a
displays,
but
we're
one
of
the
one
of
the
group's
that's
kind
of
the
pilot,
which
is
always
exciting
and
fun
and
challenging.
So,
let's
talk
about
Service
Catalog,
so
the
the
nouns
in
the
Service
Catalog
space
there's
only
four
of
them.
So
it's
pretty
easy
to
talk
about.
There's
a
broker.
A
burger
is
something
that
I
guess.
We
really
can't
see
that
it
doesn't
show
they're
a.
A
A
The
first
is
get
a
list
of
services
which,
in
the
open,
serviceworker
api,
which
is
the
actual
adi,
it
defines
where
a
service
broker
you
there's
a
thing
called
conveniently
well
identify
apically
in
conveniently,
because
there's
a
lot
of
overloaded
terminology
in
the
state
called
the
catalog
in
point
that
tells
us
what
services
this
broker
host.
Alright,
we
can
also
provision
new
instances,
as
we've
been
discussing
of
a
service
at
this
burger
knows,
then
we
can
find
to
them,
find
you
an
instance
and
then
unbind
and
the
provision.
A
So
the
catalog
in
point
is
a
fact:
a
set
of
services
which,
since
we
already
have
something
called
service,
incriminates,
we
have
to
disambiguate
that
come
now,
so
we
call
it
service
class
and
those
of
you
that
are
familiar
without
storage.
We're
computer
days
will
notice
similarity
to
storage
a
class.
Actually,
the
inspiration
birthday
when
we
a
service
class
represents
a
service
that
a
broker
gives
us
and
when
we
permission
a
new
instance
of
it.
A
When
we
provision
a
new
instance
of
it,
we
get
a.
We
had
an
instance
resource
to
represent
that,
and
since
this
as
well,
you
know
an
important
part
of
this
is
fighting
to
resources
or
started
biting
instances.
We
have
a
finding
resource
that
represents
our
intention
to
use
a
binding
in
a
particular
application.
A
So,
as
I
said
all
of
these
things,
he
started
in
our
Toobin
any
API
for
service
telephone
and
when
I
say,
determine
any
API
be
in
life.
We
have
a
particular
API
style
incriminates
that
folks
will
be
familiar
with
if
you
use
the
project
before
ego.
The
service
broker
ABI
does
not
exactly
match
that
style
and
it
doesn't
incorporate
that
you've
been
any
concepts
that
we
need
to
follow
the
stuff
into
the
Denny's.
So
Davi
Davi
that
we're
discussing
right
now
is
really
kind
of
a
wrapper,
terminating
style
wrapper
on
top
of
open
source
programs.
A
A
A
So
how
does
this
work
in
terms
of
like
what
is
this
ABI
look
like
in
terms
of
usage
patterns
is
a
question.
One
would
be
asking
if
I
pull
into,
but
I
asked
to
form.
So
he
did
so,
let's
bra
how
this
arrangement
looks
when
we
have
a
kubernetes
and
a
service
catalog,
and
we
can
talk
through
the
things
in
a
relatively
short
amount
of
time.
A
So
you
may
have
seen
some
picture
like
this,
that
I'm
drawing
on
the
board
before
and
if
anybody
can
show
me
where
I
actually
has
done
this
explanation
before
I
will
give
you
one
Internet
thumbs
up,
but
I
went
through
a
few
other
videos
in
the
YouTube,
playlist
and
I
can
play
a
really
goes
through
the
it
alright.
So,
as
I
said,
this
work
is
being
done
outside
the
course,
so
we're
going
to
start
by
drawing
some
lines.
This
line
on
the
bottom
of
this
is
terminated
for.
A
There's
a
controller
slightly
shorter,
a
controller
I
mean
this.
Is
the
kubernetes
Service
Catalog
controller
that
implements
this
the
behaviour
behind
the
safety.
So
we
start
out,
we
don't
have
any
resources
created
in
here
yet,
and
the
first
thing
that
happens
is
that
the
catalog
operator
represented
by
our
friend
just
into
here,
is
the
catalog
operator.
A
That
represents
a
broker
they
want
to
use.
So
now,
we've
got
this
broker
resources
that
the
API
server,
the
controller's
got
watch
on
this
resource.
All
right
and
part
of
the
disparate
resource
said,
is
a
URL
that
you
can
reach
the
program.
So
then
you
have
a
child.
I've
got
hair
all
right,
so
controlling
and
watching
this
and
put
hot
a
new
broker
resource
has
been
persisted
in
the
API
server
I'm,
going
to
try
to
reach
that
that
broker
at
the
URL
and
do
it
yet
on
is
catalog
employee.
A
So
now
to
kind
of
draw
another
box,
here's
the
actual
broker
process
running
somewhere,
and
this
could
be
running
inside
the
trinity
cluster.
It
could
be
running
somewhere
in
the
internet.
It.
The
point
actually
is
that
doesn't
matter
as
long
as
you
can
resolve
this
thing's
URL
and
reach
it?
That's
all
you
need
to
talk
to
you,
so
we
do
it
get
on
a
catalog
end
point
you
give
those
back
with
the
services
and.
A
Until
it
takes,
is
payload
and
transforms
it
into
ours,
service
class
resource
and
persist,
those
into
the
API
server,
so
totality
API
server
advanced.
Now
our
catalog
has
the
service
classes
of
this
broker
is
presenting
to
us
and
so
later,
when
another
thing
to
hear
comes
along.
That's
that
we'll
call
a
service
consumer.
A
And
they
can
get
back.
You
know
a
payload
as
a
list
of
service
classes
in
the
future.
We're
going
to
have
some
kind
of
like
duration
policy
around
this,
so
that
an
operator
will
be
able
to
make
a
policy
object.
That
says
this
security
principal
can
see
this
set
of
service
class,
all
right
so
service
consumer.
What
is
this,
and
they
say-
oh
sweet
I-
need
a
posto
stress.
I
am
going
to
I'm
going
to
ask,
for
instance,
to
be
created
that
so
terminated.
A
A
Controller
hands
of
wash
on
this
resource
to,
and
so
is
an
instance-
that's
been
created.
I
guess
you
can't
really
see
it
do
the
glare,
and
we
can
see
something
about
this.
Well,
maybe
editor
the
fisherman
on
voice,
alright,
so
inside
the
blindingly
bright,
reflection
of
the
fluorescent
light
here
is
a
box.
So
system
controller
has
a
watch
on
this
thing
and
is
like
aha
I'm
going
to
need
I'm
going
to
go
to
the
broker.
A
That
is
that
present,
this
service
classes,
instances
up
and
I'm
going
to
do
an
HTTP
put
on
like
a
provision
endpoint.
For
this
thing,
I'm
not
going
to
do
I'm
not
going
to
add
a
surface
those
details
here.
It's
just
provision
this
instance
I
need
and
there's
a
whole
flow
for
like
if
this.
If
it
takes
awhile
to
to
happen
of
asynchronous
provisioning,
we're
not
going
to
worry
about
that.
Now
we
just
get
back
at
200
right
away.
A
Businesses
status
fields
as
a
condition
that
says
I'm
writing
kinetics
is
great.
I
got
an
instance.
Mated
part
of
payload
is
how
do
I
like
get
to
the
dashboard
to
look
at
that
thing.
If
the
service
worker
provides
something
like
that,
but
I
want
to
know
how
to
use
it
in
my
application.
So
that's
where
the
binding
resource
comes
in
a
service
consumer
poses
a.
A
A
A
What
this
means
for
you
is
you
get
a
secret
community
secret
that
has
coordinates
credentials,
say
items
in
it,
then
you
use
it
or
that
you
need
to
use
this
instance
long
term.
There
are
going
to
be
some
changes
that
we
make
in
the
focus
service
worker
API
to
facilitate
like
teasing
out
what
the
Western
shal,
what
the
coordinate
and
what
the
config.
A
We
don't
have
that
in
the
API
right
now,
so
at
first
we're
going
to
just
dump
it
into
a
secret,
but
ultimately
we'll
be
able
to
see
that
services
secret
if
they
map
and
then
to
to
use
these
things
in
a
loosely
coupled
way
to
use
a
binding.
There
is
an
object
that
we're
working
on
another
resource
that
is
outside
with
a
bi,
sir,
my
white
element
or
might
wind
up
in
another
API
server,
depending
on
happen.
A
A
So
this
contains
what
I
want
to
use
and
I
want
to
use
it.
So
same
story
with
this
resource
controls
got
a
watch
on
this
said
AHA
visit
your
binding
of
this
of
this
instance
I'm
using
another
clip
on
the
finding
endpoint
for
this
instance
and
the
service
broker,
and
what
I
get
back
is
a
payload
that
had
the
three
C's
the
coordinates
provincial.
A
Config
and
here's,
where
I'm
skipping
ahead
a
little
bit
say
all
the
things
that
that
I
just
articulated
we've
done
all
these.
These
things
that
I
said
were
comes
out
of
ice.
They
are
done,
controller
is
going
to
help.
It
stands
up
and
it's
going
to
create
in
the
kubernetes
api
through
which
I,
for
those
of
you
that
didn't
take
your
eye
off
the
ball,
and
probably
one
wondering
where
does
this
come
into
play
already
comes
into
play.
A
Now
it's
going
to
create
a
service,
it's
going
to
create
a
secret,
it's
going
to
create
a
config
map
and
it
will
create
a
hot
injection
policy
and
those
are
created
in
the
namespace
of
this
binding.
So
what
this
one
is
look
like
making
happen,
and
the
core
is
that
how
you
got
the
primitives
that
you
need
to
consider
service
and
you've
got
an
injection
policy
that,
in
a
loosely
coupled
way,
like
selector,
says
these
columns
should
get
this
information,
and
that
is
like
me,
that's
the
gist
of
this
API.
A
In
a
nutshell,
like
I
said,
there
are
there's
unbind
me
provision
and
since
I'm
five
minutes
ahead
in
life
either
to
talk
about
that.
I
have
severe
any
questions,
but
this
is
a
YouTube
video.
So
you
can
come
our
slack
channel
and
six
service
catalog
on
the
community.
Slack
ask
ask
one
of
those
questions
were
pretty
friendly
group,
but
let's
talk
about
one
vine
so
online
with
an
intention
based
API
you're
going
to
do
is
delete,
so
you
delete
designing.
A
A
What
happens?
Incriminated,
we
have
a
resource
that
you
have
to
have
some
work
to
do
and
after
afters
and
users
issue
to
delete
for
once.
But
what
was
the
thing
actually
get
so
given
is
be
called
finalization.
The
the
the
API
services
to
the
lead
time
stamp
on
this
thing
and
there's
a
list
of
stuff
and
have
someone
before
the
actual
delete,
atom
controllers.
A
Jesus,
says
often
the
deletion
time
stamp
on
it
by
the
way
looks
like
I'm,
getting
a
little
bit
ahead
of
probably
consensus
of
service
in
the
face.
So
I
just
know
some
construction
cones
around
here.
This
might
change
a
little
bit,
but
this
is
my
best
shot,
articulating
I
think
it's
perhaps
now
controller
sees
the
lesion
timestamp
is
on
here.
So
he
goes.