Architecting Private and Hybrid Clouds:

January, 2015

January,  2015   Public:  This  content  may  be  copied  and  distributed.   2  

Architecting Private & Hybrid Clouds: Introduction

This is a practical discussion on aligning the IT foundation and solutions to support business needs. Private and hybrid clouds continue to be hot topics and we will place them in the context of IT service delivery and business value.

January,  2015   Public:  This  content  may  be  copied  and  distributed.   3  

Architecting Private & Hybrid Clouds: Introduction

Understand business stakeholder perspective. Our responsibility within IT is to understand business needs/objectives and make the right system tradeoffs needed to achieve them. §  Cost §  Usability §  Availability §  Security §  Performance §  Modifiability §  Scalability §  … Architecture is key to driving change and managing technical debt*.

*Technical  debt  references  the  cost/impact  of  complexity,  aging  technology,  and  quality  gaps  in  the  IT  environment.  It  is  a  method  to  measure  the  impact  and  determine  what,  if  any,  actions  are  needed.

January,  2015   Public:  This  content  may  be  copied  and  distributed.   4  

Architecting Private & Hybrid Clouds: Cloud Overview

Description: Hardware (network, server and storage) is “leased” on a pay-as-you-go basis. Target Audience: Independent web developers, startup companies, SMBs (Small and Medium Businesses) and large enterprises. Use Cases: Application development and testing, application hosting, elastic web applications, disaster recovery, and high performance computing (HPC)

Description: An application development framework and middleware that is highly integrated with the underlying infrastructure to scale as needed to satisfy demand. Target Audience: Developers, enterprises and Application Service Providers Use Cases: Web application development and application prototyping

Description: A service provider delivers a fully functional application to the customer using the Internet as transport and a web browser as the presentation layer. Target Audience: Consumers and businesses of all sizes Uses Cases: Most applications available as SaaS

January,  2015   Public:  This  content  may  be  copied  and  distributed.   5  

Architecting Private & Hybrid Clouds: Cloud Overview: Service Models

Multi-tenant Environment

Architecting Private & Hybrid Clouds: IT Progression

January, 2015 Public:  This  content  may  be  copied  and  distributed.   6

We are progressing from virtual to cloud delivery models. Two key private cloud characteristics are service oriented applications (resiliency and scalability) and mature cloud stacks (automation).

Architecting Private & Hybrid Clouds: Enterprise IT Reality

January, 2015 Public:  This  content  may  be  copied  and  distributed.   7

Enterprise IT is comprised of diverse legacy and current technologies (not the same as pure play cloud providers). The cloud enablement of applications will evolve over time driven by business value and refresh cycles. IT must

focus on aligning the IT foundation to support changing business needs.

January, 2015 Public:  This  content  may  be  copied  and  distributed.   8

Architecting Private & Hybrid Clouds: Journey to achieve business value*

1. Understand business partner needs/objectives 2. Determine delivery model (internal vs. SaaS vs. PaaS vs. external IaaS) 3. Architect IT foundation to support current and future needs 4.  Identify scalability, security, performance, and flexibility needed in IT

solutions and build them in 5. Build the roadmap and prioritize based on business value 6. Develop high level business case for key initiatives 7. Present plans to key business partners (approvers)

* The IT strategy is typically the reference point for achieving IT value. The approach outlined on this page streamlines time to value and doesn’t eliminate the need for the IT strategy.

January, 2015 Public:  This  content  may  be  copied  and  distributed.   9

Architecting Private & Hybrid Clouds: Understand Business Needs

The key is understanding the architecture focus that supports business objectives. This information is used to drive change and right architecture focus for the IT foundation. Owner: Enterprise Architect

January, 2015 Public:  This  content  may  be  copied  and  distributed.   10

Architecting Private & Hybrid Clouds: Establish the Right Architecture

Develop enterprise application view and conduct workshops to develop application rationalization plan. Key is understanding the business impact of applications and focusing on what’s important. Owner: Enterprise Architect

January, 2015 Public:  This  content  may  be  copied  and  distributed.   11

The enterprise architecture view is used to develop the rationalization plan. This process is critical and drives clarity for IT. A clear understanding of the application delivery provides the infrastructure team with the information needed to act and align compute, storage, and network with application needs. Conduct SaaS readiness assessment: §  Business value §  Technology readiness §  Risks Owner: Enterprise Architect

Architecting Private & Hybrid Clouds: Rationalization

January, 2015 Public:  This  content  may  be  copied  and  distributed.   12

Intranet  Services

Workflow  Integration

File  Services

Application  Integration

Simplified  Sign-­‐on

Middleware

FormsPassword  Reset

Identity  and  Access  Management

Access  Management

Data  Services  -­‐  AnalyticsReporting

Visualization

Collaboration:  email;  IM/Chat;  Web  

Conferencing;  Video  

Conferencing

Data  Services

Department  Applications:  

Internal  Audit;  Legal;  

Safety;  Recruiting

Mobile  Service  Delivery ERP

Line  of  Business  

Applications:  MES

Line  of  Business  

Applications:  Engineering

 Data  Integration

Content  Management

Content  Services

Line  of  Business  

Applications:  Engineering

Search

User  Application  Services

Common  IT  Services

Standardization

SAML RESTful  Interfaces

IDM, middleware, content services, and data services are required to support application services. A well defined standards and architecture is needed to drive simplicity. Common Services §  Identity and access management §  Application and data integration §  Content services §  Data services

Owner: Enterprise Architect, Application Architect

Architecting Private & Hybrid Clouds: Software Architecture

January, 2015 Public:  This  content  may  be  copied  and  distributed.   13

Software Architects must reconsider the design of applications. Modular application architectures that are loosely coupled and stateless support the scalability and resiliency needed for the business. Focus: § Isolation - each component performs work independently § Stateless § Loosely coupled – messaging § Static data close to the user, dynamic data close to the application server Owner: Software Architect

Architecting Private & Hybrid Clouds: Software Architecture

Cloud paradigm shift - the responsibility for resiliency shifts to software

January, 2015 Public:  This  content  may  be  copied  and  distributed.   14

Today’s infrastructure is diverse and complex. The goal is to simplify while supporting business and application needs. Achieving this while supporting a variety of workloads (OLTP, data analytics, real-time) is a tall challenge. Focus: §  Rationalize infrastructure §  Understand future business

needs and organization shifts §  Align infrastructure with

application plans §  Develop technology and process

standards §  Automate infrastructure delivery Owner: Cloud Architect, Infrastructure Architect

Architecting Private & Hybrid Clouds: Infrastructure Architecture

January, 2015 Public:  This  content  may  be  copied  and  distributed.   15

Architecting and deploying the cloud platform is not trivial. Resources nodes must be sized to handle requests and the appropriate level of resiliency must be implemented. What level of functionality is needed? §  Core services – compute,

storage, network, image, dashboard, orchestration, and identity

§  Self-service §  Chargeback or showback §  Hybrid service Owner: Cloud Architect/Infrastructure Architecture

Architecting Private & Hybrid Clouds: Cloud Infrastructure: OpenStack Example

January, 2015 Public:  This  content  may  be  copied  and  distributed.   16

 

The network supporting the cloud infrastructure can be complex. Inter and intra data center migration of workloads contributes to this challenge. Making the right network overlay decisions is key. §  L3 preferred to improve

scalability §  Cloud ready apps don’t need L2 §  Leaf and spine switches should

be open and support Openflow protocol.

Owner: Cloud Architect/Infrastructure Architect

Architecting Private & Hybrid Clouds: Cloud Infrastructure

TRILL   VxLAN   GRE  

Encapsula)on   Ethernet  over  Ethernet  

Ethernet  over  IP  

Ethernet  over  IP  

Inter-­‐datacenter  link  

Ethernet   IP   IP  

Intra-­‐datacenter  link  

Ethernet   IP   IP  

Virtual  Network  Segmenta)on  

Limited   Yes   Yes  

Firewall  Compa)bility  

Very  High  

High   Low  

Incremental  Deployability  

High   High   Low  

Mul)-­‐path  and  load  balancing  

Na)ve   Par)al   Par)al  

Network  Overlay  Protocols*

*Source:  Cloud  Networks:  Enhancing  Performance  and  Resiliency,  IEEE  October  2014

Transparent  Interconnection  of  Lots  of  Links  (TRILL),    Virtual  extensible  LAN  (VxLAN),  Generic  Routing  Encapsulation  (GRE)

January, 2015 Public:  This  content  may  be  copied  and  distributed.   17

Planning for hybrid clouds should be performed up front – all IaaS services are not the same. Ensure the provider IaaS is interoperable with the internal cloud platform. IaaS provider selection criteria: § Cost § Feature parity – compute, storage, and networks § Open APIs § Performance and availability commitments Owner: Cloud Architect/Infrastructure Architect

Architecting Private & Hybrid Clouds: Hybrid Cloud

January,  2015   Public:  This  content  may  be  copied  and  distributed.   18  

The key to success is focusing on the right IT foundation to support your business needs.

Key Takeaways: 1.  Engage business partners up front to understand what’s important for your business 2.  Leverage the value of the cloud where it makes sense for your business – scale out,

resiliency, speed of delivery 3.  Develop a plan and architecture to achieve value – don’t let it evolve otherwise

technical debt will haunt you 4.  Native cloud-enabled applications and the cloud platform are the keys to achieving

cloud value – focus there 5.  Cloud platform implementation is not trivial – build the right skills and engage

consultants when necessary to bridge gaps

Architecting Private & Hybrid Clouds: Summary

January,  2015   Public:  This  content  may  be  copied  and  distributed.   19  

§  Architecting for the cloud: best practices – AWS white paper §  Trends and Directions on Software Architecture – SEI presentation §  Technical debt – SEI library §  Using AWS for disaster recovery – AWS white paper §  OpenStack Architecture Design Guide §  OpenCompute – Facebook project to build the most efficient infrastructure for the

lowest possible cost §  SDx Central – Reference site for all things SDN, NFV, cloud, and virtual

infrastructures §  Data Center Map – Reference for data centers and cloud providers §  Key skills for technology professionals – thoughtfultechnology blog post

Architecting Private & Hybrid Clouds: Reference Information

January,  2015   Public:  This  content  may  be  copied  and  distributed.   20  

Thank  You!    

karl@akilisystems.com  blog:  thoughtfultechnology.com  

@thoughtful_tech