architecting the cloud: how eas should think about cloud computing

29
Architecting the Cloud: How EAs should think about Cloud Computing Pratheesh T S

Upload: aurora

Post on 25-Feb-2016

57 views

Category:

Documents


3 download

DESCRIPTION

Architecting the Cloud: How EAs should think about Cloud Computing. Pratheesh T S. Pratheesh T S. Introduction. How many of you are Enterprise Architects?. Agenda. Enterprise Architect role Cloud Computing Cloud Types and different trends Considerations: Architecting Cloud - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Architecting the Cloud:  How EAs should think about Cloud Computing

Architecting the Cloud: How EAs should think about Cloud

Computing

Pratheesh T S

Page 2: Architecting the Cloud:  How EAs should think about Cloud Computing

Introduction

How many of you are Enterprise Architects?

Pratheesh T S

Page 3: Architecting the Cloud:  How EAs should think about Cloud Computing

Agenda

• Enterprise Architect role• Cloud Computing • Cloud Types and different trends• Considerations: Architecting Cloud• Example: BPOS\ Office 365 and AWS• Questions

Page 4: Architecting the Cloud:  How EAs should think about Cloud Computing

Enterprise Architect Alignment of IT strategy with company's business goals. Optimization of information management approaches based on evolving business

needs and technology capabilities. Long-term strategic responsibility Promotion of shared infrastructure and applications to reduce costs Management of the risks associated with information and IT assets through appropriate

standards and security policies.

Page 5: Architecting the Cloud:  How EAs should think about Cloud Computing

Cloud Computing

Software As Service

Platform As Service

Infrastructure As Service

…………… As Service

Page 6: Architecting the Cloud:  How EAs should think about Cloud Computing

Cloud Computing

On Premises Hosted Cloud

Where do your application "Live“?

Page 7: Architecting the Cloud:  How EAs should think about Cloud Computing

Cloud Computing

Application runs on-premises

•My own hardware, connectivity, software, etc.•Complete control•Complete responsibility•Upfront capital costs for the infrastructure

Page 8: Architecting the Cloud:  How EAs should think about Cloud Computing

Cloud Computing

Application runs on-premises

Buy my own hardware, and

manage my own data center

Application runs at a hoster

Pay someone to host my

application using hardware that I specify

Application runs on-premises

•Bring my own machines, connectivity, software, etc.•Complete control and responsibility•Upfront capital costs for the infrastructure

Application runs at a hoster

•Rent machines, connectivity, software•Less control, but fewer responsibilities•Lower capital costs, but pay for fixed capacity, even if idle

Page 9: Architecting the Cloud:  How EAs should think about Cloud Computing

Cloud Computing

Application runs on-premises

Buy my own hardware, and

manage my own data center

Application runs at a hoster

Pay someone to host my

application using hardware that I specify

Application runs using cloud

platform

Pay someone for a pool of

computing resources that

can be applied to a set of

applications

Application runs on-premises

•Bring my own machines, connectivity, software, etc.•Complete control and responsibility•Upfront capital costs for the infrastructure

Application runs at a hoster

•Rent machines, connectivity, software•Less control, but fewer responsibilities•Lower capital costs, but pay for fixed capacity, even if idle

Application runs using cloud

platform

•Shared, multi-

tenant environment•Offers pool of computing resources, abstracted from infrastructure•Pay as you go

Page 10: Architecting the Cloud:  How EAs should think about Cloud Computing

What is Cloud

“A standardized IT capability, such as software, app platform, or infrastructure, delivered via Internet technologies in a

pay-per-use and self-service way”

“Pool of computing resources offered by a vendor, typically using a

“pay as you go” model”

“A pool of abstracted, highly scalable, and managed compute infrastructure capable of hosting end-customer applications and billed by consumption”

Page 11: Architecting the Cloud:  How EAs should think about Cloud Computing

Defining Cloud Type

Private Cloud

Pool of Computing resources that lives within a self managed datacenterPool of computing resources that lives within a datacenter with no sharing

Public Cloud

•Multi tenant Pool of computing resources offered by a vendor , typically using a "Pay as you go" model

Hybrid Cloud

•Combination of Public or Private cloud and On premises

Page 12: Architecting the Cloud:  How EAs should think about Cloud Computing

PaaS

Email

LOB app

Native Cloud app

IaaS

Iaas and Paas

Page 13: Architecting the Cloud:  How EAs should think about Cloud Computing

Gartner’s View of Clouds

Page 14: Architecting the Cloud:  How EAs should think about Cloud Computing

““By 2012, 80% of Fortune 1000 enterprises will By 2012, 80% of Fortune 1000 enterprises will be using some cloud computing services, 20% be using some cloud computing services, 20% of businesses will own no IT assets.”of businesses will own no IT assets.”

““The bottom line: Early adopters are finding The bottom line: Early adopters are finding serious benefits, meaning that cloud computing serious benefits, meaning that cloud computing is real and warrants your scrutiny as a new set is real and warrants your scrutiny as a new set of platforms for business applications.” of platforms for business applications.”

Page 15: Architecting the Cloud:  How EAs should think about Cloud Computing

Some PaaS\ SaaS offers are already quite mature; some others are emerging

Maturing Software Segments

Page 16: Architecting the Cloud:  How EAs should think about Cloud Computing

16

Global Cloud Market Landscape

Page 17: Architecting the Cloud:  How EAs should think about Cloud Computing

Considerations: Cloud• Lower cost: CAPEX, OPEX• Greater agility• Match capacity to demand• How to leverage on-premises, public, private and dedicated cloud

Privacy of data Latency/performance considerations

• Meet requirements for secure communication and compliance • Increase speed to market• Handle complexity of SLA

Page 18: Architecting the Cloud:  How EAs should think about Cloud Computing

Considerations: Cloud computing Abstract Resources

Focus on your needs, not on hardware specs. On-demand Provisioning

Ask for what you need, exactly when you need it. Large Scale

Cloud is conceptually of infinite capacity. No Up-front Hardware Investment

Costs are in direct proportion to actual usage. Cost-Effective & Efficient

No investment in depreciating hardware.

Page 19: Architecting the Cloud:  How EAs should think about Cloud Computing

“Enterprise PCs are wasting money. Far too many organizations leave economic and

environmental value on the table by notreducing PC-related

energy costs.”“How Much Money Are Your Idle PCs Wasting?,” Forrester Research, Inc.,

December 2008

“Green IT has reached critical mass. Virtually all the companies we surveyed (97 percent) are discussing their Green strategy.”“Green IT Report Regional Data – United States and Canada: Survey Results,” Symantec, May 2009

Cloud Considerations: Environmental Sustainability

“Transformation in theway people and businessesuse technology could reduceannual man-made global emissions by 15 per cent by 2020 and deliver energy efficiency savings to global businesses of over EUR 500 billion [GBP 400 billion/USD 800 billion].”“SMART 2020: Enabling the Low Carbon Economy in the Information Age,” The Climate Group, June 2008

“IT's role will increasingly be about applying the technology to create more-energy-

efficient, less-carbon-intensive business models, enterprises,

value chains, products and services with reduced environmental impact.”“User Survey Analysis: Sustainability and Green IT, Worldwide, 2009,” Gartner, Inc., April 2009

Page 20: Architecting the Cloud:  How EAs should think about Cloud Computing

Cloud and Environmental Sustainability

• Lower Carbon Emission due to Multi tenancy Quick Provisioning Optimization of resources Datacenter efficiency Virtualization

Enterprise can reduce the carbon emissions by 20 to 90 percentage by moving to cloud

Page 21: Architecting the Cloud:  How EAs should think about Cloud Computing

When Is Cloud Computing Fit For The Enterprise?

Speed of provisioning is constraining business execution

Existing hardware has reached end of serviceable life and refresh options are being considered

Time-constrained or event-based infrastructure is required to ramp quickly and be disposed of shortly afterwards

Applications & processes have highly variable demand

High compute capacities are required to accelerate information discovery and publishing

Internal datacenter capacity limits are being reached and hostinglocations must be re-balanced

Page 22: Architecting the Cloud:  How EAs should think about Cloud Computing

Example: BPOS\Office 365 Global company- Manufacturing Acquired multiple companies

Business ChallengesNo integrated IT, more than 5 separate companies not integratedIT Cost is very highSome of the infra is end of life cycleUnused resourcesNo maturity of ITIncreasing end user needsDifferent type of users – Users with high and demands Branding Compliance – ITAR for set of users

EA Approach Reduce IT cost

By Integrating the IT Infra Major IT investment area is

Messaging and Collaboration Cloud based messaging and

Collaboration services. On premise email service for the

specific users need ITAR compliance Overall will reduce the per user

mailbox cost (savings of 27$ per user per month)

Solution approach Consolidated single unified directory

structure Central IT BPOS Cloud based messaging and

Collaboration Services 27$ per user per month saving

Carbon Emission- 79% reduction for Exchange online, 90% reduction for SharePoint

Page 23: Architecting the Cloud:  How EAs should think about Cloud Computing

OVERVIEW

Page 24: Architecting the Cloud:  How EAs should think about Cloud Computing

Cloud Impact- BPOS/ Office 365REDUCED

MANAGEMENTNEW ECONOMICS INCREASED PRODUCTIVITY

Page 25: Architecting the Cloud:  How EAs should think about Cloud Computing

Process BenefitsWhat would it cost you to achieve…

Page 26: Architecting the Cloud:  How EAs should think about Cloud Computing

Example: AWS Major Retailer Global Market reach Has existing and future strategies using Web 2.0,

social media, crowdsourcing collaboration etc as part of it marketing and reaching the younger generation

Have Facebook group of over 650,000 members

Speed of deployment and agility are key

Business ChallengesFast changing market by its very natureExpanding Digital Media strategies with accelerated plans for launch of more social and collaborative Web areasReal need for speed of deployment and agilityBusiness groups already empowered to make own choices – IT has to keep up and supportAmbitious timescales for next launch – repeating cycleIncreasing costs of external agencies to host if not in IT

EA Approach Cloud based IaaS and Elastic Computing Cloud Workshop to describe the art of the possible Architect and Design future platform for

Internet/Extranet deployments • Resilience, Scalability, expandable• Support and management• Secure

Solution AWS based Infrastructure as a serviceBusiness Benefits Speed : Rapid deployment cycle enabled

immediate verification of application development, and launch timescales

Cost Reduction: Agility : Can quickly adapt and change in line with

instant business/artistic needs Scalable: To meet needs of planned/unplanned

peaks, and then back to normal volumes Integrated : Into client’s existing monitoring and

management environment, for minimal process impact

Extendible : To take further requirements and need and incorporate into the environment

Page 27: Architecting the Cloud:  How EAs should think about Cloud Computing

Solution Overview

Extensible Architecture ready for future applications & requirements

LAMPUbuntu, ApacheRuby

LinuxMySQL

EBS Storage

HA MySQL – Master/Master

Master DB

Image Library

Backups of Images

AMIDBsetc

S3 Storage

AWS – US Region

zManda Back-ups

Linux

VPN Security- CohesiveFT VPN CubedLoad Balancing

- AWS Load Balancing

Autoscaling

- AWS autoscaling- (Rightscale later)

Firewall Security

- VPN Cubed - EC2 Ports

Dev/TestLinux

MySQL

Test DB

Dev/TestLAMP

Ubuntu, Apache, Ruby

LAMPUbuntu, ApacheRuby

Load Balanced

Content Distribution- EdgeCast

LinuxMySQL

Master DB

VPN CubedVPN Cubed

Monitoring- Nagios Management

Server

Back-Ups

- zManda

EC2 Instances

Solution Load balanced Web/App based on

Linux, Apache, Ruby-on-Rails (using AWS Elstic Load Balancing)

MySQL DB in HA configuration Based on AWS core components

• EC2 Compute, EBS storage, Load balancing, autoscaling

• S3 Storage for holding Images Use of 3rd party CDN for Image Content

Distribution 3rd Party software solution

• CohesiveFT VPN Cubed for secure management and monitoring of AWS back to Client’s management console. VPN allowed extending the Burberry datacenter to the instances on AWS.

• zManda Backups and recovery• Nagios monitoring • SubCloud – for mapping S3 as a

drive on EC2 Integration of Nagios Alerts into Client’s

own Management console

Page 28: Architecting the Cloud:  How EAs should think about Cloud Computing

QUESTIONS?

Page 29: Architecting the Cloud:  How EAs should think about Cloud Computing

THANK YOU