What's new in Pivotal Cloud Foundry 1.6
•Download as PPTX, PDF•
4 likes•1,122 views
What's new in Pivotal Cloud Foundry 1.6 Tech talk in Israel
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to What's new in Pivotal Cloud Foundry 1.6
Similar to What's new in Pivotal Cloud Foundry 1.6 (20)
Recently uploaded
Recently uploaded (20)
What's new in Pivotal Cloud Foundry 1.6
- 1. 1© 2014 Pivotal Software, Inc. All rights reserved. Pivotal Cloud Foundry Journey To The Cloud Native Enterprise Dekel Tankel | @dekt Senior Director, Cloud Platform Product Group Israel, November 2015
- 2. 2© 2014 Pivotal Software, Inc. All rights reserved. My Personal Journey
- 3. 3© 2014 Pivotal Software, Inc. All rights reserved. Integrated platform for delivering cloud-native SW rapidly, consistently & reliably at scale, across the full app life-cycle Dev IT Ops IT Ops Dev Culture Platform Runtime Application container runtime with data services, automated build pipeline, routing, health management , APM and logging Infrastructure Automation API-based infrastructure provisioning that delivers bit-for-bit, consistent, self-healing deployments across private and public cloudBOSH Application Framework Frameworks designed for microservice architectures with components for service discovery, metrics, circuit breakers and more Spring Cloud Spring Boot
- 4. 4© 2014 Pivotal Software, Inc. All rights reserved. “Get rid of all inefficacies in a 85 year-old process” “100 days down to minutes…Conceive an Insurance product on a Monday, deliver it on a Friday” “A great platform to change the way a company thinks”Andy Zitney, SVP Infrastructure Services CF Summit 2015
- 5. 5© 2014 Pivotal Software, Inc. All rights reserved. Container Scheduling Application Framework ServicesPlatform Runtime Routing DatabaseConfigurationService Discovery Big Data Object Storage Mobile Build CI User ProvidedLogging & Metrics Messaging Circuit Breakers12 Factor Apps RESTful Services Microservices .NETSpring Boot Node.jsRuby on Rails Operations Zero Downtime Deployments Failover & Recovery Scaling Security Patching Platform Upgrades Infrastructure OpenStack AmazonVMware
- 6. 6© 2014 Pivotal Software, Inc. All rights reserved. What is new in PCF 1.6 Spring Cloud Services & Spring Boot Next Generation Runtime (Diego) Docker and .NET
- 7. 7© 2014 Pivotal Software, Inc. All rights reserved. Spring Cloud Services All the tools developers and architects need to create resilient, secure, and scalable applications
- 8. 8© 2014 Pivotal Software, Inc. All rights reserved. Empowered Culture Infrastructure Automation Runtime Platform Cloud Native Application Framework 12 factor appMicroservices Polyglot Java, Ruby, Python, Node, PHP, Go
- 9. 9© 2014 Pivotal Software, Inc. All rights reserved. What are Microservices ? Loosely coupled service oriented architecture with bounded contexts If every service has to be updated in concert, it’s not loosely coupled! If you have to know about surrounding services you don’t have a bounded context.
- 10. 10© 2014 Pivotal Software, Inc. All rights reserved. - Managed independently - Not held up by slowest “train” - Fits cloud native “scale-up” model - Reduces risk Source: Diagram from Leading the Transformation, 2015.
- 11. 11© 2014 Pivotal Software, Inc. All rights reserved. Use 12 factor app principles to create cloud ready applications A set of best practices for developing and deploying cloud-native software. Practices translate into platform features and workflow requirements. Codebase Dependencie s Config Backing Services Build, Release, Run Processes Port Binding Concurrency Disposability Dev/Prod Parity Logs Admin Processes Source: “The Twelve-Factor App.”
- 12. 12© 2014 Pivotal Software, Inc. All rights reserved. Config Server Service Registry Circuit Breaker Dashboard
- 13. 13© 2014 Pivotal Software, Inc. All rights reserved. Spring Cloud Service on Pivotal Cloud Foundry Built-in essential services – Config Server, Service Registry, Circuit Breaker Environment Provisioning / Infrastructure Automation On-Demand/Automatic Scaling Failover/Resilience Routing/Load Balancing Data Microservices (Spring Cloud Data Flow) Application and Infrastructure Monitoring
- 14. 14© 2014 Pivotal Software, Inc. All rights reserved. We wrote the book on it.
- 15. 15© 2014 Pivotal Software, Inc. All rights reserved. The Diego Runtime A distributed system that orchestrates containerized workloads
- 16. 16© 2014 Pivotal Software, Inc. All rights reserved. Core Runtime Concepts Cells Container Execution Brain Container Scheduler & Health Monitor BBS Shared Runtime State
- 17. 17© 2014 Pivotal Software, Inc. All rights reserved. Container Scheduler & Health Monitor Container Execution Shared Runtime State
- 18. 18© 2014 Pivotal Software, Inc. All rights reserved. Auctions Rep Auctioneer Desired Tasks Desired Processes Executor Cell Garden Containers Bids Rep Executor Cell Garden Containers
- 19. 19© 2014 Pivotal Software, Inc. All rights reserved. BBSBBS Services Dynamic load balancing BRAIN
- 20. 20© 2014 Pivotal Software, Inc. All rights reserved. Dynamic load balancing BBSBBS Services BRAIN
- 21. 21© 2014 Pivotal Software, Inc. All rights reserved. Remediation and rebalance of workloads BBSBBS Services BRAIN
- 22. 22© 2014 Pivotal Software, Inc. All rights reserved. Remediation and rebalance of workloads BBSBBS Services BRAIN
- 23. 23© 2014 Pivotal Software, Inc. All rights reserved. Remediation and rebalance of workloads BBSBBS Services BRAIN
- 24. 24© 2014 Pivotal Software, Inc. All rights reserved. New Workload Types Tasks A single unit of work Runs at most once N long running instances Distributed across cells for HA Monitored and restarted Long Running Processes
- 25. 25© 2014 Pivotal Software, Inc. All rights reserved. Garden WindowsGarden Linux Garden API Garden Container Abstraction A platform-neutral API for containerization
- 26. 26© 2014 Pivotal Software, Inc. All rights reserved. Run Dockerized applications Run .NET applications Run workers and tasks Develop Cloud Foundry applications locally Extending the Cloud Foundry Runtime
- 27. 27© 2014 Pivotal Software, Inc. All rights reserved. How can I run Dockerized applications?
- 28. 28© 2014 Pivotal Software, Inc. All rights reserved. Extend the deployment API to run a Docker image on our native Garden-Linux container backend. cf push APP DOCKER-REPO POST /containers { "bind_mounts": [], "grace_time": 1200, "handle": 'user-supplied-handle', "network": 'network', "rootfs": 'rootfs', "properties": [], "env": [] } 200 Ok { handle: 'handle-of-created-container' } Deploy the container image root filesystem. Attempt to parse container image metadata for memory, disk, user, launch command and port.
- 29. 29© 2014 Pivotal Software, Inc. All rights reserved. Run Docker Images on Linux Cells Garden Linux Cells Docker Linux Cells
- 30. 30© 2014 Pivotal Software, Inc. All rights reserved. How can I run .NET applications?
- 31. 31© 2014 Pivotal Software, Inc. All rights reserved. Container Scheduler & Health Monitor Windows Cells Container Execution Nodes Shared Runtime State Service Discovery & Monitoring
- 32. 32© 2014 Pivotal Software, Inc. All rights reserved. Windows Cells Garden Linux Cells .NET Windows Cells
- 33. 33© 2014 Pivotal Software, Inc. All rights reserved. Pivotal Cloud Foundry Demo USERS AGILITY OPERATORS AGILITY
- 34. 34© 2014 Pivotal Software, Inc. All rights reserved. @dekt | dtankel@pivotal.io
- 36. 36© 2014 Pivotal Software, Inc. All rights reserved. Platform Abstractions NSync
- 37. 37© 2014 Pivotal Software, Inc. All rights reserved. Layers of Abstraction NSync Generic Specific
Editor's Notes
- VP App Dev pitch deck David Soul Cloud Native Apps, Microservices & Platforms
- PCF is the 1st and only cloud native vendor at the moment
- Dev and Ops teams have to change together Our customer base was struggling with partial transitions and continuous delivery What’s the alternative to an integrated cloud native solution? Spring Boot is bringing microservices to the Java enterprise Pivotal Cloud Foundry is how your deploy Spring Boot applications. Would you rather have developers spend their time building a platform, or using one? It’s what some enterprises are doing today: adopting cloud a-la-carte today, using a combination of individual cloud services or technologies: Just EC2 + services. Just Docker. Docker with Puppet/Chef/Ansible/SALT. MesosSphere or Kubernetes with Docker on EC2. etc etc. Non-native, unintegrated approaches don’t offer the economy of scale inherent in a cloud native approach – partial approaches miss the mark. Most enterprises are considering to deploy multiple cloud applications, and would save $$$ if the process was repeatable – which you don’t get from using point solutions. Partial adoption places your efforts at the mercy of “Day 2” adoption issues – rife throughout the various, unintegrated layers of a cloud native solution. The next app is almost certain to require a different set of choices and trade-offs, so any economy of scale from the last effort goes out the window. Cloud native apps build on a repeatable, structured approach to the app framework, the elastic runtime and the infrastructure automation. Why reinvent things for every project? 12 factor app development and architecture, cloud resource connectivity Security Container Automation (create/scale more containers) IDM Log and metrics aggregation APM Etc etc
- Now let’s spend a more time going a little deeper on the Application Framework. These are the tools that provide all the functionality architects and developers need to design and deliver cloud native applications. In particular these tools should enable creating microservices and 12 factor apps with minimal friction. Organizations using these tools, and the supporting platform capabilities, create scalable secure applications while releasing new features every week, if not daily.
- Microservices allow always keeping the trains running because each service is deployed independently in loose coordination with the rest. Most of the consumer web applications that we take for granted are delivered this way. Many of them even integrate with each other. Twitter, Facebook, Google, flickr, Uber, Apple… none of them wait on each other to go ahead and deploy the applications you use everyday, but they use each other.
- If microservices describe how the architect your application, what principals do you use for the actual code. A good place to start is the 12 factor app principals. Learn from and use the same methods that the original cloud native do. These 12 simple principles give a surprising amount of detailed, prescriptive advice on how to write your applications to be ready for cloud deployment. They describe a contract between the developer and the cloud platform that, if followed, will allow an application to scale with cloud native resilience. The other side of that contract must be provided by a platform like Pivotal Cloud Foundry.
- Spring Boot is an open source Java framework optimized for developing microservices that is rapidly being adopted and has been embraced cloud native companies like Netflix. In addition to the rapid development of simple microservices, Pivotal has also embraced a number of Netflix Open Source components to provide additional microservice capabilities like services discovery, dynamic configuration and circuit breakers. This means that you can use the practices and tools relied on by Netflix and others while leveraging the Java skills you might already have.
- Finally, we wrote the book on how these microservices are used in cloud native architecture and how to get there. We should have copies here, if you'd like one, or you can get the PDF for free online.
- Now the original Cloud Foundry runtime was the DEA, Droplet Execution Agent We rewritten it in Go, hence Diego and a twist Renee French’s awesomely cute gopher icon. Let’s introduce some core Diego concepts. (Credit Onsi)
- Cloud Foundry has a brain that manages cells Almost all platform components communicate takes place through a scalable bulletin board system based on etcd* *Auctions don’t
- Let’s show some more architectural detail. Each cell contains an auction rep and an executor that manages the containers. You can see the containers in each cell. Brain communicates work through the auctioneer.
- The auctioneer asks cell reps to put forward bids to run tasks and processes The winning cell takes on the workload.
- Also, everybody is talking about containers. Pivotal Elastic Runtime is actually one of the most mature linux container scheduling environments in the world.
- The dynamic container scheduler in the Runtime distributes applications across a cluster. When there is more work, it gets balanced across the remaining of the capacity.
- The platform also monitors the applications, and if any of them crash, they get restarted and rebalanced across available capacity. None of this requires human intervention.
- The platform also monitors the applications, and if any of them crash, they get restarted and rebalanced across available capacity. None of this requires human intervention.
- The platform also monitors the applications, and if any of them crash, they get restarted and rebalanced across available capacity. None of this requires human intervention.
- Introducing tasks, short-lived work units
- Garden is a platform-neutral API for containerization The API talks to specific backends for each infrastructure. We’re also moving Garden to match the RunC implementation from Open Container Initiative, so we’ll be able to offer RunC compatibility. (Credit Onsi)
- Now we’ve covered a high level introduction to runtime concepts like the brain, cells and bulletin board system, I wanted to show how we extended this to offer 4 new capabilities not found in the original runtime. Run Dockerized applications, .NET, Workers and tasks, and a local runtime environment
- Some caveats, for example Cloud Foundry is focused on 12 Factor Docker image so no we don’t want to use permanent disk. Instead of mounting volumes, you’ll want to use object storage like Riak CS You’ll also want to handle app configuration via environment variables, so the platform can easily change them We have this running today and I’ll shortly show you all a demo
- Now we can run Docker images on our existing Garden-managed Linux cells with full native runtime support like logging, routing and health management
- Second, the original Cloud Foundry DEA runtime was only focused on Linux workloads. You need .NET applications on Windows? How much of the architecture would I need to redo?
- Turns out the major change to add Windows support is to implement a cell and Garden container backend in Windows. You can build a distribute .NET workloads as MSIs and have a Windows server provide the same logging, routing and health monitoring
- Once the Garden backend can execute on Windows MSIs as workloads, the Auctioneer can solicit bids for .NET workloads from Windows cells reps
- Looking in terms of workflow, we offer a pool of cells that manage work. Developers just need to supply the source code or a deployable artifact and some metadata.
- Each component becomes more specific as we go from task to recipe to container implementation.