►
Description
Swisscom’s Cloud Foundry Journey - Lukas Lehmann & David Zimmerli, Swisscom
Being a Cloud Foundry service provider has it’s positive as well as it’s challenging sides. We run a unique multi-cloud CF with multiple foundations and more than 30’000 containers. Adopting the latest trends and customer requests into the steadily evolving customer base is not easy. In this talk, you will learn how we have evolved over the last years and how will further develop our offering in the future to meet market needs.
For more info: https://www.cloudfoundry.org/
A
Kitten,
we
are
on
time
and
as
we
are
Swiss
citizens,
we
will
start
on
time
wherever
welcome
from
my
side.
I
hope
everyone
had
a
very
good
conference
so
far
and
is
enjoying
the
atmosphere
and
interesting
talks
here
in
the
hague
in
the
next
20
minutes.
We
will
tell
you
a
bit
more
about
our
story
about
Swisscom
story,
about
Swisscom
story
with
cloud
foundry
and
how
we
came
to
the
metric
number
of
today
over
35,000
containers
that
we
are
running
of
in
production.
A
We,
these
are
on
one
hand
David.
Similarly,
with
our
lead
product
manager
of
cloud
services
and
myself
supporting
him
on
the
technical
and
organizational
stuff.
Also
leading
the
cloud
services
so
table
will
give
you
a
few
introductory
words
about
what
Swiss
come
is
because
not
everyone
in
here
may
know
who
who
knows
Swiss
come,
who.
B
Quickly,
take
it
I'm
not
going
through
all
these.
These
points.
Don't
worry
about
that
I'm.
Just
Swiss
chemist
is
the
biggest
telecom
provider
in
Switzerland,
their
behalf
offerings
for
residential
SME
and
the
major
corporations
and
customers
so
to
speak.
I
think
you
have
a
super
strong
brand,
every
Swiss,
no
Swisscom
I,
think
even
the
smallest
children,
so
I
think
we
did
a
great
job
there
and
we
pride
ourselves
to
be
a
technology
leader
in
Switzerland.
So
we
really
also
invest
in
in
upcoming
technologies.
B
Cloud
was
one
of
them,
and
now
it's
not
so
upcoming
anymore,
but
it's
still
a
big
topic
for
us,
of
course,
and
I
think
the
last
one
is
really
we're.
Also
investing
heavily
into
startups
in
it
shouldn't
be
playing
a
role
in
this
in
this
venture
joint
venture
market.
So
to
speak.
Could
you
go
to
the
next
line.
C
B
Yourself
and
as
I
said
with
the
cloud
portfolio,
our
cloud
products,
one
of
them
is
the
application
cloud,
which
is
our
cloud
foundry
and
product,
so
to
speak.
I
guess
many
of
you
heard
about
it
already.
There
were
some
several
talks
already
today
and
one
of
the
most
famous
one
was
two
years
ago
in
Basel
talking
about
our
our
whole
set
up.
B
Basically,
what
we
have
is
we
stretch
our
our
Cloud
Foundry
platform
zone,
so
to
speak
over
three
availability
zones
over
two
data
centers,
so
that
we
really
have
a
high
availability
or
can
guarantee
a
high
high
availability.
Maybe
on
top
of
that,
we
also
offer
our
persistent
services
like
databases
or
message
queue,
services,
elastic
search
and
so
on,
and
it
is
of
course
the
Cloud
Foundry
certified
platform
I'm
not
going
more
into
detail,
because
there
are
the
talks
and
more
more
or
better
talks
about
it,
more
technically
accurate
ones.
B
So,
maybe
just
quickly
we
have
two
product
models
so
to
speak.
We
have
the
application
cloud
public
offering
which
is
really
focusing
or
targeted
at
the
individual
developers
and
ISPs
in
Switzerland.
So
our
focused
market
is
Switzerland.
Maybe
that's
also
important
to
say,
and
and
on
the
other
side
we
have
the
enterprise
application
cloud,
which
is
a
virtual
private,
offering
which
is
really
targeted
at
large.
B
Large
corporations
in
Switzerland,
I
think
our
biggest
market,
and
it's
not
a
secret
to
say
that
in
certainties
of
course,
the
financial
markets
are
banking,
insurances
and
so
on
are
very
important
for
us.
Yes,
maybe
the
main
difference
just
between
these
two
distributions
is
the
enterprise
or
the
VP
model
is
a
dedicated
models
or
you
get
your
own
Cloud
Foundry
installation
and
the
public
is
really
a
shared
one
where
multiple
customers
are
on
the
same
tenant,
that's
it
from
from
the
product
and
the
companies
or
the
person
you
want
to
take
it
away.
So.
A
As
you
have
heard
from
David,
we
are
the
biggest
telecom
provider
in
Switzerland
and,
besides
being
the
biggest
telco
provider
in
Switzerland,
we
are
also
one
of
the
biggest
IT
IT
infrastructure
provider
in
Switzerland
or
the
biggest,
and
instead
we
run
a
huge
outsourcing
business
where
bank
insurance
companies
and
other
enterprises
run
their
servers
with
our
infrastructure
there
or
we
have
housing
for
them.
So
early
2013
12,
we
already
saw
a
cloud,
is
upcoming.
A
A
So
then
2000
early
2015,
as
you
all
know,
the
birth
of
the
cloud
foundry
foundation,
was
there
where
the
foundation
was
invented
and
the
whole
IP
donated
to
the
cloud
foundry
foundation,
and
we
are
a
gold
member
ever
since
and
also
their
certified
provider.
Ever
since
the
certification
is
available
and
then
2015,
we
launched
a
public
offering
that
David
explained
before
and
February
2017.
A
We
launched
the
enterprise
offering
which
included
this
dedicated
offering
for
the
enterprise
customer
and
also
that
we
use
internally
as
well
and
ever
since
we
are
maturing
the
platform
we
are
making
us
the
transformation.
The
cloud
foundry
is
making
with
exchanging
the
components
as
they
get
exchanged
upstream
and
we
have
to
a
service
marketplace
next
to
our
cloud
foundry
offering
that
we
are
also
evolving
and
updating
that
we
built
for
ourselves
so
to
mention
here
are
highlights
from
our
end.
A
If
we,
if
you
dig
into
this
history,
are
we
have
the
honor
to
represent
a
gold
member,
a
spork
member
in
the
board,
so
Stefan
myself
is
currently
that
part
member
for
Swisscom,
which
is
for
us,
we're
interesting
to
get
those
insights.
What
is
really
going
on
with
the
foundation,
and
and
also
thanks
at
this
point
to
if
there
are
some
gold
members
in
here
who
voted
for
us?
A
We
really
really
do
that
job
like
to
do
that
job,
and
that's
it's
an
honor
for
us
to
do
that,
and
the
other
highlight
was
that
we
donated
the
donation
of
the
multi-cloud
CPI.
That
was
roughly
two
years
ago
that
there,
for
us,
was
a
huge
effort.
Also,
a
Swisscom
participating
in
such
an
open
source
ecosystem
was
very
new.
We
had
to
convince
a
lot
of
lawyers
and
internal
processes
to
to
make
sure
we
can.
A
We
we
can
really
commit
a
type
ii
and
give
back
is
for
us
something
that
was
that
was
and
is
very
important,
and
we
had
Konstantinos
as
a
full-time
committee
over
nearly
three
years
involved
in
in
various
projects
that
gave
us
insights
in
really
what
is
going
on.
Where
are
the
pain
points?
How
is
this
pairing
working
out?
What
are
the
processes
that
we
then
could
also
adopt
for
our
internal
processes
just
to
cover
the
highlights?
I
mean
the
road
was
not
always
as
shiny
as
it
looks
now.
A
A
A
B
B
This
is
the
right
way
to
go
ahead.
Developers
and
focus
on
the
developers
tell
them,
and
there
is
a
better
way
to
do
this
in
in
in
their
daily
life
right,
but
quite
frankly,
it
was
also
quite
if
or
a
challenge
internally
it
with
even
to
teach
our
sales
guys.
What
does
that
mean
actually
and
how
can
you
approach
the
the
customers
and
and
so
on?
So
it
was
missionary
internally
to
get
people,
but
it
was
a
missionary
outside
in
the
market.
B
So
we
have
quite
a
quite
a
lot
of
developers
on
our
platform,
the
public
side,
and
we
also
have
a
couple
of
major
enterprises
in
in
in
Switzerland
and
their
growth,
and
that
was
the
growth
we
were
we
saw
in
the
beginning
is
really
it's
really
enormous,
and
we
see
that
this
model
of
cloud
foundry
in
a
big
company
who
is
using
it
as
a
strategic
platform,
is
really
working.
The
problem
we
have
right
now
and
we're
very
open
about
that.
I.
B
B
But
the
other
reason
is
that,
because
this
whole
set
up
for
how
we
set
it
up
with
the
stretch,
tenants
and
and
and
everything
we
have
a
quite
a
big
resource
footprint,
which
means
that
we
also
have
a
lot
of
production
costs,
of
course,
which
forces
us
to
not
horses
us
but
needs
us
to
to
ask
for
fixed
costs
per
tenant.
So
to
speak,
and
that's
it.
That's
only
a
practical
model
if
you,
as
a
company
as
an
enterprise,
decide
that
this
is
your
strategic
platform.
B
It
doesn't
work
to
start
start
small
and
grow
into
big.
For
for
these
big
companies
and
I
think
the
even
bigger
issue
we
have
right
now
in
the
market
is
it's
clearly
the
kubernetes,
so
everyone
says
it
has
to
be
communities
inside
otherwise
I
I'm
not
deciding
for
such
a
platform,
and
that's
really
and
this
it's
clearly.
Currently,
it's
not
only
the
door.
It's
not
only
the
developers
who
make
these
decisions.
B
B
B
It's
scaling
massively
and
they're
they're
less
and
less
people
who
have
experiences
with
the
issues
we're
facing
right
now
and
that
that
also
forces
more
issues,
of
course,
and
also
takes
longer
to
fix
those
issues,
and
that
can
be
an
issue
and
what
we
also
experienced
heavily
is
that
migrations
are
super
hard.
So
if
you
exchange
components
within
cloud
foundry
or
also
all
around
platforms
or
whatever,
it's
very
it's
very
hard,
and
we
did
that.
B
A
So,
and
if
we,
if
we
go
to
the
lessons
learned
of
that
journey,
I
think
on
the
very
top
is
hey,
if
you
have
the
best
developer,
experience
infrastructure
people
to
not
care
about
this,
and
this
is
also
what
you
see
at
the
conference
today,
hey
here,
the
developer.
Experience
is
in
focus,
and
this
is
also
how
we
have
won
some
customer,
but
on
the
other
side,
if
there
are
really
users
looking
for
how
I
can
improve
my
infrastructure,
then
kubernetes
a
cloud
foundry
is
not
the
right
tool.
A
Obviously,
but
I
think-
and
we
will
get
to
this
on
the
future
state.
How
how
cloud
foundry
can
play
a
big
role
here
in
the
future
is
we
will
see
that
and
the
other
side
will
of
push
I
mean
wash
has
been
a
tremendous
key
for
us
to
manage.
We
manage
over
15,000
VMs
with
a
dozen
people
roughly,
which
would
not
be
possible
without
pushing
my
point
of
view,
because
it
just
allows
you
to
such
an
easy
life
cycle.
A
And
then
this
is
just
going
smoothly
with
a
Bosch
on
the
very
top
right
and
the
operating
the
open-source
Cloud
Foundry
is
hard
in
a
way
because
you
will
experience
issue
and
and
don't
have
anyone
to
just
call
on
the
support
line
and
say:
hey,
please
fix
it.
You
really
have
to
dig
into
it
and
know
the
details
and
bits
and
bytes
towards
the
debug.
A
We
had
quite
a
journey
on
this
until
we're
at
this
point,
but
operating
stateful
services
and
open
source
stateful
services
is
even
harder
because
in
there
is
the
state-
and
if
you
mess
that
up,
then
it
gets
even
harder
and
more
critical
and
then
on
the
bottom,
more
I
mean
what
what
I
call
a
success.
That
we
have
is
the
platforms
and
the
installations
we
have
of
Cloud
Foundry.
They
have
really
massive
growth
and
they
were
adapted
strategically
within
the
companies.
A
We
are
running
them
and
I
think
very
important,
for
that
was
that
with
him
we
built
that
community
within
those
customers
or
also
internally.
We
have.
We
are
a
big
customers
ourselves
with
the
internal
application
cloud
that
we
built
that
community
with
a
dedicated
team
that
we
call
the
cloud
empowerment
team
that
is
taking
care
of
the
relation
to
all
developers
is
putting
them
together.
A
Every
other
month
has
these
weekly
hours
to
talk
to
that
this
weekly
office
hours
to
talk
to
them
and
make
sure
their
problems
are
really
addressed,
sustainable
and
they
also
choose
a
sustainable
architecture,
so
they
run
well
on
your
plot.
I
think
this
is
really
key
if
you
want
to
grow
adoption
on
your
Cloud
Foundry
installation
and
further
its
building,
the
customer
integration
I
will
come
to
that
in
a
second
and
making
developers.
Life
easier,
which
you
will
also
see
in
that
slide.
Here
is
basically
around
the
Cloud
Foundry
installation
that
we
have.
A
A
Our
users
can
come
and
say:
hey
I
want
to
connect
to
this
back-end
put
in
the
IP
and
report,
and
this
then
does
a
request
to
the
connectivity
team
to
the
team
managing
the
firewall
and
making
sure
they
adjust
the
firewall.
So
it's
a
manual
process
still
there,
so
it
takes
two
days
until
it
gets
approved,
but
at
least
on
our
end,
its
automated
and
before
it
was
a
pain
because
they
had
to
send
around
excellent
lists
which
contained
the
target
and
the
source
IP
port.
A
And
then
someone
had
to
map
it,
and
here
they
really
just
put
it
in
in
portal
and
it's
a
standardized
format
and
it
just
works
and
makes
developers
life
really
easier
because
he
does,
he
doesn't
need
to
care
about
the
same
with
certificates.
He
can
create
technical
user
and
then,
for
example.
Nice
thing
is
also
the
Active
Directory
Federation
service,
where
today
a
developer
he
can
just
if
he
wants
to
integrate
a
Swisscom
login.
A
But
the
journeys
not
over
yet
we
are,
we
are
developing
and
developing
and
developing
life
goes
on.
Consumption
needs
to
grow,
I,
think
one
important
or
one.
You
have
one
important
slide
here:
hey
I'm,
aware
that
you
cannot
read
the
labels
below
this
is
this
is
on
purpose.
So
this
is
the
distribution
of
the
build
packs
deployed
or
used
within
our
internal
application
cloud
and
yeah.
A
You
could
guess
what
the
language
is
that
is
used
the
most
so
on
the
very
right
here
we
have
two
java,
the
chavo
build
pack
that
is
used,
but
over
here
we
have
docker.
So
that
means
more
than
20%
just
deployed
docker
images
on
cloud
foundry
today,
whatever
it
is
and
on
here
that's
the
static
file.
Will
pack
so
since
I
commit
yeah
majority
like
or
a
decent
bunch
of
the
developers
push
staff
there,
which
really
again
also
says
here:
hey
this:
this
is
this
is
emerging
emerging
technology
and
yeah.
A
Our
existing
cloud.
Foundry
installation-
and
the
third
point
here
correlates
with
the
first
point.
So
we
now
have
to
base
for
our
next
generation
infrastructure
as
we
call
it.
We
have
to
cooperate
stable,
kubernetes
service
and
we
are
now
researching
how
we
can
put
cloud
foundry.
Also,
on
top
I
mean
you
have
seen
various
talks
already
today
and
then
in
the
keynote
announcements,
how
we
can
really
do
that
move
to
convince
more
customer
of
fusing
Cloud,
Foundry,
Cloud,
Foundry
I.
Think
that
could
we
could
we
could
greatly
benefit
there
and
we
will
also.
A
A
The
Europe
European
market
is
behind
in
the
Swiss
mark
is
even
more
behind,
so
we
are
very,
very
early
here
on
just
checking
out
the
field
before
we
do
huge
investments
at
this
point
in
time,
so
that
would
be
already
about
it
of
what
we
do
and
and
how
we
did
it
and
our
lessons
learnt.
If
there
are
any
questions,
we
will
be
open
to
answer
them
now,
also
for
some
roads
or
so
on.
The
mountains
so
feel
free
to
ask
a
question.
A
Hard
question
I
would
say
it's
about,
and
you
guys
correct,
Mira
I
would
say
it's
about
50/50
sure,
really
that
we
have
episode
our
newly
or
migrated
or
newly
written
in
a
12
factor
way
and
apps,
like
all
the
WebLogic
apps
that
are
just
taken
and
lift
and
shifted
to
Cloud,
Foundry
I
would
say
it's
really
5050
and
on
kubernetes
it's
even
more.
It's
90
percent,
lift
and
shift
that
we
see.
A
C
A
Yes,
this
is
really
a
challenge.
We
didn't
tackle
a
lot
now
in
this
talk.
We
as
a
service
provider,
have
obviously
different
challenges
and
then,
if
you
just
want
to
serve
an
internal
company
and
that's
indeed
a
big
challenge,
so
we
on
infrastructure
level,
we
have
the
own
own.
We
centers
then,
and
really
have
have
them
separated
already
on
the
network
and
infrastructure
level
and
have
ohnboss
deployments
so
to
speak,
for
all
the
customers,
then
which
which
were
thought
of
that.
So
that
means
you
have
to
update
the
whole
stack.
A
Basically-
and
we
do
this
now
in
more
and
more
in
a
regular
cycle
that
every
other
week
we
update
our
public
environment
so
pretty
pretty
automated
from
the
pipeline
and
then
once
a
month
with
Fleet
time
coming
from
the
public
environment,
we
update
the
enterprise
environments
so
that
we
know
the
things
are
the
new
parts
and
bits
are
already
running
stable.
So
we
take
them
then,
to
the
enterprise
environments,
but
yeah.