Top Trends in Application Delivery Webinar 10.29.15

Editor's Notes

• #2: Stephanie
• #3: Today the IT is built around tin, + DBs, Oss Everyone has their own bridge to live under No view of customer experience, business value This needs to change There are several trends that are starting to drive this
• #4: We’ve started to see early organization shifts necessary to support it DevOps is about culture, aligning internal practices and priorities with goals of the business Though there has been a lot of maturity around DevOps There is further to go – still theoretical in most organizations
• #5: High performing IT teams that adhere to these devops practices deploy code 30x more frequently than their lower performing counterparts. It’s one thing to move fast, but what’s pretty amazing is that these high performing teams didn’t sacrifice reliability. They showed that as they deployed more frequently they were able to do so with 60x fewer failures than their lower performing counterparts. And finally, one of the correlations we saw is that organizations with these high performing IT teams had a 50% higher market cap growth (and were 1.5x more profitable) than their lower performing counterparts.
• #6: Cloud is changing things. It has become mainstream. It no longer is a vague thing now. Organizations are investing in public and private clouds Cloud will continue to grow. Servers aren’t going away. The difference between one’s own servers and servers owned by the other is APIs and SLAs. There is a move toward hybrid cloud across industries such as retail, banking, finance, insurance. There is a shift towards centralized IT brokering cloud instances as opposed to self service from lines of business. Study from RightScale: http://www.rightscale.com/blog/cloud-industry-insights/cloud-computing-trends-2015-state-cloud-survey This maturation is good for Puppet. We’ve helped people transition from primarily on premise to cloud. We work on physical, virtual, public and private…we don’t care.
• #7: Makes some things simpler, but also introduces complexity. More things to manage with much shorter life spans. Proliferation of containers is drastically impacting networking. As the number of services increases, so will the number of network connections. It creates a need for defining the network in code. We’ve done a lot of work here. Docker supported module – downloaded almost 200,000 times. We help support the massive impact on networking. Arista, Cisco, Cumulus, F5 and Huawei networks.
• #8: What does all this mean? There is no future where things are easier. More servers and more services that will be critical to the business and more complex to manage. Current technology has not solved this problem. Gartner/ Forrester - Only 85% of orgs they talk to still don’t use automation. The organizational shifts must/will continue
• #9: The future is: Moving away from IT being organized around the physical bits of tin, and maybe one layer up. Away from manual hand-offs and JIRA tickets Over time, the focus of IT needs to get closer and closer to the business value it provides. The application. The services IT provides. A reorientation around business goals. A restructuring of the organization build around business value The transition is now underway and we’re going to enable it.
• #10: We can help you get there: Reducing the timeline from the moment you get new tech to the moment it’s in the hands of your users, delivering value. On October 1 we announced Puppet Application Orchestration Substantial step toward this goal Critical link connecting all of the components with the value they deliver Part of a unified stack
• #11: Puppet is evolving to help IT organizations manage distributed applications to better align with their business. A single application is spider web of many different systems and devices, relying on a multitude of components and services. It is difficult to manage all this complexity and keep up with business and user demands. <click> The core infrastructure is the foundation of our success. We’re continue to improve the experience of Puppet to manage it, whether that’s increasing ubiquity, making it faster and more reliable. <click> Anything from the Network device layer to the OS layer but share distinct qualities. Dependencies between systems. Produce or consume information between systems. Managed in a particular order.
• #12: Consider the common mobile banking app. Things like this are driving a new way of distributed applications While they are deceptively simple, there’s a lot of infrastructure behind these. With Puppet’s model-driven approach, you can describe the relationship between these components and the information needed to exchange to work together properly.
• #13: You’ve got dependencies between systems. Produce or consume information between systems. Managed in a particular order. Puppet understands how to manage the application as a whole whenever the customer wants to deploy an update to the application or enforce a configuration change.
• #14: Puppet Application Orchestration delivers context How systems depend on each other What information they share The order to provision and maintain these systems This represents a completely new way of orchestrating activities, based on modeling rather than explicitly defining a series of actions.
• #15: Puppet Application Orchestration brings together the orchestration, execution and ongoing monitoring and remediation in a single stack versus a fractured set of tools. Define applications based on their desired state, including dependencies between different services and systems. Relies on the same declarative model-based approach that has made Puppet the most popular way to manage infrastructure. Over 3,500 modules can be assembled to create full models of application stacks Based on the dependencies you define, the Puppet Orchestrator will ensure that the right things happen in the right order on the right machines. Control the state of machines across your entire infrastructure, down to the application and application stack.
• #16: Easily model distributed application infrastructure to make installations, upgrades and ongoing management repeatable and reliable. Configure, deploy and update critical applications faster and without your customers noticing downtime. Quickly cycle in new technology, while maintaining or cycling out old technology. Centralized view of all application orchestration activities and outcomes to improve collaboration between Dev, QA and Ops.
• #17: Stephanie to moderate