User Requirements for

Cloud Computing Architecture
Roger Clarke, Xamax Consultancy, Canberra
Visiting Professor in Computer Science, ANU
and in Cyberspace Law & Policy, UNSW

2nd International Symposium on Cloud Computing
Melbourne, 17 May 2010
http://www.rogerclarke.com/II/CCSA {.html,.ppt}

Copyright
2010

1

User Requirements for Cloud Computing Architecture
AGENDA





Copyright
2010

Precursors / Related Concepts
A Working Definition
An Architectural Framework
User Benefits
Disbenefits and Risks
• Operational
• Contingent
• Security
• Business
Implications
2

The Gartner Hype-Cycle for Emerging Technologies

QuickTime™ and a
TIFF (Uncompressed) decompressor
are needed to see this picture.

" ... a snapshot of the relative maturity of technologies ...
"They highlight overhyped areas against those that are high impact, estimate how
long they will take to reach maturity, and help organizations decide when to adopt"
Copyright
2010

3

.html 4 ..media-history-through-gartner-hype..blogspot.com/2008/08/. Copyright 2010 http://adverlab.QuickTime™ and a TIFF (Uncompressed) decompressor are needed to see this picture.. .

uploads/2007/10/gartner2007. Copyright 2010 http://www..jpg 5 .com/blog/wp-content/. ..QuickTime™ and a TIFF (Uncompressed) decompressor are needed to see this picture..lostinthemagicforest..

.media-history-through-gartner-hype.blogspot.. Copyright 2010 http://adverlab.. .QuickTime™ and a TIFF (Uncompressed) decompressor are needed to see this picture..html 6 .com/2008/08/.

com/it/page.Copyright 2010 The Gartner Hype-Cycle – 2009 http://www.gartner.jsp?id=1124212 7 .

) • On the Rise • Cloud Services Governance • Cloud-Driven Prof'l IT Services.995 (53 pp. Solutions • Cloud Computing/SaaS Integration • Cloudbursting/Overdraft • Cloud Service Management Tools • Tera-architectures • Virtual Private Cloud Computing • Application Platform as a Service • Cloud Computing for the Enterprise • DBMS in the Cloud • Private Cloud Computing • Business Process Utility • Hybrid Cloud Computing • Cloud Application Development Tools • Cloud-Based E-Mail Services • Cloud-Enabled BPM Platforms • Cloud Security Concerns • Cloud Storage Copyright 2010 • • • At the Peak • Elasticity • Enterprise Portals as a Service • Cloud/Web Platforms • Compute Infrastructure Services • 'In the Cloud' Security Services • Cloud Computing • Public Cloud Computing/the Cloud Sliding Into the Trough • Real-Time Infrastructure • IT Infrastructure Utility • SaaS Climbing the Slope • SaaS Sales Force Automation • Virtualization • Cloud Advertising • Grid Computing • Integration as a Service http://www.Gartner Hype Cycle for Cloud Computing July 2009 – $US 1.gartner.com/DisplayDocument?id=1078112&ref=g_sitelink 8 .

e.Predecessor Terms • • • • • • • • • Computing as a utility / 'computer service bureaux' / 'data centres' – 1960s.g. 1970s Application Service Providers (ASPs) – 1980s working from home / tele-work – 1980s working on the move / 'road warrior' – 1990s docking portables to corporate networks portable-to-desktop synchronisation Internet Service Providers (ISPs) – late 1980s Web Services – 2000 Service-Oriented Architecture (SOA) – early-to-mid-2000s Copyright 2010 Related Concepts • • • • • • • • Software as a Service (SAAS) – late 1990s. Salesforce Cluster Computing – inter-connected stand-alone computers are managed as a single integrated computing resource Grid Computing – computational resources are assigned dynamically Peer-to-Peer (P2P) architectures Server-Virtualisation Infrastructure as a Service (IaaS) – 2006 Platform as a Service (PaaS) – 2006 Anything as a Service *aaS / AaaS 9 .

rather than assigning resources to particular clients) • rapid elasticity (i. virtualized. dynamically-scalable. resource usage is metered) Copyright 2010 10 . platforms.e. October 2009): • on-demand self-service (i. in which a pool of abstracted.e.Cloud Computing Definitions • • "a large-scale distributed computing paradigm that is driven by economies of scale. automated response by servers to direct requests by clients) • broad network access (i. managed computing power. 2008. using any device) • resource pooling (i.e.e. at the Grid Computing Environments Workshop) five 'essential characteristics' (NIST. and services are delivered on demand to external customers over the Internet" (Foster et al. resources are scalable according to demand) • measured service (i.e. storage. from anywhere. the provider allocates resources according to demand.

e.The User Organisation Perspective A Working Definition A service that satisfies all of the following conditions: • it is delivered over a telecommunications network • users place reliance on the service for data access and/or data processing • the data is under the legal control of the user • some of the resources on which the service depends are virtualised. nor where the hosting device is located • the service is acquired under a relatively flexible contractual arrangement. the user has no technical need to be aware which server running on which host is delivering the service. at least re the quantum used Copyright 2010 11 . i.

through commoditisation of service levels. and it's negotiable) • of host location.Cloud Computing is a Form of Outsourcing How is it different from earlier forms? • • • Scalability ('there when it's needed) Flexible Contractual Arrangements ('pay per use') Opaqueness ('let someone else worry about details') • which means less user control: • of the application. through resource-virtualisation • Copyright 2010 12 . through SLA dependence (assuming there's an SLA.

QuickTime™ and a TIFF (LZW) decompressor are needed to see this picture. CSA (2009) 'Security Guidance for Critical Areas of Focus in Cloud Computing' Cloud Security Alliance. April 2009 Youseff L. & Da Silva D.Sample Architectures QuickTime™ and a TIFF (LZW) decompressor are needed to see this picture. (2008) 'Toward a Unified Ontology of Cloud Computing' Proc. Butrico M. Grid Computing Environments Workshop.. 2008 Copyright 2010 13 .

.S.QuickTime™ and a TIFF (LZW) decompressor are needed to see this picture. Venugopal S. and reality for delivering computing as the 5th utility' Future Generation Computer Systems 25 (January 2009) 599-616 14 .. Fig. hype. Broberg J. 3 High-level market-oriented Cloud architecture Copyright 2010 Buyya R. Yeo C.. & Brandic I. (2009) 'Cloud computing and emerging IT platforms: Vision.

CC Architecture – The User Organisation Perspective Intermediating Infrastructure Copyright 2010 15 .

Intermediating Infrastructure Copyright 2010 A Comprehensive CC Architecture 16 .

CC's Potential Benefits • • • Copyright 2010 Enhanced Service Accessibility • Access to Services that are otherwise unavailable • Access to Services from multiple desktop devices • Access to Services from scaled-down devices • Access to Services from multiple device-types Other Technical Benefits • Professionalised backup and recovery • Scalability • Collaboration convenience • Copyright convenience Financial Benefits • Lower Investment / up-front cost • Lower Operational Costs • Lower IT Staff Costs 17 .

Downsides – The User Perspective • Operational Disbenefits and Risks Dependability on a day-to-day basis • Contingent Risks Low likelihood / Potentially highly significant • Security Risks Security in the broad • Business Disbenefits and Risks Beyond the merely technical Copyright 2010 18 .

reliability. integrity after bug-fixes. and customisability • Reliability – continuity of operation • Availability – hosts/server/database readiness/reachability • Accessibility – network readiness • Robustness – frequency of un/planned unavailability (97% uptime = 5 hrs/wk offline) • • Resilience – speed of resumption after outages Recoverability – service readiness after resumption • Integrity – sustained correctness of the service.Operational Disbenefits and Risks • Fit – to users' needs. mods Copyright 2010 19 . and the data • Maintainability – fit.

proven recovery procedures. escrow inspection. rights that are proof against actions by receivers • • • Data Survival – data backup/mirroring and accessibility Compatibility – software. protocols. data formats Flexibility Customisation Forward-compatibility (to migrate to new levels) Backward compatibility (to protect legacy systems) Lateral compatibility (to enable escape) Copyright 2010 20 . versions.Contingent Risks • • Major Service Interruptions Service Survival – supplier collapse or withdrawal Safeguards include software escrow.

second-party and third-party threats to any aspect of reliability or integrity • Data Security Environmental. both in remote storage and in transit • Authentication and Authorisation How to provide clients with convenient access to data and processes in the cloud. while denying access to imposters? • Susceptibility to DDOS Multiple.Security Risks • Service Security Environmental. but choke-points will exist Copyright 2010 21 . separate servers. second-party and third-party threats to content.

evidence discovery law. Retention Second-Party (service-provider abuse). financial services regulations. Third-Party ('data breach'.Business Disbenefits and Risks • Acquisition Lack of information. due diligence. Use. Company Directors' obligations re asset protection. because of high switching costs High-volume data transfers (large datasets. non-negotiability of terms of contract and SLA • Ongoing Usage Loss of corporate knowledge about apps. Arkansas) Copyright 2010 22 . law of confidence. Storage in Data Havens (India. risk management • Privacy Breach – Content Access. costs to deliver Inherent lock-in effect. replication/synch'n) • • Service Levels to the Organisation's Customers Legal Compliance Data protection law. business continuity. IT services. 'unauthorised disclosure').

.. • • • Copyright 2010 23 .Some Risk Management Strategies • Risk Assessment • Contract Terms Service Level Agreement (SLA) Multi-Sourcing • Parallel in-house service • Several compatible suppliers .

Restrictions on maintenance 7. 1. Responsibilities 1. Clearance information (with location and date) 1. Types of users 3. Response times from applications 3. Service Continuity commitments 1.g. Numbers and types of transactions 2. Required types and levels of support 1. Required capacity (lower/upper limit) for the service. Maintenance slots 8. Availability targets 3. Area/ locations 2. Business justification 2.ITILv3 SLA Checklist – Edited Down! 1. Types of infrastructure to be supported 4. Costs and pricing 1. Procedures for announcing interruptions to the service 8.php/Checklist_SLA_OLA_UC 24 .com/index.g. Types of users (user groups granted access to the service) 3. List of annexes http://wiki. Service and asset criticality 1. Change history 14. Requirements for scalability 4. Contract duration 1. Conditions under which the service is considered to be unavailable 2. Mandated technical standards and spec of the technical service interface 11. Business cycles (daily. Service name 2. Vital Business Functions (VBFs) supported by the service 2. Description/ desired customer outcome 1. Downtimes for maintenance 6. e. Duties of the service provider 2. Business processes/ activities oncust side supported by the service 3. IT Security aspects to be observed when using the service 12. Other critical assets used within the service 2. Desired outcome in terms of warranty 5. Identification of business-critical assets connected with the service 1. Reaction and resolution times 2. public holidays) 3. Capacity/ performance targets and commitments 1. Maintainability targets (usually defined as MTRS) 5. Time within which normal service levels must be restored 10. Area/ locations 2. Reference to further contracts which also apply (e. On-site support 1.g. Customer 3. Start and end dates 2. SLA) 7. Numbers and types of users 3. Reaction and resolution times Copyright 2010 9. Requirements regarding availability reporting 2. Remote support 1. Responsibilities of service users (e. Reliability targets (usually defined as MTBF or MTBSI ) 4.en. Exceptions (e. Rules for penalties/ charge backs 13. Estimation of the business impact caused by a loss of service or assets 6. Availability targets and commitments 1.g. Time within which a defined level of service must be re-established 2. Hours when the service is available 2. weekly) and seasonal variations 2. Desired outcome in terms of utility 4. Rules regarding termination of the agreement 4. with respect to IT security) 4. Duties of the customer (contract partner for the service) 3. Cost for the service provision 2. Requirements regarding capacity and performance reporting 3. weekends. Service Level Manager 2. Service times 1.it-processmaps. Types of infrastructure to be supported 4. Service level requirements/ targets 1.

User Requirements Essential Features • • • • • Copyright 2010 Assured Data Integrity Assured Service Integrity Assured Compliance with legal requirements within jurisdictions to which the user organisation is subject Warranties and indemnities in the contract. terms of service and SLA (if any) But who audits and certifies? 25 .

uncertain reliability.. convenience. UP3: CC is applicable depending . and adjuncts to analysis and decision-making. not essential operations Trade off loss of control.Categories of Use-Profile • • • UP1: CC is completely inappropriate • 'mission-critical systems' • systems embodying the organisation's 'core competencies' • applications whose failure or extended malperformance would threaten the organisation's health or survival UP2: CC is very well-suited Uses of computing that are highly price-sensitive. etc. scalability. • can the risks be adequately understood and managed? • trade-offs between potential benefits vs. contingent risks against cost-advantages.. uncontrollable risks Copyright 2010 26 .

Privacy Policy Enforcement Measures. to enable: • • • • Server Privacy Policy Statement User Privacy Rqmts Statement Comparison of the two Preclusion of Usage where Requirements are not satisfied 27 . Compliance Assurance • • • • • • • Service Security Service Access Controls Data Transmission Security Data Storage Security Data Use (by service-provider) Data Disclosure (by others) Jurisdictional Location(s) of Data Storage Copyright 2010 3.User Requirements for CC Infrastructure 1. Integrity Assurance • • Service Integrity Data Integrity 2. Declaration. Measurement • • • • • Service Reliability Levels Service Survival Protections Data Survival Protections Service and Data Compatibility Service and Data Flexibility 4.

OpenID) Jurisdictional Locations of Hosts must be controlled These all depend on CCAs including specs and implementation of multiple special-purpose components and features Privacy management must go beyond 'privacy through policy' and 'privacy by design' to 'Privacy through Architecture' Copyright 2010 28 . APIs. and externally-managed identities (Shibboleth. but also the client side and intermediating functions Security Risk Assessments and Solutions must be end-to-end rather than limited to the server side CCA designers must address the risks arising from vulnerable user devices and vulnerable clients Client authentication must be achieved through components. encompassing not only the server side.Implications for Cloud Computing Architectures • • • • • • • CCAs must be comprehensive.

and terms of contract and SLA • Copyright 2010 29 . applications. 2008. 5 – UC Berekeley) • CC may be just another marketing buzz-phrase that leaves corporate wreckage in its wake CC service-providers need to invest a great deal in many aspects of architecture. critical characteristics were missing" (Armbrust et al..Conclusion • "Past efforts at utility computing failed. infrastructure. and we note that in each case one or two . p..

. UNSW 2nd International Symposium on Cloud Computing Melbourne.ppt} Copyright 2010 30 .rogerclarke.User Requirements for Cloud Computing Architecture Roger Clarke. 17 May 2010 http://www. ANU and in Cyberspace Law & Policy. Xamax Consultancy.html.com/II/CCSA {. Canberra Visiting Professor in Computer Science.

Sign up to vote on this title
UsefulNot useful