1 / 31

Next Generation Datacentres

Next Generation Datacentres. Ulrich Homann, M icrosoft Corp Ian Erridge, Microsoft Ltd. Agenda. State of the Industry The Dynamic Services Platform (DSP) solution Benefits – Reasons to choose Questions…?. After Lunch Quiz. State of the Industry: Software + Services. Web 2.0. Service.

iniko
Download Presentation

Next Generation Datacentres

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Next Generation Datacentres Ulrich Homann, Microsoft Corp Ian Erridge, Microsoft Ltd.

  2. Agenda • State of the Industry • The Dynamic Services Platform (DSP) solution • Benefits – Reasons to choose • Questions…?

  3. After Lunch Quiz

  4. State of the Industry: Software + Services Web 2.0 Service SaaS SOA

  5. State of the Industry: ‘Most’ Datacentres Staffing Over-provisioning Power Space constraints Under-utilized resources Regulatory Compliance Lack of agility Demand for distributed, always available services

  6. Microsoft Confidential Datacentre Today: Management Of Servers Networking Storage Compute • Realities: • Manual processes • Service domains work independently of each other • Results: • High admin to server ratio • Extended time to production/ market • Inflexible processes and vendors • Reactive management • Lack of insight into application demographics • High number of change management tickets • Decreased service availability Service Server

  7. We Hear You – Customers Are Saying: “Our Needs Are…” • Identify service dependencies, reuse common pattern templates and service blueprints • Automation of processes. • Restart services automatically • Enable pre-built server racks and pods • Automatically • convert virtualized server instance to physical server instance, based on service usage • Reconfigure whole cluster/VLAN for an application upon failure • Enable scaling and standardization without • re-writing applications • Enable greater automation across Application, Networking, Storage, and Power management domains • Lack of automation causes high operator-to-server ratio • Common service provisioning for internal and external customers • Enable data center to publish the list of services and configurations that it supports • Enable SaaS Operations Platform

  8. Datacentre Tomorrow: Moving From Servers To Services Networking Storage Compute • Focus: • Automated processes • Greater coordination between service domains • Desired results: • Optimized admin to server ratio • Decreased time to production/ market • Automated processes • Proactive management • Greater insight into application demographics • Streamlined change management process • Higher service availability Service

  9. Dynamic Services Platform (DSP) solution Microsoft Service’s view of a service-oriented datacentre operating model, providing an end-to-end view and approach to delivering services out of a datacentre

  10. DSP: Solution Approach Group Policy, Config Mgr Role Mgmt Tool Policy, Desired Config Software/ Functional Roles Visual Studio + Dev Tools ServiceDesk Code/ Implementation Data Business (Licensing, SoftwLibrary) Security Products Ops Mgr + Monitoring Security (Credentials, Permissions, …) Health,Service Level Encoded in software models (SML) Knowledge of the service: Architectural intent Operational environment IT policies Resource needs Core Concepts(Hardware, Software,relationships…) That can be created, modified and operated on ... Across the IT Lifecycle: Develop, Operate, Analyze/Act

  11. Solution Approach

  12. Why Services?

  13. Resource Consumption – External and Internal External View Internal View Web Server Is assigned to a e.g. Mailbox accessed through a User Is Hosted on Management Interaction over WS* Mailbox Server Is resolved for message delivery using a Stores mailboxes on Provisioning Systems Resource Management Systems SLA Management Systems Service Aggregation Platforms Billing Systems Auditing Systems DNS Server Disk How it works How to build it What it does How find it Where to Host it How to publish it How to use it

  14. DSP – Solution Overview

  15. The Dynamic Services Platform (DSP) is a service focused data center automation solution that addresses the end-to-end service lifecycle, dramatically reducing cost of ownership of data center operations DSP solution overview • Service Management • Service Provisioning • Automation of routine tasks • Patch management • Managed remediation • Migration • In-service routine maintenance • Versioning and rollback • Auditing and reporting • Business Intelligence • Model • Discovery • Templates • Template validation tool • Provisioning lifecycle • Self-deployment • Versioning and rollback

  16. DSP Solution Architecture Solution Components DSP DC-Scale SharePoint DSP DC-Scale SQL Server Process Templates DSP Client UI Tool Modeling Tools IT Service Model DSP Platform Components Partner/ Custom Platform Components IT Service Manager for Distributed Applications Network ITService Manager Storage ITService Manager IT Service Manager Pattern Power ITService Manager Process Execution Environment Other….. Physical / virtual server environment housing multiple services and applications

  17. DSP Design-Time & Run-Time Service Designer models service 1 DSP models are loaded from repository and executed by DSP runtime 2 DSP infrastructure built using ITService Manager Workflows 3 Service workflows execute PS scripts 4 ITService Management application identifies workflows and other artifacts PowerShell Scripts

  18. Microsoft Confidential Expanding the Service Model… Solution Components DSP DC-Scale SharePoint DSP DC-Scale SQL Server Process Templates DSP Client UI Tool Modeling Tools IT Service Model Data Contract (SML) IT Service Model Policy / Rules (XOML) .Net Java Assemblies Process / Workflow WebServices WS-Man PowerShell VB CMD SSH XOML

  19. The DSP Data Model Data Contract (SML) <ITService> <Site> Implementation Functionality <Capabilities> <Cluster> 1..N <WorkLoad> <ServerRole> 1..N <RoleService> 1..1 instance

  20. Service Configuration Developer Experience :Integrated WorkFlow & PowerShell Development

  21. Expanding the Modeling Tools… Solution Components DSP DC-Scale SharePoint DSP DC-Scale SQL Server Process Templates DSP Client UI Tool Modeling Tools IT Service Model

  22. Expanding the Templates… Solution Components DSP DC-Scale SharePoint DSP DC-Scale SQL Server Service Model Process Templates DSP Client UI Tool Modeling Tools IT Service Model <ITService> <Cluster> • XML/CML Templates • Dependencies • Configuration • Deployment • Health / Growth <Workload> <ServerRole> XML/CML WorkFlow WF <RoleService> PowerShell Cmdlets PS SharePoint Hosted Exchange SCOM SCOM MP Images Images, patches, etc XML/CML WSS AD IIS SQL Server WF PS SCOM Images XML/CML Windows WF PS SCOM Images

  23. Projected Load Profile

  24. Load by Time of Day

  25. Going Green

  26. Guided Provisioning • Pete’s SharePoint order (representing max growth): • 50,000 users • 20,000 team sites • 150MB/site • Responses per second: 100 • Monitoring counters in the operational configuration and monitoring environment (SC OM 2007) trigger growth (or shrink) provisioning once the specific capacity driver hits 80% of specified value: • Growth based upon RPS (growth type A): initial size – 99 RPS; counter is set to 80 RPS • Growth based upon content db size (growth type B): initial size – 0.8 TB; counter is set to 0.7 TB

  27. A Responsible Dynamic Topology ASP ASP ASP ASP ASP SQL IIS IIS IIS IIS IIS

  28. Implications of Green Computing • The goal in most ‘green’ initiatives has to be focused on using only the minimally required resources for the given workloads. • Ideally, systems will be deployed with the minimally required resources and allow for ‘dynamic’ growing and shrinking of required resources based upon load heuristics. • Consolidate workloads onto fewer resources by analysis of load patterns and hotspots: • Permanently and Temporarily • Shut down non-required resources • What is the Architecture for a Green Application?

  29. Questions

More Related