Open Source in the Cloud

Transcription

1 Open Source in the Cloud

2 Open Source in the Cloud Moderator: Pete Tseronis Senior Advisor, U.S. Department of Energy Panelists: Mark Ryland National Standards Officer, Microsoft Dr. David McQueeney Vice President, Technology and Stratey, Chief Technology Officer, IBM Federal Brian Stevens Chief Technology Officer and Vice President, Engineering, Red Hat Henry Sienkiewicz Technical Program Director, Computing Services Directorate, Defense Information Systems Agency

3 Mark Ryland National Standards Officer Microsoft

4

5

6

7 Dr. David McQueeney Vice President, Technology and Strategy Chief Technology Officer IBM Federal

8 GOSCON, 2009 Some Thoughts on Open Source and the Cloud Brian Stevens Red Hat CTO, VP Engineering 05 November 2009

9 DECODING THE STATE OF THE CLOUD the signal-to-noise ratio is a tad low

10

11 WHY SHOULD A USER CARE? Because they can Quickly deploy applications and services Eliminate the need to procure and manage hardware Pay only for what they consume Scale up and down as they need Deploy an app, anywhere, any time (internal or on-premise, physical to bare metal)

12

13 THE ROLE OF OPEN SOURCE Accelerating cloud capability and adoption by Federating the technology to eliminate barriers for cloud providers Opening APIs and code to millions of researchers and developers to advance the technical obstacles of security, migration, etc. Serving as the de facto standard for ensuring rich interoperability and compatibility between clouds

14 THE OPEN SOURCE ROADMAP FOR CLOUD ENABLEMENT Defining the future for open source cloud infrastructure: Linux as the Hypervisor (Linux/KVM) - Cloud Abstraction Layer - Virtual Compute Node API Identity and Authentication Server - Application Orchestration- Security Hardening - Appliance Builder:

15 bstevens at redhat dot com

16

17 Defense Information Systems Agency: Vision & Mission Vision Leaders enabling information dominance in defense of our Nation Mission DISA, a Combat Support Agency, engineers and provides C2 capabilities and enterprise infrastructure to continuously operate and defend a global net-centric enterprise in direct support to joint warfighters, National level leaders, and other mission and coalition partners across the full spectrum of operations Network Services Program Executive Offices Computing Services 17 17

18 Defense Enterprise Computing Centers (DECC) 4,000,000+ users 2,900+ team members Defense Working Capital Fund (DWCF) 14 facilities Maintenance 445,000 sq ft raised floor Medical 34 mainframes 6,100 servers Command and Control 3,800 terabytes of storage 2,800 application / database instances 215 software vendors Logistics Financial 18

19 Building the Cloud Foundation Capacity on Demand Innovative Services Contracts Acquire processing & storage capacity as a service provided by vendor partners Pay much like a homeowner pays for utilities, e.g., by megawatt-hours, BTUs, call-minutes, CPU-hours consumed Benefits Reduces time to add capacity Reduces overhead Simplifies our cost drivers Streamlines operating system management Facilitates technological currency Virtualization Why? Many benefits: Consolidation Reduces footprint Deployment Eases provisioning of new workloads Agility Increases support for changing workload demands and fail-over situations Protection Lowers barriers to disaster recovery Savings Fewer machines means fewer administrators, less power, floor, space, and cooling Utilization Enables multiple systems to run on highperformance hardware Price Reduces the cost of service delivery and lowers the total cost of ownership day turnaround (average) 29% virtualized across DECC enterprise

20 The Cloud A style of computing where massively scalable (and elastic) ITrelated capabilities are provided as a service to customers using Internet technologies. What s new? Acquisition Model: Based on purchasing of services Business Model: Based on pay for use Access Model: Over the network to ANY device Technical Model: Scalable, elastic, dynamic, multi-tenant, & sharable Source: Gartner Computing As A Service 20

21 DISA Cloud Services Portfolio Data-as-a-Service Forge.mil Software-as-a-Service Software Development RACE GCDS Compute/Store Content Delivery Platform/Infrastructure-as-a-Service 21

22 Rapid Access Computing Environment (RACE) 1 October 2008 Development/Test 24-hour automated provisioning Customer root access Ability to promote from Dev to Test Standard CSD Operating Environments Minimized and streamlined accreditation Increase capacity ~ 24 hours Month-to-month service Reduced cost Today FY10 Initiatives Production User self-service provisioning within the PRODUCTION environment Ability to promote from test to production Streamlined/Automated accreditation Pre-established inherited IA controls SIPRNet deployment Complete integrate accreditation automation processes Continue to refine RACE Portal Interface with Forge.Mil Projects Complete integration with DISA standardized configuration management system (BladeLogic) 22 User Self-Service ~ Highly Standardized ~ Cost Effective ~ Fast

23 RACE User Interface 23

24 Application Accreditation in RACE Path-to-Production Execution Process Streamlined and automated IA C&A Standard process for customer Accreditation time reduced from 80+ days to 40 days End state objective of 7 days for C&A Test & Development Promote emass: Enterprise Mission Assurance Support to Production System (emass) : Automates the creation of select DIACAP artifacts Populates DISA s inherited controls into the workflow process Provides customer an advanced, dynamic workflow management tool 24

25 GIG Content Delivery Service (GCDS) The Global Information Grid (GIG) Content Delivery Service (GCDS): DoD OSD designated standard for content delivery service Managed by the Defense Information System Agency (DISA's) Computing Services Directorate (CSD). GCDS is a global platform Uses Akamai technology, that provides intelligent routing and caching of web-based content. Interfaces with web-based applications and portals. Requires the local system be configured to allow GCDS to handle communications between it and the Defense Information Systems Network (DISN). DISN CLOUD ARMY NAVY AIR FORCE MARINES DoD Pending TOTAL NIPRNET SIPRNET TOTAL As of Sept

26 Applications-As-A-Service: Forge.mil (Software Development) Systems Development Life Cycle (SDLC) Analysis Design The logical process used to develop an information system Includes requirements validation, training, and user ownership Planning Maintenance DoD SDLC First standardized approach to an enormous problem Proven development model Based on the open source community s approach Works like a library Code checked out, worked on, & checked in Im plem entation Forge.mil Bits & Pieces Public: Freely available to all DoD users Shared: All DoD users can access the same code development environment for DoD open source and community source software Available: General availability on March 27, 2009 Common evaluation criteria and an agile certification process to accelerate the certification of reusable, net-centric solutions Limited Operational Availability: October 2009 Private: Allows a closed development environment for DoD projects and programs Fee-for-service Availability: October 2009 DoD s Software Development Life Cycle 26

27 Forge.mil and RACE: Accelerating the Path to Production Production Zone Dashboard, Reporting & Monitoring Build Libraries & Code Repositories Cloud Test & Certification Services T&E Zone Development Zone Developers Testers Users Certifiers Decision Authorities Im plem enting t he plat form and services to support evolving governance processes and standards 27

28 Challenges and Barriers Current Balancing Security and Usability User Validation Virtualization; servers, firewalls, networks Access Business processes Flexible funding; credit cards, speeding MIPR process Cultural inertia Sharing the vision Convincing Box Huggers Controlling expectations Why can t it.. Future Security optimization Shared accreditation Validation of customer applications Integrating Software as a Service Accessing federated and shared services Varying interpretations of security guidelines Business streamlining Each Service and Agency has unique processes Funding hurdles Capital (Procurement) vs. Operating 28

29 Develop Within The Decision Cycle Orient Observe Decide Our strength is in our ability to make decisions better and faster than adversaries Web 2.0 technologies accelerate this cycle Software development has to keep up Act Military Decision Making Cycle Requirement Procure Code Test Certify Total Time to Production Traditional Approach 6 Months 6-12 Months 6 Months Months Cloud Approach 24 Hours 2-6 Months Days 3-6 Months 29

30 30

31 Backups 31

32 Enabling the Cloud Environment Infrastructure Standardization Consolidation Capacity Services Virtualization Content Delivery Rapid Provisioning Services Software (SaaS) Applications Communications Processes Metrics & benchmarking ITIL Service Level Management (SLM) Security (Certification & Accreditation (C&A)) It s A Journey 32

33 Consolidations and Savings Service/ Agency consolidation under DMRD Reduced number of mainframe sites from 194 to 71 Saved $320M/year DISA SMART DISA consolidation Megacenter consolidation under QDR and DMRD DRI 918/BRAC Reduced Reduced number of mainframe mainframe sites sites from 16 from 71 to 16 to 5 Saved Saved $206M/year $203M/year DISA combat support computing transformation Continuing computing transformation Mainframe & Server consolidation 4 primary sites w/ remote system mgmt Centralized all business functions Saved $143M/year Reduced sites from 18 to 13 Saved $XXXXM/year 33

34 Forge.mil: Agile Development Environment Building an Agile Development Environment for the DoD Collaborative environment for enabling agile software development and reuse Integration with the RACE Cloud to enable a continuous integration approach Automate system build processes Automate testing Expand the Sandbox Deliver existing DoD tools and services into the cloud Code analysis, unit testing, build testing, performance testing, interoperability testing, IA testing Integration with test networks and development labs Incorporate simulations and sandbox versions of production services Streamline and automate the deployment governance processes Enable dynamic execution of GIG Governance policies and procedures 34

35 Lessons Learned Recommendations: Understand that it s a journey Recognize that the infrastructure fundamentals matter Know your marketplace recognize that this is a different marketplace than normal IT operations Clearly define the marketplace offering Adjust the launch to satisfy requirements not timelines ensure Engage with the software developers much earlier in the design What critical success factors?: Which portion of cloud computing? How will you define and measure the return on value analysis? How will you define and measure the return on investment analysis? 35

36 A Combat Support Agency Computing Technology & DECC Evolution Percentage Change 1800% Mainframe Processing Distributed Processing Cloud Computing 1600% 1400% 1200% IBM & UNISYS platforms Centralized database processing Full data replication (since FY00) Silos Virtual Tape Systems Client-Server solutions Server Virtualization Internal storage Networks (SAN) Services- based acquisitions Storage Area Dynamic provisioning Enterprise resource Planning (ERP) implementations Utility pricing 1000% 800% 600% 400% Storage Workload Server Workload 200% Cost 0% -200% Continuous DECC consolidations and transformations have yielded significant reductions in unit cost

37 Panel Discussion

38 Questions? Tell us what you think: Complete the survey