Cloudcamp Cloud Notation

1. CloudcampCloud Notation May 2010 Boston, MA

2. The need for a meaningful Cloud Computing notation • We need to have a methodology that recognizes better how cloud computing experience “looks and feels like in the real world” • Considering an analogy; 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. Cloud computing is yet another environment / ecosystem combination of tools , assets, people, businesses and experiences that represent aspects of cloud

3. The current Provider oriented Cloud Computing reference models • While NIST is arguably the most well known http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-computing-v26.ppt , 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.scribd.com/doc/18172802/Cloud-Computing-Use-Cases-Whitepaper and the “Towards a unified Ontology of Cloud Computing” by Lamia Youseff, University of California, Santa Barbara and Maria Butrico and Dilma Da Silva of IBM T.J. Watson Research Center YorkTown, New York http://freedomhui.com/wp-content/uploads/2010/03/CloudOntology.pdf . • All these examples also provide a technology tiered framework of implementation viewpoints for cloud computing.

4. Building advocacy for a Business User prospective of Cloud Computing • But, this has been predominantly from a provider and IT viewpoint of cloud computing and less on how the consumer might see, experience or use the cloud service. These conceptual frameworks represent a description of a technology tiered architecture most meaningful to Enterprise technologies. While this is important it prevents a separation of the concerns most important from the consumer perspective of the service. • 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. • A critical goal of cloud computing is to move towards a user on-demand perspective, to use the “cloud” as a service for business.

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

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

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

8. 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 , 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.

9. 5 key Business Benefits of a User driven Cloud viewpoint • Defining a clear Cloud Computing modelling notation 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.

10. Scope What do we need to achieve Business Architecture Cloud Notation Business ProcessesProcess flows Business rules Capabilities .. Can use the cloud notation to builda business notation Use cloud services To do business Generic Model e.g. eTOM a modelof generic processes(Capabilities) Implementation specific Model How the Cloud Notationand link it back to current methods and tools

11. Benefits . Making the cloud easier to define vision andrequirements. Scope BusinessArchitecture Vision Ecosystem aware Icon inventory Concepts semantics Notation Collaboratewith vendors.. Visual Links to currentModels / languages EA links How thismightwork execute

12. 5 key Business Benefits of a User driven Cloud viewpoint • Monetizing cloud services • It is currently an area of adoption question; “how much do cloud services cost my business?”. 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. • Visualizing the real cloud • Cloud is already here, we everyday see the email, video feeds, web sites and tweets. 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. • 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”. Showing this experience and how this changes in a “mash-up”, on-demand world would greatly improve the real world representation of consumer choice , the self-service “menus” and “portfolios” open to business. • 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. Defining a user location perspective of security protection points would greatly enhance the provider conditions to address those critical concerns. • 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. Many enterprise level SLAs need OLAs that are representative of business level QoS standards, how multiple service monitoring and management systems need to be position on the provider side and the consumers side. A methodology that helps clarify this “ownership of responsibility” would be a great benefit in definition a clear boundary of service trading and exchange.

13. 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. This matches the incremental cashflow and elastic growth we so often see in cloud service use

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

15. Why do we need Cloud Module Symbols ? Reasons forusing the “Symbology”:

16. Types of Cloud Module Symbols #1/2 Standard Service Actor Security Integration & Messaging Business CompositeService Cloud Service Cart Service Container Security Service Container Avatar API Hub Concentrator IntegrationService MonitoringService Feed / AlertService Service Hub e.g. Queue IntelligentAgent Cloud Store I ? ? Industry Service Assembly “Factory” DR Service Hypervisor Message Other Search Service

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

18. Example of a Virtual Cloud Serviceexchange Example from Argugrid and www.cosmo-one.gr/en/solutions.htm

19. Cloud Catalog and marketplaces model Developer Communities & marketplaces Self ServiceCatalog AggregatorService Trading & Auctions Apps Store

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

21. Case studies – using this Cloud Nomenclature

22. Animoto Animoto Video Business WWW blog sphere AppsStoreAnimotoServices Security Monitor Service Types of VideoServices Rightscale Cloud IaaS partner DR , BackupServices included DR Integration &Mashup services

23. NASDAQ OMX Sell historical data From those stocks And funds (Marketplay) NASDAQ OMX Lightweight reader app using Adobe’s AIRtechnology that let userspull in required data Stock and fund data Amazon S3 serviceHost data DR

24. New York Times WWW blog sphere Nytimes.com Web search Subscribers too TIFF files convert to PDF ? EC2 Convert PDF app Published articles archive search S3 Amazon S3 and EC2 Queue DR

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

26. Salesforce.com Multiple Tenant Communities Controlled Tenancy Environment

27. Amazon AWS Multiple Social Communities Amazon AWS Services Multiple Location DCs Multiple Enterprise Communities

28. “..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…” Aims Cloudcamp Boston 2010

29. Noam Chomsky...(father of modern linguistics, MIT) “The structure of language determines not only thought but reality itself”

30. Todays systemic models in computer science Multiple space relationships Today you have different notations but nothingthat brings this all together. Service Metadata e.g. SOA Models e.g. Web Services Operating Model Metadata e.g. OR When everythingis working ondifferent planes They don’t workwell together Business Metadata e.g. BPML Technology Metadata e.g. OS. Java.. Governance is difficult, Integration is difficult when you have different notations

31. N-dimensional System to System model Multiple space relationships Today you have different notations but nothingthat brings this all together. Service Metadata WorldReference Meta-Universe System of System Classes Operating Model Metadata Types Of Metadata Business Metadata CCNLLanguage Technology Metadata A single unified notation to facilitategovernance and integration

32. What Cloud Meta Data ? Ecosystem Meta Model Many to many dimensional relationship Meta model Ecosystem Networks can support delivery of have Services Networks can be Social, Businessor hybrid connections Services Can be used by hosted, Private, Pubic or Hybrid Communities Networks have “Ecosystem” characteristics An Ecosystem can have one or more networks An ecosystem may span one or more marketplaces Networks Marketplace Connections Services Communities

33. An Ecosystem = a set of common conditions that describe and are followed by all participants and communities in the Ecosystem Enables a common exchange of products and services based on the ecosystem characteristics. Cloud in an Industry Sector Context Single set Ecosystem A homogenous Single Ecosystem Marketplace is made upof Business Entities ECOSYSTEM VerticalCloud Service HorizontalCloud Services MARKETPLACE MarketplaceB Distributors Suppliers e.g. Packaging MarketplaceD MarketplaceA Customers regulators e.g. Consumers MarketplaceC e.g. Manufacture Intermediates Marketplacescan have many channels e.g. Raw Materials Channels Cloud products & services can support one or many marketplacesHorizontal Common Cloud ServicesVertical Marketplace specific Cloud Services. .

34. Cloud in an Industry Sector Context Ecosystem Meta Model ECOSYSTEM Ecosystem IntermediatesProviders Browser / Portalas a Service CustomersNetwork MARKETPLACE Marketplace IaaS Self Service Private / Public PaaS Services MARKETPLACE Co-mingling Browser / Portalas a Service Network SupplierNetwork Connections SaaS MARKETPLACE SaaS IaaS Communities SLA IaaS

35. Cloud in an Industry Sector Context Poly set of Ecosystems A heterogeneous Ecosystem Ensemble example Many to Many The Ecosystems follow their own separate rules within each ecosystem – Ecosystems may exchange services There may be many marketplaces inside an ecosystem. Communities can use many marketplaces Networks may san more than one marketplace and more than one ecosystem. Networks may support one or many ecosystems IntermediatesProviders ECOSYSTEM e.g. Consumers Marketplace ECOSYSTEM SupplierNetwork ECOSYSTEM e.g. Raw Materials Marketplace e.g. Manufacture Different communities and marketplaces

36. We need to Identify where are the Cloud Servicesand Cloud Platforms (Public, Private …Vertical, Horizontal) Business Meta Model ECOSYSTEM Business Process IntermediatesProviders Browser / Portalas a Service CustomersNetwork MARKETPLACE MarketSegments IaaS Self Service Private / Public PaaS MARKETPLACE Financials& Lifecycle Co-mingling Browser / Portalas a Service Functional SupplierNetwork SaaS QoSAspects MARKETPLACE SaaS IaaS IaaS

37. How to Identify Does Cloud FIT ? – Cloud Buyers Decision Tree Is the Business Process Differentiating ? Degree of Resource Standardization Degree of Resource Sharing Business Process Business Meta Model How Business Services are described in the Universe Universe is described by many Ecosystems Sectors Geographies Company Size MarketSegments For the potential enablementservices to be procured Procuring Organizations Characteristics Contract and Delivery Terms Financials& Lifecycle Workload Characterization Average and peak users by type General steady State Usage Characterization Stepwise Growth/ Shrinkage Periodicity Predictability Functional Can I get it and keep it running Is it running How is it Running Is it running in accordance with the business mission and policies QoSAspects

38. CURN to CCNL CCNL essentially follows a Set Theorem Mathematical Approach CCNL Notation Examples…. Ecosystem Metadata Simple Example Ecosystem Profiling a Service S1 using CCNL Is sold in 2 marketplaces Service S1= M1 M2 Marketplace Service is Sold in one Ecosystem Service is Sold through 2 Channels C1, C2 Service is sold through 2 networks Services Service is sold/used by 2 communities Network Profiling the Ecosystem E1 using CCNL Has 2 Marketplaces M2 M1 Ecosystem = Connections Has 2 Channels Cn2 Cn1 Marketplace= Has 2 Networks N2 N1 Marketplace = Has 2 Services S2 S1 Channel = Communities Has 2 Connections C2 C1 Channel = Has 2 Connections C2 C1 Network = Has 2 Communities Cm2 Cm1 Marketplace =

39. CURN to CCNL Ecosystem Metadata Business Metadata Business Process Differentiation Services Business Process Periodicity Amplitude Predictability ServiceElasticityCharacteristics MarketSegments Scale, SizeDemand , Supply Capex.,Opex modesCashflowmontization mechanimsUsage patterns Financials& Lifecycle CloudServiceCharacteristics Functional Cloud Workload Characteristics QoSAspects RunningOperationSupport Cloud WorkloadCandidates

40. Cloud Workload Analysis - Ecosystem Analysis Ecosystem Model Ecosyetem(s)Profile Future Vision Scenarios Current State Profiling the Ecosystem E1 using CCNL Has 3 Marketplaces …M3 M1 Ecosystem = Has 5 Channels …Cn5 Cn1 Marketplace= Has 3 Networks N3 N1… Marketplace = Has 20 Services S1 ..S20 Channel = Has 8 Connections ..C8 C1 Channel = Has 2 Connections C1 ..C2 Network = Has 3 Communities ..Cm3 Cm1 Marketplace =