Cloudcamp Cloud Notation

meatcologneInternet and Web Development

Nov 3, 2013 (3 years and 5 months ago)

39 views

Cloudcamp

Cloud Notation


May 2010


Boston, MA



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

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.


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.

NIST Cloud Computing Reference

http://csrc.nist.gov/groups/SNS/cloud
-
computing/cloud
-
computing
-
v26.ppt


Google Hosted Cloud Computing
Taxonomy

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


“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 Reference

to Thomas J. Watson crica 2001 & 2009)

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.


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.


Scope

Business
Architecture

Cloud Notation

Business Processes

Process flows

Business rules

Capabilities

..

e.g. eTOM a model

of generic processes

(Capabilities)

Use cloud services

To do business

Can use the cloud
notation to build

a business notation

Generic Model

Implementation
specific Model

How the Cloud Notation

and link it back to current
methods and tools

What do we need to achieve

Scope

Vision

Concepts

Notation

Visual

EA links

execute

Ecosystem
aware

Links to
current

Models /
languages

Icon inventory

semantics

How this

might

work

Collaborate

with vendors..

Business

Architecture

Benefits

. Making the cloud easier to define vision and

requirements.

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.


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

How might a Cloud Network model
look like ?

Ideas on what the Entities

of this model might be:



Service



Marketplace



Boundary



Community



Transactions



Hub



Aggregator



Concentrator


In the real world Cloud Services exist

between Social and Business Collaborations

Social Network

Business

Network

Industry

Network

Cloud Network
Nomenclature

Visualizing
Behavior

Marketplace
Visualization

Why do we need Cloud Module
Symbols ?

Reasons for

using the “Symbology”:

Types of Cloud Module

Symbols #1/2

Service Hub

e.g. Queue

Service

Container

Intelligent

Agent

Actor

Composite

Service

Avatar

Hub

Concentrator

Standard Service

Container

DR
Service

Security
Service

Security

Integration & Messaging

Message

Feed / Alert

Service

Integration

Service

Hypervisor

Monitoring

Service

?

Search Service

API

Cloud

Service Cart

Business

Cloud Store

Industry
Service

Other

Assembly

“Factory”

Types of Cloud Module

Symbols #2/2

Social Network
Sphere

Boundaries

Community Cloud

Private Community

Cloud

Marketplace
Boundary

Virtual
Organization

Location

Based

Provider Name

Cloud Service
Provider

Providers

Cloud Service
Catalog

Self Service
Catalog

Provider
Name

XaaS Service
Component

Catalogs

Component
Catalog

Connections

Inter
Component

Connection

Standard
Connection

Provider Name

Business Provider

Example of a Virtual Cloud Service

exchange

Example from Argugrid and
www.cosmo
-
one.gr/en/solutions.htm


Cloud Catalog and marketplaces
model

Self Service

Catalog

Apps Store

Aggregator

Service

Developer

Communities

& marketplaces

Trading

& Auctions

Cloud Catalog and User
Experience Viewpoint Model

Social Networks

Business Networks

WWW Blogsphere

Cloud

User

Experience

Viewpoint

?

Case studies


using this Cloud
Nomenclature

Animoto

WWW blog sphere

Rightscale

Cloud IaaS partner

Animoto

Video

Business

Types of

Video

Services

Apps

Store

Animoto

Services

Integration &

Mashup services

Security

Monitor Service

DR

DR , Backup

Services included

NASDAQ OMX

Amazon S3 service

Host data

Stock and fund data

Sell historical data

From those stocks

And funds (Marketplay)

NASDAQ OMX

DR

Lightweight reader

app using Adobe’s AIR

technology that let users

pull in required data

New York Times

DR

S3

EC2

Queue

Convert PDF app

WWW blog sphere

?

Web search

Nytimes.com

Subscribers too

Published articles archive search

Amazon S3 and EC2

TIFF files convert to PDF

Google

Google
Services

?

Search

Multiple Social Communities

Multiple Enterprise Communities

Google.com

Salesforce.com

Multiple Tenant Communities

Controlled Tenancy

Environment

Amazon AWS

Multiple Social Communities

Multiple Enterprise Communities

Multiple Location DCs

Amazon AWS
Services

“..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…”

Cloudcamp Boston 2010

Aims

Noam Chomsky...(father of
modern linguistics, MIT)


“The structure of language
determines not only thought but
reality itself”

Todays systemic models in computer
science

Multiple space relationships

Today you have different notations but nothing

that brings this all together.

e.g. BPML

e.g. SOA Models

e.g. Web Services

Governance is difficult, Integration is difficult when
you have different notations

When everything

is working on

different planes

They don’t work

well together


e.g. OR

Operating Model Metadata

Business Metadata

Service Metadata

Technology
Metadata

e.g. OS. Java..

N
-
dimensional System to System
model

Multiple space relationships

Operating Model Metadata

Business Metadata

Service Metadata

World

Reference

Meta
-
Universe

Types

Of

Metadata

System of System Classes

CCNL

Language

Today you have different notations but nothing

that brings this all together.

A single unified notation to facilitate

governance and integration

Technology
Metadata

What Cloud Meta Data ?

Networks can support delivery of
have Services

Networks can be Social,
Business

or 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

Connections

Marketplace

Services

Ecosystem

Networks

Communities

Many to many dimensional relationship Meta model

Ecosystem Meta Model

Cloud in an Industry Sector Context

Cloud products & services can support one or many marketplaces

Horizontal Common Cloud Services

Vertical Marketplace specific Cloud Services. .

Suppliers

Customers

Intermediates

Distributors

regulators

Marketplace

A

Marketplace

B

Marketplace

C

e.g. Raw Materials

e.g. Manufacture

e.g. Packaging

Marketplace

D

e.g. Consumers

Marketplace is made up

of Business Entities

MARKETPLACE

ECOSYSTEM

Channels

Marketplaces

can have
many
channels

Horizontal

Cloud Services

Vertical

Cloud Service

A homogenous Single Ecosystem

An Ecosystem = a set of common conditions that describe and are followed by all participants and communities in the Ecosyste
m

Enables a common exchange of products and services based on the ecosystem characteristics.

Single set

Ecosystem

Cloud in an Industry Sector Context

IaaS

IaaS

IaaS

Customers

Network

Intermediates

Providers

Supplier

Network

Co
-
mingling

Browser /
Portal

as a
Service

PaaS

SaaS

SaaS

Self Service

Browser /
Portal

as a
Service

Private / Public

MARKETPLACE

MARKETPLACE

MARKETPLACE

Network

Connections

Services

Communities

Ecosystem

Marketplace

Ecosystem Meta Model

ECOSYSTEM

SLA

Cloud in an Industry Sector Context

Intermediates

Providers

A heterogeneous Ecosystem Ensemble example

Supplier

Network

ECOSYSTEM

ECOSYSTEM

Marketplace

ECOSYSTEM

Marketplace

e.g. Manufacture

e.g. Consumers

e.g. Raw Materials

Different communities and marketplaces

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

Poly set of Ecosystems

ECOSYSTEM

We need to Identify where are the Cloud Services

and Cloud Platforms (Public, Private …Vertical,
Horizontal)

IaaS

IaaS

IaaS

Customers

Network

Intermediates

Providers

Supplier

Network

Co
-
mingling

Browser /
Portal

as a
Service

PaaS

SaaS

SaaS

Self Service

Browser /
Portal

as a
Service

Private / Public

MARKETPLACE

MARKETPLACE

MARKETPLACE

Business Meta Model

QoS

Aspects

Functional

Financials

& Lifecycle

Business Process

Market

Segments

How to Identify Does Cloud FIT ?


Cloud Buyers Decision Tree

QoS

Aspects

Functional

Financials

& Lifecycle

Business Process

Market

Segments

Is the Business Process
Differentiating ?

Degree of Resource
Standardization

Degree of Resource Sharing

Sectors

Geographies

Company Size

For the potential enablement

services to be procured

Procuring Organizations

Characteristics

Contract and Delivery Terms

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

Workload Characterization

Average and peak users by type

General steady State Usage Characterization

Stepwise Growth/ Shrinkage

Periodicity

Predictability

Business Meta Model

How Business Services are

described in the Universe

Universe is described by many

Ecosystems


CURN to CCNL

Network

Connections

Services

Communities

Ecosystem

Marketplace

CCNL Notation Examples….

Ecosystem =

M
1

M
2

Has 2 Marketplaces

CCNL essentially follows a Set Theorem Mathematical Approach

Marketplace =

N
1

N
2

Has 2 Networks

Ecosystem Metadata

Network =

C
1

C
2

Has 2 Connections

Marketplace =

Cm
1

Cm
2

Has 2 Communities

Channel =

C
1

C
2

Has 2 Connections

Marketplace=

Cn
1

Cn
2

Has 2 Channels

Channel =

S
1

S
2

Has 2 Services

Service S1=

M
1

M
2

Is sold in 2 marketplaces

Profiling a Service S1 using CCNL

Service is Sold in one Ecosystem

Service is Sold through 2 Channels C1, C2

Service is sold through 2 networks

Service is sold/used by 2 communities

Simple Example

Profiling the Ecosystem E1 using CCNL

CURN to CCNL

QoS

Aspects

Functional

Financials

& Lifecycle

Business Process

Market

Segments

Business Metadata

Services

Ecosystem Metadata

Business Process Differentiation

Periodicity

Amplitude

Predictability

Service

Elasticity

Characteristics

Cloud

Service

Characteristics

Scale, Size

Demand , Supply

Capex.,Opex modes

Cashflow

montization mechanims

Usage patterns

Running

Operation

Support

Cloud Workload Characteristics

Cloud Workload

Candidates

Cloud Workload Analysis
-

Ecosystem Analysis

Ecosyetem
(s)

Profile

Ecosystem Model

Ecosystem =

M
1

…M
3

Has 3 Marketplaces

Marketplace =

N
1…

N3

Has 3 Networks

Network =

C
1

..C
2

Has 2 Connections

Marketplace =

Cm
1

..Cm
3

Has 3 Communities

Channel =

C
1

..C
8

Has 8 Connections

Marketplace=

Cn
1

…Cn
5

Has 5 Channels

Channel =

S
1

..S
20

Has 20 Services

Profiling the Ecosystem E1 using CCNL

Current State

Future Vision Scenarios