View
7
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
Introduction
• What is cloud computing?– When computing services are provided over the Internet rather
then locally on a user’s own machine.– Computation is run on an supporting infrastructure which is
independent of the applications themselves.– The infrastructure can take on many forms, but to the end user,
the implementation is irrelevant, hence the “cloud” abstraction.
• What isn’t cloud computing?– Cloud computing does not necessarily include grid computing,
resources as a utility, or self managing computing.– Each of these can however be used in some cloud computing
systems, but cloud computing can also be done with free and decentralized architectures.
Types of Cloud Computing Services
• Software as a service– Software is provided to end users in an “On-demand” fashion.– Reduces upfront costs, i.e. buying multiple licenses– “Utility-based” computing
• Infrastructure as a service– An “infrastructure” referring to much of the background hardware
(contrast to software) needs of an organization
• Platform as a service– When the software needed to develop cloud applications are
themselves provided in a “software as a service” fashion
Software as a service
• A common problem:– Business software installed on a work computer cannot be used
from other computers (home, mobile computers) because the EULA doesn’t allow it (licensing costs)
– Remote access a possibility, but issues with uptime, security…– Instead the software is abstracted to a cloud application which
can be accessed anywhere via cloud client (e.g. web browser)
• Features of Software as a Service:– Commercial software that can be used and configured over a
network, file servers and remote configuration storage, one application used by many clients, application updateability.
Software as a service: Types
• Multi-level architectures:– Level 1: Customized, Ad-hoc basis– Level 2: Configurability– Level 3: Configurability + multi-tenancy– Level 4: Configurability + multi-tenancy + Scalability
• Virtualization in contrast with multi-tenancy
Infrastructure as a service
• Components of Infrastructure as a service:– Computing hardware
• E.g. Client Storage Space, Processing power needs
– Virtualization• E.g. VM Ware, VirtualBox
– Networking• Security, communication speeds, servers
– Internet Access• Connecting clients applications to servers anywhere
– Utility Computing• E.g. Charging by hour, gigabyte, process load
– Contracts• Specific service levels which must be adhered too.
Platform as a service
• Implements the “Software Lifecycle” on the cloud.• Common S.E. practices: client elicitation, software
design, component design, implementation, testing, maintenance, data handling and documentation
• How does it work?– Cloud servers allow not just hosting of completed application,
but applications in progress– U.I. design tools right inside the web browser to use them– Provides testing in real situations: heavy client loads– Automatic integration with other data sources on the cloud– Tools for the developers to work efficiently with one another– Profit simulations
Clouds: Heavier than you think
• A lot of constituent elements are necessary to make Cloud Computing work:– Cloud applications– Cloud clients– Cloud hardware– Cloud platform– Cloud services– Cloud storage
Example: Google Apps
Cloud Application(Google Docs)
Cloud Client(Mozilla Firefox)
Cloud hardware(Apps Server)
Cloud Platform(Apps Engine)
Cloud Services(Word Processing)
BigTable
Cloud storage(BigTable DB)
Cloud Architecture
• Heavily relies on communication and communication protocols
• Standards are implemented openly (publicly) to aid collaboration between services
• Software designers are “cloud architects”, software is integrated into the cloud system by a “cloud integrator”
• API’s extremely important – “Without APIs, there is no cloud computing.” – Dave Rosenberg
Role-based Cloud Computing
• Providers– Responsible for creation and maintenance of the hardware
infrastructure which supports cloud computing applications.
• Developers– Responsible for the creation of software to be ran on a cloud
computing system. Often works with provides for integration.
• Users– Responsible for the consumption of cloud-computing services.
• Vendors– Responsible for creation and distribution of lower-end platforms
for cloud computing.
Ideal Cloud Computing
• Low cost for users and providers• Independence of device and software• Efficient utilization of all resources• Constant, or near-constant uptime through the
use of resource distribution• Ability to continually add new users and
applications by easily increasing resources when necessary
• Data is secure with policies to protect its security
How to keep the clouds floating
• Cloud Computing issues– Security of providers access to user data– Trustworthiness of providers– Security of data placement– Security of data representation– Recoverability of data– Tracking of illicit activities on the cloud– Long-term costs of cloud development– “Vendor” lock-in
Advantages Advantages VS.VS.
DisadvantagesDisadvantages
• Eliminating the need for expensive long-distance leased lines
• Reducing the long-distance telephone charges for remote access.
• Transferring the support burden to the service providers
• Operational costs
• Cisco VPN Savings Calculator
Advantages: Cost Savings
Flexibility of growth
Efficiency with broadband technology
Advantages: Scalability
VPNs require an in-depth understanding of public network security issues and proper deployment of precautions
Availability and performance depends on factors largely outside of their control
Immature standards
VPNs need to accommodate protocols other than IP and existing internal network technology
Disadvantages
Applications: Site-to-Site VPNs
Large-scale encryption between multiple fixed sites such as remote offices and central offices
Network traffic is sent over the branch office Internet connection
This saves the company hardware and management expenses
Site-to-Site VPNs
Applications: Remote AccessEncrypted connections between mobile or
remote users and their corporate networksRemote user can make a local call to an ISP, as
opposed to a long distance call to the corporate remote access server.
Ideal for a telecommuter or mobile sales people. VPN allows mobile workers & telecommuters to
take advantage of broadband connectivity. i.e. DSL, Cable
Industries That May Use a VPN Healthcare: enables the transferring of confidential patient
information within the medical facilities & health care provider
Manufacturing: allow suppliers to view inventory & allow clients to purchase online safely
Retail: able to securely transfer sales data or customer info between stores & the headquarters
Banking/Financial: enables account information to be transferred safely within departments & branches
General Business: communication between remote employees can be securely exchanged
Statistics From Gartner-Consulting*
50%
63%
79%
90%
0% 20% 40% 60% 80% 100%
Access to network forbusiness
partners/customers
Site-to-site connectivitybetween offices
Remote access foremployees while
traveling
Remote access foremployees working out
of homes
% of Respondents
Percentages
*Source: www.cisco.com
Some Businesses using a VPN
CVS Pharmaceutical Corporation upgraded their frame relay network to an IP VPN
ITW Foilmark secured remote location orders, running reports, & internet/intranet communications w/ a 168-bit encryption by switching to OpenReach VPN
Bacardi & Co. Implemented a 21-country, 44-location VPN
Where Do We See VPNs Going in the Future?
VPNs are continually being enhanced.
Example: Equant NV
• As the VPN market becomes larger, more applications will be created along with more VPN providers and new VPN types.
• Networks are expected to converge to create an integrated VPN
• Improved protocols are expected, which will also improve VPNs.
24
Agenda
• What and why is Cloud Computing?
• Cloud Computing and Storage
• Ensembles as Cloud and Enterprise Infrastructure
• Storage Ensembles
Cloud Computing
Notes:
Abstraction – alleviates IT consumers from the operations of applications, allowing end users to focus instead on the execution and high-value activities
Virtualization – access to business services on-demand independent of location and resource constraints
Dynamic allocation – dynamically provisions, configures, reconfigures, and de-provisions IT capability as and when needed, transparently and seamlessly
Speed and reliability through standardization, higher level of automation, and abstractionFlexibility through virtualization, dynamic resource sharing, and proactive capacity allocationEfficiency through higher level of automation, catalog standardization, and prioritization
SOA
Service Mgmt
Emerging model where users can have access to applications or compute resources from anywhere through their connected devices through a simplified UI
Applications reside in massively-scalable data centers where compute resources can be dynamically provisioned and shared to achieve significant economies of scale
A strong service management platform results in only marginal incremental management cost, if any, when more workload needs to be handled by the cloud
Virtual-ization
Information
Key Attributes of Cloud Computing
Simple “self service” user interface
where underlying technology and
services are irrelevant to the user.
*A Service Management platform allows an operations management team to collect or discover information about how the resources associated with a service are configured and consumed and then access that information to support integrated management processes that address changes to and problems with the service.
When adding IT resources to
the service, the incremental
cost to manage these new
resources approaches zero
Provides for an infinitely scalable
pool of connected computing
resources
Although often associated with Internet Services, clouds will exist
both inside a data center to support that customers & internal
users as well as supporting third-party managed service offerings.
Efficient, green, and cost effective
infrastructure
• AaaS - Architecture as a Service • BaaS - Business as a Service • CaaS - Computing as a Service• CRMaaS - CRM as a Service• DaaS - Data as a Service • DBaaS - Database as a Service• EaaS - Ethernet as a Service • FaaS - Frameworks as a Service • GaaS - Globalization or Governance as a Service• HaaS - Hardware as a Service • IaaS - Infrastructure or Integration as a Service• IDaaS - Identity as a Service • LaaS - Lending as a Service • MaaS - Mashups as a Service • OaaS - Organization or Operations as a Service• SaaS - Software as a Service• StaaS - Storage as a Service• PaaS - Platform as a Service • TaaS - Technology or Testing as a Service• VaaS - Voice as a Service
A variety of ‘as-a-Service’ terms have been used to describe the
services offered in Clouds:
Who’s Offering Cloud Services today?
3Tera Grid-based Platform For Cloud AppsAkamai Application Performance ServicesAmazon.com Amazon Web ServicesAretiInternet Virtual HostingBungee Labs Virtual Labs-as-a-Service softwareCohesiveFT Cloud PlatformElastra Hosted Elastic ComputingEMC Storage Cloud – Decho(Mozy, Pi) + Cloud Infrastructure &
Services DivisionEnki Computing UtilityFlexiscale Utility Computing on DemandFortress ITX DynamicGridGoogle Search ServicesHP Adaptive Infrastructure as a ServiceiCloud Desktop CloudIBM Computing Cloud, Advanced UIs, Deep Capacity on DemandJoyent Accelerator for ApplicationsLayered Technology GridLayerMicrosoft CRM, email and IM ServicesMosso Hosting CloudSalesforce.com Force.comTerremark InfinistructureXCalibre FlexiScale
29
Cloud Computing Users and Business ModelsMain actors and their interaction mode in the use and delivery of Cloud
Services, enable the identification of the models and evolving technologies that support the Cloud Computing strategy:
• Acquisition Model (Service): "All that matters is results; I don't care how it's done"
• Business Model (Pay for usage): "I don't want to own assets - I want to pay for elastic usage, like a utility"
• Access Model (Internet): "I want accessibility from anywhere, from any device"• Technical Model (Scalable, elastic, shareable): "It's about economies of scale, with
effective and dynamic sharing"
Service Consumers
Service Catalog,ComponentLibrary
CloudAdministrator
DatacenterInfrastructure
Monitor & ManageServices & Resources
Component Vendors /Software Publishers
Publish & UpdateComponents,Service Templates
AccessServices
IT Cloud
Garter, 2008
Cloud Computing: A New Paradigm
Enterprise Cloud
Network Cloud
INNOVATIVE BUSINESS MODELS
End Users / Requestors
Government/ Academics
Industry(Startups/ SMB/ Enterprise) Consumers
• An “Elastic” pool of high performance virtualized compute resources
• Cloud applications enable the simplificationof complex services
• A cloud computing platform combines modular componentson a service oriented architecture
• New combinations of services to form differentiating value propositions at lowercosts in shorter time
• Internet protocol based convergence of networks and devices
SIMPLIFIED SERVICES
Source: Corporate Strategy
Cloud computing perceived benefits and demand drivers• Awareness and demand for cloud computing are fueled by perceived / potential benefits to business
entities, individual users, and IT providers (includes enterprises + service providers)
Cloud computing’s “nirvana-like” promise drives higher service level expectations among business
entities and individual users
Which in turn puts pressure on the enterprise data center to deliver higher service quality (at lower
cost)
IT Providers
Key Benefit:
Competitivenes• Lower TCO• Faster Time to Market• Higher Cust Rentention• Service quality• Resource optimization• Resiliency• Flexibility• Efficiency• “Green”• Enhanced chargeback
Business Entities
Key Benefit:
Innovation • Faster, easier innovation• New business models• New products and services• Faster time to market• Lower IT cost• Lower IT risk (brand
protection)• Improved IT user productivity• Improved Client Satisfaction• Improved Disaster Recovery
IT Users
Key Benefit:
Quality of Experience• Speed of access• Ease of access
(anywhere, anytime)• Ease of use• Minimal software
requirements on access device
• No long-term commitments
Model for Delivering Cloud Services (single provider)
Fulfillment Services
• End Users make requests using a catalog of services• The Provider delivers service using fulfillment processes and technology• Services are normalized to achieve Abstraction and Encapsulation
Fulfillment Process
Fulfillment + Enterprise Process (e.g. Open Account)
Fulfillment + Enterprise Process + Governance (e.g. ITIL)
Provisioning Services
Usage & Accounting
Services
MonitoringServices
SecurityServices
EnergyManagement
Services
Technology
….
End User Requestors& Operators
…
ServiceRequestor
Service CatalogRequest UI
Operational UI
ServiceProvider
ServiceCreator
Federated Data Repository
ServiceDefinition
Tools
ServicePublishing
Tools
ServiceFulfillment &Configuration
ToolsUI, Fulfillment, Data, MetaData
ServiceMonitoring
ToolsKPIs
ServicePlanning
August 24, 2008
Architectural Model for Cloud Computing
End User Requests
& Operators
…
Service Request & Operations
Design & Build
Image Library (Store)
Deployment
OperationalLifecycle of Images
IT Infrastructure & Application
Provider
ServiceCreation & Deployment
Virtual Image Management
Service CatalogRequest UI
Operational UI
Standards Based Interfaces
Virtualized Infrastructure
Service Management
Service Oriented Architecture Information Architecture
Standards Based Interfaces
Service Catalog,Component
Library
DatacenterInfrastructure
Cloud Administrator
AccessServices
Optimized Middleware(image deployment, integrated security, workload mgmt., high-
availability)
Service Oriented Architecture Information Architecture
User Request Management/Self Service Portal
Security: Identity, Access, Integrity, Isolation, Audit & Compliance
Usage Accounting
License Managemen
t
Image Lifecycle
ManagementProvisioning
Performance
Management
Availability/Backup/ Restore
Service Lifecycle Management
Service Management
Virtual Resources & Aggregations
SMP Servers Network HardwareStorage Servers
System Resources
Blades Storage
Virtualized Infrastructure
Server Virt. Storage Virt. Network Virt.
The Role of Storage in Clouds - 1 Deep Infrastructure
(What cloud?)
Service Management
SOAApplicationMiddleware
Virtualized InfrastructureServer / Storage / Network
Virtu
al Im
ag
e
Ma
na
ge
me
nt
Clo
ud
Se
rvic
e
Us
er
The ‘Cloud Service’ is an application or upper layer function, or a platform service
e.g. Salesforce.com, hosted computing
“Application computing” is done by the Cloud Service and is co-located with the storage
Incremental cost and time to add a new user is effectively zero
Desired Storage Infrastructure is the same as advanced Enterprise Storage (only cheaper)
Integrated server & storage managementAutomated provisioningPerformance & security controlsChargebackTCO challenges
Value of the Cloud ServiceComplete application stack offload
Compute
Requires some new/better storage function
The Role of Storage in Clouds - 2 Storage Application
As a Cloud Service
Service Management
SOAStorage Application
Storage Optimized Infrastructure
Virtu
al Im
ag
e
Ma
na
ge
me
nt
Clo
ud
Se
rvic
e
Us
er
The ‘Cloud Service’ is a Storage Intensive application or upper layer function
e.g. Medical Image ArchiveBackup/DR for SMBData WarehousingContent servingClient could be an individual or a server farm
Desired Storage Infrastructure is an optimized Storage Application
Archive + Indexing + Search, long term retentionVideo/large object access
Local compute limited to:Ingest and playbackOptimization, management
Value in the Cloud ServiceMulti-tenancyContentSpecialty storage application
ComputeCompute
Requires some new/better storage function
Requires specialty storage/function
The Role of Storage in Clouds - 3 ‘Storage in the Cloud’
(like the old SSPs)
Service Management
SOAStorage Application –
Device emulation
Storage Optimized Infrastructure
Virtu
al Im
ag
e
Ma
na
ge
me
nt
Clo
ud
Se
rvic
e
Us
er
Storage devices are seen as local, deployed across the cloud
E: drive on laptop/desktops – Amazon S3‘Capacity on Demand’ for server farms
Desired Storage Infrastructure is a very low cost ‘Network Virtual Disk’ facility
Upsell services? Archive + Indexing + Search, long term retention
Local compute limited to:Ingest and playbackOptimization, management
Value in the Cloud ServiceConvenience, costCapacity on demand
ChallengesMulti-tenancyCostPerformanceApplication Synergy
Compute
Compute
Making Cloud Computing a Reality requires:
Virt
ualiz
atio
n
Integrated virtualization and management with optimized systems and networks to break the lock between IT resources and business services
Autonomic ManagementAutonomic management methods for both application and infrastructure services to meet user needs and expectations for delivery of high quality of service
Ensembles
Simplified IT infrastructure, reduced complexity and management through the creation of large, consistent pools of resources that are managed as one.
Software
Services
Hardware
Methods for IT Simplification
Business Processes as Services
Service oriented architecture technologies frame business processes as services, ease of deployment, composition, reuse, change…
Topologies of federated services must be mapped onto large numbers of diverse physical and virtual resources
Heterogeneous servers, storage, networks
“Enterprises report that IT operational overhead = 70% of their IT budgetand growing . . . leaving precious few resources for new initiatives.”
– Forrester, 2007
OLD
Virtual Resource Objects/Appliances, Libraries will reduce the labor required for software stack development and management
Ensemble
Ensemble
Ensemble
Ensembles, scalable pools of like systems that are manageable as single systems will replace multitudes of individual servers and reduce the labor required for physical systems management
Service management software spans the diversity of heterogeneous physical and virtual resources, providing unified cross-platform management in support of SOA
NEW
Ensemble Components
An Ensemble generally consists of the following components:– A pool of compatible system nodes (e.g., N physical servers; need not be
homogeneous)
– Virtual resource mobility within an ensemble and with compatible ensembles
– The networks which interconnect the ensemble nodes (may be local / optimized)
– Resource virtualizers (hypervisors, I/O virtualizers, storage virtualizers, …)
– An ensemble manager appliance that provides platform management for the ensemble virtual and physical resources
– Tools for planning, ensemble creation, P2V migration, image mgmt. & composition, …
– Ensemble-local automated optimization software of performance, availability, energy usage, security, … with intelligent defaults
– Multi-system services (locking, caching, message queuing, …) may be integrated with some ensembles
OS OS OS
Hypervisor
Server
OS OS OS
Hypervisor
Server
WorkloadMobility
Server Ensemble Example
EnsembleManager
Ensemble definition:a pool of like systemsthat is manageable asa single system
Standards for Cloud Storage• Service access interfaces
• Storage service interfaces– Provisioning– QOS– Performance management– Chargeback accounting– Data protection– Storage Security
• Storage infrastructure management interfaces (SMIS)
Service Management
SOAApplicationMiddleware
Virtualized InfrastructureServer / Storage / Network
Virtu
al Im
ag
e
Ma
na
ge
me
nt
Clo
ud
Se
rvic
e
Us
er
Compute
41
What is Cloud Computing?
Multiple Choice: Cloud Computing is…• A way to access applications hosted on the web
through your web browser (Software as a Service -- SaaS)
• A pay-as-you-go model for IT resources accessed over the Internet (Platform as a Service – PaaS)
• Use of commodity computers, distributed throughout an internet, to perform parallel processing, distributed storage, indexing and mining of data
• Gartner: “Cloud computing is a style of computing where massively scalable IT-related capabilities are provided ‘as a service’ across the Internet to multiple external customers”
• An IT buzzword that assures potential clients that your product is on the cutting edge of technology
• All of the above
42
Common Cloud Themes
They’re big – massively scalable Always there when you need them – on-demand, dynamic Only use what you need – elastic, no upfront commitments, use on
short term basis Out there on the network somewhere – accessible via Internet,
location independent Transparent – complexity concealed from users, virtualized,
abstracted Service oriented – easy to use, SLAs, accessible
Simple MetaphorLike Power Company
Better MetaphorCooperatively OwnedSemiconductor Fab
43
IT Trends enabling (and driven by) Cloud Computing
Increased Parallelism New Moore’s Law - 2X processors per chip generation Parallel software industries emerging to address challenges Redundant networks and storage increasing performance
Increased Virtualization Processing, Storage, Bandwidth, Delivery
Commodity Components X86 servers, consumer hard drives, ethernet Open Source SW – Freedom to customize and adapt
Increased Outsourcing of Core Elements “By 2012, 80 percent of Fortune 1000 companies will pay for
some cloud computing service, and 30 percent of them will pay for cloud computing infrastructure.” Gartner
44
Commercial Cloud Formation
45
Cloud Deployment Models
Deployment Models:• Internal (private) cloud. The cloud infrastructure is operated
within the consumer’s organization.• Community cloud. The cloud infrastructure is jointly owned
by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations).
• Public cloud. The cloud infrastructure is owned by an organization selling cloud services to the general public or to a large industry group.
• Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (internal, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability. NIST working definitions
46
Business Case for Cloud Computing
Automation/On-Demand = Better, Faster & Cheaper• Moving from ‘hand crafted’ software to repeatable assembly• Reuse of interchangeable components• Repeatable processes with increased automation & collaboration• Division of labor – let developers focus on new software• Ease of use – abstract complexity out of developers’ lives• Avoid over & under provisioning – CAPEX outlays
Data Intensive Computing• Ability to index and make sense of large data sets – parallization• Pre-format data in large repositories for low BW transmissions• Better access to data with large multi-tenant distributed cloud databases• Default backup and most cost effective archival of large data sets.
Accessibility = Any time, any place, any device• Cloud serviced clients• Leverage low cost compute cycles and assured data storage in the cloud• Communications is pacing factor• Challenge is to balance platform agnostic vs. end point device innovations
47
Ease of Assembly - Fabrication
Abstract complexity away from developers & users (virtualization, widgets, open APIs)
Put skills in the machines, enabling use of semi-skilled rural work force
Moving from hand crafted -> repeatable assembly.
Let SW developers focus on value add new functionality, let others focus on repeatable hosting and underlying platform tasks
Division of labor, specialization
Repeatable SW development CM processes with increased automation & collaboration
New materials handling processes
Interchangeable abstracted resources, reuse of SW components, web service standards
Interchangeable parts, engineering tolerances
Cloud SW Development & Deployment, Data Fusion
2009
Assembly Line – Muskets -> Ford
1815
48
Cloud Related Service Offerings
• GoDaddy.com• Rackspace• Savvis
• Managed Hosting• Collocation• Internet Service Provider• Unmanaged hosting
Physical Infrastructure
Adapted from Forrester Research Taxonomy
• Akamai• Amazon EC2• CohesiveFT• Mosso (from Rackspace)• Joyent Accelerators• Nirvanix Storage Delivery Network
• Virtual servers• Logical disks• VLAN networks• Systems Management
Virtual Infrastructure-as-a-Service
• Google App Engine and BigTable• Microsoft SQL Server Data Services• Engine Yard• Salesforce.com’s Force.com
• Development-platform-as-a-service• Database• Message Queue• App Servicer• Blob or object data stores
Software-platform-as-a-Service
• Amazon Flexible Payments Service and DevPay• Salesforce.com’s AppExchange• Yahoo! Maps API• Google Calendar API• zembly
• APIs for specific service access for integration• Web-based software service than can combine to create new services, as in a mashup
App-components
-as-a-Service
• Flikr• Myspace.com• Cisco WebEx office• Gmail• IBM Bluehouse
• Rich Internet application web sites• Application as Web Sites• Collaboration and email• Office Productivity• Client apps that connect to services in the cloud
Software-as-a-Service
ExamplesTypes of OfferingsCloud Market Types
Level ofAbstraction
49
RACE Rapid Access Computing Environment – What is it Today?
Track - Thursday, April 23 1:30-2:30 PM CSD - Cloud Computing & Software as a Service
Track - Thursday, April 23 1:30-2:30 PM CSD - Cloud Computing & Software as a Service
forge
50
RACE Phase IIa Pathway to Production (dev-test-
prod)
Track - Thursday, April 23 1:30-2:30 PM CSD - Cloud Computing & Software as a Service
Track - Thursday, April 23 1:30-2:30 PM CSD - Cloud Computing & Software as a Service
51
Extending the Cloud to Deployed Users
WebWebServicesServices
CDN/WOA/PEPsCDN/WOA/PEPsRIA RIA
SynchronizationSynchronizationLow BW protocolsLow BW protocols
User-hosted CachesFixed Sites
RichWeb-based
Access
Remote/MobileAccess
Diverse Users
DiverseInfrastructures
SMART-T_v04
DISA Delivery Efforts• GCDS Akamai• EFDS• JIPM• TSP/GBS• IW• PS4 • UVDS• Consumer RIA Clients
Track - Wednesday, April 22, 3:00-4:30 PM PEO-GES Accelerating and Optimizing the Delivery of InformationTrack – Friday, April 24 8:00 – 9:00AM PEO-GES GIG Content Delivery Service and EFD WorkshopTrack - Tuesday, April 21 4:30-5:30 PM PEO-STS Joint IP Modem (JIPM)Track – Wednesday, April 22, 3:00-4:30 PM PEO-STS Joint IP Modem (JIPM)
Track - Wednesday, April 22, 3:00-4:30 PM PEO-GES Accelerating and Optimizing the Delivery of InformationTrack – Friday, April 24 8:00 – 9:00AM PEO-GES GIG Content Delivery Service and EFD WorkshopTrack - Tuesday, April 21 4:30-5:30 PM PEO-STS Joint IP Modem (JIPM)Track – Wednesday, April 22, 3:00-4:30 PM PEO-STS Joint IP Modem (JIPM)
52
CTO Cloud Research Areas of Interest
• Automated Dev -> Test -> Production Capabilities• Data Clouds
– Applicability of cloud “shared nothing” databases to C2 app challenges
– Common structured data stores handling multiple data models
• Utility Computing Programming Models for Production Environments
• Common Edge Caching & Acceleration Techniques• Cloud serviced client platforms
– Enterprise Mashups: Shindig/GWT, JackBe Presto– Geo-visualization – NASA Worldwind– Mediaplayers – VLC– Mobile computing– Virtual Desktop Infrastructure (VDI) soft & hard thin clients
• Common HW Infrastructure Templates & Data Center Practices
53
Programming ModelsWhat’s the right fit for DoD?
Compute Storage Networking Content Delivery
Hardware ResourcesPhysical
infrastructure
Software-platform-as-a-
service
App-components-as-
a-service
Virtual-Infrastructure-
as-a-Service
Data IntensiveAmazon Hadoop, Public Data Sets, Simple DB
GoogleApp Engine
GCDS Akamai
54
CTO Cloud Research Outreach
• Partnering with other cloud researchers in DoD/IC aka Multi-Agency Cloud Computing Forum
• Working to track any emerging vendor neutral standards
• Intellipedia-U site for DISA cloud computing research https://www.intelink.gov/wiki/Cloud_Computing_Research_Program
Let us know about your cloud effortsWe want to partner & share!
Let us know about your cloud effortsWe want to partner & share!
Tom GreenfieldDISA Office of the CTO
Email: [email protected]
55
Some Suggested Readings
• “Above the Clouds: A Berkley View of Cloud Computing” 10 Feb 09 – Great overview of cloud computing < 20 pages
• Study– Amazon Web Services– Google App Engine – MS Azure (future)
• “Data Analysis Challenges” JASON Report, Dec 2008 – Good description of cloud applicability to DoD data analysis challenges
56
Increasing the Value of “our” CloudClouds Exhibit Network Effect
• More participation increases value of the system to everyone
• More indexed data = greater opportunity to uncover patterns & make connections
• More participation in collaborative SW development = increased contributions of reusable code
• More design interactions = more seamless interfaces and lower friction processes
• More use = greater statistical multiplexing of loads = increased ability for surge computing
• More use = more machines = better economies of scale