Post on 18-Dec-2014
description
1
2
Michael Behrendt, IBMSenior Technical Staff Member
Multi-site Architecture Considerations
3
Improve redundancy of apps and CloudFoundry itself
Control location of apps and services –for latency, governance, etc. reasons
Objectives of running CloudFoundry across multiple sites
4
All CloudFoundry-internal components
Apps
Services
Components in scope
NATS
RouterRouterRouters
Blobstore
Health Manager
RouterRouterDEAs
RouterRouterServicesUAA
UAA_DB
RouterRouterCloud Controllers
CC_DB
AppsAppsApps
Application End users
Developers
5
Key Considerations
6
1. Support any number of sites
Site A
Site B
Site …
Site C
Application End usersDevelopers
7
2. Tolerate outage of any number of sites
Site A
Site B
Site …
Site C
XX
Application End usersDevelopers
8
2. Tolerate outage of any number of sites dedicated CF deployment per site?
Site A
Site B
Site …
Site C
AppsApps
AppsApps
AppsApps
AppsApps
Application End usersDevelopers
9
3. Access all sites from a single point of entry cross-site management & traffic distribution function needed?
Site A
Site B
Site …
AppsApps
AppsApps
AppsApps
Cross-site management & traffic distribution
• “See” all apps & services across sites • Push & update etc. apps in dedicated regions• Create/bind service instances
in dedicated regions
Access apps deployed across multiple sites via a single URL
Site C
AppsApps
Application End usersDevelopers
10
Site A
Site B
Site …
Site C
AppsApps
AppsApps
AppsApps
AppsApps
Cross-site management & traffic distribution
4. Cross-regional management Shared cross-regional knowledge needed?
• Bind service instances against apps running in multiple sites
• Spaces across sites• …
Shared data
• Cross-site app services binding• Use of linked data?
Application End usersDevelopers
11
Thank you
– We’re hiring –
12