Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Continuous Mission: Transforming Government IT

Continuous Mission: Transforming Government IT

Keynote from the EMC Federal Summit, 2015.
Why Continuous Delivery is the *only* path forward for Federal IT.

Cf1cd92ec0f82ce8c66076604f19b9cb?s=128

Joshua McKenty

November 18, 2015
Tweet

More Decks by Joshua McKenty

Other Decks in Technology

Transcript

  1. In times of rapid change, experience could be your worst

    enemy. - J. Paul Getty
  2. 2 © 2014 Pivotal Software, Inc. All rights reserved. 2

    © 2014 Pivotal Software, Inc. All rights reserved. Continuous Mission Transforming Government IT Joshua McKenty, Field CTO, Pivotal
  3. We the people of the United States, in order to

    form a more perfect union, establish justice, insure domestic tranquility, provide for the common defense, promote the general welfare, and secure the blessings of liberty to ourselves and our posterity, do ordain and establish this Constitution for the United States of America.
  4. 4 © 2014 Pivotal Software, Inc. All rights reserved. 4

    The Federal CIO’s IT strategy is oriented around three core objectives: (1) driving value in Federal IT investments, (2) delivering world-class digital services, and (3) protecting Federal IT assets and information. Prioritizing these three objectives will help build upon successes from key initiatives such as PortfolioStat, the Federal Data Center Consolidation Initiative (FDCCI), the launch of the U.S. Digital Service, and shifting to more agile development practices.
  5. $86.3B

  6. None
  7. 7 © 2014 Pivotal Software, Inc. All rights reserved. Cycle

    Time: From Idea to Production
  8. 8 © 2014 Pivotal Software, Inc. All rights reserved. …high

    performing organizations ship code 30 times faster (and complete these deployments 8,000 times faster), have 50% fewer failed deployments, and restore service 12 times faster than their peers.
  9. 9 © 2014 Pivotal Software, Inc. All rights reserved. Ten

    years of change… •  Puppet Configuration Management is invented 2005 •  Launch of Amazon AWS EC2 Beta •  Google BigTable Paper published •  Facebook becomes publicly available 2006 •  Netflix launches Video-on-Demand •  First release of open source Hadoop 2007 •  Apple launches the App Store •  Amazon AWS comes out of Beta 2008
  10. 10 © 2014 Pivotal Software, Inc. All rights reserved.

  11. In times of profound change, the learners inherit the earth,

    while the learned find themselves beautifully equipped to deal with a world that no longer exists. - Eric Hoffer
  12. None
  13. 13 © 2014 Pivotal Software, Inc. All rights reserved.

  14. 14 © 2014 Pivotal Software, Inc. All rights reserved. (AKA:

    Cloud Foundry)
  15. 15 © 2014 Pivotal Software, Inc. All rights reserved. Cloud

    Foundry Foundation PLATINUM GOLD SILVER
  16. CLOUD NATIVE Cloud DevOps Agile Lean Continuous Delivery Microservices

  17. Services (stateful): Run in virtual machines Applications (stateless): Run in

    containers A (narrow) Artificial Intelligence that manages transformations between existing and desired system states, using immutable infrastructure. Amend (Re)deploy (Re)configure (Re)connect Monitor Current State Desired State def: Platform
  18. Cloud Native Framework Contract: 12 Factor App Contract: BOSH Release

    Contract: Cloud Provider Interface Culture Dev Dev IT Ops Tools Spring Cloud Spring Boot Cloud Foundry BOSH AWS VMware OpenStack Application Framework Runtime Platform Infrastructure Automation Infrastructure IT Ops IT Ops
  19. 1 Spring Cloud Spring Boot Dev Spring Boot From 0

    to app in < 5 min Spring Cloud Designed for fragile infrastructure in partnership with Netflix Application Framework
  20. 2 Cloud Foundry Dev IT Ops Self healing Container management

    Integrated logging Auto scaling Application Performance Management Runtime Platform Self service
  21. 2 Infrastructure Automation Infrastructure BOSH AWS VMware OpenStack manage services

    not servers zero downtime no maintenance windows infra as code multi cloud support IT Ops IT Ops embedded OS
  22. 22 © 2014 Pivotal Software, Inc. All rights reserved.

  23. The key in such a transition to continuous delivery is

    to expect things to get worse before you’ll be able to make them better. – Matthias Marschal
  24. 24 © 2014 Pivotal Software, Inc. All rights reserved.

  25. None
  26. All changes, even the most longed for, have their melancholy;

    for what we leave behind us is a part of ourselves; we must die to one life before we can enter another. ~Anatole France
  27. 27 © 2014 Pivotal Software, Inc. All rights reserved. #ChatOps

    "Culture does not change because we desire to change it. Culture changes when the organization is transformed; the culture reflects the realities of people working together every day.” — Frances Hesselbein
  28. None
  29. 29 © 2014 Pivotal Software, Inc. All rights reserved. Why

    Cloud Foundry? “It’s definitely around speed to market, but it’s also about getting it right faster,” George Sherman, JPMC CIO “From 100 days to minutes. That’s what Pivotal CF gives us.” Andy Zitney, Allstate “I said to my vendors, I don’t want five years ago. I want five years from now. Where is it going?” Richard Leurig, CoreLogic
  30. 30 © 2014 Pivotal Software, Inc. All rights reserved. 30

    The price of doing the same old thing is far higher than the price of change. - Bill Clinton
  31. • Micro-service Architecture and Principles • API first design Cloud

    Native • Design for failure • Apps are unaffected by dependant service failure • Proactive testing for failure • Metrics and monitoring baked in • Cloud agnostic runtime implementation Cloud Resilient • Twelve Factor App • Horizontally scalable • Leverage platform for HA Cloud Friendly • No file-system requirements or uses S3 API • Self contained application • Platform managed ports and addressing • Consume off platform services using platform semantics Cloud Ready Cloud Native Maturity Model
  32. 32 © 2014 Pivotal Software, Inc. All rights reserved.

  33. 33 © 2014 Pivotal Software, Inc. All rights reserved. Getting

    there from here…
  34. Application Lifecycle Management: CI/CD Delivery High Quality Software, Faster and

    Continuously From Idea to Production Solution: Distributed revision control and source code management. Collaborative software development Solution: Build and test software projects continuously and incrementally. Hundreds of compatible plugins Solution: Share binaries and manage distributions. Manage artifact lifecycle. Avoid license violations Develop, test, QA and production on the same platform. Simple, developer friendly commands and APIs. Operational benefits for every app. Built-in ecosystem services. Deploy, operate and scale on any IAAS AUTOMATION. Integrate tools and automate processes from testing to builds and deployment SPEED. Release more frequently with smaller bits will reduce complexity and improve time-to-market QUALITY. Reduce feedback loop using test- driven development to surface problems sooner and be responsive AGILITY. Push updates on regular basis with no downtime to improve customer experience and time to market Commit Code Change Automate Build & Test (Unit Test, Static Code Analysis) Store Binaries & Build Artifacts Automated Integration Testing Acceptance, Performance & Load Zero Downtime Upgrade to Production Build Pipeline Operations Tool Chain Gitlab Jenkins Development Test + UAT + Staging Production Problem: Customers want to use Git distributed source code control system, yet maintain on-premise control of it Problem: Current application delivery pipeline is manual and error-prone, and lacks automation, scale, speed, transparency, compliance and reliability. Problem: Development requires management of binary artifacts to incorporate 3rd party components and track application binary artifacts
  35. 35 © 2014 Pivotal Software, Inc. All rights reserved. 35

    © 2014 Pivotal Software, Inc. All rights reserved. Compliance as Code: OpenControl A YAML-Powered Antidote to Bureaucracy As reported by Joshua McKenty, @jmckenty
  36. None
  37. None
  38. None
  39. http://open-control.org