53

Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Embed Size (px)

Citation preview

Page 1: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services
Page 2: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Optimize Your Data Center with Datacenter Services from Microsoft Services

David ZiembickiSolution ArchitectMicrosoft

SD-B307

Adam FazioSolution ArchitectMicrosoft

Page 3: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Introduction

Lead Architect for Microsoft Services Private Cloud Solutions

David ZiembickiSolution Architect Office of the Americas CTOMicrosoft Services

Contributor to:

Blog: http://davidzi.comTwitter: http://twitter.com/davidzi

Lead Architect for Microsoft Services Private Cloud Solutions

Adam FazioSolution Architect WW Datacenter COEMicrosoft Services

Contributor to:

Blog: http://technet.microsoft.com/privatecloudTwitter: http://twitter.com/adamfazio

Page 4: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

• Who is Microsoft Services and what is the Datacenter Services Portfolio?

• What is the IaaS Product Line Architecture?• Why a standard reference architecture?• Fabric Architecture (Windows Server, Hyper-V, Failover Clustering)• Management Architecture (System Center)• Deployment Scenarios

• Availability and Call to Action

Session Objectives

Page 5: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Who is Microsoft Services and what is the Datacenter Services Portfolio?

Page 6: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Microsoft Enterprise Services

• 13 areas / 82 countries

• 17,341 employees

• 44 languages

• 35,000 partners

• 715 million customer touch points per year

Accountability for Your Success Global Scale and Demonstrated Experience

World Class Expertise Globally, innovating to demonstrate what is possible with Microsoft

Distinctive Intellectual Property (IP) to allow our people and partners to deliver impact

Long-term Customer Relationships committed to long-term customer success

Connection with our Product Groups to resolve problems and influence product roadmaps

A Relentless Focus on Driving Customer Impact through architecture, deployment, adoption, and support, helping to make sure our customers use and get value from their investments in Microsoft, providing a competitive differentiator for Microsoft

Canada349

Canada349

US6588US

6588

Latam516

Latam516

WE1939WE

1939

France519

France519

Germany870

Germany870

CEE886CEE886

Japan789

Japan789

India1891India1891

APAC758

APAC758

MEA547MEA547

GCR770GCR770

UK919UK919

Mic

roso

ftServ

ices

Strategy Consulting Support

Page 7: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Microsoft WW Datacenter Center of Excellence and Community

• 13 areas / 28 countries

• 100 Architects

• 300 Consultants

• Hundreds of partners

• Hundreds of customer projects delivered per year

Deep Datacenter Expertise Global Scale and Demonstrated Experience

World Class Expertise Globally, through datacenter architecture, virtualization, management, and operations

Distinctive Intellectual Property (IP) to enable rapid and consistent deployment of the Microsoft cloud platform

Deep Industry Expertise in the Commercial and Public Sectors

Connection with our Product Groups to map customer requirements to product design

A Relentless Focus on Driving Customer Impact through architecture, deployment, adoption, and support, helping to make sure our customers use and get value from their investments in the Microsoft cloud platform

Data

cente

rServ

ices

PrivateCloud

PublicCloud

HybridCloud

Page 8: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

MICROSOFT CONFIDENTIAL – INTERNAL ONLY

Current Architecture Landscape

• Mixed guidance on how to architect, plan, design Microsoft solutionsVirtually unlimited number of configuration variations

• “Islands of Best Practice” are commonplace

• Delivering various levels of cloud attributes across implementations

• Long planning and deployment cycles

Time to Value

Cloud Compatibility

Islands of Best Practice

Complexity

We need a consistent way to deploy…

Page 9: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Services Solutions and Offerings

Extensible Platform

Solution platform provides capability for extensions and value-added services

Product Line Architectures

Best practices for architecture, design, and operations of datacenter and cloud infrastructures

Deployment Frameworks

Frameworks for assessing, planning, and deploying datacenter capabilities

Packaged Services

Packaged solution for deploying highly-automated datacenter and cloud services

Page 10: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Datacenter Services Portfolio

Intellectual Property

IaaS Management Architecture

IaaS Fabric Architecture

Hybrid Cloud

VDI

Large/Complex Environments

Multi-Site / Disaster Recovery

Services Offerings

Datacenter Infrastructure & Management

Datacenter Consolidation & Migration

Datacenter Automation

Datacenter Modernization

Datacenter Operations

Content

Reference Architectures

Project Plans

Deployment Guides

Tools and Automation

Operations Guides

Page 11: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

MICROSOFT CONFIDENTIAL – INTERNAL ONLY

What is a PLA?A Product Line Architecture (PLA) is a set of rules and architectural patterns that provide a method for predictable and supportable deployments

The IaaS PLA – Fabric Architecture includes the concepts of compute, storage, and network fabric layers. The IaaS PLA – Management Architecture includes guidance for

deploying System Center to manage the IaaS fabric.

Cloud Management(System Center)

Fabric(Virtualization, Compute, Storage,

Network)

Page 12: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Who is the PLA for?

Organizations which fit in

defined scale points as defined by each product

New Deployments and

Upgrades from Legacy Solutions

Customers looking for reliability,

stability and supportability

Page 13: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

PLA AttributesMicrosoft evolves the Product Line Architecture as we capture learnings from customer deployments and support incidents to continuously improve the architecture and our deployment practices.

The Benefits of using the PLA include:

Performance ScalabilityInteroperability Resilience

ManageabilityQuality

Supportability

Disaster Recovery Portability

• Proven deployment model • Deployed right the first time • Reduced time to deployment

• Predictable and achievable SLA’s• The best user experience • All workload capabilities realized

The PLA delivers the highest quality deployment by following design principles to support/enable …

Rulebook

Page 14: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

The IaaS PLA Design Process

Guidance(Mandatory, Recommended, Optional)

Early Adoption and OEM Programs

Solution Offerings

MCS Deploym

ents

Request change / new rule

Approve Updates / Release

Engagement

Delivery / PG Updates

Feedback Loop

Page 15: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Private Cloud Fast Track• Fabric Validation Guide• Mgmt Validation Guide

Fast Track (OEM)Fabric Architecture Validation Guidance

Windows Server 2012 Design Patterns

Fast Track (OEM)Fabric Management Architecture Validation Guidance

System Center 2012 SP1 Design Pattern

Fast

Track v

ers

ion

3

OEM

Order Hardware in Days vs. Weeks

IaaS PLA• Fabric PLA• Management PLA

Fabric Architecture Guidance

Windows Server 2012 Design Patterns

Fabric Management Architecture Guidance

System Center 2012 SP1 Design Pattern

IaaS

PLA

Service Provider/Enterprise

Design and Deploy in Weeks vs. Months

ScenariosWorkloads

Hybrid Cloud

Cloud Packs

Multi-Site Datacenters and DR

End-to-End

Monitoring

Service Mgmt

Datacenter

Chargeback/Showb

ack

Complex System Center

IT Process Automatio

n

Deploy Enable workloads and complex scenarios inMonths vs. Years

What does the IaaS PLA Enable?

Page 16: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

IaaS PLA – Fabric Architecture

Page 17: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Continuous Availability over SMB Storage Pattern

Converged Infrastructure Pattern

Non-Converged Infrastructure Pattern

IaaS PLA – Fabric Architectural Patterns

Page 18: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Emphasis on minimizing risk and cost of new hardware and designs

Optimal for leveraging an existing SAN investment

Large or recent investment in server/blade hardware with HBAs

SAN Based Storage

Volumes

FC FC

Hyper-V Cluster

Volume1

Cluster Shared Volumes (CSV2)

Volume-n

Teamed Network Interfaces (LBFO)

iSC

SI

iSC

SI

Non-Converged Infrastructure Pattern

Page 19: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Non-Converged Infrastructure Pattern

Fibre Channel/iSCSI

SAN Storage Hyper-V Host Cluster(s)

Eth NIC

Eth NIC

NIC Teaming (LBFO)

Hyper-V Extensible

Switch

VMs

VMs

VHDs

LAN

Fibre Channel/iSCSI

Fibre Channel/iSCSI

Fibre Channel/iSCSI

Cluster Shared Volumes (CSV2) + CSV Cache

Volumes

Page 20: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Non-Converged -Physical Host and Network Design

Page 21: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Cost savings and operational efficiency of a single common Ethernet network vs. multiple physical networks and HBAs for storage traffic

Optimal for leveraging a converged-network architecture

Large or recent investment in blade servers with converged-network and storage-network infrastructure

SAN Based Storage

Volumes

Hyper-V Cluster

Volume1

Cluster Shared Volumes (CSV2)

Volume-n

Converged Network

Architecture

Converged Infrastructure Pattern

Page 22: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Converged Infrastructure Pattern

SAN Storage

Volumes

Cluster Shared Volumes (CSV2) + CSV Cache

Fiber Channel / iSCSI

Hyper-V Host Cluster(s)

CNA

CNA

Hyper-V Extensible

Switch

VMs

VMs

VHDsLAN

Fiber Channel / iSCSI

Fiber ChanneliSCSI

SMB Direct

NIC Teaming

Page 23: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Converged -Physical Host and Network Design

Page 24: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Hyper-V clusters consuming storage from scale-out file server clusters or SMB3 enabled storage devices

Optimal for low cost JBOD strategy enabled by networking capabilities of SMB Multichannel and RDMA

Requires network infrastructure between theHyper-V servers and file servers

Shared SAS Storage

RDMA

Storage Spaces

Clustered File Servers

SA

S

SA

S

RDMA

Hyper-V Cluster

\ \ cno\ share-1

SMB Direct Shares(SMB3 over RDMA)

\ \ cno\ share-n

Teamed Network Interfaces (LBFO)

Continuous Availability over SMB Storage Pattern

Page 25: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Variation ASMB Direct using

Shared SAS/Storage

Spaces

Variation CSMB3-Enabled

Storage

Variation BSMB Direct using

SAN

Continuous Availability over SMB Storage Pattern

Page 26: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Variation ASMB Direct using

Shared SAS/Storage

Spaces

Continuous Availability over SMB Storage Pattern

SAS Disks

SAS Controller

SAS Controller

Scale-Out File Server Cluster

Storage Spaces

Cluster Shared Volumes (CSV2) + CSV Cache

RDMA NIC

RDMA NIC

Hyper-V Host Cluster(s)

RDMA NIC

RDMA NIC

SMB3 DirectSMB3 Transparent Failover

SMB3 Multi-Channel

Eth NIC

Eth NIC

NIC Teaming

Hyper-V Extensible

Switch

VMs

VMs

VHDs

LAN

Page 27: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

CA Over SMB Variation A

Storage Design with

Scale-Out File Server Cluster,

Storage Spaces, SAS

SAS Disks

SAS HBA SAS HBA

Scale-Out File Server Cluster Node

Storage Spaces

Cluster Shared Volumes (CSV v2) + CSV Cache

VHDs

SAS Port

SAS Port

SAS Port

SAS Port

SAS HBA SAS HBA

SAS Port

SAS Port

SAS Port

SAS Port

VHDs

Scale-Out File Server Cluster Node

SAS Expander SAS Expander

SAS JBOD Array with Dual Expander/Dual Port Drives

Storage Pool(s)

10Gb-E RDMA Port

10Gb-E RDMA Port

10Gb-E RDMA Port

10Gb-E RDMA Port

Continuous Availability over SMB Storage Pattern

Page 28: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

CA Over SMB Variation A

Storage Design with

Scale-Out File Server Cluster,

Storage Spaces, Switched SAS

SAS Disks

SAS HBA SAS HBA

Scale-Out File Server Cluster Node

Storage Spaces

Cluster Shared Volumes (CSV v2) + CSV Cache

VHDs

SAS Port

SAS Port

SAS Port

SAS Port

SAS HBA SAS HBA

SAS Port

SAS Port

SAS Port

SAS Port

VHDs

Scale-Out File Server Cluster Node

SAS Switch SAS Switch

SAS JBOD Array with Dual Expander/Dual Port Drives

Storage Pool(s)

SAS Expander

SAS Expander

SAS Disks

SAS JBOD Array with Dual Expander/Dual Port Drives

SAS Expander

SAS Expander

10Gb-E RDMA Port

10Gb-E RDMA Port

10Gb-E RDMA Port

10Gb-E RDMA Port

SAS Disks

SAS JBOD Array with Dual Expander/Dual Port Drives

SAS Expander

SAS Expander

Continuous Availability over SMB Storage Pattern

Page 29: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

CA Over SMB Variation A

Storage Design with

Scale-Out File Server Cluster, Clustered HW

RAID (no spaces), SAS

SAS Disks

PCI RAID PCI RAID

Scale-Out File Server Cluster Node

Cluster Shared Volumes (CSV v2) + CSV Cache

VHDs

SAS Port

SAS Port

SAS Port

SAS Port

PCI RAID PCI RAID

SAS Port

SAS Port

SAS Port

SAS Port

VHDs

Scale-Out File Server Cluster Node

SAS Expander SAS Expander

SAS JBOD Array with Dual Expander/Dual Port Drives

PCI Clustered RAID Volumes

10Gb-E RDMA Port

10Gb-E RDMA Port

10Gb-E RDMA Port

10Gb-E RDMA Port

Continuous Availability over SMB Storage Pattern

Page 30: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

MICROSOFT CONFIDENTIAL – INTERNAL ONLY

Continuous Availability over SMB Storage PatternVariation A ConsiderationsSAS switches enable multiple host servers to be connected to multiple storage trays (SAS JBODs) via multiple pathsConnectivity between scale-out file servers and storage are critical to overall performanceSAS drives are used in conjunction with a JBOD storage enclosure to enable the Storage Spaces featureSmaller storage footprint designs can use Fast Track “small” or “Cluster-in-a-Box” (CiB) appliances

SAS RequirementsPort associationSymmetric access for multi-port drivesPersistent ReservationsDrive Enclosure requires drive identification services and direct access to the drives

Page 31: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

IaaS PLA –Management Architecture

Page 32: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Service Delivery

Process Automation & Orchestration

Fabric Management

IaaS PLA – Management Architecture Scenarios

Page 33: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Self Service

Service Delivery

and Automatio

n

Deploy

Configure

Service Model

DCAdmin

Operate

Monitor

Virtual Machine Manager

Operations Manager

App Controller

Service Manager

Service Manager

Orchestrator

Configuration Manager

Application ManagementService Delivery and

Automation Infrastructure Management

Data Protection Manager

AppOwner

Microsoft

On-premises

Service Provider

System Center – Unified management for the Cloud OS

Page 34: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Architectural Overview

Page 35: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services
Page 36: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

• Key to design is to rationalize scale points across all components

• References below cover the private cloud components• Always review and refer to product documentationComponent Scalability Reference NotesVirtual Machine Manager

800 hosts/25,000 virtual machines per instance A VMM instance is defined as a standalone or cluster installation. Scalability is limited to 5000 virtual machines when Service Provider Foundation (SPF) is installed. A single SPF installation can support up to five Virtual Machine Manager instances.

App Controller Scalability is proportional to Virtual Machine Manager (VMM)

Supports 250 virtual machines per Virtual Machine Manager User Role

Operations Manager 3,000 agents per management server, 15,000 agents per management group

 

Orchestrator Simultaneous execution of 50 runbooks per Runbook server

 

Service Manager Large deployment supports up to 20,000 computers

Topology dependent. Note that in Fast Track Service Manager is used solely for private cloud virtual machine management. An advanced deployment topology can support up to 50,000 computers

Scalability

Page 37: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Service Accounts, Groups and Permissions• Define all Service Accounts,

Groups (and group memberships) and Permissions in advance• Don’t assume that installations will be done

with Enterprise or Domain Admin account• Log on as a Service right (Orchestrator Service

Account)

• Use principle of Least Privilege

Page 38: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

SQL Server per Component

vs.

SQL Server Multi-Instance Failover Cluster

Key Decision PointsSQL Server

Page 39: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

SQL Availability

• Defined pattern and detailed design for the Fast Track and IaaS PLA

• Leverage SQL Server Failover Clustering:• On-prem (Host/Guest cluster)

• Leverage SQL Always On for:• Remote site

Page 40: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

SCSMDB

Orchestrator

ServiceManager CMDWDataMart

OMDWDataMart

DWDataMart

DWStagingAndConfig

DWSRepository

SCSMDW

SCSM SSAS

ReportServer

ReportServerTempDB

SCSMAS

SharePoint_Config

SharePoint_Content DBs

WSS DBs

SCDB

VirtualManagerDB

SCVMMDB

OperationsManager

SCOMDB

OperationsManagerDW

ReportServer

ReportServerTempDB

SCOMASRS

AppController

WSUS DB

Optional Component

LUN4: Data

LUN5: Logs

LUN6: Data

LUN7: Logs

LUN8: Data

LUN9: Logs

LUN2: Data

LUN3: Logs

LUN10: Data

LUN11: Logs

LUN12: Data

LUN13: Logs

LUN14: Data

LUN15: Logs

LUN1: Quorum

SCOMDW

SSAS and SSRS Installed Remotely on the SCOM Reporting Server

SQL Instances, DBs, & LUNs

Page 41: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Key Decision PointsVirtual Machine Manager

• Why make VMM highly available? • VMM is a key part of the Private Cloud management toolset• VMM HA is a fault tolerant service feature, but does not increase

scale/performance

• For complete highly availability, all SCVMM components need to be HA

• SQL• Library

• VMM setup is integrated with Failover Clustering• VMM console connections should use the cluster name of the HA VMM service

instead of an individual node

Page 42: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Key Decision PointsService Manager

• Connectors• Ports , Service Accounts

• TechNet guidance is focused on deployment of the Component scenario

• Not developed for Private Cloud deployment

• SharePoint considerations• SQL/SharePoint and Portal• Certificates• Version

Page 43: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Key Decision PointsService Manager Active Directory Connector

• Default behavior of the connector will synchronize ALL objects from Active Directory

• Solution – Be targeted

Example : 1. Use wildcard for group name prefixes in AD Connector properties

I.E. – “cn=SM*” for ‘SMAdmins’, ‘SMUsers’, etc.2. Select “Automatically add users of AD groups imported by this connector”

Page 44: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

• Installation is a breeze!• Configuration depends on VMM

constructs• VMM Self-Service Users• Library Resources• Logical Networks• Clouds

App Controller

Page 45: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

• Orchestrator Integration Packs enable automation of the various System Center components (VMM, Operations Manager, Service Manager, etc.)

• System Center Orchestrator Connector requires the SCO Web Service URL – where do you find this?• Default install = Web Service URL is Port 81 of the Orchestrator

SQL Server / Instance• Example:

http://SCO2012SQL:81/Orchestrator2012/Orchestrator.svc• Runbook scalability• Service Manager connectors populate the CMDB with

CIs

Orchestrator

Page 46: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Service Manager

Service Manager

Portal

CMDB

App Controller

Portal

Azure

Hyper-V

SM Data Warehouse

OM Data WarehouseOrchestrator

Operations Manager

Virtual Machine Manager

Active Directory

CI Connector

VMM/OM Integration

IntegrationPack

ReportingData

Integration

Page 47: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

• The IaaS Product Line Architecture is the Microsoft best practices reference architecture for Windows Server, Hyper-V, and System Center Deployment for private cloud IaaS

• The PLA is the basis for Microsoft, OEM, and Partner Programs• The PLA was created by a team of experts from across the

world:

Summary

Adam FazioJoel YokerDavid ZiembickiRicardo MachadoArtem Pronichkin

Thomas EllermannRobert LarsonAaron LightleMichael LubanskiRay Maker

Ian NelsonShai OfekAnders RavnholtRyan SokolowskiAvery SpatesAndrew Weiss

Page 48: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Call to Action

Page 49: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Private Cloud Fast Track Program

Page 50: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Next Steps

Do-it-Yourself Microsoft Consulting Services Partner

Private Cloud Fast Track

PLA Reference Architecture & Deployment Guideblogs.technet.com/privatecloud (coming soon!)

Microsoft Virtual Academymicrosoftvirtualacademy.com

Executive and Technical Briefings

Workshops

Proof-of-Concept

Jumpstart Engagement (Rapid, 5-week deployment)

Full Engagement

Practice Accelerators

Datacenter Services Partner Program

Page 51: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Evaluation

Complete your session evaluations today and enter to win prizes daily. Provide your feedback at a CommNet kiosk or log on at www.2013mms.com.Upon submission you will receive instant notification if you have won a prize. Prize pickup is at the Information Desk located in Attendee Services in the Mandalay Bay Foyer. Entry details can be found on the MMS website.

We want to hear from you!

Page 52: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

Resources

http://channel9.msdn.com/Events

Access MMS Online to view session recordings after the event.

Page 53: Introduction Lead Architect for Microsoft Services Private Cloud Solutions David Ziembicki Solution Architect Office of the Americas CTO Microsoft Services

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.