1

Case Study: Orange Labs &
Cloud Foundry
Guillaume Berche

Intro
• About Orange
• ElPaaso team
• Disclaimer
• Contact me: @gberche or guillaume.berche [at] orange.com
El Paso, Texas, USA ?Grenoble, France
3

Session overview
• CF adoption history within Orange
• ElPaaso
– product goals
– feature overview
– screenshots
– tech internals
– future work and challenges
• Could future CF extensions help ?
4

ElPaaso team & CF history
• 2010 : Iaas won’t be the silver bullet for our apps. How can
Paas help massive cloud migration ?
– Orange specificities: OS, DB, WAS, network architecture, IaaS
– First ElPaaso protototype on vCloud,
– dynamic vm image generation + ssh post-config
– dbaas product (on demand pg + mysql instances)
• 2012: try bosh on AWS
• 2013: prototype migrating to CF using PWS / run.pivotal.io
• 2014: vcloud cpi released, host private CF instance,
ElPaaso leverages CF
• 2015: Dual hosting mode: raw CF + ElPaaso
5

ElPaaso product role
• A playground for cloud-native architecture
• A lab to experiment how to ease paas
adoption
6

ElPaaso & CF Overview
7

ElPaaso goals and use-cases
• Decentralized autonomy… with
transparency
• Gradual adoption for the majority, beyond
innovators
• Integration in ecosystem and work
processes
• Capture expertise/best practices
8

ElPaaso current features
• Org-specific meta-data
• Versionned app templates
• Org-specific service catalog
• Common operations base
– fetch artefacts from corp repo
– app supported config
– logs
9

10

Example of a interative development: v0.1
11

Example of a interative development: v1
12

Example of a interative development: v2
13
Just implementing
new features,
resulting in a new
versionned artifact
in maven repo

Example of a interative development: v3
14

Example of a interative development: v4
15

Example of a interative development: v5
16

17

18

19

20

21

22

23

24

25

26

ElPaaso data model
27
application
useruseruser
processing
service
releasereleaserelease
architecture
releasereleaseenvironment
{ data, comm, mgt}
service
ElPaaso CF
environment space + space_roles
processing-service app + syslog_drain service + buildpack params
data service service instance
comm service route, esb service instance (arb param)
mgt service app env var
CF modelElPaaso model
with org-specific
meta-data
Pluggeable,
versionned
projection

Internal architecture and design
Iaas (vCD)
Splunk ESB
CF Plugin
DbaaS plugin
Technical Model
Orchestration
Projection
Logical model
Business API
UI User-facing API
Servicebroker
API
DbaaS SB
Splunk SB
ESB SB
Object Store Plugin RiakCs SB28

Future work, and challenges
• Automated env upgrade/rollback workflows
• Better operations basics
• Mixed elpaaso-managed and user-managed modes
– expert mode: lock/unlock
– CLI plugins for parity with UI/APIs
– Post-process native CC API user requests: notification and events
• More orange specifics projections
– fine tuned security groups
– cmdb
– monitoring and alerting
– sso
• support for multi-region/cf-instances application deployments
– for the simple case of replicated state service across regions (Cassandra) and elpaaso-managed deployments
29

Opensourcing elpaaso
• why we’re opensourcing
• current status
30

Potential CF extensions
• Meta-data attached to cf entities (tags?)
– Entities queryable by tags
– Syslog drains template include to tags
• CC API interception model
31

Conclusion
• CF add-on can be an option
• Is it interesting/useful to you ?
Thank you!
32