Downloaded 48 times
Uploaded byStormy Peters
Cloud Foundry Technical Overview at IBM Interconnect 2016
Cloud Foundry is an open source platform that allows developers to build, deploy, and manage cloud applications. It provides tools for continuous integration, deployment, and scaling of applications. The platform handles tasks like provisioning infrastructure, load balancing, and managing services so developers can focus on their code. Cloud Foundry uses containers and a buildpack system to make applications portable and scalable across different cloud environments.
More Related Content
Similar to Cloud Foundry Technical Overview at IBM Interconnect 2016
![Lect 1 Number systems and base conversions. [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/lect1numbersystemsandbaseconversions-260111134109-67c2d865-thumbnail.jpg?width=640&height=640&fit=bounds)
Cloud Foundry Technical Overview at IBM Interconnect 2016
- 1.
- 2.
- 3. Cloud Foundry isan open source platform for application life cycle automation. Develop with your favorite cloud native application framework, and then just cf push.
- 4.
- 5.
- 8.
- 9.
- 10. Year of theCloud
- 11. Year of theLinux desktop
- 12. Year of theLinux desktop 2001
- 13. Year of theLinux desktop 2007
- 14. Year of theLinux desktop 2010
- 16.
- 17. Waves & Waves Photoby Kevin N. Murphy
- 18. Cusp of abrand new thing, big like electricty, big like the internet, big like the assembly line
- 19. Year of theCloud
- 21.
- 22. tough for normal humans underthe covers, it’s in the code and in the infrastructre
- 23.
- 24.
- 25.
- 26.
- 27.
- 28. Demo • Sign upfor trial Cloud Foundry account • Check out a demo app from github • Download Cloud Foundry CLI • And then …
- 30.
- 31.
- 32. • Public, private,and hybrid deployment (Multi cloud) • Portable and interoperable, enabling users and developers to move their applications wherever they need to go. • Massive ecosystem of applications and developers based on an efficient marketplace. Cloud Foundry Foundation Vision: Cloud native platform supporting applications
- 33.
- 35. Since 2000, 52%of the Fortune 500 are no longer on the list
- 37.
- 38. Right-sizing digital innovation Focusedon cycle time optimization Smaller teams and faster tools
- 39.
- 40.
- 41.
- 42.
- 43.
- 45. “Any organization thatdesigns a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. Melvyn Conway, 1967
- 46.
- 47.
- 49. Microservices are great,but they require: rapid provisioning basic monitoring rapid application deployment devops culture Per Martin Fowler
- 51. • Use declarativeformats for setup automation, to minimize time and cost for new developers joining the project; • Have a clean contract with the underlying OS, offering maximum portability between execution environments; • Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration; • Minimize divergence between development and production, enabling continuous deployment for maximum agility; • And can scale up without significant changes to tooling, architecture, or development practices.
- 52. But even that’snot enough…
- 53. • Role basedaccess to resources: the right people should be able to do things and the wrong people shouldn’t • Run specified bits on demand: take code, put it together with all the rest of the things it needs and and get it running • Coordinate cross service configurations: in a service oriented world, services need to be configured to connect with each other • Route public requests to running bits: the next big thing needs access to the internet • Read and write persistent data: data has to live somewhere • Add and remove resources: scaling is a great problem to have, but still • Isolate resources and failures without isolation and decoupling, that is one big distributed single point of failure • Measure performance/health: can’t manage what you don’t measure • Detect and determine failure: sometimes, things get real… but how do you know • Recover failures: someone is going to have to clean this mess • Work tomorrow: when everything you’ve thought to be true has been shown not to
- 54. Unit of Value IaaS== Virtual Machine • Opaque to the system • Orchestration is post-hoc • System changes are imperative (“launch” stuff) App Platform == Application • Containers are transparent • Lifecycle is fully managed • System changes are declarative (manifest.yml)
- 55. Platforms make promises Constraintsare the contract that allows a platform to keep promises
- 56. Here is mysource code Run it on the cloud for me I do not care how Cloud Foundry Haiku Onsi Fakhouri
- 57. .war .jar dependencies libraries service manifest AppApp App LB DB Multi-server run time environment(s) .tar.gz Turning this: Into this:
- 58. BUILD APPLICATION PUSH FIRST RELEASE MAINTAIN APPLICATION UPDATE APPLICATIONS RETIRE APPLICATIONS • Auto-detectframeworks • Link to App Platform • Self-service deploy • Dynamic routing • A/B versioning • Live upgrades • Self-service removal • Elastic scale • Integrated HA • Log aggregation • Policy and Auth
- 59. target <mycf> push <myapp> create-service<myservice> bind <myapp> <myservice> start <myapp> scale <myapp> -i 100 … cf App DB LB App App
- 60. Where’s the containerin this story?
- 61.
- 62. harmonize Kubernetes andMesos reimagine schedulers as plugins Photo by izumiflowers
- 63.
- 64.
- 65.
- 66. Prescriptive Do ityourself CHRONOS scheduler.next gorouter CloudController Auth Loggregator Staging Buildpacks BOSH Service Broker Diego etcd Core Services container.nextrunC
- 67. = + + ContentsProcesses ? ? Isolation Rules PID User Network cgroups cflinuxfs2
- 68. Containers Are Awesome,but Not Enough
- 69. We’re going toneed a platform
- 70. Is BASH aplatform? Is config mgmt with $YOURFAVTOOL?
- 71. Anatomy of acf push (abridged)
- 72. Let’s talk aboutBuildpacks / Staging • Ruby code that detects language, frameworks, whatnot… • Compiles the code into executable binaries (*) /bin/detect < Am I supposed to run? /bin/compile < Build the thing /bin/release < Pass along potential metadata cflinuxfs2
- 73. That was allabout 12 factor apps… What about services?
- 75. .war .jar dependencies libraries service manifest AppApp App LB DB Multi-server run time environment(s) .tar.gz Turning this: Into this:
- 76. The Cloud NativeAdvantage: Simple Patterns Highly Automated Scaled with Ease
- 78. A platform isa promise that the products will function in ways beyond what’s “written on the box”; that the product is extensible and has value provided by an ecosystem bigger than the original vendor. Horace Dediu, 2011 http://www.asymco.com/2011/02/25/the-platform-as-a-promise/
- 79.
- 81. We’re rebalancing thesystem towards user-driven roadmaps and control of the upstream project. We’re building support for specific industry clusters in Financial Services, Industrial IoT, and Telecommunications.
- 82.
- 83.
- 84. We’re focusing oncertification to guarantee portability of apps across clouds. Make it lasting and durable. Build the ecosystem of opportunity.
- 85. ▪ Absolutely criticalfor CF users and ecosystem ▪ CF “Core”: • Certified Product • Certified Service • Hybrid Certification ▪ CF Extensions • Target Early 2016 Cloud Foundry Certification Program CF Core CF Core Cloud Foundry Core • Certified Products and “As a Service” Implementations • Must Use Specific CF-Release CFF Maintained Add-ons • Projects owned by the foundation • Extend or work with CF Core • Must meet qualifications for relevant CF Extension certification Certified CF Extensions • Projects and products external to the foundation • Are certified by the foundation as interoperable with CF Core Extended Ecosystem • Projects and products external to the foundation • Not certified BOSH, while not in CF Core, remains critical to our ecosystem development efforts and represents several opportunities for certification programs.
- 86.
- 88. Download it, play withit, contribute
- 89. To Try CloudFoundry, Download CF Lattice Lattice is a cloud-native development experience on your laptop. It’s the essential components of Cloud Foundry: • App scheduler • Router • Logging mechanisms To create, deploy and manage your apps in containers. Download it now to try cloud-native development! https://github.com/cloudfoundry-incubator/lattice
- 91.
- 92.
- 93. Learn more atcloudfoundry.org Thanks - @storming