►
From YouTube: Cloud Foundry Community Advisory Board [Feb 2017]
Description
Video from the monthly Cloud Foundry Community Advisory Board (CAB) meeting. Learn more at https://www.cloudfoundry.org/.
Agenda:
Calendar
- Now every 3rd Wed of the month.
Tooling for the call
- See Zoom info above in and the #CAB Slack channel
CFF update
- CF-summit 2017 - June 13-15 in Santa Clara, CA
- CFP - talk proposal deadline is Feb 17th, 2017 @ midnight
Projects updates
- CAPI
- BOSH
- CF-extensions
- Diego
- UAA
Proposals on cf-dev
- Community projects
Prepared questions from the community
A
D
A
A
A
C
E
A
C
A
Well,
I
mean
part
of
the
reason
is
I
mean
I'm
impressed
that
people
are
joining
and
they
are
actually
removing
themselves
from
video,
but
I
can
still
see
the
video
that
time
so
I
saw
you
exactly
that's
pretty
good,
all
right
yeah.
We
have
one
801,
so
we'll
start
in
two
more
minutes,
but
we
get
more.
Actually
there
is
a
number
so
I
don't
know
who
that
is.
That's.
D
A
C
A
D
A
D
A
It
actually
okay,
so
this
is
working
out
hey.
We
got
area
care
so
anyway,
this
is
fantastic.
I
think
one
thing
Wade
and
I
were
chatting
about
this
before
that
we
have
a
representative
from
from
zoom
that
basically
increased
capacity
to
a
hundred,
so
maybe
when
you
can
introduce
it
and
briefly
mention
it.
C
Intimidated
by
us,
well,
that's
fair,
so
everybody!
This
is
a
tool
we
use
so
a
lot
for
remote
work,
remote
pairing,
it's
very
high
bandwidth,
very
nice.
Obviously
it
works
well
with
a
lot
of
people
and
it's
called
zoom
a
lot
of
you
probably
figured
out
by
clicking
on
the
URL
in
order
to
mute
and
unmute
yourself
on
the
bottom
left
hand
corner
the
screen
is
usually
a
little
microphone
icon.
That's
also
where
you
can
adjust
your
settings,
there's
usually
a
little
up
arrow
next
to
them.
A
Indeed,
Thank
You
Wayne
any
question
for
the
zoom.
No
I
think
this
is
gonna
work
out.
Well.
So,
if
you
have
commenters
question
I
guess
let
us
know
so
we
have
an
agenda.
So
if
you
go
to
the
link
for
the
agenda,
there's
a
little
bit
I
think
I
was
hoping.
Chip
would
be
here
to
cover
anything
on
CSF.
But
I
mentioned
a
few
things.
A
As
you
know,
I
don't
know
if
he's
gonna
join
first
thing
is:
the
summit
is
coming,
of
course,
is
June
13
to
15
and
Seneca,
so
it's
gonna
be
similar
to
what
we
had
before.
The
key
important
information
is
that
the
proposal,
the
top
proposal
deadline,
is
coming
up
on
the
17th,
so
basically
a
few
days
from
here
so
I
think
Friday
at
midnight.
A
So
if
you
have
something
that
you're
trying
to
submit
or
your
team
make
sure
to
remind
them,
I
think
you
can
not
only
just
proposed
talks,
but
you
can
also
propose
panels
and
other
things.
So
if
you
go
to
the
link
that
I
that
I
have
in
the
agenda
for
the
CFP
that
you
can
see
the
kind
of
things
that
are
being
requested,
that.
C
A
If
you
submitted
something
like
this,
especially
if
you
get
out
of
like
a
CFM
that
I
think
few
people
would
join
so
yeah
all
right,
so
don't
forget
to
submit
I,
mean
I,
think
I
think
at
the
end
of
the
day.
It's
it's
really
about.
You
know
community,
so
you
got
to
propose
your
talk
all
right.
So
usually
what
we
do
is
to
see
if
there
are
any
project
highlights
I
know,
Demetri
is
on
the
call
decay
you
hear.
I
saw
you
join.
No.
You
have
to
unmute
yourself,
though,
can't.
A
H
H
Course,
team
has
been
working
a
lot
on
implementing
closing
down
the
config
server
integration,
which
will
allow
us
to
use
the
director
with
upcoming,
open
source
Crudup,
to
manage
all
the
credentials
for
board
deployments
and
I'll
automatically
generate
them.
So
that's
very,
very
close
to
being
computed.
H
We
have
an
upcoming
boss,
release
two
six
one
that
will
include
majority
of
it.
Then,
after
that
we'll
do
some
additional
polishing
we've
been
also
working
on
adding
multi
CPI
integration,
thanks
to
some
contributions
from
Swisscom
and
IBM,
and
that's
also
going
to
be
in
the
upcoming
release.
But
with
the
beginning
carry
at
that
right
now,
you'll
be
able
to
use
it
only
again,
the
same
type
of
CPI
and
then
the
next
release
will
allow
us
to
use
any
combination
of
CGI's.
H
So
that
would
help
us.
You
know,
customers
who
are
trying
to
let's
say,
run
a
single
cloud
foundry
across
multiple
open
stacks,
let's
say
because
they
don't
necessarily
want
to
use
OpenStack
easy
concept,
or
maybe
you
know
if
you
have
multiple
vSphere
installations,
you
want
to
connect
the
two
data
centers
together
that
kind
of
stuff.
So
that's
quite
exciting
and
of
course
eventually
it
will
allow
us
to,
for
example,
combined.
H
You
know,
usage
of
let's
say
you
know
any
ayahs
like
AWS
and
wash
light.
For
example.
If
you
want
to
be
easy
running
your
errands
or
maybe
doing
some
calculation
of
Bosch
light
figuration
and
you
know
actually
play
the
workload
onto
a
different
set
of
machines,
say
that's
that's
kind
of
a
to
highlight
that
have
been
come
along
for
some
time.
We've
been,
of
course,
working
on
a
variety
of
other
fixes
and
you
know,
features
actually
one
more.
That's
really
kind
of
a
big
one
is
upcoming.
C
H
There's,
probably
you
know,
I,
don't
know
how
many
people
are
kind
of
keeping
up
with
the
CEO
IV
to
work,
but
we
see
live
it
it.
You
know,
kind
of
subsumes,
the
boss,
in
its
functionality
into
two
commands,
create
and
then
delete
an
and
with
those
two
commands
we
actually
pulled
out
this
new
repo
out
of
I
guess
main
boss
resource
that's
called
Borge
deployment
and
boards
deployment
is
the
repo
that
really
contains
all
of
the
llamo
configurations
that
are
typically
documented
on
bojayá.
H
But
we
used
to
expect
that
you
know
people
would
kind
of
change
them
and
maybe
drop
them
off
somewhere
and
their
configuration
folders
so
on
and
so
forth.
But
instead
of
doing
that
nowadays,
wisdom,
you
see
why
we
are
you
know
having
all
these
configurations
recorded
in
the
bush
deployment
repo
and
we've
made
it
such
that
it's
very
easy
to
you
know,
let's
say
enable
you
a
functionality
on
your
director
or
maybe
enable
a
fixer
of
so
you
know
that.
That's
that
repo
is
a
kind
of
a
or
master
copy.
H
For
you
know
what
is
the
recommended
way
to
configure
the
director
and
configure
all
the
stuff
around
the
director?
Like
you,
a
integration,
so
I
expect
that
majority
of
both
I/o
documentation
that
will
be
updated
to
use
CLI
the
two
would
actually
be
referencing.
Both
deployment
people
to
you
know
to
effect
we
say,
run
this
one
command
to
enable
UA,
and
if
you
want
more
details
on
what
exactly
is
being
dropped
in
looking
into
the
UA
operations
file
that
describes
you
know,
what
exactly
are
we
turning
on
and
turning
off?
H
So
that's
been
kind
of
a
side
side
effect
of
switching
over
to
seal
IV.
To
for
sound
the
team?
Is
there
now
not
have
to?
You
know,
think
about
maintaining
there.
You
know
you
used
to
be
borscht
in
it
manifests
they
just
pull
down
the
board's
deployment
repo
and
obtain
into
the
features
that
they
did
care
about
further
environment
and,
of
course,
all
the
you
know,
passwords
and
certificates.
Now
that
get
generated,
so
users,
don't
have
to
think
about
this
as
well,
so
I,
don't
think
I
have
any
other
bigger
updates.
H
C
So
you
said,
you're
working
on
documentation,
assuming
that's
like
also
going
to
include
like
here,
is
how
you
transition
from
working
with
v1
CLI
to
the
p2,
CLI
and
I.
Think
you
had
a
little
bit
of
that,
but
as
that
could
be
fleshed
out
more
and
is
that
what
I
was
hearing
was
that's
the
kind
of
focus
yeah.
H
Whatever
the
commentation
existed
for
C
lightly
to
up
to
now
was
really
just
some
notes
that
you
know
written
down
before,
just
to
not
forget
mention
it,
but
yeah
there's
a
there
is
no.
There
has
not
been
any
official
documentation
for
saliva
to
has
been
published.
So
that's
that's.
Definitely
one
of
their
first
before
the
release.
A
C
A
F
F
We
look
forward
to
exercising
it
more
rigor
in
production
environments
since
we're
not
aware
of
any
outstanding
bugs
with
it,
and
then
we're
also
exploring
moving
the
locks
that
components
such
as
say
the
BBS
and
the
auctioneer
and
the
cells
maintain
for
their
presences
out
of
constable
in
something
that's
just
backed
by
the
BBS.
This
relational
database.
F
F
C
F
I
think
it's
still
kind
of
down
at
the
garden
level.
At
this
point,
I
think
it
looks
like
Jules
is
on.
He
might
be
able
to
provide
a
little
more
detail
so
effectively
all
of
the
action
there
has
to
happen
when
garden
order.
The
new
Goethe
fest
component
actually
pulls
the
image
from
a
docker
registry
repository
that
requires
authentication,
so
we're
expecting
the
bulk
of
the
work
to
happen
down
there
and
then
effectively.
The
rest
of
it
is
just
wiring.
F
There's
one
additional
piece
to
that
where,
when,
when
we're
doing
a
staging
task
for
a
doctor
image
based
app,
we
also
need
to
have
those
credentials
available.
So
we
have
to
change
something
in
the
docker
app
lifecycle
builder,
but
I
think
there's
a
proposal
document
that
has
been
circulated
to
some
extent
soliciting
feedback
on
the
api's
that
we'll
have
to
run
through
at
the
Diego
and
garden
layer
to
fist
flow.
The
docker
registry
credentials
through
the
system
down
to
the
garden
site
that
hosts
the
image.
C
C
A
A
I
A
B
A
B
B
B
I
E
I'm
Zak
I'm,
the
new
p.m.
for
the
capi
team
I,
was
previously
an
engineer
on
the
Cappy
team
ever
since
it
existed
so
been
around
for
a
little
while,
let's
do
a
quick
update,
we
sort
of
have
two
main
tracks
of
work.
One
is
finished
enough,
compute
isolation
segments,
the
functionality
was
done
probably
around
this
call
last
month,
but
we
got
some
feedback
from
the
CLI
had
asked
for
some
updates
to
the
API.
E
So
we
relaxed
that
restriction,
and
so
now
you
can
apply
isolation,
segments
to
spaces
with
existing
maps
and
then,
if
you
perform
like
a
Bluegreen
and
deploy
you'll,
get
your
app
will
go
over
into
an
isolation
segment,
so
that
works
pretty
close
to
being
done
and
we're
thinking,
CLI,
we'll
start
building
out
commands,
probably
in
the
next
week
or
two
so
hopefully,
by
this
call.
Next
month,
we'll
be
able
to
say
that
compute
isolation
is
live
and
done
so
that's
good,
going
good.
E
Our
other
main
track
of
work
is
securing
our
communication
path
to
other
components.
That
has
essentially
meant
that
most
of
the
CCC
bridge
components
are
being
removed
and
instead
sort
of
pulled
it
into
the
cloud
controller
so
that
we
just
talked
directly
to
Diego
to
components
and
we're
doing
that
over
mutual
TLS
that
works
in
flight
there's,
there's
quite
a
few
components.
We've
we've
probably
got
through.
You
know,
roughly
half
of
them
being
consumed
by
the
CC.
I
Like
very
small
items,
I'd
like
to
highlight
as
well
recent
functionalities
is,
we
now
have
support
for
a
global
of
Auditors
scope,
so
this
is
more
or
less
like
an
auditor.
The
the
permissions
that
you'd
have
access
that
you'd
have
as
an
auditor,
but
without
actually
having
to
be
explicitly
added
to
those
faces
orgs.
So
you
can
have
an
auditor
that
doesn't
have
access
to
unique
app
services
for
all
of
the
apps,
for
example,
which
has
been
somewhat
long
and
requested.
I
So
that's
one
one
nice
thing
to
check
out
in
the
latest
CF
release
and
the
other
one
small
life
improvement
is
that
we
added
support
for
an
HTTP
health
check
and
CLIA
added
support
for
this
with
their
latest
release.
And
so,
if
you
an
app
that
wants
to
signal
more
explicitly
whether
it's
ready
to
receive
a
request,
it
just
needs
to
implement
a
health
tracking
and
point
and
return
into
100.
H
A
A
Okay,
I
don't
hear
anything.
So
let
me
give
a
quick
update
on
CF
extensions,
so
you
guys
saw
that
we
had
a
process
proposal.
Part
of
the
idea.
There
is
to
make
sure
that
people
go
into
this
with
your
eyes
wide,
open
and
understanding.
What's
gonna
happen
next,
it's
a
commitment
for
us
working
in
the
community,
but
also
it's
a
commitment
from
you.
A
If
you
submitted
something
that
you
want
to
be
an
extension
and
what
I
want
to
try
to
do
is
to
make
sure
that
every
project
that
submitted
it
actually
goes
to
who
all
gets
put
it
out,
so
that
we
can
have
a
stream
of
extension,
but
also
we
bet
them
and
they
go
through
the
whole
process.
So
I
think
generally
it's
a
not
controversial
process.
So,
if
you
get
a
chance,
make
some
comment,
otherwise,
that's
pretty
much
gonna
be
couldn't
put
the
law
right.
A
So
one
example
of
this
is
that
the
back
your
service
worker
that
SAT
submitted
is
actually
going
to
a
little
bit
of
it
because
it
came
after
we
had
the
first
test,
but
essentially
it's
incubating
right
now,
so
I
created
project
space
for
them
and
there's
actually
a
team
and
SAT.
That's
started
when
that
another
good
example
of
this
is
a
credible.
A
So
when
Demetri
was
talking,
he
talked
about
the
fact
that
config
server
is
an
API
and
there
is
an
implementation
that
the
Boche
team
did,
but
there's
also
a
more
complete
implementation
that
also
they
turtle
did
call
cred
hub
and
then
he's
on
a
call
right
now
and
presented
I.
Think
maybe
two
two
tabs
ago
is
an
implementation
of
this
API.
That
is
more
complete
and
the
turtle
has
submitted
it
to
the
extensions
group
and
right
now,
I
think
it's
at
a
point.
Where
do
you
want
to
move
it
to
a
vote?
A
So
after
this
call,
I
will
send
an
email
and
asking
if
there
are
any
comments?
That's
your
last
chance.
Otherwise,
we
are
just
gonna,
do
a
vote
and
hopefully,
if
it
goes
through,
then
you'll
see
next
time
a
CF
incubating
project.
Where
then
and
his
team
will
have
everything
and
you
can
just
go
and
check
it
out.
Okay,.
A
There's
a
series
of
other
proposals
in
extensions.
One
of
the
things
I've
been
trying
to
do
is
to
collect
them
because
I'm
creating
a
little
Club
I've
actually
took
both
URIs
advice
and
dimitris
where
the
database
is
actually
gonna,
be
github.
So
there's
a
few
rules
I'm
gonna
have
to
put
on
you
know
how
you
tag
your
projects
and
so
on,
because
I'm
just
pulling
that
information
from
github.
So
we
can
talk
about
that.
Once
I
went
I'm
ready
to
make
that
public,
but
for
now
I
have
a
doc.
A
That's
collecting
those
projects,
there's
actually
a
couple
of
them
that
are
often
often
sorry
so
I'm
just
gonna
assume
by
the
time
I
send
an
XML
like
no
answers
that
I
just
get
rid
of
them.
So
basically
we'll
only
have
projects
that
are
active
and
that
are
you
know,
valid
I'll,
put
the
link
of
the
corrected
project
URL.
So
that
way
people
can
can
go
check
it
out.
So
any
questions
for
extensions.
A
I
A
J
J
Awesome
he
got
the
3dr
he's
out.
The
release
notes
are
up
as
well
and
it
is
part
of
CF
release.
252
there
are.
There
are
some
breaking
changes
in
this
release,
so
please
read
the
release,
notes
to
get
an
understanding
of
what
those
are,
and,
apart
from
this,
the
next
major
version
of
UA
is
going
to
be
for
dot.
Oh,
and
we
have
plans
to
do
some
consolidation
around
configuration
properties.
J
You
AAA
has
you
know
like
a
legacy:
login
dot
Hamill,
that
is
from
the
hadees'
when
organ
server
and
UA
were
separate.
So
we
have
plans
to
consolidate
it
for
ease
of
use
and
documentation
as
well.
So
that
is
one
major
change
that
is
going
to
be
coming
for
OH.
Apart
from
that,
there
will
be
some
other
changes
as
well.
I
have
plans
to
basically
send
out
a
note
on
the
three
of
them
list,
with
the
plan
for
full
bottle.
D
H
A
A
A
D
A
Guess
you
can't
work
with
there
and
also
to
get
access
to
it.
Yeah,
okay,
but
I,
think
part
of
it
also
is
to
I
guess
the
overarching
goal
of
the
process
is
to
move
things
forward
fast.
So
we
want
to
remove
you
know,
hurdles,
but
I
also
want
the
community
to
be
able
to
chime
in
on
any
point
in
time
and
invoice
the
opinion,
so
we'll
figure
it
out.
I
guess
for
this
particular
case,
any
other
questions
comments.
I
Recently
and
appreciate
a
digital
feedback,
if
you
get
time,
even
if
you
you
know
like
it
hate
it,
that's
great
in
particular,
there's
the
multi
build
proposal
on
the
longer
data
team
has
a
couple
of
proposals
about
independently
scalable,
syslog
I
think
their
most
recent
one
was
loving.
A
turn
tells
check
console.
I
I
A
A
Okay,
let's
see
if
there
are
any
questions
that
were
posted
on
the
agenda.
I,
don't
see
anything
that
wasn't
answered
yet.
So,
if
you
don't
have
any
questions
these,
this
is
I
get
the
first
part
of
the
program
where
we
just
cover
projects,
PMC's
basic
stuff,
you
know,
highlights
and
then
now
we're
going
to
move
to
community
projects
and,
as
I
mentioned
our
friends
from
Stockton
Wayne
super
busy
or
guess
they've
been
busy
for
years.
So
they
have
a
list
of
projects.
A
I
know
and
Wayne
has
been
very
good
at
you
know
getting
me
in
contact
with
a
bunch
of
different
teams
so
pretty
much
every
month,
you're
gonna
see
something
from
him
stuck
in
line.
Unless
somebody
else
has
a
project
and
we're
gonna
try
to
do
two
of
those
right
so
that
we
can
go
deep
into
each
and
last
time
we
covered
shield,
but
there
was
no
demo
and
and
because
it's
such
a
I
guess
it's
a
big
project
and
it's
pretty
nice.
D
D
C
G
Everyone's
watching
their
laptops
and
reading
slacks.
No,
so
yes
they're
all
my
name's
John.
If
you
can't
tell
from
the
name
on
my
zoom
Tyler
I'm
a
carve
engineer,
it's
dark
and
moving,
which
is
fine.
When
I
tell
people
that
aren't
technical
related
because
we
say
cloud
engineer,
I
think
they
just
imagine
we
like
boil
water
or
something
I,
don't
know
but
anyways.
G
A
G
I
D
G
Yes,
so
this
is
the
repo
that
it's
in
it's
under
Stark
and
Wayne,
and
shield
is
basically
used
to
backup
and
restore
a
bunch
of
different
systems.
We've
designed
it
in
such
a
way
to
where
we
have
a
plugin
system
where
what
you're
actually
backing
up.
We
call
it
target
and
then
the
way
that
we
actually
save
these
cups
use
a
plugin
called
a
store.
G
So
if
I
scroll
down
here
a
little
bit,
we
have
this
nice
table
where
you
can
see
all
the
different
things
that
we
can
backup,
which
would
be
under
this
target
and
the
things
that
where
we
can
actually
save
our
backups
to
so
you
just
click
on
any
of
these.
You
get
this
documentation.
That
shows
you
how
to
configure
it.
G
G
So
this
is
the
Postgres
one
in
the
first
80
lines
is
documentation,
but
the
entire
go
file
is
300
lines.
You
know
80
lines
for
comments,
so
it's
actually
not
as
crazy
as
you
might
think.
So
you
can
look
at
any
of
these
different
plugins
to
be
able
to
implement
one
so
anyways
about.
Like
a
few
weeks
ago,
I
was
working
with
a
client
and
I
had
to
get
familiar
with
shield,
so
what
I
did
is
normally.
G
We
just
deployed
this
using
a
Bosch
release,
but
what
I
went
through
and
did
is
create
a
local
version
that
you
can
run
inside
docker
compose.
So
if
we,
so
this
is
a
new
edition
just
a
few
days
ago.
So
if
we
go
to
the
dev
folder
inside
shield,
you
can
just
set
up.
Docker
compose
and
I
have
a
bunch
of
directions
in
this
directory
and
the
readme
on
how
to
set
it
up.
It's
pretty
pretty
straightforward
and
what
it
will
do
is
it
will
actually
spin
up
web
UI.
G
G
Yes,
so
this
this
particular
evening
has
examples
on
how
to
use
the
CI
and
it
doesn't
show
every
command,
but
it
gives
you
like
a
good
run
through
on
how
to
use
it,
but
what
I'm
going
to
do
is
show
the
web
UI
and
then,
if
anyone
wants
to
go
through
and
kind
of
play
around
with
the
COI,
he
can
look
through
this
readme
and
you
can
run
it
in
docker
compose
setup
or
you
can
do
it
on
a
Bosch
release
or
you
can
do
it.
However,
you
want
to
set
up
shield.
B
G
G
G
So
what
was
I
so?
Basically,
you
can
just
clone
the
repo
and
then
you
can
just
run
stackert
or
compose
up,
and
that
will
this
is
like
Baker
nut,
so
I
I
don't
know
if
I
really
need
to
go
into
this
much
detail,
so
I
apologize
if
everyone's
like
yeah
yeah
yeah,
we
know
so
so
what
I'm
going
to
do
over
here.
My
terminal
I'm
just
going
to
run
the
command
docker
compose.
Oh
yeah,
so
I
just
use
docker
compose
because
I
wanted
to
just
see
what
it
was
like
to
use.
G
Docker
compose,
but
so
I
didn't
have
any
real
particular
reason.
But
it's
got
several
different
services
in
here
and
what
I
did
is
I,
went
through
the
shield
box
release
and
then
kind
of
copied
that
to
make
this
docker
compose,
you
know
set
up
so
anyway,
so
we
have
killed
running
here.
I'm
gonna
go
over
to
the
web
UI.
A
G
Yeah
I
think
I.
Might
you
know
ask
one
of
the
other
people
would
start
going
to
do
that
because
they
have
more
experience
with
that
than
me,
but
I
think
we
have
quite
a
few
start.
Grooming
people,
so
someone
in
the
collective
knowledge
can
can
pull
it
up.
I'm
sure
so,
I
know.
Yeah
I
will
definitely
bring
that
up
thanks
for
asking.
G
But
so
if
you
look
here
on
the
web
UI
we
have
this
idea
of
retention
policies,
so
you
can
create
one
basically
I
already
created
one
for
ten
days.
So
but
I
could
click
this
button
and
I
fill
out
this
form.
So
basically,
what
that
is
is
like
how
long
all
your
backups
going
to
stay
around.
So
you
know
in
this
particular
case,
I
just
did
ten
days.
You
know
just
for
the
demo
here,
but
maybe
you
have
a
lot
longer.
G
One
I
think
on
some
of
our
clients:
we've
done
ones
where
we'll
maybe
do
like
an
hourly
one,
but
then
those
only
stay
around
for
like
maybe
four
days
or
something
like
that,
and
then
they
start
clearing
out,
and
then
you
know
if
one's
there
maybe
daily
and
those
wants
to
stay
for
longer.
So
you
can
kind
of
mix
and
match
how
you
do
backups.
G
With
with
how
long
you
retain
in
how
often
you
schedule,
so
you
can
have
that
flexibility,
so
schedule
is
probably
sort
of
someone
gonna
ask
a
question
or
no
okay,
so
the
schedule
is
just
what
you
would
think
you
could
say:
I
want
to
do
daily
at
10:00
a.m.
I
want
to
do
it
hourly
at
you
know
every
you
know
at
when
the
clock
starts
whatever
15
20
30,
whatever
so
I
set
one
up
for
a
daily
backup
at
10
a.m.
G
and
then
your
targets
are
going
to
be
the
services
that
you
want
to
backup,
and
this
is
where
shield
like
I
mentioned.
It
earlier-
has
abstracted
targets
and
stores
in
such
a
way
that
makes
it
really
easy
to
implement.
But
then,
obviously
every
service
has
its
own
unique,
config
duration.
So
that's
where
we
have
this
configuration
field
where
you
can
drop
in
information,
that's
specific
to
that
service
and
that's
determined
by
whoever
writes
the
plug-in.
So,
however,
the
plug-in
wants
to
do
it.
G
That's
how
you
get
your
configuration
for
that
so
right
now,
it's
just
a
JSON
blob
that
we
drop
in,
but
in
the
future,
we'll
probably
make
it
a
way
where
the
plugins
will
actually
say
what
fields
they
need.
And
then
you
have
a
slightly
better
user
interaction
here,
rather
than
disrupting
in
a
JSON
blob
one
over
one.
Other
thing
of
note
here
where
it
says
remote,
IP,
port,
that's
gonna,
be
the
shield
agent.
That's
running
I'm
not
going
to
get
into
too
much
crazy
detail
here,
but
you
have
a
shield
daemon,
that's
the
actual
server!
G
That's
accepting
API
requests!
Then
you
have
a
separate
in
this
case
it's
a
docker
container,
but
it
would
be
its
own
via
typically,
and
this
is
where
you
would
enter
it:
the
IP
address
or
hostname
and
port
for
that
shield
agent.
That's
configured
it
that
that's
the
thing
that
will
go
and
actually
directly
talk
to
Postgres
to
my
sequel
to
ever
service
you're
backing
up
so
just
make
sure
that
that
box
can
talk
to
that
source
and
that's
good,
and
then
the
shield
Damon
needs
to
know
how
to
talk
to
that.
G
G
So
this
is
the
configuration
is
pretty
simple
here:
I'm
just
setting
where
I
want
to
store
that,
but
there's
also
other
fields
that
you
may
think
of
that
you
may
use.
But
those
are
all
documented
if
you
go
into
the
readme
here
and
we
just
go
to
like
file
system
and
we'll
see
up
here
where
it
says:
plugging
configuration
all
the
plugins
have
a
section
like
this,
where
it
will
show
you
the
fields
that
are
optional,
the
fields
that
are
required
and
then
maybe
what
the
default
configuration
is
she'll
go
out
of
the
box.
G
Just
assumes
that
it's
going
to
be
running
in
the
Bosch
release.
So
there's
a
few
fields
that
you
may
need
to
like
override
if
you're
running
it
not
inside
Bosch.
But
who
do
we
do
that
right?
Everyone
uses
Bosch,
so
yeah
and
then
the
last
little
piece
here
is
a
job
which
actually
pulls
in
all
the
different
pieces
that
we've
just
made.
So
you
give
it
a
name,
and
all
these
different
fields
have
a
summary
field
where
the
summary
is
kind
of
just
used
for
whatever
information
you
want
to
fill
in
there.
G
So
it's
not
actually
used
by
the
system,
it's
more
by
the
humans
that
are
looking
at
it.
So
so,
for
this
particular
setup,
I
made
like
a
just
like
I,
have
a
Postgres
database
running
and
I
have
and
just
some
dummy
data.
All
it
is
is
just
a
table
called
people,
and
then
it
has
three
entries
that
I'm
showing
here
so
I
just
said,
dummy
data
and
then
I
call
the
table
people
so
I'm,
not
calling
these
people
dummies,
but
anyways
realize
that.
G
So
if
we
go
to
I'm
going
to
use
PG
admin
and
I'm
going
to
connect
to
that
docker
Postgres
that's
running
and
then
what
I'm
going
to
do
is
to
show
we
have
this
people
table
I'm,
going
to
make
a
backup
and
then
I'm
going
to
drop
the
table
table
and
then
I'm
going
to
restore
it
just
so
you
kind
of
see
how
it
all
works
together
and
then,
after
that,
we'll
do
some
questions
and
answers
and
stuff
like
that.
So
all
right
so
like
this
job
is
scheduled
to
run
daily
at
10:00
a.m.
G
but
I
click.
This
little
button
here.
This
will
go
out
and
manually
run
the
job
for
us.
So
now,
if
I
go
over
to
the
dashboard
now,
this
was
a
really
quick
backup.
So
normally
you'd
see
it
under
running
tasks
here
and
in
this
particular
case
I'm
just
going
to
click
here
and
what's
really
cool
is
it
shows
you
all
the
output
that
you
actually
got
from
the
system,
and
this
is
really
helpful
for
debugging
purposes.
So
if
you
see
something
like
a
backup
fail,
maybe
things
aren't
communicating
properly
or
whatever
you
can
imagine.
G
D
G
Go
to
our
shield
database
that
I
made
and
then
basically
what
we're
really
gonna
be
looking
at
here
is
the
tables
back,
so
I
dropped
the
table
and
then
I
restored
it.
So
that's
kind
of
just
a
super
basic
workflow
and
then
a
different
concept.
So
apologize.
If
everybody
already
knows
all
this,
but
you
can
do
all
this
and
more
with
the
CLI
and
that
readme
and
that
dev
folder
in
our
project
will
show
you
how
to
go
through
I'm
using
the
CLI
for
a
bunch
of
search
with
that.
So
with.
C
So
we
for
our
customers
a
lot
of
times
what
we
do
is.
We
will
actually
do
exactly
that.
We
backup
the
CCD
be
the
Diego
DB
and
please
call
the
core
databases.
We
usually
use
this
to
back
them
up,
whether
it's,
unfortunately
on
Pola,
minus
QL
or
if
it's
actually,
fortunately,
on
Postgres
no
bias
there.
C
We
have
plug-ins
for
those
databases,
for
example,
in
whatever
the
customer
happens,
running
uses
to
back
up
the
systems
itself.
We
also
had
shield
also
has
a
special
mode
for
complete.
It
actually
is
first
class
concept
for
recovery
from
disaster
for
the
entire
Cloud
Foundry
itself,
and
then
cluding
washed
databases
and
stuff
like
that,
and
so
we
also
use
this
to
backup
like
the
core
Bosch
databases
and
all
of
those
things
so
that
yeah.
This
is
a
true
disaster
recovery
solution
for
Cloud
Foundry,
whether
it's
OSS
or
PCF.
I
C
D
D
D
D
C
You
like,
he
showed
the
basically
the
schedules
and
stuff
like
that.
If
you
have
some,
an
agent
backs
up
the
core
databases
at
a
certain
time
as
well.
Another
agent
backs
up
the
blob
storage.
At
that
same
time,
then,
you
could
actually
have
all
the
things
snapshot
at
around
the
same
time
right
and
then
you
would
minimize
you
or
inconsistency
surface,
but
yeah,
it's
better
than
nothing.
So.
I
A
A
Please
make
sure
you
line
up
your
projects
that
us
know
the
other
thing
is
I'm
looking
for
feedback
on
this
call.
So
if
you
have
feedback,
you
know
feel
free
to
ping
me
or
you,
we
or
anybody
I'll
chip
directly,
if
you,
if
you
have
feedback
on
me
right,
whatever
you
have
feedback
on
just
make
sure
you
provide
that
and
we
can
collect
it.
A
D
To
max
I
just
want
to
jump
in
and
say
that
part
of
the
great
part
of
zoom
is
video
like
to
encourage
next
time.
Hopefully,
people
install
their
video
cameras,
ryan
metallicy.
Oh,
let's
start
from
whence
you
know
this
person
is
talking
and
if
you
guys
want
to
know
more
about
zoom,
we
use
it
all
the
time.
D
G
A
And
again
guys,
this
is
MIT
license
so
nothing's
preventing
you
from
trying
it
really.
So.
Thank
you.
Stop,
anyway,
all
right,
everybody,
I
guess
we'll
talk
again
in
March
I
will
send
the
notes.
I
appreciate
everybody
joining
will
chat
again.
Cheers
don't
forget
to
submit
your
talk
proposal,
it's
Friday,
okay,
Bastien!
Thank
you.
Take
care
just.