Borisov kirill maudo_cdod_k_ungurskii_raion_darovaniy_prikam_y (1)
Dynamic Systems Initiative (DSI) Model- and Policy-Based Systems Management Kirill Tatarinov...
13
Dynamic Systems Initiative (DSI) Model- and Policy-Based Systems Management Kirill Tatarinov [email protected] Corporate Vice President Server and Tools Business
-
Upload
destiny-russo -
Category
Documents
-
view
217 -
download
0
Transcript of Dynamic Systems Initiative (DSI) Model- and Policy-Based Systems Management Kirill Tatarinov...
Dynamic Systems Initiative (DSI)
Model- and Policy-BasedSystems Management
Kirill [email protected] Corporate Vice PresidentServer and Tools Business
2
Design for Operations
Manageability must bearchitected into the system
Just like scalability Just like security
3
Knowledge-Based Management
Knowledge is the key to management;models are rigorous definitions of knowledge
“Ought-ness” is sent down – models, constraints, policy, prescriptive guidance, SLAs, patches
“Is-ness” is sent up – inventory, metrics, events, alerts, compliance, service level, results
Management consists ofdetecting and resolving discrepancies between ought-ness and is-ness
Developer IT Admin
Model
CMDB
CentralManager
RemoteManager
LocalModel
ManagedSystem
“Ought-ness” “I
s-ne
ss”
4
Self-ManagingDynamic Systems
Scale, complexity, agility, mobile systemsrequire self-managing systems
Self-deploying Self-configuring Self-adapting Self-optimizing Self-protecting Self-monitoring Self-diagnosing Self-healing
Cure
Prevention
5
Developer IT Admin
Model
CMDB
CentralManager
RemoteManager
LocalModel
ManagedSystem
“Ought-ness” “I
s-ne
ss”
Self-Managing Systems In Practice
We use asynchronous replicationwith policy-based latency management
With these opposing asynchronous flows, where do we place the resolution of discrepancies? Scalability Agility Autonomy Staleness (latency * volatility) Scope of control for distributed systems
Management should be pushed down as far as possible, but no further
6
Developer IT Admin
Model
CMDB
CentralManager
RemoteManager
LocalModel
ManagedSystem
“Ought-ness” “I
s-ne
ss”
Self-Managing Systems are Model-Based
If management requires knowledge,self-management requires self-knowledge
A self-managing system is self-aware Self-management is the epitome of
model-based management
Pervasive model: Every application is delivered with a model Model in every Windows system
“Ought-ness” “I
s-ne
ss”
Developer IT Admin
Model
CMDB
CentralManager
RemoteManager
LocalModel
ManagedSystem
7
Model-Based Management
System Definition Model An XML-based modeling language
that is used to capture a formal model of a system
Model contains “all informationpertinent to deployment and operations” System topology Developer constraints IT policy Installation directives Health model Monitoring rules Service Level Agreements Reports
Extensible models
8
Dynamic Systems Initiative – Implemented
Visual Studio 2005 authoring and validation
System Center Capacity Planner 2006capacity planning
System Center Operations Manager 2007service monitoring
System Center Configuration Manager 2007
desired configuration management
Windows Server Codename “Longhorn”role and workload configuration
System Center VM ManagerVM and workload management
System Center “Service Desk”MOF/ITIL-based workflow and change manager
9
SC VM Manager andWorkload Placement Scenarios Type of Placement
Server consolidationLegacy OS rehosting
Staticplace now, keep until further notice
Service availabilityScheduled maintenanceTest
Scheduledstart and end at certain time
On-demand scale-outDisaster recovery
Event drivenstart or end on demand
Batch job scheduling Jobscheduled start, end when done;
Agile ITService level controlHardware maintenance
Move or adjustad hoc, scheduled, event
Model repository Workloads with
requirements Compute resources with
capabilities Data and storage
resources
10
Model-Based Constraint Validation
E.g. hierarchical hardware configurations: A rack contains several Chassis, which contain several Blades, which contain several Motherboards, which contain several Processors, which contain several Cores
How much of this can we consider one computer? From an SMP perspective? From a management perspective? From a licensing perspective?
All these rules will change over the next decade: new capabilities in the fabric, new licensing models…
The rules must be explicitly stated in the model, none can be hardcoded
11
Models and Policy
Models describe the system Policy describes how the system is managed Policy is targeted to models
Services, not just groups Scenarios:
New policy applied and adapted to service Service changed, policy adjusts Service re-deployed, policy applies, adapts
12
A Management Revolution
DSI is about changing the industry’s mindset
A very ambitious, long-range initiative
Lead with Microsoft adoption
© 2002 Microsoft Corporation. All rights reserved.© 2002 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.in this summary.
