►
From YouTube: Cloud Foundry Community Advisory Board [July 2019]
Description
1. External DNS Connector for Cloud Foundry [1] by David Grizzanti of Comcast
2. Stratos UI Update - now with Kubernetes support [2] by Neil MacDougall of SUSE
A
A
A
I
think
it's
being
recorded
excellent,
welcome
to
Cloud
Foundry
July
community
advisory
board.
I
guess
the
meeting
is
being
recorded.
So
if
you
sort
disapprove
of
that
I
guess
you
have
to
drop
with.
That
said,
we
have
a
nice
agenda
today
and
we'll
get
started.
I'm
actually
very
excited
about.
You
know
some
of
the
talks,
oh
so
that
should
be
good.
Let's
see
if
we
can
give
them
as
much
time
as
possible,
we
usually
go
and
do
kind
of
a
regular
set
of
checks.
A
B
I
will
keep
it
short
and
sweet.
The
schedule
is
now
live
it's
on
the
website,
so
you
can
take
a
look
at
it
and
start
adding
sessions
to
your
agenda.
There
are
a
lot
of
pre-summit
activities,
even
though
the
summit
actually
starts
on
September
11th,
which
is
17
months
away.
There
are
a
lot
of
these
zero
activities
like
unconference
contributors,
some
ID
user
day,
certification
hackathon.
So,
let's
check
up
on
all
of
those
in
the
agenda
document
or
the
meeting
notes
documents.
B
So
take
a
look
at
those
and
make
sure
that
you
are
attending
planning
your
travel
accordingly,
so
that
you
can
attend
one
or
more
of
those
Stasia
activities.
Just
quick
reminder:
the
standard
registration
ends
on
August
2nd,
so
the
prices
will
go
up
from
August
3rd.
So
if
you
are
not
registered
yet
I
would
highly
recommend
get
registered.
Now,
if
you
are
a
current
or
a
past
contributor,
there
is
a
code
where
you
can
register
at
0
go.
B
A
Excellent
very
efficient
think
he's
gonna
again,
I
guess
I'll.
You
know,
rien
cyst
on
the
hackathon
be
helped
run
that
again.
So
it's
it's
a
great
opportunity
for
you
to
happen.
Something
you'll
have
a
day
and
there's
good
prizes
and
you
get
to
be
to
go
in
on
stage
and
chicken
with
happy
addy.
So
that's
that's
what
something
I
think
we.
B
A
A
C
C
The
idea
is
to
have
using
github
issues
and
projects
with
them
somewhat
more
systematic
format
to
track
those
proposals
where
to
find
them
who
to
contact
expectations
around
deadlines
for
commentary.
That
kind
of
thing
and
statuses,
of
course,
like,
if
they're
still
under
review,
if
teams
working
on
them
that
kind
of
thing
yeah,
so
definitely
thanks.
Just
wanna
and
chip
and
Li
Chen
here
live
Atal
or
helping
actually
make
that
happen.
Definitely
appreciate
it.
A
few
other
things
to
note.
C
Speaking
of
proposals
we've
had
Necedah
breaking
changes
for
safe
deployment
version,
10
proposed
should
be
getting
released
soon.
I
think
most
of
the
discussions
died
down
on
that
document
also
had
a
minor
release
of
the
CLI
I.
Think
the
main
feature
there
is
some
experimental
support
for
initiating
upgrades
of
service
instances
through
the
CLI.
So
that's
pretty
exciting.
Some
of
the
updates
know
Kathy
is
continuing
to
work
on
better
States
and
reporting
around
rolling
deployments
tactic
of
all
the
proposals
and
that
proposals
repo
address
those
I
think
there's
still
time
for
some
commentary
on
those.
C
If
you
haven't
had
a
chance
to
take
a
look
at
those
one
thing
of
note,
UAA
apparently
has
some
dramatic
performance
improvements
on
its
users
end
point.
So
if
you've
been
using
that
frame,
kind
of
polling
or
synchronization
time
systems,
some
other
things.
Diego
has
closed
up.
Some
of
the
last
non
TLS
communication
inside
of
fly.
Fabri
we've
had
this
little
file
server
component
to
deliver
some
fairly
static
assets
that
had
previously
been
overplayed
HTTP.
C
They
also
recently
had
a
internal
team
intention
about
the
next
set
of
priorities,
so
I
will
be
getting
some
up
a
schedule
so
that
seen
some
other
things
speaking
of
scale
of
the
networking
program,
is
continuing
to
improve
the
scale
on
which
they
can
support.
Various
new
integrations,
so
kind
of
weighted
routing
for
traffic
ingressing
to
the
platform
and
then
also
continuing
to
support
better
scale
for
the
still
experimental,
sidecar,
client-side
load.
Balancing
that
takes
takes
advantage
of
ESI
coverage
there
and
all
in
those
lines.
C
We've
we've
had
something
of
a
gap
between
Linux
and
Windows
apps
in
terms
of
having
goo
routers
do
TLS
to
application
instances
and
the
garden
windows
team
has
been
making
great
progress
on
actually
using
nginx
to
absorb
some
of
the
Envoy
configuration
and
provide
that
on
Windows,
given
that
envoy
is
still
pretty
unstable
and
not
really
supported
on
with
it.
It's
all.
A
A
Is
it
anyone
unless
it's
27
but
I'm,
not
sure,
but
that's
what
they
said
and
then
they
mentioned
that
the
director
team
is
main
focus
right
now
is
working
on
new
endpoints
to
improve
the
behavior
of
Bosch
start/stop,
recreate
restart
types
of
come
in
so
very
small
updates
on
Bosch,
but
I
guess
they're
training
alone,
I'm,
not
able
to
answer
any
questions
on
Bosch
at
this
point.
So
maybe,
if
you
have
questions
you
can
ping
Morgan
or
Marco.
Thank
you
and
for
extensions
briefly.
A
I'll
mention
that
you
know
a
lot
of
the
projects
have
graduated,
or
at
least
one
of
them
is
moving
to
attic.
I
keep
them
there,
I'll
remove
it
for
next
time.
I
said
that
last
time,
but
I'll
do
it
this
time
and
we
have
a
demo
from
Stratos,
which
is
probably
our
most
that's
whole
project
and
you'll
see
it's
actually
quite
good
and
me'll
is
here
to
give
us
some
of
where
he's
moving
the
project
he's
also
looking
to
graduate.
So
that
will
graduate
you.
A
So
if
you
have
projects
that
you
want
to
submit
to
extension,
you
let
me
know,
and
with
that
we'll
stop
here
and
see.
If
there's
any
questions
on
you
know,
communities
start
for
projects,
otherwise
we'll
ask
David
to
take
over.
So
he
can
present
this
from
the
Comcast
team
and
it's
presenting
a
external
DNS
connection
for
my
laundry
I.
A
D
Cool
okay,
let
me
get
started
so
I.
Think
a
few
few,
the
Comcast
folks,
including
myself
around
two
months
ago,
we
were
gonna
talk
about
two
projects.
I
think
you
only
got
a
chance
to
talk
about
the
vault
plug
app,
so
I'm
gonna
spend
some
time
today
talking
about
some
DNS
connector
work,
we've
been
doing
or
that
was
proposed
by
some
of
the
Cloud
Foundry
operators
here
Comcast.
A
D
I'll,
keep
it
off
presentation
load
them
all
right.
Perfect,
not
wait.
Okay,
cool,
so
problem
statement,
I
think
in
this
leg,
Ana
I'm
coming
in
as
a
developer,
I
think
some
of
these
features
were
described
to
me
and
some
of
the
developer
folks
from
the
operators
as
problems
that
they
have
found
with
or
people
that
developers
using
Cloud
Foundry
have
found
with
some
things
here
at
Comcast
were
just
generally
so
from
a
developer's
perspective.
D
You
know
your
application
is
only
bound
to
a
single
Cloud
Foundry
foundation,
so
not
necessarily
that
portable
and
the
DNS
name
is
tied
to
the
name
of
the
application.
So
what
we
started
looking
at
is
there's
a
project
called
external
DNS.
It's
a
kubernetes
incubator
project
and
if
the
premise
of
that
project
is
that
configures
external
DNS
servers
so
AWS
1:53
GCP,
it's
got
a
whole
list
of
them
for
kubernetes,
ingress
and
services.
So
our
proposal
was
to
look
at.
D
Could
we
extend
that
project
to
also
support
Cloud
Foundry
so
that
way,
you'd
get
the
benefit
of
having
all
the
integration
with
the
existing
DNS
providers
and
extend
that
to
Cloud
Foundry,
so
70
functionality
of
external
DNS
to
include
cloud
hugger
as
a
source
type
and
that
will
basically
extract
DNS.
So
the
fqdn
s
are
not
tied
to
a
single
foundation,
so
the
general
idea
would
be.
Let's
say
you
have
two
Cloud
Foundry
sites
and
you
have
this
external
DNS.
D
D
D
D
D
And
you
see
this
ok
yeah
looks
ok
well,
so
one
of
the
challenges
I
had
with
this
was
just
trying
to
record
a
video
using
our
Cloud
Foundry
instance
I'm,
not
showing
too
many
host
names.
So
the
demo
is
a
little
sparse
since
it's
being
recorded
but
I'll
go
through
and
then
we
can
kinda
just
explain
what's
happening
so
in
the
let's
say:
I
have
no
apps
deployed
on
the
cloud
country
that
I'm
using
no
apps
no
routes
so
I
push
a
new
app
I
sped
this
up,
because
it
takes
a
long
time.
D
Say
I
have
that
new
app
and
that's
some
some
random
generally
a
name,
and
then
this
is
the
DNS
name,
I
chose,
which
is
just
a
zone
that
we
had
here
at
Comcast
that
we
use
for
testing
and,
let's
say
I,
add
another
route
to
that.
So
in
the
end,
I
have
two
routes
for
my
app
this
random
name
and
then,
let's
say
demo
site
in
theory
this
this
first
one
wouldn't
be
mapped
this
time.
D
I
just
wanted
to
hide
what
the
actual
Cloud
Foundry
domain
here
is
a
Comcast,
but
the
the
general
idea
is
that
if
I
want
to
keep
this
demo
site
dot,
illness
not
kept
SPS
that
Comcast
that
net
name
portable
across
Cloud,
Foundry
grande
gyms
I'd
like
to
map
this
to
the
DNS
provider
outside
of
cloud
foundry.
So
now
that
this
is
these
routes
are
there
and
the
app
is
up
and
running
external?
The
DNS
is
basically
running
it
in
the
background
the
default
is
it
runs
every
minute,
so
it's
gonna
look
and
see.
D
Also
it's
not
nothing's
gonna.
It's
not
gonna
work
just
because
the
DNS
isn't
resolved
yet
I,
basically
waited
a
minute
or
two
and
then
from
another
machine
basically
show
that
the
curl
will
work
against
that
site
now
again,
I'm
not
showing
the
DNS
ID,
but
that
was
just
because
I
was
trying
to
you
know
hide
hide
some
details
for
the
for
the
video.
A
D
D
So
if
you
go
to
the
external
DNS
site
now,
what
you
end
up
seeing
is
it
mostly
talks
about
kubernetes,
not
necessarily
cloud
boundary,
but
the
source
is
in
there,
so
they
support,
like
I,
said
the
two
kubernetes
sources
and
then
the
the
Cloud
Foundry
boundary.
Basically,
they
look
for
anything
with
routes.
Now.
A
D
So
you
would,
though,
the
common
pattern
I
think
to
run
external
DNS
now
for
kubernetes
is
to
run
it
within
the
pod
that
you're
running
kubernetes,
so
the
way
that
I
have
been
running
in
the
way
that
we
talked
about
running
it
is
kind
of
similar,
like
you
would
just
run
it
within
your
within
your
Cloud
Foundry
site.
So
maybe
each
developer
would
run
it
for
their
app
or
you
can
run
it
within
your
organization
or
whatever
there's
no
restrictions
of
that
a
certain
Cloud
Foundry,
it's
just
a
docker
container.
D
D
The
idea
is,
and
I
mean
this
might
be
a
difference
between
I
guess
how
people
set
up
Cloud
Foundry
different
companies.
The
way
that
ours
is
the
way
that
ours
is
set
up
is
that
there's
a
wild-card
DNS
to
everything
on
a
certain
foundation
site
so
like
site,
1
Comcast
on
that,
whatever
the
URL
is
so.
D
The
as
long
as
you
you're
getting
back
to
that
Cloud
Foundry
foundation
with
the
right
app
name
and
you
know,
wildcard
DNS
came
to
get
you
back
to
the
foundation.
It
doesn't
necessarily
matter
where
it's
deployed
behind
the
scenes.
I
don't
know
if
that's
like
a
nuance
of
our
deployment
or
not,
but
I
think
one
of
the
things
that
would
be
would
be
good
is
if
people
think
this
would
be
useful
to
get
some
feedback
on
like.
A
D
A
D
So
that
that
would
be
doable,
I
think
the,
and
this
is
kind
of
DNS
provider,
specific
I,
think
so
some
providers
like
let's
say
that
run
53.
Let
you
do
like
wait
and
see
names,
and
then
they
do
health
checks
so,
like
you
can
imagine
creating
to
see
names
with
the
same
DMS
into
two
different
foundations.
So
it
could
kind
of
do
like
global
load,
balancing
based
on
DNS
but
I
think
that
each
DNS
provider
is
slightly
different.
So
I
could
imagine
doing
something
like
that.
The
future
cool.
A
A
D
A
A
E
Looking
weird
on
my
screen:
it's
not
just.
Can
you
just
see
the
slide?
Yeah
I
just
see
the
size.
Green's
awesome,
oh
good!
Okay!
So,
let's
see
the
last
time
we
we
did.
A
Stratis
sort
of
demo
at
the
cab
meeting
was
back
in
2017
when
we
were
I
think
we
were
just
about
to
propose
for
incubation
yeah.
We
do
various
updates
for
the
summit
and,
as
dr.
Mac
said,
we're
I
think
we're
hoping
to
kind
of
graduate
or
suggest
graduation,
maybe
next
month,
but
he
he's
gestured.
E
It
would
be
good
good
opportunity
to
give
an
update
on
Stratos
and
also
demo,
some
of
the
I'll
call
it
naan
Cloud
Foundry
bits
that
we've
added
in
from
Souza's
point
of
view
I
just
so
the
community
are
kind
of
aware
of
those,
so
I
spend
a
bit
of
time.
Just
on
a
few
of
the
things
you
might
have
missed
that
we've
added
to
Stratos
talk
about
the
Sousa
bits,
we've
added
and
then
I
will
switch
to
a
demo.
So
you
can
actually
see
those
in
action.
E
So
kind
of
real,
quick
I
was
trying
to
think
of
some
of
the
things
we've
had
it
more
recently
in
Stratos
that
you'll
see
as
I
do
the
demo,
so
lots
of
look
and
feel
improvements,
so
particularly
around
the
navigation.
So
that's
something.
We've
been
toying
with
playing
with
trying
to
trying
to
improve
and
get
right.
There's
still
more
to
do
and
you'll
see,
it's
maybe
changed
since
you
last
looked
it
lots
of
bug,
fixes
and
improvements
too
many
to
mention
they're
harder
to
see
something.
E
E
So
we
now
have
the
ability
to
just
favorite
an
org
or
a
space
or
an
app
or
even
a
car
foundry,
to
make
it
easier
for
you
to
then
get
to
where
you
want
to
go
kind
of
from
a
home
home
screen
and
you'll
see
what
I'm
talking
about
this
is
something
that
some
some
of
our
users
had.
A
problem
with-
and
hopefully
this
feature
helps
helps
with
that
invite
users.
E
So,
although
we
do
some
sort
of
role
management
within
Stratis,
we
don't
have
sort
of
full
user
management
in
terms
of
being
able,
to,
you
know,
add
users
with
an
AOA.
This
was
a
feature
that
was
requested
where
you
can
now
invite
users
into
your
Cloud
Foundry,
so
you
can
be
within
an
augur
a
space.
If
you
have
the
right
permissions,
you
can
invite
users
by
email.
They
will
be
sent
an
invitation
email
if
they
accept
it.
They
can
then
log
in
to
your
cloud
foundry
and
start
start
developing
I'm,
quoting
management
again.
E
This
is
something
that's
not
quite
in,
but
adding
the
ability
to
view
a
quota
and
then
manage
open
space
quotas
metrics.
This
is
something
we
have
had
for
a
while.
I
want
to
just
show
it
in
case
you've
not
seen
it
and
I
think
the
point
there
is
this
works
with
not
only
with
the
kind
of
metrics
how
Charlotte
we
are
with
Suzy
use,
but
also
with
the
Prometheus
boss
relations.
So
it
does
add
a
few
things.
E
E
We've
been
working
with
them
for
a
while
they've
been
doing
all
of
the
hard
work
actually
building
the
UI
we've
been
kind
of
assisting
with
helping
to
integrate
that
and
just
give
them
some
initial
kind
of
help
getting
started
with
Stratus
and
I'll
talk
about
that,
maybe
in
the
context
of
extensibility
and
then
lastly,
as
I've
shown
here,
extensibility
we're
doing
a
lot
of
work
at
the
moment
on
kind
of
improving
the
way
you
can
extend
Stratus.
This
is
this
is
worth
taking
quite
a
bit
of
time.
E
There's
a
lot
more
to
do
so,
yeah
a
bit
more
on
that
kind
of
the
way
we've
done.
Extensibility
at
the
moment
is
very
much
as
a
kind
of
a
company
or
organization
wanting
to
have
your
own
custom
version
of
Stratus.
You
would
fork
Stratus
repo,
there's
a
space
in
the
kind
of
repositories
where
you
can
create
your
customizations
and
then,
when
you
build
it,
those
will
be
bought
in
and
so
there's
a
good
separation
between
your
customizations
and
the
core
code.
E
So
when
you
come
to
have
to
rebase-
and
you
know
update-
hopefully
you
know
there
are
they're
all
you
know,
none,
maybe
one
or
two
small
things.
You
need
to
merge
conflicts
you
might
need
to
resolve,
but
typically
there
are
none,
and
so
you
can
just
keep
building
and
refreshing.
That's
the
model
we
have
at
the
moment
where
we
want
to
get
to
is
make
it
easier
for
people
to
build
and
publish
extension
and
separately
so
that
people
can
then
share
those.
So
the
the
auto-scale
is
a
good
example
of
this.
E
We're
at
the
moment
that's
being
brought
into
the
core
and
Stratus
repository,
but
our
intent
would
be
that
that
would
be
in
a
separate,
Gaborik,
positive
maintained
by
the
IBM
team.
People
building
their
own,
Stratus
or
or
kind
of
taking
a
Stratus
distribution
can
choose
which
extensions
they
want
be
in
that
release
by
just
effectively
declaring
those
dependencies.
So
this
is
where
we
want
to
get
to.
This
is
what
we're
doing
at
the
moment,
and
this
consuming
quite
a
lot
there
F
of
the
team.
So
that's
a
quick
update
on
Stratus
I'll
demo.
E
Those
in
a
sec
I
also
wanted
to
talk
about
the
work
we
do.
A
Sousa
dr.
max
saw
a
presentation.
I
gave
her
Sousa
conference
and
suggested
might
be
of
interest
to
the
broader
community.
So
obviously,
I
won't
talk
too
much
about
Souza's
kind
of
patient
platform
porosity,
that's
our
Cloud
Foundry
distribution
and
we
can
tenderize
it.
We
deploy
it
on
top
of
Cuba
Nessie's.
Obviously,
the
users
of
that
have
the
option
of
using
either
Cloud,
Foundry
or
obviously
developing
workloads
on
directly
on
top
of
kubernetes.
E
Obviously,
the
application
platform
being
based
on
committees
can
run
on
various
kubernetes
distribution,
so
the
ones
you
see
here
from
that
the
standard
vendors
as
well
as
in
this
case
Souza's
own
and
so
sort
of
guys
that
Susan
said
why?
What
can
we
sort
of
extend
Stratos
to
offer
an
experience
for
both
of
those
environments?
So
that's
kind
of
what
we've
been
doing.
We've
been
taking
Stratis
with
the
extensibility
framework
and
adding
in
our
own
extensions
to
allow
you
to
connect
in
kubernetes
and
I'll,
show.
Also
how
so
the
extensions
we've
got.
E
E
So,
as
your
addresses
you
key
and
our
initial
focus
was
on
views
that
would
help
you
understand
how
Clara
foundry
is
running
on
top
of
the
kubernetes
platform,
but
that's
something
we
can
choose
to
build
out
and
we
also
are
adding
the
ability
to
kind
of
link
into
and
embed
the
kubinashi
dashboard
if
that's
deployed,
because
clearly
that's
a
UI
that
does
quite
a
lot
of
nice
stuff,
Prometheus's
optometric.
So
this
is
something
that's
obviously
in
the
upstream
version.
I
just
wanted
to
call
out
here.
E
The
main
thing
really
here
is
we
have
a
separate
pound
chart
if
you're
on
the
committee's
work
for
deploying
metrics,
the
other
one
we've
added
more
recently
as
a
kind
of
tech
preview
in
the
suzer
world
is
the
ability
to
at
home
repositories
so
we're
we're
leveraging
an
open
source
project
called
binocular,
integrating
that
into
Stratis.
This
allows
you
to
add
how
repositories
you
can
view
charts.
You
can
review
releases,
you
can
install
a
release
from
a
home
chart
and
you
can
delete
and
all
that
kind
of
management.
E
Okay,
so
I'll
try
and
get
onto
demo
quickly.
Point
I
want
to
make.
You
know
this
is
all
open
source.
So
Stratus
is
the
Cloud
Foundry
incubator
get
AB
repo.
The
Sousa
version
is,
as
you
can
see
there,
forked
off
of
that
repo,
both
completely
open-source
they're,
both
with
apache
license.
So
you
can
take
any
of
this
stuff
and
use
it
yourself,
we're
using
the
same
extensibility
mechanism
in
the
suzer
kind
of
variant
as
we
use
for
autoscaler
and
for
other
extensions,
and
so
they
look
a
little
bit
different.
E
A
Neo
one
thing
as
you
do
this
yeah
I
mean,
as
you
graduate
straddles
from
town
drink
a
bit
of
you
go
to
some
place,
that
is
bigger,
like
let's
say,
CN
CF
or
something
that
is
sort
of
more
encompassing
so
that
since
it
it's
dealing
with
multiple
different
projects,
now
you
have
an
idea.
Can
you
internet
I,.
E
Don't
know
I
think
our
plan
was
to
stay
within
the
Cloud
Foundry.
Is
this
a
question
to
stay?
Wasn't
a
Clara
friendly
organization
right
in
graduate
from
incubation,
within
that
the
suzer
extensions
that
we
develop
as
we
improve
the
extension
mechanism,
we
would
like
those
to
be
published
in
a
separate
github
repos
to
make
it
easier
for
other
people
to
leverage
those
at
the
moment.
We're
kind
of
keeping
this
separate
from
the
core
Stratos,
because
you
know
a
lot
of
the
users
are
just
you
know.
E
You
know
vanilla
cloud,
foundry
users,
if
you
like,
and
so
not
everybody
obviously
wants
kubernetes
functionality
from
the
outset.
So
we
want
to
make
it
easy
for
those
users
that
do
want
it
to
to
kind
of
include
it
if
they
need
it,
I
think
we
will
maybe
start
to
look
at.
You
know
showcasing
some
of
this
stuff
at
other,
almost
like
some
acute
combat,
but
if
we
have
any
any
motivation
at
the
moment
to
kind
of
move
Stratis
to
a
different
foundation,
if
that
was
the
question
right.
E
So
yeah,
who
knows,
but
for
not
right
now,
can
you
see
this
now?
Yes,
we
can
see
it
awesome.
So
this
is
the
suit
of
Aaron.
So
everything
that's
upstream
is
in
this
version,
plus
the
extra
stuff
I
just
show
this
also
as
a
way
of
illustrating
you
can.
You
can
take
Stratus
and
obviously
theme
it
differently
and
change
the
names
of
stuff
and
add
a
copyright
or
that
kind
of
stuff.
If
you
wish.
E
So
I'll
just
talk
about
some
of
the
changes
or
updates
that
I
mention
on
that
first,
like
before
I
get
into
the
kubernetes
stuff.
So
when
you
come
in
now,
instead
of
going
into
applications,
you
get
this
favorites
sort
of
homepage
screen
this,
the
small.
What
we
want
to
do
just
to
make
it
look
a
bit
nicer
than
it
does
at
the
moment.
A
couple
of
things
really
to
point
out
here
when
originally
you'd
go
into
applications
which
shows
you
all
if
your
applications
across
your
cloud
foundries.
E
So
you
know,
if
you
had
a
large
number
of
those
you
know
it
could
take
a
little
while
to
load.
So
you
know
when
you
come
in
now
to
home,
it's
nice
and
quick.
If
applications
is
not
your
destination,
then
it
makes
it
much
easier
to
kind
of
not
have
to
wait
for
that
to
load
and
jump
somewhere
else.
What
you
do
see
here
are
the
the
entities
that
you've
favorited
and
those
can
be
I
can
say
they
can
be
a
Cloud
Foundry.
You
can
see
actually
a
favorite
of
kubernetes.
E
They
can
be
an
application
or
an
organ.
I
can
just
click
straight
through
and
get
to
the
view
for
that
particular
entity.
So,
if
I'm
a
developer
working
on
a
small
number
of
applications-
or
you
know
working
in
a
particular
space,
it
makes
it
easy
for
me
to
jump
straight
into
that
part
of
the
UI
without
having
to
kind
of
navigate
through
the
verse
hierarchy.
E
E
E
Now
these
are
down
the
side,
which
I
think
is
better
and
it
allows
us
to
kind
of
have
global
actions,
just
at
the
top
here
in
actions
specific
to
your
kind
of
context
in
this
area
here,
which
has
cleared
up
some
some
kind
of
usability
issues
that
we've
had
reported
back
from
our
users-
okay,
so
that's
just
a
hint
of
RAM,
some
of
the
restructuring
we've
done.
These
are
favorites
I!
Guess
if
I
go
into
cloud
foundry,
one
of
the
things
we've
added
here
is
the
invitations
what
I
mentioned.
So
this
needs
configuring.
E
You
need
to
configure
a
UA,
a
client
that
has
a
CM
invite
access.
So
you
have
to
be
a
cloud
foundry
administrator
to
do
this
and
that
once
you've
done
that
it
means
you
can
drill
in
to
an
organization.
You
can
look
at
the
users
and
then
I
can
invite
a
user.
So
I
can
maybe
win
to
it
right
now,
but
I
can
go
well.
Total
user,
nate
entry
users,
email
address.
E
Hit
invite
so
this
will
actually
create
a
user
in
the
system
for
this
person
it
will
add
them
as
a
user
of
the
New
York
that
I'm
in
and
as
soon
as
they
then
will
see
that
email
and
click
on
it
to
kind
of
set
up
their
account.
They
can
automatically
log
straight
into
cloud
foundry
and
and
start
using
it.
So
this
was
a
feature.
The
cloud
gov
guys
kind
of
requested
and
relied
on,
so
you
can
do
this
at
both
the
org
and
also
the
space
level.
E
So
if
you
do
at
the
space
level
you
can
specify
which
roles
those
users
should
get
within
the
space
by
default
and
you
can
also
do
multiple
users,
so
I
just
did
one
there,
but
you
can
you
can
put
in
many.
So
that's
user
invites
I
guess
the
next
thing
we've
added
is
quotas.
So
if
I
look
at
the
top
level,
Cloud
Foundry
view
you
can
see,
I
can
see
all
quotas
now.
So
this
is
showing
me
all
of
the
all
quotas
I
have
within
this
Cloud
Foundry.
E
If
I
go
back,
actually
select
the
IBM
Cloud
Foundry
you'll
see
it's
got
quite
a
few
more
I
can
look
at
one
of
those
and
I
can
see
the
quote
limits
for
the
verse
memory.
Application
I
can
actually
edit
there's
a
bit
of
tied
up
to
do
here
with
the
the
ones
that
are
unlimited,
but
you
can
go
and
either
edit
that
quota
I
can
go
back
and
from
an
organization
I
can
get
onto
quota.
E
So
that's
the
quotas,
stuff,
we've
added
recently,
that's
a
thing
that
we
for
an
area
that
Claire
foundry,
okay,
we've
not
had
a
coverage
for
up
till
now,
just
quickly
on
metrics
I've,
pre,
registered
and
connected
everything
up
here
in
the
interest
of
time.
If
you're
familiar
then
the
way
the
EU
had
endpoints
in
the
UI
is
from
this
endpoint
screen.
This
has
been
made
a
bit
more
visuals
and
then
previously
just
kind
of
help
users.
E
So
in
the
upstream
version
you
would
only
see
Cloud
Foundry
metrics
because,
as
version
has
some
extra
extensions,
then
you
get
different
endpoint
types
as
well.
So
you
can
add
a
metric
standpoint.
You
give
it
the
name.
The
address
of
your
Prometheus
server
connect
with
your
credentials
if
they're
needed,
and
then
you
Stratos
will
work
out
which
Cloud,
Foundry
and
off
also
kubernetes,
if
that's
relevant,
that
prometheus
service
has
metrics
for
and
then
you'll
get
additional
views
within
the
UI.
E
So
if
you
just
click
on
the
metric
standpoint,
you
can
at
least
see
which
polices
exporters
are
configured
and
where
they're
getting
a
day
trying
to
fit
some
cutting.
It
got
any
errors
if
I
go
back
to
my
cloud
foundry
and
if
I
pick
like
an
application
here,
you
can
see
I
get
next.
Metrics
tab
and
I
can
see
some
basic
CPU
memory.
Disk
metrics
for
the
applications
only
got
one
instance.
I
only
get
one
graph
but
office.
E
E
E
So
if
I
go
to
the
IBM
Cloud
Foundry
and
look
at
a
dead,
simple
app,
then
you'll
see
because
auto
scale
is
enabled
on
this
CAD
foundry
I
get
auto
scale,
tab,
so
I
side,
side
item
and
this
ones
I
just
set
up
with
a
policy
I'm
not
going
to
go
into
too
much
detail
this.
It's
not
gonna.
Take
too
much
credit
for
great
with
you
guys
have
done
they're
working
to
refine
this
a
bit
further,
but
you
can
see
you
can
enable
it.
You
can
enable
all
scalar
for
particular
app
from
here.
E
You
can
set
the
limits
in
terms
of
how
many
instances
it
can
scale
between.
So
this
can
sculpt
2115.
You
can
set
up
the
scaling
rules.
This
is
showing
the
last
metrics.
The
auto
scale
has
collected
that
it's
then
using
to
drive
weather
scale
things
up
and
down,
and
you
can
see
earlier
on.
I
was
testing
this,
so
I
scaled,
the
app
instance
to
two
and
then
after
a
while
it
spotted
that
I
was
using
a
less
than
15
megabytes,
which
is
my
rule
here,
and
so
it
scaled
it
back
down
to
one.
E
E
So
that's
everything
on
the
sort
of
strata
side
that
we've
we've
been
added
here
in
the
last
couple
of
months
or
so
on
the
kubernetes
side.
So
this
is
this
is
stuff
that
we've
added
as
the
Sousa
point
of
view,
it's
in
the
suitor
repo
but
you'll.
You
know
it's
awfully
open
source
you're
welcome
to
take
it
put
it
in
your
own
version.
If
you
wish,
as
I
said
you
go
into
endpoints,
you
can
add
a
Cuban
a
ten-point,
just
as
you
would
add
a
Cloud
Foundry
endpoint.
E
You
give
it
a
name
and
address
and
then
on
the
next
screen
you
can
optionally
connect
straight
through
it.
So
that's
one
improvement.
We've
made
Stratos
previously
you
registered
and
connected
there's
two
steps
would
make
it
easier
to
do
that
in
one
go
now
and
depending
on
which
kubernetes
environment,
you're
you're
registering
the
authentication
is
different,
so
there's
different
forms
to
supply
the
right
amount
of
information.
E
This
is
just
a
dev
system,
so
I'm
using
mini
cube
for
simplicity
and
I've
gone
ahead
and
connected
that
I
can
drill
down
into
the
kubernetes
we'll
talk
to
the
Cuban
and
his
API.
In
the
same
way,
we
would
talk
to
the
cloud
foundry
API,
so
these
views.
You
know
this
more
refinement
to
be
done,
but
you
can
see
we
get
some
high
level
kind
of
gross
in
terms
of
usage
and
whether
there's
any
pressure
application
count.
That
kind
of
stuff
there's
some
views.
E
Where
you
can
look
at
the
nodes,
you
can
drill
into
a
node
again,
because
we've
got
some
the
metric
server
connected
up.
We
can
get
some
basic
metrics
from
the
communities
as
well.
We
can
see
some
pod
information
in
terms
of
the
pods
running
on
this
particular
node,
so
some
of
this
you
can
get
obviously
from
the
cube
dashboard.
Our
focus
was
some
initial
work
here
to
make
it
easy,
if
people,
in
the
context
of
Stratos,
to
see
what's
going
on
with
their
Cloud
Foundry
deployment.
E
So
here
I've
got
Sousa
Cloud
Foundry
as
part
of
the
cloud
application
platform
running
on
Cuba
Nettie's
and
also
jump
through
to
the
dashboard
if
I
wish.
So,
if
I
know
this
things
I
want
to
in
the
cube
dashboard,
then
if
it's
installed,
we
figure
that
out
and
we
can
proxy
it
through
using
the
cube
proxy
or
tunneling
API
and
I
can
use
it
within
Stratos.
E
Here
we
can
also
I,
don't
think
I've
got
it
here,
but
you
can
jump
through
to
you
know
from
a
namespace
view
directly
into
the
namespace
view
inside
of
the
cube
dashboard.
This
is
something
we're
thinking
a
bit
more
about
in
terms
of
how
best
to
kind
of
integrate
the
Cuban
eighties
dashboard
and
then
also,
if
I
wish,
I
can
open
a
console.
E
So
hopefully
this
will
work
so
we'll
spin
up
a
pod
in
the
background
in
kubernetes
and
then
we'll
configure
it
and
then
we'll
exit
through
using
the
Cuban
eighties
API,
because
I've
already
registered
the
ham
repository
we'll
also
set
up
for
as
hair
as
well.
So
what
this
is
done
is
it's
set
me
up
with
an
environment
or
I
can
basically
run
in
Cuba,
CTL
commands
and
also
ham
commands,
and
so
this
is
all
configured
with
the
Cuba
config
already
generated
before
me,
based
on
my
mini
cube
environment.
E
If
I
had
other
cloud
providers
connected,
I
can
do
the
same
right
and
not
have
to
do
all
that
different
setup
for
the
different
environments.
So
this
shorty
shows
I've
got
you
know
the
cloud
application
platform,
the
metrics
deployed
UA
a,
and
it's
also
configured
the
ham
repositories
that
I've
added.
E
So
that's
that's
quite
useful
from
develop
point
of
view.
They
seem
to
know
just
skip
applications,
then
the
other
last
bit
I
want
to
show
quickly.
Is
that
helm?
So
obviously,
helm
is
described
as
the
package
manager
for
kubernetes,
so
you
can
have
hound
charts
which
make
it
easy
for
you
to
install
applications
or
services
within
cubed
eTI's.
We
use
project
called
binocular,
as
I
mentioned,
which
has
a
UI
and
we've
done
some
extensions
to
that.
E
E
Hopefully,
it'll
work
cool,
so
you
can
see.
I've
got
a
second
home
repository
now
and
it's
busy
synchronizing.
The
charts
from
that
repository
into
a
local
store
by
can
then
browse.
I
can
jump
through
to
see
what
my
stay
at
my
two
repositories
are,
I
can
look
at
charts
and
I
can
then
view
the
the
charts.
This
is
a
bit
like
the
services
view
that
we
have,
if
you
seen
the
marketplace,
but
instead
of
it
being
for
Clara
foundry
services,
it's
for
kind
of
kublai,
teased
or
helm
chance.
E
Go
back
so
I
can
pick
a
computer
a
chart
like
airflow.
We
get
the
view
of
of
the
chart
in
terms
of
the
readme
the
icon,
and
we
can
then
send
a
bit
more
about
that
chart.
The
various
versions
I
can
pick
a
different
version.
I
can
understand
how
I
wouldn't
deploy
it
from
the
you
are.
The
CLI
or
I
can
also
deploy
it
from
directly
from
the
UI
here
to
work.
E
Okay,
it's
hopefully
that!
Well,
though,
it's
a
little
bit
slow
here
with
the
helm
API
at
the
moment
in
helm
version
3.
This
will
improve
drastically
when
they
remove
the
backing
component.
So
you
can
see
now
the
we've
deployed
that
helm
chart
so
there's
now
a
new
release,
containers,
etc.
Inside
of
Cuba
Nettie's,
which
we
can
then
retrieve
cool,
so
we're
in
a
state
of
our
chart
or
release
being
created,
sort
of
six
pods,
crating
I'll
go
back
and
just
quickly
show
you
I
can
look
at
the
fabrication
platform.
E
Cloud
Foundry
I
get
a
summary
of
this
release
in
terms
of
pots
and
containers
to
see
what
version
I've
got
deployed
when
a
ham
chart
deploys
at
the
end.
Typically,
you
get
some
notes,
so
we
can
retrieve
those
for
you.
We
can
show
you
what
helm
values
you
deployed
this
chart
with,
and
then
we
can
also
show
you
which
pods
and
services
are
part
of
this.
This
release.
E
It's
pretty
much
it
so
at
the
moment,
and
also
you
can
actually
look
at
what
version
of
how
you've
got
deployed
in
each
of
your
kubernetes
environments.
So
any
much
like
Cloud
Foundry
you
can
there's
kind
of
ethos
with
Stratis
is
that
you
should
be
the
connect
as
many
a
multiple
of
each
of
the
different
type
of
endpoint.
So
I've
only
got
one
kubernetes
connected
here,
but
I
could
have
connected.
E
Okay,
so
I
tried
to
wade
through
that
quite
quickly.
It's
a
probably
a
few
minutes
left
I
think
I
covered
everything.
I
wanted
to
cover
a
lot
of
the
helm.
Kubernetes
work
some
some
of
it's
actually
already
in
Susak
an
application
platform.
We
consider
it
production
ready
some
of
the
new,
your
stuff
in
here
it's
kind
of
in
a
tech
preview
state
and
that's
that's
functionality
where
I'm
we're
kind
of
finishing
off
at
the
moment,
if
I
pause
there
and
for
any
questions
happy
to
take
them.
E
A
E
Yeah
I
mean
we're
trying
to
be
careful
right
because
there
are
there.
Are
you
guys
like
to
keep
Nettie's
dashboard
I'm
on
oculus?
So
our
approach
is
to
try
and
integrate
those
in
the
best
way
and
leverage
their
functionality
fill
gaps
and
make
it
easy
for
people
to
to
kind
of
see
stuff
in
the
right
context
right.
So
the
metrics
here
you
know
you
want
to.
We
don't
want
people
to
have
to
jump
in
and
out
differently,
always
want
to
make
it
easy
to
context
rise.
So
definition,
they're
saying
that.
B
The
beautiful
thing
and
the
part
that
I
love
is
the
fact
that
you
guys
are
embracing
the
other.
You
eyes,
all
the
other.
You
guys
are
very
context
box
founded
right,
like
therefore
specific
context
like
a
single
cluster
or
a
single
entity
at
them,
and
you
guys
are
basically
embracing
that
wrapping
that
that's
what
I
absolutely
love
about
this.
B
E
A
E
Is
I
think
that
there
are
there
is
more
to
do.
We
did
a
recent
round
of
I
guess
regression
fixing
where
some
things
had
had
not
got
so
easy
to
use
on
a
phone
and
I
think
there
is
more,
we
can.
We
can
do
there,
but
I
missed
it
stood.
It
should
still
be
useful
on
their
mobile
device
yeah
and
if
it's
not,
then,
then
you
know
file
for
defects
on
issues
and
well
certainly
look
at
those
okay.
E
I
mean
it's
not
the
highest
priority
in
our
list,
because
it's
quite
a
rich
UI.
So
some
of
the
you
know
some
of
the
things
you
do
it's.
It
is
harder
to
make
them
scale
down
to
a
mobile
device,
but
it
is
a
certainly
a
a
goal
we
would
like
to
have
that.
Ultimately,
we
make
the
best
of
the
device
that
you
have
cool
any.
A
Other
question,
actually
is
something
we've
been
chatting
with
some
some
colleagues
at
IBM
is.
Are
you
planning
to
add
something
like
you
know,
order
I,
guess
with
the
endpoint
mechanism
that
job
now
in
theory,
you
should
be
able
to
add
order,
components
right
so
something
like,
for
instance,
K
native.
That
sort
of
you
know
burgeoning
this.
Is
that
on
your
radar?
Is
it
something
that
maybe
you
would
be
willing
to
have
other
people
help
you
well.
E
Oh
yeah,
so
I'm
not
sure
Kennedy
was
directly
on
my
radar
right
now,
because
we,
you
know
a
small
team
and
we're
trying
to
juggle
all
of
this
stuff.
I
have,
but
certainly
if
other
people
are
interested
in
pitching
in,
we
would
definitely
be
welcoming.
Of
that.
You
know,
like
I
said
this
does
use
the
extensions
mechanism,
so
you
know
you
can
add
new
endpoint
types
through
the
extensions
api's
and
new
authentication.
You
know
mechanisms
and
types
through
that
API.
E
A
All
right,
we
only
have
a
few
more
minutes,
but
this
again
this
was
awesome.
Please
pass
along
this
this
message
to
to
everybody
on
your
team.
This
is
great
and
we
look
forward
to
seeing
you
in
The,
Hague,
yeah,
sure,
excellent,
Thank,
You,
Neal
again
and
I
don't
see
any
other
questions,
so
we
really
appreciate
this
and
we'll
all
be
trying
it.
So,
thank
you
again.
All
right
take
care.