Chris Kemp: NASA Nebula
3 likes623 views
The document discusses NASA's views on cloud computing. It notes that NASA currently has many websites running on different platforms, which results in high costs, long provisioning times, security issues, and other problems. NASA is interested in cloud computing because it could help the agency focus more on its missions and science rather than infrastructure. The document then provides NIST's definition of cloud computing and outlines five key cloud attributes. It introduces NASA's Nebula hybrid cloud platform, which is designed for science, collaboration, developers, and partners. Finally, it discusses federal cloud computing standards and governance.
Chris Kemp: NASA Nebula
- 2. Part 1: NASA’s View of Cloud
- 3. Why is NASA focused on cloud? Many, many, many websites Many, many, many different platforms Very high operating cost Long provisioning times Very large attack surface Confusing to outside users Lock-in, portability, and interoperability issues
- 4. More reasons… Missions are focused on the Mission Scientists are focused on the Science Large-scale infrastructure requirements Too much is spent on infrastructure Missions Completely Fail (OCO) Missions Completely Succeed (Rovers) Politics impact Missions (Triana)
- 5. NIST Definition of Cloud Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.
- 6. 5 Cloud Attributes Service-based Scalable and elastic Shared Metered by Use Uses Internet Technologies Excerpts from Gartner‟s “Five Attributes of Cloud Computing”
- 7. Service-based Abstracted from the implementation Completely automated Near real-time delivery (seconds or minutes)
- 8. Scalable and Elastic Resources are drawn from a common pool Dynamically allocated to meet demand Dynamically released when appropriate Fully automated
- 9. Shared Common resources build economies of scale Common infrastructure runs at high efficiency
- 10. Metered by Use Consumers pay for services used Underlying hardware costs are irrelevant
- 11. Uses Internet ‘Standards’ Open standards and APIs Almost always IP, HTTP, and REST
- 12. Part 2: Nebula
- 13. Nebula: A Hybrid Cloud
- 14. Built for Science Science-Class Cloud CPU Computing High CPU-to-Disk Ratio Disk Built for Research MAE-West Peering (Internet2, Web NLR, CENIC, 11 Tier-1 ISPs) Massively Parallel, Loosely Coupled In a Federal Security Perimeter
- 16. Cloud Platforms, Compared AWS AppEngine Nebula Storage S3, EBS SimpleStorage Luster API Database SimpleDB CouchDB MySQL Queue SQS -- RabbitMQ Virtualization EC2 (Xen) -- Eucalyptus (KVM) Framework -- Django Django User Accounts -- Google eAuth Accounts Search -- Google Search SOLR+Lucene Networking 1GigE 1GigE 10GigE+ CDN/Cache CloudFront Varnish
- 17. Application Time to Market Current Web App Process NEBULA Cloud Platform Procure Server – 6-12 weeks Procure VM – 60-120 seconds Configure Server – 2-3 days Included. AWRS Filing – 2-3 days Already done. (APPS.NASA.GOV) Set up Source Control – 2-3 hours. Included. Security Plan – 3 weeks, min. Included. SSL Certificates – 2-4 weeks. Included. Develop Terms of Use – 6 months. Included, for most collaboration. eAuth Integration – 40 hours. Included. Develop Processes – 3-6 weeks. Basic moderation included. Set up backups – 2-3 hours. Included. 24,192,000 Seconds. 60-120 Seconds.
- 18. Must insert budget wedges now!
- 19. Built for Collaboration True Single-Sign-On, for the Public Enterprise Search, across the Cloud All Cloud apps live at apps.nasa.gov
- 20. Built for the Web Friendly URLs Designed for Search Engines, RSS, and aggregation Components are RSSable, Tweetable What if NASA was on the first page of Google results for the term „Space‟?
- 21. Built for Partners Your science partners can instantly connect from your NEBULA app, to their own research tasks within public Cloud Services (EC2, Azure, AppEngine) Your private fleet of Post-Docs can work on your data – at 10 cents an hour
- 22. Built for Government Policy compliant for contributions Consolidated moderation interface Everything-compliant (PII, First Amendment, COPPA, Section 508, etc)
- 23. Built for Developers Integrated Development Environment Revision control Automated testing Continuous Integration Bug tracking
- 24. Built for Community Cloud means Turnkey Dedicated Platform Staff Engaged External Partners Common KB shares code, tricks, tips
- 25. Nebula - the way to Data.gov Best practices in moderation, open collaboration Open and Public APIs, everywhere Feeds (RSS, Atom) power mash-ups Open-source platform, apps, and data Full transparency
- 26. Pilot Projects White House USASpending.gov 2.0 Microsoft World Wide Telescope (Mars / Moon) Google Earth Planetary Content (Mars) LMMP Program Data Processing (Moon) TOPS Earth Climate Modeling
- 27. Nebula Timeline Under development since May 2008 Pilot projects underway now Full Launch, Q2 2010 (in Apps.gov) Concurrent Open Source Release of Code
- 28. Part 3: Federal Standards
- 29. Federal Cloud Computing Governance CIO Council • Strategic Objective Definition • Overall Guidance • Adjudication PMO (GSA) Cloud Computing Executive Steering Committee (ESC) • Day to Day Management of • Strategic Direction the Federal Cloud Computing • Priority Setting Initiative • Issue Resolution • Development of required • Approval deliverables • Provide Technical Guidance and Subject Matter Expertise Cloud Computing Advisory Council (AC) • Provide Collaborate Federal Agency Input and Feedback for Cloud Computing Initiatives/Deliverables • Support the PMO and Cloud Computing Subcommittee with Federal Subject Matter Expertise • Approve Cloud Computing deliverables for submission to the Cloud Computing ESC • Cross-Functional Collaboration
- 30. Cloud Standards Working Group CC Advisory Council Mission Statement: Drive the government-wide adoption of cost effective, green and sustainable Federal cloud computing solutions. CC Standards WG Mission Statement: Establish a framework and roadmap to drive standards to facilitate interoperability, portability, security and manageability for federal cloud computing services.
- 31. Federal vs. Commercial Our Focus Federal Requirements Commercial Requirements
- 32. Goal of Federal Standards Activities Provide guidance to industry and government for the creation and management of relevant cloud computing standards allowing all parties to gain the maximum value from cloud computing
- 33. Government Cloud Framework Cloud User Tools Software as a Service (SaaS) / Applications Application User/ Reporting & Integration Admin Analytics Citizen Engagement Gov Productivity Gov Enterprise Apps Business Svcs Portal Wikis / Blogs Email / IM Customer / Apps Core Mission Account Social Networking Virtual Desktop Mgmt Analytic Apps API‟s Core Cloud Services Agency Website Legacy Apps Tools Office Automation User Profile Hosting (Mainframes) Workflow Mgmt Data Mgmt Engine Platform as a Order Testing Developer Reporting Service (PaaS) Database Tools Tools EAI Mgmt Directory Knowledge DBMS Trouble Services Mobile Device Mgmt Mgmt Integration Billing / Infrastructure as a Virtual Data Migration Invoice Storage Service (IaaS) Machines Tools Tracking Product CDN Web Servers Server Hosting ETL Catalog Service Mgmt & Delivery Capabilities Service Performance DR / Operations Provisioning SLA Mgmt Provisioning Monitoring Backup Mgmt Cloud Service Security & Data/Network Certification & Authentication & Auditing & Data Privacy Data Privacy Security Compliance Authorization Accounting Data Center Routers / Internet Hosting LAN/WAN Facilities Firewalls Access Centers
- 34. Focus on Business Use Cases 1 Description Focus Business Business Use Cases present Define boundaries Use Case and describe a top level view of a and characteristics category of related cloud of a business focus business issues area 2 Scenario Scenarios illustrate a particular Describe conditions facet of a business use case in for the scenario and order to highlight kinds of the required kinds of standards needed standards to fulfill the need 3 Example Examples animate a scenario Show how a with a limited and specific case to scenario plays out in illustrate practical implications of a real world situation a scenario including references to with reference to potential standards existing standards 4 implementations where available Detail Use Case Detail Use Cases break down a Defines specific scenario into actual functional activities. NOT components, tasks and activities. PART OF This is the traditional CURRENT “programming” use case used in DISCUSSION SDLC
- 35. Business Use Case 1: Initiating Cloud Service Description An agency wishes to initiate a new cloud service Service Models IaaS, SaaS, PaaS Pre-conditions None Post conditions Target services commissioned and provisioned Key Considerations Security policy specification including location dependencies and Dependencies Identity federation and management (All) Physical infrastructure selection, sizing and configuration (IaaS) Virtual Machine selection, sizing and configuration (IaaS) Storage selection, sizing and configuration (IaaS) Provisioning /deployment standards and specifications (IaaS, PaaS) Monitoring and management specification (All) Application and Document lifecycle specification (All) Platform selection and configuration specification (PaaS) Application selection and configuration specification (SaaS) Service Level specification and benchmarking (All) References and Cloud Computing Use Cases Group 3.6.2 Notes Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09
- 36. Scenario 1.1 Establish IaaS Service Conditions Agency wishes to establish an IaaS Service Requirements Identity management standards to establish identity, authentication and authorization Security standards related to encryption, location-specific data storage, etc. Specification standards for physical boundaries, e.g. shared, dedicated or community pools of processors, networks, storage devices, etc. Specification standards for virtual resources including virtual machines, standard images, storage and virtual network configuration Provisioning standards to specify virtual resource elasticity parameters Monitoring and management standards for thresholds and controls Lifecycle standards for storage replication, retention and destruction Service level standards Desired Results Essential portions of infrastructure are provisioned by standard specification References and Notes Cloud Computing Use Cases Group 3.6.1 Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09
- 37. Example 1.1.1 IaaS for Scientific Computing Description Agency wishes to establish an IaaS Service for process-intensive scientific computing Activities Authorized individual accesses an IaaS provider by preexisting account Declare identity domain by referencing established federated identities (SAML, WS-Federation, Liberty, ID-FF) Declare standards-based authorization /entitlement rules (XACML) Declare key management and data encryption at rest and in flight (PKI, PKCS, KEYPROV (CT-KIP, DSKPP), EKMI) Declare physical boundaries: SPARC processors and SAN disk-accessable storage, drawn from community pool X only, shared machines and devices allowed (Standards do not exist) Define virtual resources: Specify multicore high memory instances and large amounts of nonpersistant storage (Standards do not exist) Select a vendor-specific virtual image (DMTF OVF) using a standard query and selection API (Standards do not exist) following risk based security standards (PCI-DSS) Define a persistent storage structure and mapping (Amazon S3, GFS, Azure Storage, SNIA CDMI) Define a VPN configuration (Amazon EC2) Declare provisioning rules (OGF OCCI, EC2 API) Declare new instance spinup at 85% utilization of all running instances and termination at 20% utilization of any instance (Standards do not Exist) Declare notification at 105 instances and notification and end of escalation at 150 (Standards do not Exist) Declare data backup on a nightly basis to CONUS resource, and data destruction after 60 days (ISO 15489 but no implementation standards) Service level standards (Standards do not Exist) References and Notes Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09
- 38. Business Use Case 2: Changing Cloud Vendors Description An agency wishes to migrate some or all of a set of existing cloud services to a new vendor Service Models IaaS, SaaS, PaaS Pre-conditions • An existing set of cloud services with source vendor • A plan for replacement or migrated services with destination vendor Post conditions • Source services decommissioned • Target services operating with minimal loss of data, security or business rule functionality Key Considerations Identity federation and management across vendors and Dependencies Security specification standards across vendors Industry-specific common standards for application types (SaaS) Platform standards and configuration (PaaS) Platform component (middleware) standards and configuration (PaaS) Application language standardization and portability (PaaS) Virtual machine standards, configuration and portability (IaaS) Storage standards and configuration (IaaS) References and Cloud Computing Use Cases Group 3.6.2 Notes Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09
- 39. Scenario 2.1 Migrate SaaS Vendors Conditions Agency has an existing SaaS application and wishes to migrate all or part of it to a similar application with a new vendor Requirements Identity management standards to migrate identity, authentication and authorization Security standards related to encryption, location-specific data storage, etc. Storage standards for migrating existing data Application-specific formatting standards for importing or reusing data Application-specific business rule standards (in some cases) Service level standards Desired Results Users are able to access new application with appropriate permissions Migrated data is available within the defined security envelope Business rules are in operation on the target system References and Notes Cloud Computing Use Cases Group 3.6.1 Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09
- 40. Scenario 2.2 Migrate PaaS Vendors: Similar Platform Conditions Agency has an existing PaaS platform and wishes to migrate to a similar platform from another vendor 1. Requirements Include Identity, Security, Storage standards from 1.1 Platform standards for configuring and managing platform operation and management Platform standards for configuring and managing application deployment Platform enabler standards for configuring and operating databases, message queues, service buses and related enablers Desired Results Users are able to access new application with appropriate permissions Migrated data is available within the defined security envelope Business rules are in operation on the target system References and Notes Cloud Computing Use Cases Group 3.6.2, 3.6.3 Scope reduced to exclude migrations across dissimilar platform stacks 1 1 Similar platform refers to migration within similar PaaS stacks, e.g. LAMP to
- 41. Scenario 2.3 Migrate PaaS Vendors: Dissimilar Platform Conditions Agency has an existing PaaS platform and wishes to migrate to a dissimilar platform from another vendor 1. Requirements Include all requirements from Scenario 1.2 Language standards and cross-language portability standards or compatibility APIs Data management standards and API‟s to address different data models across platform, e.g. relational versus flat Desired Results Users are able to access new application with appropriate permissions Migrated data is available within the defined security envelope Business rules are in operation on the target system References and Notes Cloud Computing Use Cases Group 3.6.2, 3.6.3 Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09 1 Similar platform refers to migration within similar PaaS stacks, e.g. LAMP to
- 42. Business Use Case 3: Hybrid Cloud Operation Description An agency wishes to operate services across multiple clouds hosted by multiple vendors, potentially including private or community clouds Service Models IaaS, SaaS, PaaS Pre-conditions Services in multiple clouds with established SOA interoperability Post conditions Services interoperating across cloud boundaries Key Considerations Include: Business Case 1: Initiate Cloud Service and Dependencies Transactional and Concurrency standards Additional security standards for cross-cloud trust References and Cloud Computing Use Cases Group 3.4.1. Note that Transactionality Notes is excluded for Hybrid by CCUC but included here Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09
- 43. Business Use Case 4: Platform Configuration and Operation Description An agency wishes to configure a platform on which to develop, test or deploy SaaS applications Service Models PaaS Pre-conditions Available cloud infrastructure if required by the platform Post conditions Scalable platform available for development, testing or deployment of SaaS applications Key Considerations Include: Business Case 1: Initiate Cloud Service and Dependencies Platform standards and configuration (PaaS) Platform component (middleware) standards and configuration (PaaS) Application language standardization and portability (PaaS) Platform management and reporting standards (PaaS) References and Grance, Mell (NIST) A Roadmap for Cloud Standards, 9/15/09 Notes
- 44. Next Steps Federal Standards Web Workshop Crowd-source ideas for roadmap 3rd week of January Open public invitation Federal Standards Summit April 2010 Present Federal Roadmap Present Prioritized Federal Use Cases