VMworld 2015: Build and Run Cloud Native Apps in your Software Defined Data Center

Editor's Notes

• #10: Datacenter-in-a-laptop, model production deployments on your laptop Same battle-tested virtualization engine as Fusion and Workstation Drop-in replacement for Virtualbox in Docker Machine and Vagrant Developer-Friendly Optimized to support developer workflows Exposes REST API with command-line interface No UI to mess with, built to run fast and mean
• #13: CI / CD and DevOps enables breakthrough business performance, according to the survey results from the 2013 and 2014 State of DevOps Report. This report is based on the answers from 9,200 and 4,000 survey responses respectively. The benefits of DevOps are clear and impressive: High performers are more agile, they are more reliable and most of all they win in the market place.
• #14: Over the past few years, Developers have adopted Agile methodologies to rapidly make changes to code. This process is called Continuous Integration where groups of changes are tested regularly to make sure the code is working correctly. So now we have Development using agile or continuous integration, they want to push small sets of changes frequently into production and as a result Development became fast. However, the rest of the process has not changed and thus applications are still delivered late. The challenges are now very different: With the traditional release process, the challenge was the amount of change – and thus risk - hitting the production system. Now releases are very small and therefore they are much less risky. Even if a problem occurs in production, it is easier to identify the change and roll it back. Also, the traditional release process moved in 1 or 3 months rhythms so the manual nature of the process was not a big problem since there was enough time. Now with many frequent releases the manual nature of the process becomes a major problem and a repeatable and consistent process is needed. In fact Gartner states that 40% of unplanned operations downtime is caused by operations errors (e.g. not performing an operations task or performing a task incorrectly)*. In the end development became fast and they want to push changes quickly into production while operations has not changed yet and they view changes as a source of instability. This is why the conflict between Dev and Ops escalated over the last years and this of course is referred to as the DevOps conflict. I am sure you see the same challenges in your organization? ----- *Gartner, Roberta J. Witty, John P Morency, Survey Analysis: BCM Program Posture, 24 October 2013,
• #20: Pivotal Cloud Foundry (PCF) is Pivotal’s platform for deploying cloud-native apps, and can be used to deploy apps to the private cloud or the public cloud. It enables 3 key benefits that enterprises are in critical need of: the ability to deliver software fast, at internet scale and with confidence, knowing that the platform enforces constraints and encourages practices that will ensure application uptime, and availability. PCF provides a collaboration platform for developers and operators to learn and use the same tools and practices across teams and across stages of application delivery, from development through testing and production deployment. Such consistency is key for effective devops. Developer benefits include a rich and growing set of services for app development and dead simple app deployment with “cf push”. PCF also unlocks operational excellence in the enterprise, to handle Day 2 concerns for managing the software after it is in production. Operators need to be able to handle myriad concerns after software has been deployed to production, including ensuring high availability, enabling adaptive scalability to incoming load, providing security from threat vectors outside and inside the enterprise and managing software updates without downtime. Through integrated and automated features such as monitoring/logging, automatic scaling and health monitoring and high availability, the platform eliminates the need for teams to continue with manual workflows that are time consuming, inconsistent and error prone. It further obviates the need to cobble together tool chains to create a “platform”, which can present a substantial investment over its lifetime. Finally, enterprises that leverage Pivotal Cloud Foundry can feel confident knowing that their investment in PCF gives them flexibility and choice in deploying PCF and their apps on any one of multiple underlying cloud infrastructure technologies.
• #21: Pivotal Cloud Foundry is based on open source Cloud Foundry, and now guided by the Cloud Foundry Foundation comprised of a plethora of industry leaders. VMWare is proud to have initiated the project and helped it grow over the years. In 2013, we helped create Pivotal and transferred stewardship of the project to Pivotal. Last year, in 2014, with the help of Pivotal, we helped recruit broad industry traction for the project, with companies representing over 1 trillion dollars of market cap, supporting its mission and direction. Finally, this year, we and the broader industry rejoiced, as the torch of stewardship for the project officially passed into the hands of the Cloud Foundry Foundation. With 1000s of developers across 50 countries, this is truly a global phenomenon! We in the software industry are not the only ones excited by what the future holds for Cloud Foundry! Our counterparts in other industries are equally excited by the potential of Cloud Foundry to help them transform their businesses! <Allude to quotes from GE and JPMC>
• #26: https://www.docker.io/learn_more/
• #32: When Creating a Container: Receives “docker run” API request. Download any new image layers to datastore. Select container VM IP. Set up any network mappings for exposed ports. Identify ESX host to run VM. Use InstantClone to create “child” PhotonOS-Pico container VM with IP address. Creates VMDKs representing container image (layers) and volumes, attach to the container VM. Container VM executes the “entrypoint” command for the container image. Handles further API requests (e.g., “docker stop, docker start, docker rm) with corresponding VM life-cycle operations.
• #34: VMware is committed to the OpenStack project. VMware was the #4 contributor to OpenStack integrated projects in the Icehouse release. VMware has a growing number of developers contributing to OpenStack. Contributions span across a number of OpenStack projects listed in this slide.
• #45: Will provide script
• #46: Will provide script