Adopting the Open Group Cloud

EcoSystem Reference Model

CCICI eGov Reference ArchitectureTask Force

(Parameswaran, Rena, Raghavendra, Madhav & Krishna)

21st and 22nd September 2015

Agenda

Cloud EcoSystem Reference Model

➢Overview and Architecture Building Blocks

➢Architecture Principles

TOGAF

➢9.1 Components & ADM Phases

➢Architecture

➢Drivers, Goals, Opportunities and solutions

GI Cloud

➢Objectives, Components

➢Selection process, Adoption Phases

Discussion….

Cloud EcoSystem Reference ModelOverview, Goals & Objectives

The Cloud Ecosystem Reference Model extends the

Enterprise Architecture Model, and -

➢serves as an abstract foundation for the

instantiations of architectures and business solutions

of an enterprise cloud ecosystem.

➢defines a flexible and agile collaborative enterprise

cloud ecosystem.

➢provides an effective digital CX for secure sharing of

business data irrespective of physical location.

➢establishes a common language for the various

participants of an enterprise Cloud Ecosystem.

➢describes the relationships and dependencies

between the various enterprise management

frameworks to manage the life cycle of Cloud

Services utilizing the Architecture Building Blocks

(ABB)

➢ensures consistency and wide applicability to the

delivery of Cloud Services.

Cloud EcoSystem Reference ModelCloud Services and Architecture Building Blocks (ABB)

The Cloud Ecosystem Reference Model defines the –

➢major actors and their relationships

▪ Cloud Service Provider, Cloud Service Auditor,

Cloud Service Consumer, Cloud Service Broker,

Cloud Service Developer

➢Cloud Services and the minimum set of ABBs needed to

achieve architectural integrity

▪ Business Support Services

▪ Operational Support Services

▪ Cloud Security Services

▪ Performance Services

▪ Interoperability & Portability Services

▪ Product Catalog Services

▪ Resource Catalog Services

Cloud EcoSystem Reference ModelEnterprise Architecture Principles

Enterprise Architecture Principles of

the Cloud Ecosystem

➢defines the underlying rules and

guidelines for the use of ABBs to

manage the life cycle of Cloud

Services across the enterprise.

➢reflects an architectural

consensus across the enterprise

➢ensures consistency and integrity

of the Enterprise Architecture

➢forms the basis for making future

decisions pertinent to an

enterprise’s Cloud Ecosystem.

Auto-provisioned sharable system infrastructure.

Cloud solutions are designed to address performance variance

Automated ways to measure and optimize cloud solutions

Automatic provisioning to enable horizontal scaling for distributed workload

Loosely-coupled Cloud Services

Cloud Service abstraction and control

Multi-tenancy

TOGAF 9.1 Components OverView

TOGAF 9.1 ADM Phases

EA Drivers & Goals TOGAF ADM Opportunities & Solutions phase

Start from here

What are our drivers (Business drivers or

Technology drivers)?

• Digital India Vision and GI Cloud strategy

• Better service to citizens?

• Optimal use of funds?

• Cloud, a powerful technology driver

• Technology drivers must be linked to Business

drivers

What are our goals in response to those drivers?

• E-governance, M-governance & Digitize records

• Share data centers and leverage unused capacity

• Cloud-enable data centers

• Avoid capital investment with long term ROI?

• Avoid new infrastructure in data center?

• Reduce wasteful expenditure?

• E-gov App store?

• Mass adoption & High penetration in the country

Identify candidate services in the Cloud

Now is the time to think about implementation of

ECA

For each Gap in phases B,C, and D (i.e. Business,

Application, Data, and Technology)

• Evaluate options:

Private/Public/Hybrid/Community, Buy or Build,

Proprietary or Open Source, implement or Out

source, etc.

• If you are going for private cloud decide on style –

Bare-metal, Hosted Virtualization, Virtualization,

Containers, etc.

For each Gap, select one of the options above

based on principles, standards, fitment with the

ABB functionalities/requirements, Cost (TCO), and

the selected option becomes SBB (Solution

Building Block)

TOGAFArchitecture

Business Architecture

- Refer various models & pick up relevant ABBs

- Top-Down – Start with Business Architecture

- Driven by Business goals, principles and standards

- Consider Services, Functions, Processes & People

- Document As-Is (i.e. Baseline) Business Architecture

- Come up with To-Be (i.e. Target) Architecture

- Do Gap Analysis between Target and Baseline

- The Gaps, need to be implemented

Data Architecture

- Supports & Driven by Business Architecture

- Relate to the Application Architecture Domain

- As-Is and To-Be Data Architectures and Gap Analysis

- Data integration

- Data migration,

- Data quality

- Standard Data Definition (Metadata)

- Data and privacy classification

Application Architecture

- Supports & Driven by Business Architecture

- As-Is and To-Be Application Gap Analysis

- The ABBs in the Application Architecture CRUD

- Includes SaaS, Information Systems, logical apps

- Decide Application integration mechanisms

- Duplicate applications, redundant applications, silo

- Interoperability - IEEE P2302 - (SIIF)

- API-based integration

Technology Architecture

- Supports Application and Data Architectures

- As-Is and To-Be Technology Gap Analysis

- ABBs are PaaS, IaaS, and all OS/Hardware stack

- Interoperability requirements between Technology

- API-based integration components and services

- Interoperability - IEEE P2302 - (SIIF)

- clouds, roots, exchanges, gateways

- name spaces, messaging, resources

GI Cloud Initiative (MeghRaj)

Objectives:

••Optimum utilization of Infrastructure

••Speeding up the IT procurement cycle

••Moving from Capex to Opex model

••Infrastructure elasticity – scale up & scale down

••Easy replicable productized applications at one place

•Policy Principles

••All Government clouds to follow the standards & guidelines set by Government of India.

••At the time of conceptualization of any new MMP or other government project the existing services (IaaS, PaaS, SaaS) of GI

Cloud to be first evaluated for usage.

••All new applications to be cloud ready.

For more details please refer to http://www.mmp.cips.org.in/documents/Workshops/2015/19th-March/MeghRaj.pdf

and http://deity.gov.in/content/gi-cloud-initiative-meghraj

Adoption Phases

Discussion on the interconnection…..

TOGAF

GI Cloud

Open Cloud Eco System Reference

Model