Your SlideShare is downloading. ×
Cloud Foundry at NTT
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Cloud Foundry at NTT

2,352

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,352
On Slideshare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
49
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 1
  • 2. 2 Yudai Iwasaki NTT Group Cloud Foundry at NTT Group
  • 3. 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. 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. 5 Public Cloud Service “Cloudn”
  • 6. 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 HQ
  • 7. 7  Reliable low-cost cloud services with rich API  Including PaaS based on Cloud Foundry Public Cloud Service “Cloudn” http://www.ntt.com/cloudn_e/
  • 8. 8  3 countries and 5 locations by 2013 Dec.  Users can choose preferred locations Cloudn Datacenters US 1 location Japan 3 locations Asia-Pacific 1 location planned in 2013 Dec.
  • 9. 9 Cloudn PaaS Why We Chose Cloud Foundry
  • 10. 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. 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. 12 Scalable, extensible, reliable, and portable Working code Why We Chose Cloud Foundry
  • 13. 13 Scalable, extensible, reliable, and portable Working code Loosely coupled components & APIs Why We Chose Cloud Foundry From 1 node to 500+ nodes Many OSS frameworks minimum SPOF
  • 14. 14 Scalable, extensible, reliable, and portable Working code Loosely coupled components & APIs Why We Chose Cloud Foundry From 1 node to 500+ nodes Many OSS frameworks minimum SPOF Ruby
  • 15. 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.5 years
  • 16. 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. 17  Easy application management  Using CC REST API internally User-friendly Web User Interface
  • 18. 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 Agent Log Storage Query
  • 19. 19  Added a new service gateway  Users can provision reliable MySQL clusters from the CLI Cloudn RDB Service Support RDB Gateway
  • 20. 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. 21  We succeeded in launching our service rapidly thanks to Cloud Foundry.  Cloud Foundry is: • Extensible • Portable • Scalable • Reliable • Mature Conclusion Ready for building your own PaaS!
  • 22. 22

×