2. Welcome to the Microsoft Architect Forum Infrastructure and Business Priorities 24 th October 2005

3. Infrastructure Models Giovanni Marchetti Infrastructure Architect Microsoft Ltd.

4. Agenda Do I need a model? What modeling instruments are available? What can I use a model for? The vision Two questions

5. Why Modelling

6. What Makes a Model E=mc 2 Symbols Operations Syntax

7. Model Semantics

8. Infrastructure models System Definition Model Microsoft initiative, supported by HP, Dell, Fujitsu, CA, Opsware, etc… SDK available, V1 in November 2005 Data Center Markup Language OASIS initiative, supported by Opsware, CA, EDS, BMC, etc… V1 Spec. published

9. SDM Basics An SDM Model captures Structure – the various pieces of a system, how they relate to each other (web application communicates with catalog DB, catalog DB hosted on SQL, etc.) Behavior – the set of operational tasks that can be applied to the system ( start, stop, backup, add user, etc.) Constraints and invariants – the set of rules or policies that must remain true for the system to be considered operational (host customer transaction DB on SQL cluster, etc.)

10. SDM Example: A File Server NB: NOT the final syntax namespace FileServer { public class FileShare { public key string name; int maximumUsers; bool cachingEnabled = True; } public class FileServer : Windows.Server { bool shadowCopyEnabled = False } public relationship ServerHostsShares { public role FileServer host[1]; public role FileShare guest[*]; } } New type definition Key properties identify real-world instances Specialized type through inheritance Relationship states a file server can host multiple file shares, but a file share must be hosted on a single file server File Share File Server HostedBy Model * 1 Types are typically declared in a namespace

11. SDM and DCML Can SDM use DCML? Yes, e.g. to interact with heterogeneous CMDB SDM and DCML could feed each other to maintain respective view of infrastructure OASIS positions DCML in Service Management area. E.g. to describe ITIL configuration management process

12. What can I use a model for?

13. The Tao of Management (according to marketing dept…) Knowledge is the key to management Desired state is replicated down -models, constraints, policy, prescriptive guidance, SLAs, patches Actual state is replicated up -inventory, metrics, events, alerts, compliance, service level, results Management consists of resolving conflicts between desired and actual state Desired state DeveloperIT Admin Model CMDB Central Manager Remote Manager Local Model Managed System Actual state

14. Model-Based Management SDM Model Real-World System 3. Model Updated System Administrator 1. Model Update Request 2. Validate Update Request 4. Adapters Update Real World System

15. Operations Lifecycle Service Level Management Capacity Management Availability Management Financial Management Workforce Management Service Continuity Mgt Change Management Configuration Management Release Management Security Administration System Administration Network Administration Service Monitoring & Control Directory Services Admin Storage Management Job Scheduling Print/Output Management Service Desk Incident Management Problem Management Release Readiness Review Release Approved Review SLAReview OperationsReview Changing OperatingSupporting Optimizing

16. Models in development The goal of SDM is to facilitate the design of application services through design-time validation of models IT Architect ApplicationDeveloper DeploymentandOperationalRequirements Data Center Policy and Constraints SDM Models ModelValidation SDM in VS2005 Errors

17. Core classes : System, Resource, and Endpoint Core relationships : Containment, Hosting, Communication, Delegation, and Reference Classes and relationships for design-time validation of web services Classes: Web Service, ASP.NET, SQL, IIS, Database, Web Directory, etc. Relationships : SQL hosts Database, File System hosts Directory, Web Client communicates with Web Service, etc. No support for behavior Just checking constraints

18. Modelling in deployment Deployment is instantiation of model Web [1..*] Application Catalog [1..*] Database Customer [1] TransactionDatabase IIS 6 [1..*] SQL Server [1] 2000 Enterprise Cluster Communication via SSL Hosted On Worker Process Isolation SQL Server [1..*] 2000Standard Communication Hosted On Constraints: Create a new instance of Web Application for every 10,000 users Each Web Application instance must have its own instance of Catalog Database Behavior:StartStopBackupDataUpgradeSQL 1 1

19. Deploying e-Shop SDM Models Application Application Host OS Hardware Deployment Tool Create new instance of e-Shop 1.Verify that actual hardware complies with the hardware model 2.Install OS as per the OS model 3.Install SQL and IIS as per the Application Host model 4.Install the Web Application, Catalog DB, and Customer Transaction DB as per the Application model

20. Modelling in operations Create a health model Maintain live view of service and infrastructure status Execute tasks on model in response to: Change requests Status changes in health model Performance constraints / rules

21. Task Example: Invoking Behavior E-Shop Instance Catalog DB servers 1. AddProduct (Ferrari) 3. Instance Updated 4. Adapter Updates the Catalog Task: Add a new product – Ferrari – to the Catalog 2. Validate AddProduct Request Create Ferrari in Publisher DB Replicate to Subscriber Catalog Catalog1 Catalog2

22. What makes a health model? A finite state machine in software E.g. MOM 2005, then v3 State transitions defined by rules Reflects systems conditions Tasks respond to state changes Tasks can trigger state change

23. Why use a health model? Easy to extend Define custom state transition rules No need to reinvent the basic mechanisms Capture operational knowledge In the model In task associated to it

24. How to build a health model Top-down For service views Quasi-boolean logic for state transition: R = critical, Y = degraded, G = OK ShopPAD R**R R*R* RR** Y**Y Y*YG YYGG GGGG

25. How to build a health model Bottom-up For component views Require: Detectors: E.g. events in event log Verifiers: E.g. scripts to test for condition Diagnosers: Functions in rule base D(event1, 2,..)->root cause Resolvers: tasks to be executed after diagnosis

26. Example: Printer component

27. Recursive health models Used to build composite models

28. Modeling for optimization Capacity Planning Can we handle the increased load expected in 6 months? Bottleneck Analysis Which component should we upgrade next? Hardware Configuration Should we replace two-CPU servers with four-CPU servers? Architectural Assessment How do two alternative system architectures scale? User Scenarios What happens if the typical user behavior changes? Software Upgrades How will software changes affect system performance?

29. Why not MIPS? MIPS = relative performance indicators Highly centralized, strictly controlled infrastructure Most architectures are distributed & heterogeneous Could build RPIs based on typical workloads (Fujitsu, EDS…) What is typical?

30. Ways to build a perf. model ProductDesignPost-Production CA Unicenter Trending IBM Tivoli Trending HP OpenView Trending BMC Analytical Modeling Hyperformix IPS Tx. Simulation

31. Event-Based Model (Indy) Generate Workload Schedule Actions Process Events Model Resources Client Search request IIS Server Creates page IIS Server Request to SQL SQL Server Select statement SQL Server Return result Client Receives page Choose SQL server DB002 Choose disk for I/O ops StaticDynamic Static or Dynamic now time Thread Choose CPU on DB002 CPU queue shared among threads x N TxTx Software contention latency (server software, operation, load) – e.g. thread pools, locks Hardware utilization (hardware configuration, operation counts) – e.g. 193 Mcycles on a 3.0GHz P4 Other overheads (operating system, other workloads, background operations) Transaction latency Transaction analysis Workload mix Clusters Load balancing Networks Architecture Queuing Resource sharing Device utilization Hardware devices Software costs and contention OS overheads Background workloads Virtual PC Single Datacenter

32. topology.xml Indy Architecture Workload Generator Hardware Models System Configuration Engine Workload Engine Evaluation Engine Meta Directory System Event List Hierarchy Event Lists Events mdir.xml Kernel data repositories engines user defined

33. Traditional Process Modeling Approach Use performance counters to characterize workload Advantages: Relatively easy to construct and configure models Good for basic hardware capacity planning No scalability issues (only a single server per tier is considered) Disadvantages: Cannot model individual transactions (only a single transaction mix) Cannot model latencies (only resource utilization) Very limited network modeling Many assumptions such as perfect balancing of servers in a cluster

34. Pros and cons of Indy Pros: Dynamic: model populated with trace of real system or its model Can consume SDM, as populated by system Modular & extensible Cons: Difficult to represent: SDM is mainly static Computationally intensive (analytical shortcuts used)

35. ..and now the marketing message…

36. DSI Vision: Self-managing Systems Self-* systems Self-configuring & self-adapting Self-optimizing Self-deploying & self-cleaning Self-protectingSelf-monitoringSelf-diagnosingSelf-healing Prevention better than cure A self-* system needs knowledge of self & its environment, it is self-aware Self-* is the epitome of model- based management Pervasive model Every app delivered with a model Model in every Windows system Desired state DeveloperIT Admin Model CMDB Central Manager Remote Manager Local Model Managed System Actual state HAL9000!

37. Where did I hear this before? IBMs Autonomic Computing Autonomic Run-time System Host B AIK Repository Event Server Host A MAS A CS2CS1 Application Management Editor MAS: Mobile Agent System CS: Computer Server Component AMS Component Repository Resource Repository Application Management Repository Application State Repository Users Application Task Agent Policy Engine Self Protecting Self Optimizing Self Healing AME Parser Interface Resource Monitor Application Delegated Manager (ADM) Repository Interface Self Deploying MAS A Component Task Agent Interface Resource Monitor AIK: Application Information Knowledgebase AMS: Autonomic Middleware Service

38. The Questions Is DCML better suited to management than SDM? Is IBM far ahead of the rest of us with autonomic computing?

39. References The Dynamic Systems Initiative & SDM http://www.microsoft.com/dsi DCML http://www.dcml.org Performance models http://research.microsoft.com/sysperf/ Autonomic Computing http://www.redbooks.ibm.com/abstracts/sg246665.ht ml?Open http://www.redbooks.ibm.com/abstracts/sg246665.ht ml?Open http://www.redbooks.ibm.com/abstracts/sg246635.ht ml?Open http://www.redbooks.ibm.com/abstracts/sg246635.ht ml?Open

40. Next steps Complete your evaluation form Review todays slides www.microsoft.com/uk/msdn/events/postevents.aspx Sign up for the Newsletter www.microsoft.com/uk/msdn/architecture/newsletter.aspx www.microsoft.com/uk/msdn/architecture/newsletter.aspx Subscribe to the free Architecture Journal www.microsoft.com/architecture www.microsoft.com/architecture Register for the Solution Architect Forum, 9 December (via UK Architecture Centre) Additional resources: UK Architecture Centre www.microsoft.com/uk/msdn/architecture www.microsoft.com/uk/msdn/architecture US Architecture Centre www.microsoft.com/architecture www.microsoft.com/architecture

41. © 2005 Microsoft Limited. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.