You are on page 1of 42

Cloud Notation for Users

A cloud modelling notation for business users to express requirements
concepts
Towards a business user driven view of cloud computing

Workshop to discuss idea and approach

August 26, 2010

Webex details
 Meeting Date: AUG 26, 2010
 Start Time: 5:00 PM Europe/London
BST (British Summer Time)
 http://meetingplace.capgemini.co.uk/a/9121233649110
e2c70928189629c5061
 UK Number: 01483 788788
 International Number: +44 1483 788788
 Meeting ID: 0127
Please, go to mute during the first part of the
presentation - do not put your phone on hold during
the meeting

Looking for active volunteers….

Agenda
 A walk through the Cloud Business Notation ideas
and concepts - 30 minutes - by Mark Skilton
 A discuss on the ideas and concepts presented - all
 Identify advantages and any concerns that need to
be addressed - all
 Identify ideas on how the Cloud Notation may fit with
other architecture models - the intention is to work
with other stack type models such as NIST, TOGAF
for example - to generate different views of cloud
models for different types of stakeholders , both
technical and business oriented.

Introduction
 The following notes and diagrams are from
the meeting attended by a range of
participants at the Cloudcamp Boston July 21
 The objective was to identify ideas and
approaches to define a Cloud Computing
Reference Architecture that better defined
and represented the evolving nature of the
Cloud and how it could be provided and used.

.. Google UCs .  But will talk about the scope of models for different stakeholders to put in context System of Systems Interoperability SOSi Industry NIST. NATO.UC-SB Levels of System System of SOSI and LiSi stacks DoD.  I am just looking at one model view of Cloud Architecture for business users. LiSi A Cloud User Ideas Notation . C-M interoperability Systems Value Network Analysis. Scope of what I’m focusing on.

Zachmann and other concepts have resulted in a perspective of a Provider oriented style “tiers” in Cloud which has limitations  Syntax and semantics have been focused on by community and industry forums but other aspects of behavior interoperability and choreography modelling that could help describe cloud and cloud services is potentially a gap a present  There are many discussions and standards forums on interoperability in the industry but little methodology evolving from an overview of how different parties might work across a cloud service  There are Industry efforts to extend SOA and security standards but these come from a pre-existing viewpoint rather than a clean start on cloud descriptions  We are seeing academic research and evidence in Grid computing. The nature of cloud is emerging continually and the CCRA could help narrate aspects of requirements and how to use Cloud . examples seen in 4+1. agent based technology and some vendors providing examples of how to visualize and potentially represent cloud services more closely relating to the cloud experience. Why do we need a Cloud Computing Reference Architecture CCRA? A range of comments included:  Current reference models are from a seller perspective and don’t fit how cloud “feels” from a User perspective  SOA and Web 2.0 have provided foundation message and payload standards but need to move to into describing how the service “looks and feels”  Historically the “tiers” approach to describing architecture has originated from the Client-server era.

we have seen examples such as virtual reality VR software standards that has attempted to represented a more realistic software representation of the real world – the point is not the VR but that the aim is to create a language and approach that represents how business and technology are working together. people. assets.The need for a meaningful Cloud Computing Reference Architecture Methodology  We need to have a methodology that recognizes better how cloud computing experience “looks and feels like in the real world”  Considering an analogy. Cloud computing is yet another environment / ecosystem combination of tools . businesses and experiences that represent aspects of cloud .

The current Provider oriented Cloud Computing reference models  While NIST is arguably the most well known http://csrc.pdf . University of California.scribd. New York http://freedomhui. there are many examples of equally significant and influential models including the Cloud Computing taxonomy from the Google hosted Cloud Computing Use cases Group http://www.com/wp-content/uploads/2010/03/CloudOntology. Santa Barbara and Maria Butrico and Dilma Da Silva of IBM T.J. Watson Research Center YorkTown. .nist.ppt .gov/groups/SNS/cloud-computing/cloud-computing-v26.com/doc/18172802/Cloud-Computing-Use-Cases-Whitepaper and the “Towards a unified Ontology of Cloud Computing” by Lamia Youseff.  All these examples also provide a technology tiered framework of implementation viewpoints for cloud computing.

to use the “cloud” as a service for business.Building advocacy for a Business User prospective of Cloud Computing  But. . These conceptual frameworks represent a description of a technology tiered architecture most meaningful to Enterprise technologies.  The customer experience and the business user viewpoint of cloud is quite different from the discussions of design and run time choices for cloud services. experience or use the cloud service. While this is important it prevents a separation of the concerns most important from the consumer perspective of the service.  A critical goal of cloud computing is to move towards a user on- demand perspective. this has been predominantly from a provider viewpoint of cloud computing and less on how the consumer might see.

nist.gov/groups/SNS/cloud-computing/cloud-computing-v26. NIST Cloud Computing Reference http://csrc.ppt .

Google Hosted Cloud Computing Taxonomy http://www.scribd.com/doc/18172802/Cloud-Computing-Use-Cases-Whitepaper .

Watson reference here – see Tim O’Reilly & Clay Shirky Reference to Thomas J.com/wp-content/uploads/2010/03/CloudOntology.J.J.pdf Note: The T. Watson Research center http://freedomhui. Santa Barbara & IBM T. Watson crica 2001 & 2009) . “Towards a Unified Ontology of Cloud Computing” – University of California.

the buyer and seller and other intermediate roles that support the types of homogeneous and heterogeneous platforms and subclasses of data and user devices that are found in the real world of IT.Balancing the Buyer and Seller perspective  We are not advocating a different cloud computing model but a set of models that take into account both the consumer and provider side . .

5 key Business Benefits of a User driven Cloud viewpoint  Defining a clear Cloud Computing Architecture Modelling approach will help further develop Cloud Computing adoption  Defining a common set of standard terminology is key to any new emerging technology trend in helping to raise awareness and express requirements of that technology. .

Defining a user location perspective of security protection points would greatly enhance the provider conditions to address those critical concerns. how multiple service monitoring and management systems need to be position on the provider side and the consumers side. Business needs a way of describing this from that perspective so that we can accelerate the meaning full integration and adoption of cloud into everyday experience.  Visualizing the real cloud  Cloud is already here. 5 key Business Benefits of a User driven Cloud viewpoint  Monetizing cloud services  It is currently an area of adoption question. Many enterprise level SLAs need OLAs that are representative of business level QoS standards. “how much do cloud services cost my business?”.  Defining a clear Customer experience  Probably the biggest affect on everyday lives has been the attention span and impact on people and business through on-demand and real-time exchange of messages and content enabled by an increasing social and dynamic network of services that can be described as “the cloud”. web sites and tweets. Showing this experience and how this changes in a “mash-up”.  Describing who has ownership of Security Risk in the cloud  The greatest impediment to cloud is probably the risk and security aspects of the data. location and control of services. video feeds. A methodology that helps clarify this “ownership of responsibility” would be a great benefit in definition a clear boundary of service trading and exchange. on-demand world would greatly improve the real world representation of consumer choice . we everyday see the email. Defining a way to show individual services and their common shared service or incremental growth could help accelerate an adoption profile where users understand the cost of service better. the self-service “menus” and “portfolios” open to business.  Defining how to monitoring Quality of Service QoS in the cloud  Overall how the service level performance monitoring and disaster recovery aspects of the cloud service needs to be shown in a heterogeneous context. .

This matches the incremental cashflow and elastic growth we so often see in cloud service use .Why this helps monetize Cloud  Because it is a middle-out not a outward-in approach – it drives the user journey through using the cloud  You look at cloud from the viewpoint of using one to many cloud services which can be used and built on incrementally.

Defining Models for Cloud Computing that considered the Business User viewpoint .

This is not Web services or BPEL style protocols and workflow styles  How the service meta data might be defined  Cloud Actor Model  The types if actors that might participate in a cloud service from all perspectives  Cloud network (Choreography) Model  How the overall flow of a Cloud service transaction might flow  How the cloud service “communities” might look and interact  How trading and marketplaces might interoperate  Integrated Cloud Framework  How to design Cloud Components  How to define a Cloud Service Lifecycle  Cloud catalog and user experience model  How a catalog or catalogs of business and IT services might be represented in the cloud  How the services might be visualized . SOCCI etc . Examples. They provide a provider technology perspective of the cloud solution  Cloud services model  A description of the types of services we see in cloud computing – more from the perspective of the type of “operations” and services that cloud might support. Some of these relate to CCA. At Cloudcamp we discussed… What a Cloud Computing Reference Architecture CCRA might contain ?  Cloud Computing Technology reference model  This is arguably already covered in the many technology stack reference models: NIST etal. discovered and used  Cloud Meta data and Behavior (Cloud Contract) Model  A description of the service exchange meta data model  Others……..

Why do we need Cloud Model Symbols ? Reasons for using the “Symbology”: .

EX AM P What a Cloud Computing Reference LE Architecture CCRA might contain ? .

Source : Vladimir Baranek EX AM P What a Cloud Computing Reference LE Architecture CCRA might contain ? .

pricing & Payments Shopping basket Integration management Identity management PaaS Audit & compliance management SSO & authorization Service maintenance IaaS Recovery services Backup services Resources Deployment Platforms .Cloud Computing Tier Reference Model “Stack” Example Deployment channels Demand management Channels / Devices Supply management Component library Provisioning management RIM tools Common Shared BPaaS Monitoring Management Configuration management Operating Services Services Billing & reporting SaaS Usage.

How might a Cloud Network model In the real world Cloud Services exist look like ? between Social and Business Collaborations Ideas on what the Entities of this model might be: Business • Service Social Network • Marketplace Network • Boundary • Community • Transactions • Hub • Aggregator • Concentrator Industry Network .

g. Queue Agent Device Service Service Service Cloud Shop ? DR Search Industry Light (Client) DR Component Other Service Hyperviso Message Service Device Service Store r Self Service Catalog . Types of Cloud Module Symbols #1/3 Standard Service Actor Device Security Integration & Messaging Business Service Mobile Security Composite Cloud Container Avatar Container Device Service Service API Service Cart Hub Service Hub Intelligent Fat (Client) Monitoring Integration Feed / Alert Concentrator e.

Types of Cloud Module Symbols #2/3 Boundaries Connections Providers Catalogs Provider Name Standard Cloud Service Cloud Community Private Community Cloud Service Connection Provider Catalog Provider Name Location Business Provider Self Service Social Network Cloud Based Sphere Catalog Provider Name Inter Marketplace Virtual Component XaaS Service Component Boundary Organization Connection Provider Catalog .

Types of Cloud Module Symbols #3/3 Management Cloud Environments Deploy Public Private Hybrid Enterprise Service Components Configure Provid Provide er Provider Provider r Provider Provider Provider Provider BaaS INaaS BPaaS DaaS SaaS PaaS IaaS DCaaS Assembly Cloud Domains “Factory” ORG NET IN OUT CRM HR Report Semantic Based Re/Source Based Business Based .

My focus here is just on a Business Notation for describing Cloud requirements .

and Deliver Terms •QoS Aspects – Non-functional Characteristics •Functional Characteristics – Workload Characterization •Types of Cloud Stack services: IaaS. Contract (including SLAs). The Cloud Notation is just one model view of a number of models Cloud Business Artifacts Cloud Buyer/User Cloud Requirements User Metadata Notation •Business Roles •Business Processes •Market Segments •Financial and Lifecycle Terms •Sell. etc . SaaS. PaaS.

Leading Cloud evangelist .xmind.net/share/_embed/kvjacksn/cloud .Some examples using the Cloud notation  The following uses examples from Kevin Jackson. CloudComputingJournal http://cloudcomputing. http://www.sys-con.com/ recent blog publications to illustrate the point.

WWW blog sphere Animoto Video Business Apps Store Animoto Security Services Monitor Service Types of Rightscale Video Cloud IaaS partner Services DR DR . Brad discusses Animoto their infamous week where Animoto went from 25k users to 700k users in 5 days and they had to scale from 50 to 5k servers.com/intro/1?gclid=COPA7s22iaMCFRJNagod7W_5bA Animoto uses Rightscale as their cloud infrastructure partner. Backup Services included Integration & Mashup services . Animoto Video Shows http://animoto.

com and then creates the replay animations from them. and created a lightweight reader app using Adobe's AIR technology that let users pull in the required data. But for this offering.nasdaqomx. Nasdaq http://www. So it turned to Amazon's S3 service to host the data. The result: "We don't need a Lightweight reader database constantly staging app using Adobe’s data on the server side. And AIR the price is right.com/ Nasdaq OMX has lots of stock and fund data. the company didn't want to worry about optimizing its databases and NASDAQ OMX servers to handle the new load. called Market Replay. Sell historical data From those stocks And funds (Marketplay) The Adobe AIR app Courbois' NASDAQ OMX team put together in just a couple days pulls in the flat files stored at Amazon. and it wanted to make extra revenue selling historic data for those stocks and funds." technology that let users pull in required data Stock and fund data Amazon S3 service DR Host data .

The Times scanned in the stories. Using 100 Linux computers. the Times ran a PDF conversion Subscribers too app that converted that 4TB of TIFF data into 1. New York Times http://www.com using Amazon. cut up into columns to fit in the scanners (as TIFF files).nytimes. to make them available through its Web site search engine.com/ The New York Times also used S3 for a data-intensive project: converting 11 million articles published from the New York Times newspaper's founding in 1851 through 1989. EC2 Convert PDF app Published articles DR archive search S3 Amazon S3 and EC2 Queue . then uploaded those to S3 WWW blog sphere ? Nytimes.5TB of PDF files. the job took TIFF files convert to PDF about 24 hours.com's EC2 Web search computing platform.

Google Multiple Social Communities Google Services ? Search Google.com Multiple Enterprise Communities .

com Multiple Tenant Communities Controlled Tenancy Environment .Salesforce.

fast-moving "two-pizza teams" could add new features faster and easier. Multiple Social Communities Amazon AWS Services Multiple Location DCs Multiple Enterprise Communities . Amazon played a key role in the development of cloud computing by modernizing their data centers after the dot-com bubble. Having found that the new Amazon AWS cloud architecture resulted in significant internal efficiency improvements whereby small. like most computer networks. which. were using as little as 10% of their capacity at any one time just to leave room for occasional spikes. Amazon started providing access to their systems through Amazon Web Services on a utility computing basis in 2005.

Cloud Environment Encapsulation Deployment & Orchestration Example Facebook Public Cloud API Hybrid Environment Social Cloud Industry Cloud Amazon Facebook Fedex UPS Customer Advocacy Amazon iPhone Portal Shop iPhone API B2B API Shop Consumer API Industry Cloud Hybrid Environment Enterprise Environment Paypal Rackspace B2C Portal eCommerce Payments Delivery B2B Integration Public Cloud Business Cloud .

com IN Microsoft Dynamics CRM CRM Local Force API Company DC COM Dynamics API . Example of Cloud Domains Leads Salesforce 360 Leads API OUT Sales force Force .

.. see new opportunities.properties that are vital for Different types of Interoperability people working together as network ecosystems Levels of conceptual interoperability valuenetworks. Value network Analysis System of Systems (circa 2003-4) Value Network visualization and analysis helps people SOSi and LiSi stacks which DoD and NATO have worked negotiate their work.com. This has been explored before but not in cloud. Layers of Coalition Interoperability Tight and loose coupling Network of interoperable services within system of Systems . build stronger on with Cargnie-Mellon University relationships and increase trust.

Next steps  Is this notation something that The Open Group Cloud Work Group think has merit and should be carried forward ?  Should this be a set up as a separate Project within the Cloud Work Group with new chairs and a Charter ?  Should this be kept within the current CBA Project as it has links with the metadata work in CBA ?  How should this be linked with the CCA and SOCCI project teams .the intention is to position CBAN as separate to other projects and to be business oriented notation .

Cloud Catalog and marketplaces model Developer Communities & marketplaces Aggregator Self Service Service Catalog Trading & Auctions Apps Store .

Cloud Catalog and User Experience Viewpoint Model Social Networks Business Networks WWW Blogsphere Cloud ? User Experience Viewpoint .

Security --- Semantics Integration Syntax Behavioral Information Interoperability Model . Service SaaS --. Type --. How might a Cloud Service Meta data be described for static and behavioral interoperability ? Conceptual Choreography Behavioral Cloud interoperability Container Interoperability IaaS Needs Cloud Contract PaaS --. QoS --- --.