►
From YouTube: Cloud Foundry Community Advisory Board [November 2017]
Description
Video from the monthly Cloud Foundry Community Advisory Board (CAB) meeting. Learn more at https://www.cloudfoundry.org/.
Agenda:
Calendar and tooling
Now every 3rd Wed of the month (see above)
See Zoom info above ^^^ in and the #CAB Slack channel
CFF update
CF-Summit 2018 CFP deadline approaching 12/08
Projects updates
Runtime PMC [Dieu]
Diego
Buildpacks
RootFS
BitService
Services API
Service instance sharing almost ready. Now PRing support into the CF CLI.
Async bindings design agreed upon by Open Service Broker API working group. Work on this can now be started.
BOSH [Dmitryi and Danny]
New release
Xenial stemcell work
Open Service Broker API [Alex Ley]
2 day face to face event with PMC and community at Red Hat Raleigh, NC, USA 28th - 29th November.
Please raise any issues or proposals you would like discussed here.
Remote attendees welcome to join for all or particular sessions. Agenda document here - feedback welcome.
325 users in OSBAPI slack come join!
Google launch service-catalog installer for k8s project
Proposal to add validation tool for service brokers to OSBAPI project
Extensions [Max]
Accepted for incubation: Service Fabrik
New proposals: CF-Scheduler from Pivotal
CF-Abacus v1.0 released and v2 inception planned 11/23
Clean up end of year
Community projects and presentations
SUSE’s stratos-ui
https://github.com/SUSE/stratos-ui
Incubation proposal document
Slack channel: #stratos (there you will also find the slides from the presentation)
Prepared questions from the community:
Cloud we submit the deprecated bosh-workspace project for removal from CF incubator?
A
A
A
A
A
A
All
right,
let's
get
started
and
then
we'll
get
to
her
when
she
gets
there.
So
I
think
so.
Apologies
for
this
little
hiccup
I
think
part
of
the
problem
is
maybe
the
conference,
since
we
only
used
it
once
a
month.
It's
causing
this,
but
I
think
zoom
has
a
way
to
use
letters
instead
of
numbers.
So
maybe
we
can
try
to
use
that
as
a
as
a
indirection,
so
I'll
see
if
I
can
set
up
one
for
xcf
cap
so
that
way
people
always
remember
it
anyway.
A
A
B
Yeah
sure
I
think
this
is
kind
of
at
the
intersection
of
Bosch
and
CF,
but
the
Diego
team,
for
example,
is
now
running
an
environment
where
a
console
is
entirely
removed.
So
that's
pretty
exciting.
It's
been
been
working,
fine
and
so
we're,
obviously
relying
on
Bosch
DNS
for
service
discovery
in
that
environment.
B
Some
things.
On
the
Diego
side,
we've
been
working
with
the
routing
team.
To
finish
out,
this
track
work
around
ensuring
integrity
of
connections
from
the
garage
application
back
ends
by
making
TLS
connections
and
verifying
the
instance
identity
credentials.
So
again,
that's
almost
done.
I
think
there's
just
one
little
router
bug
that
we
need
to
resolve
before
we
could
recommend
turning
it
on
experimentally,
in
some
environments,.
C
D
D
This
means
it's
finally,
finally
time,
if
you
still
have
privileged
containers
running,
you
need
to
fairly
urgently
figure
out
how
to
get
off
privileged
containers,
because
we
will
no
longer
have
the
ability
to
create
them,
so
that
hasn't
been
the
default
a
really
long
time
now
and
I
can't
I
can't
say
strongly
enough
how
much
better
unprivileged
containers
are
in
terms
of
security.
So
there
are
a
lot
of
reasons
to
move
anyway,
but
also
people
lose
the
abilities
with
rootless
to
even
make
them.
So
it's
time.
C
B
Can
hear
me
yeah,
I,
guess
a
quick
update
for
build
packs,
we're
introducing
an
engine
X
build
pack
soon
and
you'll
see
an
email
about
that
to
cff
that'll.
Take
some
of
the
use
cases
for
the
static
file
build
pack
that
don't
have
to
do
with
a
static
content.
You
know
those
those
use
cases
a
new
place
to
live.
We're
also
gonna
send
an
email
out
soon
about
what
the
next
distribution
of
the
route
FS
will
look
like,
and
what
the
timeline
is
there
for
it
becoming
available
so
that
people
can
migrate
over.
C
B
D
And
sharing
a
lust
which
will
be
pretty
good
and
we're
working
with
the
CLI
team
at
the
moment
to
do
some
PRS
to
get
support
in
that,
hopefully,
by
the
next
year.
A
few
weeks
time
and
last
night,
we
kind
of
agreed
with
the
open
service
broker
egg
API
working
group.
What
I'm
acing
the
bindings
could
look
like.
So
now
we're
ready
to
start
work
on
that
precinct.
C
B
I'm
too
excited
yeah,
so
we
are
finished
well.
We
basically
finished
with
all
the
feature
function,
functionalities
that
we
have
kind
of
been
promising
for
the
bit
service
and
are
starting
to
integrate
that
into
the
proper
I
apply,
and
hopefully
now,
with
the
help
of
this
year
from
each
integration
team.
Sata
said
at
one
point
in
time
down
the
road
we
might
be
able
to
make
the
bit
service
a
default
component
in
CF
release
or
in
CF
deployment.
B
I
should
rather
say
and
therefore
heading
it
into
the
critical
path
of
off
the
system
and
having
a
properly
defined
blobstore
API.
Once
once
that's
happening,
there
is
some
work
upcoming
for
adding
MPLS
because
so
far
we
have.
We
do
not
have
a
full
support
for
MPLS.
So
that's
an
ongoing
work
and
we're
also
what
to
do
some
more
work
on
optimizing
resource
matching
and
a
bunch
of
other
features.
C
So,
there's
lots
of
other
updates.
You
can
find
about
many
of
the
core
run-time
teams
in
the
or
application
runtime
teams
in
higher
rpm
cenotes.
Repo
few
highlights
there.
Cf
deployment
is
on
PWS,
fully
completely
transitioned
away
from
CIF
release.
Months
EWS
and
Davidson
Eddie
is
working
on
a
set
of
instructions
and
planning
to
send
out
an
email
declaring
one
dato
on
Siesta
claimant
I'm
very
excited
about
that
and.
C
A
Cool
Thank,
You
Julian
local
team
I
have
not
been
on
my
cell
phone
and
iPad,
so
I
wasn't
able
to
update
so
people
can
just
Jack
judge
jut,
like
a
line
on
your
thing.
What
you
what
you
said
on
the
agenda
that
would
be
nice.
This
was
postera
t
okay,
so
we
move
on
to
unless
there
any
questions,
I,
don't
see
anything
stacked
up,
we'll
move
on
to
Bosch.
A
F
Last
week
we
released
the
latest
version
of
Bosch.
It
includes
few
things
like
generic
configs,
so
you
can
get
multiple
configurations
to
the
director
and
let
it
deal
with
merging
includes
a
few
security
improvements
around
like
director
agent
communications.
We
continue
to
work
and
improve
some
of
the
internal
security
of
the
components
we're
working
on
bringing
in
the
new
boom
xenial
stem
cell.
F
It's
one
of
the
things
we're
working
on
and
there's
some
yeah
other
tracks
going
on
around
like
improving
how
we
work
with
links
kind
of
working
around
an
API
for
that
for
external
consumption
and
trying
to
finish
up
some
basic
support
for
ipv6
in
stem
cells.
I
think
that's
the
bulk
of
what
I
record.
A
A
E
Everyone
so
I
just
recap:
if
you're
new
to
the
open
service
broker
API,
because
it
always
causes
confusion,
that
is
actually
just
a
rename
of
Cloud
Foundry
Service
Worker
API,
that's
been
split
out
into
a
new
working
group.
We've
got
people
from
IBM
Red
Hat,
Google
s,
ap,
Fujitsu,
Microsoft,
Dell,
all
working
on
specification
and
testing
this
out
with
with
various
platforms,
including
our
boundary
and
most
the
other
big
one
is
kubernetes,
and
so
over
the
past
few
months
we've
been
doing
regular
face-to-face
meetups.
E
Over
the
past
year,
we've
got
another
face-to-face
meet
up
with
the
the
PMC
group
and
some
community
members
that's
happening
on
the
28th
to
29th
November.
This
is
going
to
be
a
Red
Hat's
office
in
Raleigh,
North,
Carolina,
so
I
think
the
the
kind
of
attendees
in-person
is
closed
too
close.
Now
because
we've
reached
capacity,
but
all
of
the
sessions
are
going
to
be
open
to
remote,
attendees,
Avaya,
zoom,
and
so
we've
got
an
agenda
document
I've
linked
to
in
the
in
the
cab
notes.
And
if
there's
anything
you
would
like
raise
that
this
face-to-face.
E
You
can
raise
your
proposal
and
add
it
to
the
agenda,
so
it's
a
good
chance
to
start
getting
involved,
or
at
least
come
listening
to
some
of
the
working
group
sessions.
These
are
normally
quite
productive.
A
few
days
so
recommend
that
other
things
to
call
out
is:
it
were
growing
community
that
are
using
the
open
service
broker.
Slack
we've
got
three
hundred
and
twenty-five
users,
it's
getting
fairly
active
in
there.
So
this
is
another
slack
to
join
I'll.
Put
that
link
in
the
car
as
well
and
to
other
interestings.
E
But
we
like
some
kind
of
reviews
on
this,
to
see
if
people
find
this
tool
usable
what
they
think
of
the
co
quality
and
maintainability
aspects.
So
feedback.
There's
some
questions
to
think
about
on
the
issue
that
I've
linked
to,
but
we'd
love
to
get
some
more
Service.
Worker
authors
trying
this
out
and
giving
feedback
before
we
merge
it
into
the
project.
A
Excellent,
thank
you.
Alex
for
detailed
update
and
I'll
mention
one
thing
I'm
actually
in
Europe
for
a
long
period
of
time
is
always
attending
worst
meetings
and
we
can
either
go.
I
was
at
SSC
and
and
I
saw
a
presentation
on
open,
serviceworker
API
by
Microsoft
and
giving
a
demo
using
kubernetes.
It
was
mind-blowing
to
see
that
right,
like
all
of
these
different
groups
working
together.
That's
that's
a
beautiful
thing.
So
great
semester.
B
A
Yeah
yeah
yeah
all
right,
so
let
me
give
a
quick
update
on
extensions
and
then
we'll
pass
it
to
suami
so
that
she
can
give
us
an
update
on
the
CFF,
which
we
usually
do.
First,
so
of
course,
towards
the
end
of
this
call,
we're
gonna
have
the
SUSE
presentation
of
Stratus.
Ui
I
saw
them
at
CEO
summit
in
Basel,
and
they
have
a
list
of
projects
that
they
want
to
bring
forward
so
I'll
introduce
that
later,
but
just
know
that
this
is
coming.
A
One
big
announcement
is
that
the
service
fabric
project
from
SAT
got
accepted
and
Ashish
is
here,
so
we
have
questions
for
him.
This
is
a
great
time
to
sort
of
raise
it
if
you
want
to
just
chat
with
them,
but
they
have
a
whole
team,
of
course
SAT,
especially
in
India,
pushing
forward
with
the
service
fabric
good
stuff,
coming
down
the
pipeline
for
this
one
more
thing
is
that
Scott
Lunger
from
pivotal
actually
has
a
proposal
for
a
presentation
he
made
before
the
on
the
CF
scheduler.
A
So
if
you
get
a
chance
to
review
that
soon
take
a
look
at
it,
it's
gonna
come
out
pretty
soon
and
then
for
backers.
There
is
a
inception.
That's
then
I
believe
it's
next
week
on
the
23rd,
but
will
will
be
announcing
it.
So
if
you're
interested
in
what's
going
to
happen
with
the
back
thanks
version
make
sure
to
attend
this
there's
worldwide
people,
so
we'll
probably
have
to
presentation
to
meetings
for
two
hours
each
with
a
break
in
between,
so
you
can
choose
which
one
you
want.
A
A
If
you
have
a
question
your
mute,
because
we
can't
hear
otherwise
we'll
move
to
to
suami
No.
Okay,
so
I
can
see
you,
oh
no.
This
is
the
first
time
my
writing.
Thank
you
for
being
here
and
taking
chips
place.
Maybe
you
can
give
us
an
update
on
what's
happening
with
the
foundation.
People
should
care
about
ensuring.
G
A
G
These
calls
based
on
Chris
and
chips,
recommendations
that
I
have
to
be
on
this
call,
so
at
least
for
now,
I
don't
have
any
updates
per
se
other
than
the
fact
that
the
nominations,
the
co-chair
nominations
for
CFP
is
due
today.
So
if
any
of
you
hasn't
done
finished
up
crosses
like
submitting
nominating
yourself
or
nominating
anyone
else
for
the
call
for
papers
co-chairing,
please
do
that.
I
will
be
presenting
the
link
across
in
the
mailing
list
and
on
slack
channel,
but
please
do
that.
I
think
it's
11:59
p.m.
G
Pacific
time,
if
I
remember
about
the
deadline
for
tonight
other
than
that
I
will
be
focusing
a
lot
more
on
the
community
activities.
If
you
are
on
the
Ambassador
Program,
you
probably
already
have
seen
an
email
or
you,
you
will
see
an
email
from
me.
Pretty
soon,
but
would
love
to
hear
in
general,
from
the
rest
of
the
community
as
well,
I
would
love
to
hear
feedback
on
how
things
have
been
going.
What
great
ideas
do
we
have
in
terms
of
what
we
can
do
better
in
terms
of
community
and
gearing
of
this
summit?
G
A
H
A
G
A
And
let
me
speak
about
this.
A
second
I
I
was
but
you're,
not
the
current
one
and
the
recent
one
in
Basel,
but
the
one
before
and
it's
very,
very
rewarding
thing
you
do
have
to
do
some
work.
But
what
of
the
idea
is
that
you
get
a
very
broad
view
of
what
people
care
about
and
what
they
are
submitting
and
you
get
to
choose
it.
So
you
get
to
put
together
the
program
for
a
particular
track
and
and
I
think
it's
it's
something
to
do.
G
I
think
just
to
add
on
that
I
really
agree
that
it's
a
very
rewarding
experience
and
it
also
adds
to
the
content
quality
for
the
summit
as
well.
I
think
we
have
much
fewer
nominations
for
the
node
trek
from
what
I
hear
from
the
events
team.
So
if
you
know
anyone
specific
for
the
node
track,
especially
please
do
nominate
them
or
please
do
reach
out
to
them
if
they
would
be
interested.
If
you
are
not
sure,
they'd
be
able
to
come
into
that
kind
of
responsibility.
G
G
So
if
you
know
that
you
can
take
all
the
responsibility,
please
do
that
and
we
will,
of
course
the
foundation
team
will
be
with
you
the
whole
time,
and
if
you
cannot,
if
you're
not
sure
what
to
do
or
how
to
go
to
that
kind
of
next
step,
you'll
definitely
be
there.
But
we
would
love
to
get
more
involvement
and
engagement
from
the
community.
All
that
yeah.
A
A
H
You
that
was
just
formed,
a
question
that
we
would
remove
brush
workspace
from
incubator
purgative.
How
can
organization
we
have
a?
We
have
a
chat.
We
had
a
chat
with
the
author,
Robin
Costa
and
we
emerged
a
depreciation
notice
into
the
ring
me.
So
maybe
this
would
this
could
go
back
to
catenary
community
or
maybe
clattery
attic
I,
don't
know,
but
I
think
it's
here
the
where
we
vote
for
such
the
decisions.
A
Not
so
sure
it's
an
interesting
one
because
it
was
there
before
the
extensions
got
started,
been
started
taking
over
the
incubator,
so
it
was
already
there.
So
I
think
I
think
the
author
is
already
in
it
as
far
as
I
know,
if
you
let's
ask,
let's
ask
by
email,
I
think
Yui
has
done
a
few
where
she
moved
stuff
to
addict
by.
If
I
don't
want
to
miss
with
you
Yui
but
I.
Remember
you.
You
essentially
sent
an
email
saying
that
it's
gonna
move
to
a
date.
That's
the
air!
A
A
A
You
know,
since
you
already
had
talked
to
the
author,
that
sent
it
since
I'm
not
overseeing
it
yet
and
then
I'll
certainly
approve
I
mean
agree
with
you
and
then
let's
see,
if
anybody
has
any
objection,
if
there's
no
objection
by
the
end
of
the
week
and
we
can
work
with
Chris
Chris
Clark
is
on
the
call
he's
great.
He
can
help
us
with
a
lot
of
this
he's
part
of
the
founders
yeah
I'm,
always.
A
Okay,
so
let
me
quickly
introduce
this
another
project,
but
I
think
there's
gonna
be
a
suit.
Oh
sorry,
somebody
wants
to
add
no
okay,
so
at
the
a
lot
of
you
should
probably
know
Cornelius
Schumacher.
He
is
the
de
souza
that
actually
spent
some
time
caring
with
us
and
Bosh,
and
he's
done
quite
a
bit
already
in
foundry.
So
he's
he's
a
dojo.
A
You
know
graduate,
but
at
the
Basel
summit,
I
spent
a
lot
of
time
chatting
with
him
and
also
a
bunch
of
his
colleagues
from
Sousa,
and
they
have
a
series
of
project
and
they're
gonna
present,
one
close
to
Otto's
and
Canadians
will
introduce
it,
but
the
one
thing
I
wanted
to
mention,
which
I
learned
that
I
didn't
know
about
Susa.
That
I
think
it's
worth
mentioning
because
I
don't
know
if
he's
going
to
talk
about
it
is
that
it's
not
only.
A
Of
course,
a
huge
you
know
just
true
for
or
for
Linux,
and
they
have
tons
of
expertise
and
contributions
or
but
what's
interesting
about
Zeus
is
that
their
business
model
is
itself
okay,
so
everything
they
do
is
open,
but
their
business
model
and
their
processes.
So
I
think
it's
a
fantastic.
You
know
set
of
colleagues
and
engineers
that
are
gonna
help
join
and
they're
gonna
talk
about
this
particular
project,
but
there's
at
least
two
more
projects
that
they
also
are
considering
submitted.
A
F
Great,
thank
you
yeah.
We
sometimes
call
ourself
the
the
open
open
company.
So
that's
that's
what
I
told
you
at
the
summit
and
it's
kind
of
cheesy
but
I-
think
it's
actually
describing
how
we
are
working
quite
well,
and
part
of
that
is
of
course
working
as
upstream
as
possible,
and
that's
why
we
are
talking
today
about
the
the
straightest
UI.
So
this
is
our
fully
open
source
UI
for
Cloud
Foundry,
and
we
are
proposing
this
for
incubation.
F
As
an
extension
in
cloud,
foundry
I
sent
the
document
to
the
CF
def
mailing
list
earlier
today,
so
this
should
be
there
also
with
the
links
to
the
for
document
yeah,
and
we
have
Nia
mcdougal
here.
Who
is
the
lead
for
the
team
working
on
the
straightest
UI
and
he
will
give
us
some
more
information,
some
introduction
and
also
a
demo.
So
we
can
now
see
that
and
I
will
hand
over
to
near
then.
I
I
Awesome,
thank
you
very
much.
Okay.
So,
as
clearly
said,
and
dr.
max
introduced
I'm
going
to
talk
a
bit
about
Stratus
UI,
so
this
is
a
user
interface
forward.
Cloud
Foundry,
we'll
talk
about
that
and
we
have
submitted
this
to
the
SIV.
Extensions
will
be
that
we
considered
for
acceptance
of
this
clock.
Wheel
is
just
to
to
kind
of
tell
you
a
bit
more
about
what
it
is.
I
I
I
So
just
touch
on
a
couple
of
things
that
we
put
in
the
proposal
for
this
if
extensions
track,
so,
firstly
some
assumptions.
The
the
reason
that
we're
kind
of
proposing
this
is
is
under
the
assumption
that
users
there
are
some
desire
to
access
the
functionality
of
Cloud
Foundry
through
a
web
user
interface.
In
addition
to
what
you
would
get
through
the
CF
client
API
clients
did
I
also
that
you
know,
having
kind
of
a
fairly
comprehensive
user
interface
may
or
will
help.
I
You
know,
maybe
bring
more
people
on
board,
particularly
maybe
some
of
the
sort
of
country
who
are
those
may
not
may
not
use
it
intimidated.
Maybe
some
bit
strong,
but
some
some
users
find
find
user
interface
is
particularly
initially
a
good
way
of
kind
of
getting
plugged
in
understanding
what
they're
saying.
I
So
I'll
come
on
to
that
next,
one
I
guess
we
almost
make
it
fairly
flexible
to
deploy,
but
I'm.
Also,
you
want
to
make
sure
it's
to
global
by
Bosch
and
as
a
kind
of
hungry,
app
and
one
one
difference,
I
think
maybe
to
some
other
things
that
you
may
have
seen
is
we
with
we
try
to
make
sure
that
you
can
manage
multiple
cloud.
Foundry
instruments
is
through
through
one
UI,
so
it's
not
a
you
know.
I
One-To-One
here
you
can,
you
can
look
at
multiple
cloud,
foundry
deployments,
attributions
and
kind
of
manage
those
and
we've
also
bearing
in
mind
today.
We
want
to
have
others
take
this
use
it
we're
trying
to
make
sure
it's
easily
themed.
At
the
moment,
I
can
show
you
a
Sousa
theme,
but
obviously
other
people
may
or
will
want
to
change
that,
and
we
all
sort
of
make
sure
that
it's
easy
for
people
to
extend
to
swap
this
out
at
noob
ascend,
very
quickly,
antico,
so
I
think
the
top
ones
very
important
for
us.
I
We
we
want
to
make
sure
we
only
work
against
the
the
public
endpoints
for
Clara
foundry,
not
having
to
dig
in
20
internal
databases
or
components
through
private
interfaces.
So
we
work
clearly
at
the
you
know,
the
API
level
with
them
and
using
the
SSH
endpoint,
for
example,
in
the
Doppler
logging
endpoint
and
we're
not
going
to
add
any
features
that
might
size
20,
specific
distribution.
I
So,
as
I
said,
we've
tried
to
make
it
fairly
flexible
in
the
way
you
can
deploy
it
so
go
check
out
yourself.
You
can
just
check
out
our
repo
and
ocf
push
to
push
it's
a
foundry
app.
We've
got
a
Bosch
deployment
wave
point
of
our
Bosch,
also
for
our
own
products,
where
you
can
deploy
it
in
communities
with
home,
or
you
can
just
run
it
in
a
in
docker
using
docker
compose.
So
we've
tried
to
make
it
as
flexible
as
possible
to
to
deploy
the
UN
device.
I
I
come
on
to
a
demo,
but
very
quickly,
sort
of
touching
on
the
features
at
a
high
level
authentication.
So
we
do
work
against
the
UI
a
so
you
do
have
to
login
to
the
console
and
we
differentiate
between
administrators
and
and
sort
of
regular
users.
We've
tried
a
way
to
manage
endpoints.
We
used
two
term
endpoint
at
the
moment,
really
just
means
Cloud
Foundry
clusters,
but
down
the
line
it
could
mean
something
you
know
more
generic.
This
is
a
way
that
people
can
connect
in
different
countries
and
connect
with
their
credentials.
I
Come
on
to
that.
We
provide
an
application
of
view
where
you
can
see
all
of
your
applications
and
we
kind
of
consolidate
those
across
multiple
boundaries.
You
can
drive
into
a
single
application
and
get
application
view.
We've
done
a
fair
amount
on
being
able
to
kind
of
create
apps,
so
the
kind
of
the
equivalent
of
safe
push
three
for
the
UI
and
then.
Lastly,
we
have
more
of
the
management
of
Clara
friend
where
you
can
dive
in
and
view
various
metadata
about,
or
your
Clara
foundry
cluster
okay.
I
So
it's
a
bunch
of
screenshots
here
which
I'll
skip
over
I'll
come
back
to
I
can
make
this
the
slides
available.
I
put
the
screenshots
in
here
office,
leader
I'm,
going
to
show
the
demo,
but
if
you're
looking
at
these
offline,
then
that
will
make
more
sense.
You
bring
it
up.
Hopefully
so
I'll
give
you
a
quick
demo.
I
won't
take
too
much
of
your
time,
but
I
want
you
to
kind
of
see,
see
some
of
the
cool
features.
I
Just
you've
got
a
feel
for
put
in
that
and
if
it's,
how
mendl's
come
back
and
talk
a
little
bit
about
how
it's
built
and
how
we've
tried
to
make
it
extensible.
So
this
is
the
Sousa
look
and
feel
that
I'll
I'll
demo
I
think
you
know
if
we're
gonna
propose
this
as
a
session,
that's
accepted,
then
no
ceased
his
skin.
So
here's
a
here's,
a
kind
of
example
of
a
cloud
foundry
theme
that
I
knocked
up
that
would
I
think
we'd
make
the
default.
So
it's
fairly
easy
to
kind
of
change.
I
The
look
and
feel
I
don't
know
if
this
one
for
now
so
say,
I
log
in
to
the
system
we're
gonna
authenticate
with
the
UI
a
we're
fully
localized.
So
I
can
change
the
locale
where
any
have
variants
of
English
at
the
moment.
But
it's
very
easy
to
add
in
you
and
your
language
packs
or,
although
close
to
the
UI.
I
This
so
you've
actually
deployed
the
UI
within
Cloud
Foundry,
as
well
as
accessing
the
console
through
this
different
instance.
I'll
keep
this
fairly
quick,
so
endpoints.
This
is
where
I
connect
up
and
register
multiple
boundaries.
So
here
the
one
I
was
showing
you
was
actually
sa
piece.
Hana
platform,
Clara
foundry
and
I've
got
a
second
one,
which
is
Souza's
Claire
foundry,
that's
in
beta,
which
is
currently
disconnected
so
I'm.
Only
seeing
application
from
one
I
can
go
in
and
I
can
connect
that
up
so
now
I
have
to
registered
for
about
applications.
I
I
should
see
the
applications
aggregated
from
both
foundries
so
with
administrators
are
able
to
add
in
new
endpoints
system
and
then
every
user
who
logs
in
is
able
to
connect
with
their
credential.
So
they
only
see
their
the
view
that
they're
allowed
to
see
on
to
a
particular
cloud
foundry.
So
we
do
come.
You
know
honor.
All
of
that
level
of
access.
I
won't
talk
too
much
about
this.
This
is
the
application
view
we
do
support,
grid
and
list.
You
can
change
the
way
you
sort.
You
know
all
the
stuff
you
might
expect.
I
You
can
search
for
an
app.
You
can
straight
down
to
just
looking
at
one
particular
Cloud
Foundry,
and
then
you
can
choose
an
organ
space.
So
that's
you
know,
that's
looking
looking
the
applications,
let
me
undo
this
deploy
new
app,
so
I
can
add
a
kind
of
scalar,
snap
or
I.
Can
kind
of
deploy
an
app,
so
this
is
where
we've
tried
to
allow
users
to
do
the
equivalent
of
CF
push
push
but
through
the
UI.
I
So
let
me
just
go
ahead
and
deploy
quick
app,
so
I
can
choose
the
which
Claire
for
Andrew
I
wish
in
the
organ
space
I
can
deploy
either
from
get
at
the
moment
or
a
local
file
a
folder.
So
you
can
run
sure
here,
but
you
can
drag
and
drop
a
folder
or
an
archive
file
onto
this
UI
here
and
we'll
read
that
in
and
we'll
check
for
a
see
if
ignore
and
all
those
kind
of
things
to
make
sure
we
do
the
right
stuff.
I
And
then
you
upload,
the
bare
minimum
or
I
can
actually
browse
with
those
icons
or
sensitively.
I
need
to
enter
a
github
project
or
a
euro
for
any
get
protectors
as
well
and
publicly.
So
let
me
just
choose
one:
that's
one
of
mine,
so
we'll
go
out
and
we'll
fetch
the
list
of
branches
and
stuff
like
that.
Give
you
a
bit
of
information
if
you
click
on
those
you'll
get
links
out
to
github
all
that
kind
of
stuff.
I
If
I
hit
deploy,
we
will
clone
that
in
the
backend
and
then
we
use
the
CF
client
to
actually
push
that
to
to
the
Claire
foundry
and
will
stream
the
log
here.
So
this
is
done
all
over
WebSockets
them
securely,
so
I
could
sit
and
watch
this
or
I
can
dive
into
the
app.
So
this
is
the
application
view
that
I
talked
about
very
quickly,
and
this
is
where,
for
the
individual
app,
you
can
kind
of
see.
What's
going
on
so
a
bunch
of
metadata,
you
can
see
a
number
of
instances
we've
got.
I
I
can
see
that
it's
currently
staging
all
good
stuff
like
like
that
this
is
updated.
Periodically
I
can
get
a
log
stream
again.
This
is
done
over
WebSockets.
So
we
kind
of
view
this
in
real
time.
I
can
see
of
any
service
instance
is
abound.
I
can
look
at
my
variables,
see
the
events
or
all
that
kind
of
stuff
which
is
so
just
nice
up.
Here
we
have
the
various
actions,
these
change,
depending
on
the
state
of
the
app.
So
you
can
see
it's
gone
green
now,
so
they've
changed
I
can
get
some
CLI
info.
I
So
if
you
want
to
transition
from
the
web
UI
detail,
I,
we
give
some
contextual
ice
cut
help
there.
This
is
now
running.
You
can
see
I'm
sure
the
instance
says
I
could
choose
to,
and
this
scale
is
up
and
or
should
refresh
this
in
a
second.
So
we
do.
You
know
we
do
the
sort
of
basic
kind
of
first
cut
of
stuff
that
developers
hope
you'll,
find
useful
and
make
it
much
easier
if
them
to
come
and
get
started.
I
I
I
So
we
can
show
the
Service
Catalog.
You
can
pick
service
create
an
instance.
You
can
set
service
parameters
and
tags
all
that
kind
of
stuff.
Interesting
I'll
speed
up
a
little
bit,
Cloud
Foundry.
So
this
is
kind
of
a
second
kind
of
view
where
you
can
dive
down
individual
Cloud
Foundry,
because
I've
got
multiple
registered,
we
kind
of
kept
top
level
tiles.
I
fear
only
had
one,
then
you
know
you'd
go
straight
through
to
the
one
you
had
and
that
moment
you
kind
of
drill
down
and
again
gets
from
top
level
metadata.
I
You
can
create
walls
and
spaces,
you
can
drill
down
into
the
organizations
in
the
spaces
and
then
you
view
the
applications,
substances,
routes
and
users.
You
can,
you
know
unwrap
and
delete
routes
and
tidy
up
things
at
the
space
level.
Again
we
shall
see
like
commands
users,
you
can,
let's
see
yeah,
we
can
manage
user
access
to
individual
space
and
orgs
here.
So
I
can
either
do
it
individually
by
you
know,
removing
a
particular
role
off
of
a
user
or
we
have
a
UI
that
should
go
through
a
new
kind
of
bulk
level.
I
User
changes
for
accessing
orgs
and
spaces
I
think
back
up
at
the
top
level,
okay
space
in
orgs,
okay,
oops,
okay,
so
we
do
also
show
some
some
other
kind
of
top-level
Cloud
Foundry
metadata
again
at
the
moment
this.
This
is
kind
of
a
read-only
view.
Much
of
this,
so
you
can
sort
of
stream
the
the
firehose
obviously
see
after
yeah.
You
can
turn
on/off
different
aspects
of
the
firehose
I.
I
Can
you
know
if
you
feature
flags
what
Bill
packs
I've
got
installed
the
specs,
and
so
you
see
what
the
suits
are
stacking
this
one
and
you
can
check
these
security
groups.
So
this
is
a
kind
of
a
cut
of
first
level
of
Clara
French
arrangement,
there's
kind
of
more
that
we're
adding
in
the
background
as
we
go.
So
that's,
hopefully,
a
quick
whizz
through
through
all
we
have
a
bunch
of
stuff
aimed
at
developers
to
allow
them
to
see
their
apps.
Add
new
apps
manage
the
apps
they've
got
in
here:
delete
apps
Galya.
I
I
I
I
I
So
we
have
a
web
front-end,
which
is
a
single
page,
angularjs,
app
and
back-end,
which
is
running,
go
and
we
use
a
database
which
can
be
Postgres,
my
sequel,
SQL,
Lite
and,
depending
on
how
you
want
deploy
it,
which
just
stores,
endpoint
information,
we
don't
store
any
other
information
other
than
which
endpoints
you've
got
registered
and
we
store
some
encrypted
tokens.
So
you
don't
have
to
reconnect
every
time
you
log
in
and
really
what
this
kind
of
API
server
does
as
well
as
manage
those
endpoints.
I
It
proxies
for
calls
through
to
the
appropriate
back-end
and
that's
in
the
appropriate
authentication
headers
for
us.
So
I
won't
talk
through
this,
but
it
makes
sure
that
when
the
friend
asks
say
the
list
of
apps
will
go
out
to
all
of
the
cloud.
Foundries
you've
got
registered
with
the
appropriate
tokens.
If
any
tokens
expired,
we
will
automatically,
you
know,
get
a
new
access
token
before
you
make
the
call
again
I
go
get
responses
and
send
them
back
the
front
end.
I
So
just.
Lastly,
you
know
we're
talking
about
trying
to
make
this
extensible
we've
tried
to
build
all
kind
of
lay
that
the
code
out
and
put
things
together
in
a
way
that
people
can
add
and
change
components.
So
much
of
the
functionality
that
I
showed
you
around
say,
deploying
your
applications
or
SSH
in
into
apps
are
done
as
plugins.
That
can
be
turned
on
or
off.
If
you
don't
want
that
functionality,
the
souza
branding,
for
example,
is
also
a
plugin
that
you
can
swap
out
for
another
one.
I
I
I
So
kind
of
examples,
what
you
can
do,
hopefull
if
you
can
think
back
to
what
I
showed
you
it's
very
easy
to
add
new
top-level
menu
items,
to
extend
out
many
of
the
views
to
add
a
new
tab.
So,
for
example,
the
kind
of
application
view
all
of
those
tabs.
I've
done
this
sort
of
plugins
and
you
can,
you
can
add
new
tabs.
You
can
get
rid
of
tabs,
you
can
have
tabs
to
both
apps
and
Cloud
Foundry.
I
I
So
here's
the
current
set
of
components-
we've
got
a
lot
of
the
kind
of
cool
stuff,
is
in
some
of
these
top-level
Cloud
Foundry
and
have
core
components,
but
we
starts
to
pull
out
more
functionality,
as
I
said
into
some
of
these
separate
components:
okay,
so
that
was
it.
Hopefully
I
gave
you
a
good
flavor
of
what
we've
done
that
we've
tried
to
build
in
a
way.
That's
extensible
that
others
can
take
contribute
to
by
either
adding
new
functionality
or,
you
know
replacing,
say
a
theme
with
their
own
theme,
I'm
available
in
slack.
A
Yeah,
let
me
be
the
first
to
say:
this
is
pretty
amazing:
I
mean
wow
I,
think
there's
no
excuse
not
to
have
a
UI
for
Cloud
Foundry
or
start
your
own
company,
and
you
have
a
UI
you
can.
Just
this
is
really
cool.
Let
me
see
if
other
people
have
questions
or
if
I'm,
the
only
one.
That's
pretty
impressed
by
this
anybody.
If
you're
trying
to
ask
a
question
you're
new,
so.
H
H
I
Doesn't
at
the
moment,
but
that's
my
roadmap
very
easy
to
add
in
for
us.
So
that's
one
of
the
areas
that
we
are
kind
of
active
building
out
is
improving
the
the
support
for
services,
service,
catalog
and
I'm.
Aware
that,
yes
being
able
to
you,
know
give
to
that
link
and
then
manage
your
service
would
be
very
useful,
so
yeah
it.
H
I
A
I
No,
yes,
SUSE
is
very
open.
You
know
one
of
the
first
things
we
did
make
sure
wait
state
this
whole
UI,
it's
all
out
there
in
the
open.
You
can
take
it,
you
can
I
believe
you
can
do
whatever
you
want
with
it
and
we've
got.
Hopefully
you
contribute
back,
hopefully
yeah
yeah,
that's
what
that's.
What
we're
looking
for.
So
the
whole
community
kind
of
benefits
from
the
improvements
and
changes.
Other
people
make
cool.
A
I
Although
they're
kind
of,
although
the
separate
now
view
it's
not,
the
administrators
can
only
see
that
Cloud
Foundry
view,
so
both
developers
and
administrators
can
go
into
both
of
those
views,
but
they
will
only.
They
will
only
see
what
are
at
sea.
So
an
administrator
will
see
a
lot
more,
particularly
in
that
Clara
foundry
view.
But
a
developer
will
see
the
information
on
developers
can
go
into
that
org
space
view
and
manage
permissions
for
users
if
they
have
the
right
permissions
within
that
space
or
org.
A
I
I
I
guess
not
yeah
I
mean
so
the
I
guess
the
kubernetes
project
has
coop
dashboard
right,
which
is
a
very
rich
UI
and
I.
Think
for
me,
coming
into
Clara,
foundry
I'm,
not
saying
Stratos
is
its
comparable
at
all,
but
I
think
if
we
can
have
something
that
at
least
we've
got
a
you,
I
am
on
Cloud
Foundry,
that's
great
because
clearly
cube
Nettie's
is
marching
forward
with
cube,
but
I'm
not
sure
what
we
would
bring
in
for
the
run
time.
I
A
So
just
FYI,
as
you
think,
of
your
question
and
what's
gonna
happen
next,
is
that
we're
gonna
go
through
the
process
of
review
and,
of
course,
feedback
to
Cornelius
and
its
team.
And
then
hopefully
we
go
to
vote
and
if
it
gets
incubated
and
it's
gonna
transfer
the
assets
to
the
foundation
and
into
the
incubator
and
so
on.
So.
A
B
I
So
we
we
are
doing
that
collation
in
the
in
the
front
end.
So
beyond
a
certain
point
you
will,
you
will
have
problems,
we've
I
think
we've
had
you
know
a
couple
of
thousand
apps
and
not
had
any
any
issues.
I
think
it
I'm
interested
to
hear
from
people
up
and
custom
used
cases
where
maybe
they've
got
you
know
significantly
more
apps
and
I
think
my
have
to
consider
a
different
approach
to
that
we
use.
I
You
know
we
use
various
caching
mechanisms
to
try
maintain
to
maintain
stuff
so
there,
but
there's
stuff
we
can
do
if
performance
comes
a
problem.
We've
not
seen
that
at
the
moment
the
browser
copes
quite
well,
but
if,
if
people
are
seeing
apps
more
or
more
than
maybe
2000
or
so
apps,
then
yeah
I
think
it
stops
to
slow
down.