Recommended
More Related Content
What's hot
What's hot (20)
Similar to Cloud Foundry 101
Similar to Cloud Foundry 101 (20)
Recently uploaded
Recently uploaded (20)
Cloud Foundry 101
- 1. © Copyright 2017 Dell Inc.1 CloudFoundry 101
- 2. © Copyright 2017 Dell Inc.2 Xuebin He Software Developer Dell EMC Dojo Contributor of CloudFoundry xuebin.he@dell.com @hexuebin0201
- 3. © Copyright 2017 Dell Inc.3 A Japanese term which literally means "place of the way”. A room in which martial arts are practiced DOJO - noun ˈdō-(ˌ)jō Contribute to Cloud Foundry Foundation sanctioned OS projects. Train new Cloud Foundry contributors. Innovate around the platform. CLOUD FOUNDRY OS CONTRIBUTIONS & INNOVATION Practice a modern software development methodology (XP, Lean Startup). Evangelize new work patterns ‘the way’ to internal Dell EMC product teams. DIGITAL TRANSFORMATION Dell EMC Dojo CLOUD FOUNDRY DOJO GOALS
- 4. © Copyright 2017 Dell Inc.4 World is changing Move faster Stay focused
- 5. © Copyright 2017 Dell Inc.5 Developer
- 6. © Copyright 2017 Dell Inc.6 IT
- 7. © Copyright 2017 Dell Inc.7 What is PaaS? How does that help me?
- 8. © Copyright 2017 Dell Inc.8 Data Application Networking Storage Compute Virtualization Operating System Runtime App Server Services IaaS PaaS
- 9. © Copyright 2017 Dell Inc.9 Open Source Community Automated Container and App Orchestration Self-Service Marketplace High Availability and Scalability Multi-Cloud Support DevOps Friendly Platform as a Service
- 10. © Copyright 2017 Dell Inc.10 What are the pains? How does Cloud Foundry save me?
- 11. © Copyright 2017 Dell Inc.11 I need to deploy my App Submit a ticket please! EmailTicket: Create a VMTicket: Give me a Database ITDeveloper Ticket Passing
- 12. © Copyright 2017 Dell Inc.12 Marketplace Service Broker API
- 13. © Copyright 2017 Dell Inc.13 Services Easy Access
- 14. © Copyright 2017 Dell Inc.14 Manual Deployment
- 15. © Copyright 2017 Dell Inc.15 Developer Superman Dev
- 16. © Copyright 2017 Dell Inc.16 CF Push
- 17. © Copyright 2017 Dell Inc.17 No More Manual Deployment
- 18. © Copyright 2017 Dell Inc.18 Stay Focused
- 19. © Copyright 2017 Dell Inc.19 CF Push Demo
- 20. © Copyright 2017 Dell Inc.20 CF Push Demo
- 21. © Copyright 2017 Dell Inc.21 Development Test Production It works on my laptop
- 22. © Copyright 2017 Dell Inc.22 Container Services Buildpack Identical • Identical Environments across Development, Test, and Production • Buildpack - Container Environment • Runtime • Application Server • Services Development Test Production Runtime App Server Environments
- 23. © Copyright 2017 Dell Inc.23 z Infrastructure Dependency
- 24. © Copyright 2017 Dell Inc.24 Diego Brain Consul HA Proxy Loggregator Cloud Controller Diego Cell UAA PostgreSQL Router Cloud Foundry Azure GCP AWS vSphere Openstack RackHD IaaS Abstraction
- 25. © Copyright 2017 Dell Inc.25 Midnight Redeploy TroubleshootDelivery 2AM Call Redeploy
- 26. © Copyright 2017 Dell Inc.26 High Availability 24/7 Monitoring Automated Resurrection Multiple App Instances Auto Scaling Instances Easy Blue-Green Upgrade
- 27. © Copyright 2017 Dell Inc.27 Logs
- 28. © Copyright 2017 Dell Inc.28 12 Factor App Logs Treat logs as event streams Dev/Prod parity Keep dev, staging and prod as similar as possible Disposability Robustness with fast startup and graceful shutdown Concurrency Scale out via the process model Port Binding Export services via port binding Admin Processes Run management tasks as one-off process Build, Release, Run Strictly separate build and run stages Backing Services Treat backing services as attached resources Config Store config in the environment Dependencies Explicitly declare and isolate dependencies Code Base One codebase tracked in version control, many deploys Processes Execute app as one or more stateless processes
- 29. © Copyright 2017 Dell Inc.29 ITDeveloper Cloud What does the cloud look like?
- 30. © Copyright 2017 Dell Inc.30
- 31. © Copyright 2017 Dell Inc.31
- 32. © Copyright 2017 Dell Inc.32 All in one, one for all.
- 33. © Copyright 2017 Dell Inc.33
- 34. © Copyright 2017 Dell Inc.34 How does CF Work?
- 35. © Copyright 2017 Dell Inc.35 Runner Scheduler Developer Customer Router Logging Auth Runner Cloud Foundry Orchestrator Runtime Marketplace Rose .com
- 36. © Copyright 2017 Dell Inc.36 { HA Proxy } { UAA } { Loggregator } { Router } { Cloud Controller } { Diego Cell } { Diego Brain } { Consul } { PostgreSQL } { Cloud Controller worker } { NATS } { Diego BBS } { MySQL Proxy } { Doppler } { etcd } High Availability 5 7 2 2 2 2
- 37. © Copyright 2017 Dell Inc.37 CF HA Demo
- 38. © Copyright 2017 Dell Inc.38 CF HA Demo
- 39. © Copyright 2017 Dell Inc.39 Upcoming Talks 7 Lessons Learned from Implementing DevOps Brian Roche & Emily Kaiser Using GPU-as-a-Service in Cloud Foundry Victor Fong & Layne Peng Adventure of Pair Programming Gary White DevOps from a Developer Perspective Megan Murawski
- 40. © Copyright 2017 Dell Inc.40 Q & A
- 41. © Copyright 2017 Dell Inc.41
Editor's Notes
- Introduction Dell EMC Dojo The need for speed! World is moving at a much faster pace Deploy new software version every 10 seconds What is a platform? Cloud Foundry Introduction What are the problems that IT faces everyday? How functionalities of CF solve these problems? Demo Cloud Foundry High Level Architecture Cloud Foundry with Agile Development Comparison to Waterfall Functionalities of Cloud Foundry Application Design Pattern (12 Factor?) Upgrade / Scalability 2nd Demo Q&A
- - As we all can see, our world is changing. It’s moving at a much faster pace that It had never been! Tons of new ideas and technologies are coming out quickly. - Things are becoming more complicate and sophisticated. That leads to the market even harder to predict. We want our products and teams to be unstoppable in front of any kinds of changes. We want to catch up, but we also need to stay focused on the business value we want to create. - Lets talk a little about the pains we are having because of these changes.
- - As developers, we create value by delivering awesome code with no bugs. Few years ago, you can be a good developer by being pro in java and SQL. Now, there are more and more you need to know other than languages themselves. - Let me give you an example, lot more companies are using micro-services architecture for products, for reasons like better robustness of software, agile team structure or fast development. As a developer, I need to figure out which tool is the best to coordinate all the micro services, and setup the dev environment with the one I chose. And then apply it into my code. - This is just one particular example. There are more you need to explore.
- - As an administrator, you probably need to handle tons of emails everyday asking questions like how to get a dev environment. You replied, and then they come back with even more tickets to ask you do them favor with an unrejectable way. - Most of the work could be well automated or could be taken much less efforts to achieve. You could work on things are more valuable to your team, your company. Like creating latest Machine Learning environment for your data science developers. - Our administrators are fully overloaded, and it’s never getting better because the pace of changing never slows down . You as a manager either need to hire more people OR you can try CF.
- Putting these layers together, it's PaaS. A good question would be where is your business value? You really don’t want to deal with all the layers below the value line. If we want to drive to work, we don’t build cars ourselves, we buy them. It's the same thing here.
- CloudFoundry is the car you want to have because it has lot great features that tie to your business. Now we might have a little bit clue about what is CloudFoundry. Before we go deeper, lets talk about the pains we are having in detail that we mentioned.
- - You definitely know this better than me, but I still want to go through it very quick. - This is a classic pain for both sides. Emailing back and forth takes long. Developers might be totally blocked by that. The relationship between dev and administrators is kind like customers and vendors in the old marketplace. Dev always get what they want from administrators after certain bargain. Instead of paying by themselves, they are covered by company. - Now days, even traditional companies are digitalizing themselves like Walmart. Do you have to talk to the vendors to buy things? No, you can just to visit their websites and click buttons. It’s so easy, even cars could be delivered to your front door. Why can't we?
- - CF has a digitalized marketplace. It provides all kinds of services like database, persistence, tools for big data analysis, testing, CICD and many more. Developers could just go to the marketplace and buy whatever services they want. It's just few clicks with almost instant delivery. - Normally, the services live outside CF. CF talk to them through Service Broker API. It’s created by CF community. Now it’s becoming a industry standard. Lots of big companies are already adopting this API to some of their own services. - What does that mean?
- This is how the marketplace looks like in CloudFoundry web GUI.
- - Manual deploying applications is kinds like pushing round stone to the top of mountain. - They both may have few hundred steps, mistakes could be easily made. Even though you won’t get hurt or die when there is a failure, but you probably need to start from the very beginning. Some of the step might be very critical like database backup and migration. - And the situation is becoming worse. Remember in the begin I mentioned micro-services, which makes manual deployment even harder than before. Previously, you only have to deploy one giant monster application, but now you have to deploy many small version of it.
- As a developers, I need to investigate all kinds of new technologies. I am a Superman dev, we all know that this is not realistic.
- In CF, applications could be deployed literally by typing cf push, the rest will be handled by CF. CF is the cli we use to talk to CF. Basically, It will upload your source code to CF. Then do some calculation and figure out how to download your dependencies, compile your code and run it.
- No more yelling at innocent laptops. Let’s put some smile on face instead. Now you can investigate all kinds of new technologies and be a rockstar.
- Instead of being distracted by ticketing to IT, installing VMs, settings up dev databases, developer can be more creative on the application itself, and have more ideas on how to implements features and be a rockstar too.
- - We always have different environments because we have different teams. Sometimes, its really hard for IT to replicate production environments. Like VMAX, it's so expensive that developers have to use software defined version. - One day, You created a fantastic button and worked perfectly on you laptop. It's so beautiful that you want look at it for whole day everyday. Few days later, testers came back complaining you broke tests or administrators yelled you crashed production. And you were confused while starring at your awesome button, and replied: it worked on my laptop. Of course, It worked on your laptop! Otherwise, how could you push it. - Wearing their hats, It's none of their fault. But our company are losing value because it slows down the process or it gives a really bad user experience to our greatest customers.
- - In CF, its really easy to create separate but identical environments. - Each environment has the same container for running applications. - Say I'm pushing a java application, CF will use the same buildpack to pull your dependencies, compile your source code, setup the same runtime environment and use the same application server to run your application. - All the services are created in the marketplace, so they are identical too. But we can still create a powerful instance for production and low cost one for development. - If the button works on dev environments, it will work on other environments too. With CF, you can continue enjoy your fantastic button without interruption.
- Because of reasons, like better performance, lower cost, stronger security, sometimes we want to migrate our environments from one Infrastructure to another.
- - CloudFoundry is basically a bunch of micro-services running in different VMs being deployed together. - Migrating CF basically means redeploying the VMs on different IaaS. - CF has its own deployment tool to deploy softwares on different infrastructures, like vSphere.
- - I bet some of you have similar experience. Things do crash sometimes. And your company are losing money. - In a dark midnight, a madly ringing phone broke the silence and your sweetest dream that you had ever had, complaining the production environment went down. Some customers visited the website in an unexpected way hitting a mysterious bug. - Because `developers you shall not touch policy`, you, as an administrator, have to go to your production environment redeploy applications and download all logs and deliver them to developers for them to do troubleshooting. After they came with a hotfix, you need to redeploy again with the lasted change. - From the beginning to the end, It’s not your fault at all. But you are the first one to be blamed and the last one to leave the scene. It is not fair.
- - CF provides high availability in many different ways. - It will automatically resurrect your crushed apps. - We want to deliver our new features more often, so upgrading our application with 0 downtime is very import. CF provides very easy way to do blue-green upgrade with 0 downtime. With CF, you can continue on your sweetest dream.
- - Why it crash, most of the case its because our developers write crappy code. You could say nay, but bugs do come from development. - CloudFoundry encourage developers to build applications in a good modern way, 12 factor application, which is well adopted by lots companies. This should be separate talk. If you are interested, checkout 12factor.net - I wont go through the detail here, but basically, if you follow the rules here, It provides better robustness, better migrating, scaling troubleshooting abilities.
- At this point, I think we agree on that private cloud could solve problems for both developers and administrators and frictions between them. So what does the cloud look like or what it should look like?
- On a sunny day, a developer and an operator were lying down on the grass, thinking about the meaning of life. Suddenly, they wanted to figure out what does that cloud look like. They googled as we always do. But this time, they didn't get what they want. It's just another buzzword, cloud. Since google can't tell us, lets do it ourselves.
- You probably want security service to prevent bad guys from crashing your application. I feel container is a cool technology and I want to run my website inside a container. Your application is a website for a flower store, the visiting goes insane on mothers’ day, what would you do? Dev app~~~~~~~~~~~~~~~~~~~~~~~~~~ This is cloud foundry! All in one!
- You may don’t care about How does CF actually work, but you may curious about what happened after your application being pushed to CF.
- I totally forgot I need to scale up my application before the coming mother's day. In a traditional world, I might be doomed. But since I'm using CF, it doesn't matter. I can scale my applications in seconds.
- That’s all I have today. we have more awesome talks from our team.
- Any questions?