►
Description
OSB Local - Start Coding in No Time - Christian Brinker & Yannic Remmet, evoila
Do you remember tamagotchis? A little electronic pet you try to keep alive. Developers often face the same on their laptops. A little database they need for local testing. In CF you get it easy via the marketplace. Managed by the provider of the service. But locally? Here the developer has to install and keep the database alive. Wouldn’t it be cool have the CF marketplace on your laptop? With Open Service Broker local the speakers present a solution to that. Accessible via command line, deployed locally and easy to use. So getting a new database for development gets a no-brainer.
https://cfseu18.sched.com/event/FRyq/osb-local-start-coding-in-no-time-christian-brinker-yannic-remmet-evoila
A
A
What
is
what
is
the
problem
we
want
to
solve
with
this
I'm
a
death
and
unfortunately,
sometimes
I'm,
also
consulting
somewhere
and
in
between.
I
I
want
to
develop
something
in
the
Train,
maybe
on
the
drive
to
the
customer
and
to
test
something
and
unfortunately
I
like
Cloud
Foundry
and
the
Cloud
Foundry
experience.
But
at
some
times
you
don't
have
internet
access.
You
cannot
access
your
cloud
foundry.
Maybe
you
may
be
remote
and
or
in
a
hotel
room
with
a
bad
Wi-Fi,
and
you
want
to
test
something,
and
then
you
don't
have
a
Cloud
Foundry.
A
So
several
people
came
up
with
this
idea:
hey.
Why
don't
have
a
local
Cloud
Foundry
on
your
local
computer,
which
is
C
of
local
CF
def
different
types
of
of
ideas
by
the
one
you
have
docker
containers.
By
the
other
hand,
you
have
a
fully-fledged.
We
am
in
the
hyper
kid
running
on
your
local
machine
and
you
have
all
the
things
stuffed
in
there.
A
So
this
is
cool.
Now
you
have
local
Cloud
Foundry,
okay,
see
if
def
is
not
that
unconsumed
of
hardware
resources
in
your
laptop.
So
with
this
old
guy
here
it's
a
little
bit
of
frustrating.
Sometimes
what
do
you
have
it?
You
can
test
things
you
can
experiment
and
so
on.
So
you
have
this
idea
of
a
cloud
it's
more
or
less
equal
to
this
local
cloud
thing.
A
But
let's
face
another
problem:
I
am
a
deaf
when
I
have
my
local
cloud,
and
now
my
friend
here
comes
and
says:
yeah
I
have
a
cool
idea.
Let's
make
great
again,
and
you
no
project
now
gets
sad,
because
why
my
local
cloud
PSF
PCF
there-
I
see
if
the
f
may
only
have
my
sequel
in
it,
but
no
so
I
have
the
problem
to
get
a
local
MongoDB
stuck
in
there.
Somehow
so
I'm.
Really,
oh
okay,
we're
gonna
make
a
do.
A
Mongodb,
maybe
I,
take
a
docker
container,
spawn
it
wire
it
somehow,
in
the
network
of
the
CF,
deaf
and
okay
or
I,
have
to
look
for
some
service
broker
and
look.
How
could
I
shape
this
thingy
and
I'm
really
getting
a
little
bit
frustrated?
So
the
cool
idea
is
I
want
to
have
local
cloud
with
my
mom
would
be
service
in
the
marketplace.
That
would
be
awesome
and
that's
what
makes
me
happy
so
I
can
develop
with
it,
but
not
only
with
MongoDB,
with
every
service
broker
around
I
want
to
start
with.
A
So
what
is
the
idea?
I
have
my
local
PSE
of
death
with
cloud
foundry
with
a
Bosch
director
with
my
sequel,
I
didn't
use,
CF
local,
because
most
service
brokers
need
a
Bosch
director
to
deploy
something
which
we
don't
have
in
C.
If
local,
then
I
want
to
have
service
broker
somewhat
sing
and
I
want
to
have
a
seal.
I
plug
in
for
my
Cloud
Foundry
CLI
to
start
that
thing
up
to
make
the
service
broke
available
in
my
CF
def
in
an
easy
way.
I
don't
have
to
think
much
about
it.
A
I
only
start
working
and
then
I
get
my
marketplace
things
there.
So
this
is
then
I
was
below
cool
as
a
concept,
so
what
we
we
have
to
achieve
and
first
of
all,
you
have
to
have
some
kind
of
vendor
in
mechanism
for
the
service
brokers.
Why
that,
if
you
look
at
service
brokers,
they
are
a
little
bit
different.
They
are
all
I'll
have
to
be
a
little
bit
started
differently,
how
to
how
they
work,
how
they
will
be
shaped.
How
will
they
will
deployed
tires?
A
There
are
no
tires
they're
deployed
as
VMs
as
cloud
native
application
inside
cloud
foundry.
It's
all
a
little
bit
different
if
you
look
at
different
kinds
of
service
brokers
out
there,
so
you
have
to
have
a
standardized
rendering
system
for
that
the
service
brokers.
Then
you
have
to
load
them
via
CLI
in
CF
deaf,
so
they
can
use
them
in
a
marketplace.
Create
service
instances
create
service
keys,
maybe
to
falafels
testing
outside
of
the
CF
def.
A
So
you
can
use
these
service
instances
with
your
IDE,
so
you
can
directly
use
them
out
from
your
items
in
my
IntelliJ
starting
some
some
of
my
stuff.
They
are
locally
and
connect
to
that
database.
Also
so
because
I've
it
there
it's
available
and
then
I
can
also
push
to
see
if
left
my
app
and
the
best
thing
with
that
is,
if
I
want
to
restart
my
tests,
I
delete
that
service
instance
create
a
new
one
and
start
over.
A
So
if
you
look
at
docker
containers,
you
have
that
problem
may
be
that
the
Turku
container
may
be
stopped
and
started
and
may
be
loose
things
in
here.
You
have
the
proper
lifecycle
management
through
the
service
broker.
Maybe-
and
we
also
have
the
possibility
to
you
to
add
amounts
of
saving
to
the
local
disk,
so
you
can
restart
things
and
so
on.
A
A
It
could
be
something
different,
but
I
have
an
an
tar
file,
a
tarball
with
and
deploying
and
a
remove
script,
which
can
be
run
on
my
machine
locally
to
startup
that
service
broker
to
deploy
it
somehow
and
to
remove
it
and
have
some
binaries
in
there
some
partial
leases,
maybe
some
conflict
files,
maybe
I,
don't
know
because
the
deploy
file
I
want
to
start
with.
My
C
lies
during
the
and
what
is
done.
The
deploy
script
is
called
from
the
CLI
to
with
giving
me
a
horse
costume.
A
A
So,
for
example,
with
our
MongoDB
I
have
a
ploy
script.
My
remove
script.
I
have
a
jar
file
which
is:
is
the
service
broker?
I
have
a
Porsche
lease
which
create
the
NEBOSH,
a
MongoDB
VM
inside
of
the
hyper
kit.
Maybe
I
have
an
this
I
have
some
conflict
files
I
want
to
use
for
for
the
deployment
here
and
I
deployed
with
my
service
broker
admin
admin
and
later
on,
I.
Remove
it
that
way.
A
So
what
are
benefits?
What
did
I
achieve
against
getting
darker?
First
of
all,
I
have
the
same
deployment
methods
used
alike
in
production
if
I
give
a
later
on
to
Cloud
Foundry.
My
test
experience
on
my
local
machine
is
the
same,
so
I've
completely
parent
completely
the
same
thing
to
the
same
way
to
use
the
services
I
don't
have
to
you
use
caps
on
my
local
machine
to
get
that
docker
stuff
used
for
my
CF
death.
A
If
don't
do
not
have
to
tackle
with
my
networking
on
my
local
machine
to
the
hyper
kid
I've
in
where
I
have
to
tackle
this,
these
different
things
with
my
Tucker,
the
service
brokers,
are
maybe
the
same
things
I
used
also
in
the
production
environment,
because
they
only
I
used
a
small
plan
instead
of
big
cluster.
But
it's
it's
more
or
less
could
be
the
same
service
broker.
With
this
different
plan,
which
is
used
for
a
local
chess
which
are
used
for
testing.
A
Also
in
the
in
the
test
stage
in
my
production
environment,
I
can
use
this
year,
I
received
a
yellow,
I
plug
in
scripting
indifference.
To
that
I.
Can
you
have
Dhaka
files
which
are
mostly
I
have
to
get
from
somewhere,
so
I
get
some
from
Dhaka
have
some
MongoDB
docker
file
and
then
sa
a
cool.
Yet
this
doesn't
work
that
way.
I
thought
so
then
this
and
it's
the
MongoDB
is
completely
different.
Configurator
than
in
production,
then
mainly
bad.
A
A
A
A
B
A
B
B
A
A
In
the
meantime,
any
questions
until
now
I
know
it's
a
little
bit
flaky
with
a
weather,
demas
a
hands-on
demo.
What
I
created
is
I'm
a
it
started,
a
service
where
a
child,
the
files
are
described
beforehand
into
the
table.
All
upload
made
it
available
with
her
with
the
HTTP
process,
then
I
said
I
wanted
to
edit
as
a
new
service
to
my
to
my
sea
of
death
and
make
things
available.
There.
A
In
the
meantime,
we
wait
let's
talk
about
where
we
want
you
to
go
with
that
in
the
long
run.
We
want
to
go
to
see
if
local,
because
this
is
a
little
bit
more
less
aggressive
in
the
resources
of
your
local
machine,
but
the
drawback
is,
you
have
no
boss
directory
with
that
which
most
service
brokers
needs.
So
we
have
to
circumvent
that.
A
You've
seen
that
the
back
lock
is
not
that
optimized,
so
we
need
a
bit
more
for
there
and
only
at
the
moment
because
of
CF
dev
and
so
on.
We
only
support
Mac
OS
with
a
CF
local.
You
have
also
other
distributions
like
Windows
working,
and
so
this
would
also
improve
the
the
footprint
on
the
local
machine.
A
Our
documentation
could
be
better
and
we
want
to
have
a
standalone
mode
without
CF,
deaf
or
CF
local.
So
you
can
also
use
this
for
providing
your
your
database
locally
without
doing
it
all
of
the
other
stuff.
So
you
can
only
for
your
IDE
spawn
up
the
the
MongoDB
then
remove
it
and
so
on,
maybe
with
Eden
CLI
and
so
on.
So
you
can
directly
interact
with
that.
D
B
B
B
A
C
B
B
C
C
A
B
A
C
A
And
so
what
we
were
talking
about,
what
I
meant
was
we're
using
CF
dev,
so
I've
run
see
if
Jeff
starts
during
the
keynote
startup
mercy
of
death
and
use
this
now
here
and
but
the
cfd
F
has
a
very
big
footprint
on
your
machine.
If
you
look
at
the
it
takes
about
more
or
less
of
this
old
laptop
here,
the
full
memory,
which
is
not
cool
if
you
want
to
run
an
IDE
next
to
it.
A
For
that
see,
if
local,
which
uses
docker
containers,
it's
a
little
bit
less
strong
from
the
footprint
and
because
it
doesn't
utilize,
it
makes
it
about
the
users
experience,
but
not
about
creating
a
complete
Cloud
Foundry.
Next
to
it,
it
would
be
much
better
for
the
for
the
users
for
the
developer,
so
we
want
to
go
there
but
see
if
locally,
because
it's
a
platform
deployment
doesn't
have
a
Bosh
directly,
which
most
of
the
the
service
brokers
need.
A
So
what
we
have
to
do,
then
it's
deploys
a
Bosh
director
for
the
CF
locale
and
to
work
with
it,
and
by
that
we
have
to
to
look
when
start
making
this
year,
the
CFL's
be
ad
that
he
looks.
Is
there
a
sea
of
death
or
see
if
local
and
then
starting
the
the
things
for
it?
So
this
is
what
you
do
so
you
can
use
the
rest
footprint
and
also
you
can.
We
have
to
come
up
with
a
with
the
trick,
if
there's
nothing
of
both,
so
you
can
use
it
in
standalone
mode.
E
A
The
problem
is
suppose
of
the
service
brokers
at
the
moment.
Do
so,
if
you
want
to
use
the
arbitrary
service
brokers
with
that,
you
have
to
have
a
Bosch
director
for
them
prepared,
so
they
can
utilize
that
you're
right
if
you
want
to
get
along
without
a
Bosch
director
in
the
long
run,
and
you
want
to
use
kubernetes
for
your
data
services,
you
want
don't
want
to
have
that.
So
we
may
add
some
information
in
the
configuration
of
the
service
broker
tarball
to
to
show
I
need
wash
director.
A
A
D
D
Quite
a
few
differences
between
death
and
production
once
you
use
them
because
you
have
completely
different
set
up
locally
than
in
production.
So
would
you
say
that
this
small
gain
of
death
brought
parity?
You
gain
by
the
setup
is
really
worth
the
effort
compared
to
running
those
services
in
doctor
and
just
bind
him
to
talker
and.
A
The
problem
with
the
doctor
thing
is:
you
have
with
you
when
using
service
broker,
you
have
a
distinct
configuration
of
your
service,
so
it's
not
about
the
the
it's
a
cluster
another
cluster
and
for
most
services,
but
also
which
are
the
predefined
type
character
sets
and
so
on,
in
the
configuration
to
have
how
it
preparations
for
the
represent
configurations
on
for
bigger
clusters.
Yes,
also
in
the
Indus
Mahler,
deaf
versions
of
these
service
brokers,
often
and
the
if
you
look
at
the
the
darker
versions,
you
find
on
docker
hub,
for
example,
they
are
completely
different.