1
2
Yudai IwasakiNTT Group
Cloud Foundry at NTT Group
3
Yudai Iwasaki (@i_yudai) Research engineer at NTT R&D Lead engineer on CF project since
2011 Nise BOSH and cf_nise_installer JavaScript, Ruby, and Ada
My Profile
4
Public Cloud Service “Cloudn”• NTT Group overview• Cloudn service overview
Cloudn PaaS: Why We Chose Cloud Foundry Our requirements
• Successful activities on Cloud Foundry• Conclusion
Outline
5
Public Cloud Service“Cloudn”
6
No. 1 telecom company in the world by revenue Providing substantial cloud services Cloud Foundry as a part of Global Cloud Vision
NTT Group Overview
72countries
130 Billion $revenue in total
+ 10,000enterprise clients
+
HQ
7
Reliable low-cost cloud services with rich API Including PaaS based on Cloud Foundry
Public Cloud Service “Cloudn”
Free data transfer
http://www.ntt.com/cloudn_e/
8
3 countries and 5 locations by 2013 Dec. Users can choose preferred locations
Cloudn Datacenters
US1 location
Japan3 locations
Asia-Pacific1 location planned in 2013 Dec.
9
Cloudn PaaS
Why We Chose Cloud Foundry
10
Launched last March Based on Cloud Foundry v1
• with some backported v2 components Cloud Foundry CORE compatible Integrated with other Cloudn services
Cloudn PaaS Overview
11
Portability of user applications• Works on public & private clouds and in standalone
environments Extensible design
• Integration with other Cloudn services Scalability for public services 24/7 reliable system
Why We Chose Cloud Foundry
Our requirements at starting point
12
Scalable, extensible,
reliable, and portable
Working code
Why We Chose Cloud Foundry
13
Scalable, extensible,
reliable, and portable
Working code
Loosely coupled components & APIs
Why We Chose Cloud FoundryFrom 1 node to 500+ nodes
Many OSS frameworksminimum SPOF
14
Scalable, extensible,
reliable, and portable
Working code
Loosely coupled components & APIs
Why We Chose Cloud FoundryFrom 1 node to 500+ nodes
Many OSS frameworksminimum SPOF
Ruby
15
2011 Oct: Project launched• Learning CF and conducting feasibility tests
2012 Feb: Closed beta service started• Limited features with strategic partners
2012 Dec: Limited commercial service started• First production release
2013 Mar: Public commercial service started
Cloudn PaaS Development Timeline
1.5years
16
User-friendly web user interface Persistent application log management Cloudn RDB service support Integrated authentication system Integrated billing system Source IP address access restriction Resin Java application server support Deployment tools
Developed Extensions over 2 Years
And more...
17
Easy application management
Using CC REST API internally
User-friendly Web User Interface
18
Users can view, search, and download application logs on web UI
Persistent in restarting instances
Logger agent on each DEA
Persistent Application Log Management
DEA
Log Agent
DEA
Log Agent
DEA
Log Agent
DEA
Log AgentLog
Storage
Query
19
Added a new service gateway Users can provision reliable MySQL
clusters from the CLI
Cloudn RDB Service Support
RDB Gateway
20
Thin wrapper to connect Cloudn
IDs and CF internal IDs
Provisions user IDs by calling Cloud Controller REST API
Cloud Foundry v.2 uses UAA instead of Cloud Controller for provisioning
Integrated Authentication System
CCDB(User Info)
Cloudn ID Manager
REST API
ID Provisioner Component
Cloud Controller
REST API
21
We succeeded in launching our service rapidly thanks to Cloud Foundry.
Cloud Foundry is:• Extensible• Portable• Scalable• Reliable• Mature
Conclusion
Ready for buildingyour own PaaS!
22
Top Related