Developing the Future

Transcription

1

2

3 Developing the Future Adap%ng IT Skill Sets to a Dynamic Technology Landscape Robin Geddes Infrastructure Architect Public Sector, State and Local May, 2015

4 AdapKng IT skill sets: Topics Culture AdopKon of DevOps AutomaKon Many, many, new Tools Making it happen

5 AdapKng IT skill sets: Topics Culture adopkon of DevOps AutomaKon - New Tools Making it happen

6 Familiar? DevOps seeks to solve this It's not my machines, it's your code! It's not my code, it's your machines!

7 Dev and Ops Constantly Argue Code is wri*en...it s your problem now Hey Ops - Here s our code...good luck!

8 DevOps Principles Cultural movement enabled by technology Dev Paid to add new features Ops Paid to keep system stable, fast and available DevOps New goal: Add new features and keep the system stable, fast and available

9 Capital + AutomaKon Always Win Over Labor

10 DevOps = Culture + Technology Movement Culture is what s behind DevOps; technology is the enabler Culture Constrained By Technology

11 DevOps Tenet #1: Culture Dev respect for ops Ops respect for dev Don t stereotype Don t just say no Respect Discuss Don t hide things Ops should be in dev discussions Dev should be in ops discussions Shared runbooks/escalakon plans Ops should give devs access to systems Dev s responsibility ends when it s in produckon Throwing it over the wall is dead Done Means Released Avoid Blaming No fingerpoinkng!

12 DevOps Tenant #2: Technology Use config mgmt to build environments Scripts checked in and managed as src Infra as Code Shared Version Control Single system for code and build arkfacts Every Kme someone commits a change it triggers a build and automated build verificakon tests Ship trunk Enable features through flags If something breaks, re- deploy. Don t fix Fix environment setup scripts Don t Fix Anything One Step Build/ Deploy One bugon build/deploy (manual) Scheduled builds/deploys If verificakon fails, stop and alert

13 DevOps Is In the Eye of the Beholder What s important is that you adhere to principles that lead to business value

14 Culture and Principles Are more important than Are more important than > > People Processes Tools are important!

15 Old Culture and ExpectaKons Don t Work! Commonly overheard in offices It ll take us three months to build you a development environment I have to stay up all night to do a build Uh...that s not my problem. Go talk to Ops That code change will have to wait for our monthly build Why does your code always break my infrastructure? The new switch we need is sikng on the loading dock

16 AdapKng IT skill sets: Topics Culture adopkon of DevOps AutomaKon - New Tools Making it happen

17 Resources are Available to Help Make the Change Copyright 2015, Oracle and/or its affiliates. All rights reserved.

18 PaaS / IaaS Now Allows Resources to be Easily Provisioned Past: Ops manually provisioned each layer ApplicaKon Today: Developers can provision enkre stacks of hardware + somware through REST API App Server JVM OperaKng System Hypervisor Compute PaaS IaaS Storage Network

19 Good Technology is Now Available DevOps technology all < 10 years old 2008 Chef New Relic SOASTA 2012 Ansible Vagrant Gradle Puppet Git SaltStack Jenkins Docker Capital + mechanical automakon always win over labor

20 Investment in DevOps Shows No Signs of Slowing DevOps- related technology solves real business problems 90 Cumula%ve Investments in Puppet and Chef, Cumula%ve $ Raised ($m) Puppet Chef

21 Popular DevOps Technology Remember: You can't get DevOps by buying a single product Configura%on Management Ansible Puppet Chef SaltStack Con%nuous Integra%on Con%nuous Delivery Ansible Jenkins / Hudson Rundeck Version Control Git Perforce Subversion Docker Vagrant Virtualiza%on Build & Func%onal Tes%ng Gradle Jenkins / Hudson Robot Arquillian Binary Management ArKfactory Nexus

22 Did We MenKon Docker? Google Trends Interest Over Time 22

23 AdapKng IT skill sets: Topics Culture adopkon of DevOps AutomaKon - New Tools Making it happen

24 Oracle is serious about Cloud Development Lifecycle OperaKons mointoring, metrics, showback Plauorm- as- a- Service Infrastructure- as- a- Service

25 Using Developer Cloud Service for DevOps What is It? Hosted offering for sekng up development infrastructure Integrates Hudson, Git, Maven, Eclipse, JDeveloper, and Netbeans to offer a complete development environment as a service What Problems Does it Solve? Facilitates discussion Supports done means released ethos Prevents you from having to do it on your own How Does it Support DevOps? Offers shared version control, one step build/deploy and collaborakon tooling as a hosted service Features include a dashboard, tasks, one- step build, code reviews, one- step deploy, wiki, integrakon with IDEs 25

26 Using Enterprise Manager for DevOps What is It? Manage/monitor cloud, applicakons, middleware, databases, and hardware Agent/controller- based system Best for on premises workloads What Problems Does it Solve? Support infrastructure as code by allowing for enkre environments to be hydrated, stored, and dehydrated Centrally manage and monitor all hardware and somware How Does it Support DevOps? ApplicaKon performance management ApplicaKon quality management Manage/monitor cloud, applicakons, middleware, databases, and hardware 26

27 Using Oracle PaaS for DevOps What is It? What Problems Does it Solve? Java- based PaaS offered on premises (Oracle Exalogic) and off premises (Oracle Cloud). Whether deployed on/off premises, it s called Java Cloud Service Includes automakc provisioning of applicakon server, infrastructure, storage and database Prevents you from manually sekng up and provisioning a plauorm Full lifecycle is built in to the solukon Save costs - pay for what you use How Does it Support DevOps? Offers a ready- built plauorm for deploying your applicakons to. You deploy your applicakon - Oracle worries about provisioning and managing Same code powers both private and public versions; very easy portability 27

28 Using IaaS for DevOps What is It? Comprehensive IaaS solukon offered on (Oracle Exalogic) and off (Oracle Cloud) premises Includes secure provisioning of hardware, network and operakng system What Problems Does it Solve? Prevents you from manually sekng up and provisioning infrastructure Infrastructure lifecycle is built in to the solukon Save costs - pay for what you use How Does it Support DevOps? Offers ready- built infrastructure for you to install your somware to - Oracle worries about provisioning and managing Same code powers both private and public versions; very easy portability 28

29 Oracle Can Help You Lead Change in Your OrganizaKon But real change begins with you How Oracle Can Help with DevOps DevOps Tenet #1: Culture Respect Discuss Avoid Blaming Your responsibility Simplify InstallaKon Shrink RunKme Done Means Released Simplify DevOps Tenet #2: Technology Shared Version Control Infrastructure as Code One Step Build/Deploy Don t Fix Anything Your responsibility, but can help Support Lifecycle Simplify Provisioning 29

30 Oracle is Serious About DevOps Oracle products support DevOps DevOps Tenet #1: Culture DevOps Tenet #2: Technology Respect Discuss Avoid Blaming Done Means Released Shared Version Control Infrastructure as Code One Step Build/Deploy Don t Fix Anything Light Fast Modular Modern Easy 30

31 More deployment choice should not equal more complexity Automate. Automate. Automate. DEPLOY ANYWHERE On Premise Private Cloud Oracle Public Cloud 3 rd Party Public Cloud Cloud shouldn t mean you should have a different set of of tools and processes You should be able to use the same tools, same APIs in- cloud or on- premise

32 Oracle Product Development IT (PDIT) Suppor%ng enterprise, development IT, cloud and managed hos%ng at Oracle 602 Exadata 383 Exalogic 69,290 Sun x86 servers 6,854 SPARC servers 1,768 Sun ZFS appliances Thousands of other systems 924 Oracle Products 135,000 Employees Copyright 2015, Oracle and/or its affiliates. All rights reserved. 32

33 PDIT is Modernizing Using Oracle Products Servers per System Admin Storage Devices per Storage Admin TB of Storage per Storage Admin Q1 FY14 Q1 FY14 Q1 FY14 Q4 FY13 Q4 FY13 Q4 FY13 Q3 FY13 Q3 FY13 Q3 FY13 Q2 FY13 Q2 FY13 Q2 FY13 Q1 FY13 Q1 FY13 Q1 FY13 Q4 FY12 Q4 FY12 Q4 FY x 2.8x 3.6x 33

34 How Did PDIT Improve Efficiency by > 2x in 18 Months? Culture changes enabled by technology powered by + + powered by Culture (Campbell Webb, Sr. VP, Oracle) Cloud The Same Products Oracle Sells Infrastructure Automa%on 34

35 Other PDIT Changes Standardize Hardware Standardize Somware (N, N- 1) IaaS (Nimbula/OpenStack) Symmetric Test/Prod/DR Environments Nearline Backups, Compression, Dedup VLAN s => VxLAN s Big Data Security AnalyKcs (Hadoop) ElasKcsearch+Logstash+Kibana AnalyKcs OrchestraKon (McollecKve) Comprehensive Monitoring CMDB / Asset Management ProacKve Monitoring Offshoring (1 x US + 2 x IDC shims) Maximize DepreciaKon Defense in Depth Security Posture Centralized IdenKty Management Config Management (Chef/Puppet) 35

36 Oracle Cloud is Provisioned Using Chef Oracle Cloud is run on Chef Database Services Java Services Developer Services Mobile Services Messaging Services Storage Services Iden%ty Services No%fica%on Services Caching Services Collabora%on Services Analy%cs Services Applica%on Store Powered By 36

37 So what about you?

38 AcKvely Build Trust Trust is the #1 ingredient to a successful DevOps culture Dev + Ops + Social AcKvity Outside Work + Time = Trust

39 PracKcal steps - How to get there Start small. Prototype. Sponsor bolom- up change and Evangelize. Longer Kme to market (inikally) due to work required to automate High up- front costs due to automakon work AutomaKon always pays off over Kme Start with a small team with a mix of experience Include seasoned veterans that yours teams respect and will listen to Include new blood to focus on new processes who doesn t need to unlearn how things have historically been done

40 Steps Required to Change Culture Empower Change From the Bogom Up Align Interests Bring In New Blood Build Trust Let Dev + Ops collaborate to find solukons Let Dev + Ops jointly pick tools. Limit corporate mandates Don t restrict the choice of public cloud solukons Put Dev + Ops people under same line- level managers Change the way you measure/reward performance Flagen org chart to reduce fiefdoms Hire technical people who are skilled in DevOps Set up training for DevOps skills Bring in consultants to help get started Sponsor teambuilding events Give Dev + Ops common goals to work towards When there's a failure, don't dwell on Dev or Ops failure 40

41

42

43 OrganizaKonal Misalignment Leads to DysfuncKon Pre- DevOps org structure CEO CIO CFO IncenKvized to keep systems up VP of OperaKons VP of Development IncenKvized to innovate VP of Finance IncenKvized to keep ops busy by building each layer the old way Layers of Middle Management Layers of Middle Management IncenKvized to keep developers developing. Ops is someone else s job Layers of Middle Management Sys Admin Developer Ops and developers report to CIO through different tracks, have opposing management, and opposing incenkves Full stack developers cost a lot of money - don t fit into exiskng salary bands Accountant Wants a fix to business problem ASAP. Can t wait for Kme required to automate 43

44 Change Your OrganizaKon s Structure Incen%ves drive behavior CIO CIO VP of OperaKons VP of Development VP of Product IncenKvized to innovate and release Layers of Middle Management Layers of Middle Management Layers of Middle Management Sys Admin Developer Sys Admin Developer Report to same manager. IncenKvized to work together to develop and release 44

45 DevOps ImplicaKons To Business Time Longer Kme to market (inikally) due to work required to automate More builds / faster Kme- to- market for individual features Lower MTTR because problems are fixed by rebuilding Higher MTBF due to increased accuracy Cost High up- front costs due to automakon work Low ongoing costs because roukne operakons is automated Lower capex, higher opex as workloads shim to cloud Culture ConKnues to empower developers AutomaKon increases operakonal efficiencies Distracts developers from developing code Movement eschews rockstars but that s naturally what happens 45