Getting an open systems cloud strategy right the first time linthicm

August 29, 2012| Page 1© 2012 Blue Mountain Labs, A Bick Group Company

August 29, 2012

Getting an Open Systems Cloud Strategy Right the First Time

David S. LinthicumCTO, Blue Mountain LabsEmail: [email protected]


Abstract:

The ability for enterprise IT to effectively leverage cloud computing means a transformational change in the way that IT thinks about and executes system design, development, and implementation. For many organizations, there is still much confusion around technical approaches, including the proper use of open systems technology. Those who sell highly proprietary technology are creating both hype and confusion. In many instances, the proper approaches get pushed to the back of the room.

This presentation will take the mystery out of both cloud computing, and the proper fit and function of open systems technology when building a cloud computing strategy. Instead of mere theory, this session will guide you through a step-by-step process for understanding your own requirements, creating the business cases, and selecting the right technology that will lead your enterprise to success in the cloud.


Where To Find Out More

Slides available:


Where to find me.

• @DavidLinthicum• [email protected]• www.bluemountainlabs.com • www.davidlinthicum.com• http://www.linkedin.com/in/davidlinthicum

• Grab a card after the presentation.

mailto:[email protected]

http://www.bluemountainlabs.com/

http://www.davidlinthicum.com/

http://www.linkedin.com/in/davidlinthicum


Geek Level for this Presentation

Systems Programmer andDungeon Master

Your Grandparents that are Still Using AOL Dialup


Setting the Stage



Source: Chander Khanna


The fight begins…


…and, things are getting crowded.


“Inside Baseball”

• Watch… the number of offerings out there, and the quality of the distributions.

the hype, what’s real versus perception.

• Understand…that rigorous testing is required, before implementation.

your own security requirements.

that you may be mixing and matching technology.

the roadmap for each product.

the near-term and long-term costs.


Why You Should Care


Most Open System Cloud-Based Systems are Lacking Architecture



The results:

• Inefficient utilization of resources. • Resource saturation.• Lack of elasticity and scalability. • Lack of security and governance. • Frequent outages. • Bad or no tenant management. • Other very bad things.


Common Mistakes

• Not understanding how to make architectures scale.

• Not dealing with tenant management issues.• Not understanding that security is systemic. • Not understanding the proper use of services.• Tossing technology at the problem.• Listening to the wrong people. • Managing-by-magazine.


The Multitenant Thing

• No two multitenant architectures are alike.

• Needs to be effective in the context of the problem.

• Needs to leverage best architecture practices.

• Needs to practice isolation and protection.

“With a multitenant architecture, a software application is designed to virtually partition its data and configuration so that each client organization works with a customized virtual application instance.”

Source: Wikipedia



ABCs of Multitenancy

Source: Steve Bobrowski

Amazon Machine Images


Virtualization is Not Always a Requirement


The Big Picture


Objective

Provide a future vision for how the cloud can be adopted within the enterprise to increase agility and drive innovation

1 2 3

Examine the infrastructure aspect of cloud technologies to determine a path

Create a starting point to identifying potential open source vendors that may be a fit to the needs of of the enterprise to build a solution


The Journey to the Cloud

IT-as-a-ServiceImprove Agility

Tactical IT EfficiencyLower Costs

Leveraging Shared ServicesImprove Quality of Service

% Efficiency

15%

30%

50%

85% 95%

Run IT as a Business

PlatinumGold

Manual Provisioning Self-Service Provisioning

IaaS


1 2 3 4 5

Identify Candidate Cloud Opportunities

Identify cloud services opportunities based on business needs, value proposition, and the ability to adopt/support those services. This will be the services portfolio

Actions to Support an Open Systems Cloud StrategyOptimize the Current Environment

Optimize the current IT environment with the goal of providing an internal set of cloud services and enabling the incorporation of external services. This will be the services. roadmap

Build and Communicate a Project Plan

Communicate with the BUs about cloud services and the roadmap and process for incorporating them into the architecture, whether the services are internal or external. This will be the communication plan.

Build a Lab and conduct POC’s

Experiment with and pilot various services, both internal and external, to identify where the real issues will arise. This will be the lab.

Establish a Center of Excellence

Designate a cross-functional team to monitor continually which new services, providers, and standards are in this space and determine if they affect the roadmap. This will be the sensing and strategy-evolution function.


How You Should Proceed


IaaS Building Blocks

Sec

urity &

Iden

tityM

ana

gem

ent &

Serv

ice G

ove

rnan

ce S

ervices

Primitives: Network, Storage and Compute

Database Services

APIs/Services

Use-Based AccountingServices

Tenant ManagementServices

Monitoring and Management Services

Provisioning Services

File System Services

This is a logical framework for IaaS and all of these components need to exist. Use this as a framework of understanding to evaluate the core components of an open IaaS product. For each area identified, there are dozens of requirements that must be defined-


Primitive Services: Network, Storage and Compute

Gather the Requirements for the Cloud

Step 1: Define core primitive services.

Requirements:

1. Storage capacity requirements

2. Storage growth requirements

3. Existing technology analysis

4. Security planning

5. Governance planning

6. Existing network analysis

7. Elasticity requirements

8. Integration requirements

9. Management requirements

10. API service design

11. ..…..

12. …….


Step 2: Define database and file systems services, as well as access service/APIs.

Requirements:

1. Use cases

2. Data growth


4. File system growth

5. File system performance

6. API/service implementation

7. Database service analysis

8. Migration planning

9. Database performance

10. File system security requirements

11. …..

12. …..


Database Services

APIs/Services




Step 3: Define approaches and technology for use-based accounting, provisioning services, and tenant management services.

Requirements:

1. Accounting use cases

2. Governance planning

3. Service management

4. Tenant management requirements

5. Provisioning use case planning

6. Provisioning security

7. Cost models

8. Tenant management approaches

9. Integration planning

10. Migration planning

11. …..

12. …..


Database Services

APIs/Services



Use-Based Accounting

Services

Tenant Management

Services



Monitoring and Management Services

Use-Based Accounting

Services

Tenant Management

Services



Database Services

APIs/Services



Step 4: Define monitoring and management services.

Requirements:

1. Use cases monitoring

2. Use cases management

3. BC/DR requirements

4. BC/DR planning

5. Compliance requirements

6. Auditing requirements

7. Management interface requirements


9. Integration with governance

10. Integration with security

11. …..

12. …..



Step 5: Define Security, Identity Management and Service Governance

Requirements:

1. Compliance planning

2. Governance approach

3. Approaches to encryption

4. Identity design

5. Integration with existing directory management

6. Policy requirements

7. Policy design

8. Policy implementation planning

9. Policy life-cycle management

10. Security and governance integration

11. …..

12. …..


“as-is”


“to be”


deploy


Q&A

Technology

Getting an open systems cloud strategy right the first time linthicm