Open source Windows Management Infrastructure server implemented by Microsoft. Portable Includes...
-
Upload
marjorie-cummings -
Category
Documents
-
view
232 -
download
0
Transcript of Open source Windows Management Infrastructure server implemented by Microsoft. Portable Includes...
Compute
NetworkStorage
Consumerization
of IT
New social and app patterns
Data explosion
Cloud computing
Transformational trends
Customer needs and opportunities
Application owners pressing us for agility and availability, going directly to public clouds.
Protect my existing investments through easy systems integration.
Enable me to build and operate infrastructure efficiently across my customer base.
Provide differentiated services to customers.
IT budgets flat or shrinking even as business expectations increase.
We spent most of our time keeping the lights on, not staffed to take on impactful projects.
Need a solution that works across my diverse datacenter environments.
Multiserver management
Ecosystem and extensibility
Simplify your routine tasks
Standards-based management
Deployment options
Scenario summary
Standard models
Standard APIs
Standard protocols
Windows Management FrameworkSimplifies the
management of a diverse ecosystem
Standards-based management
Managing a diverse ecosystem
Methods to manage each device
Number of devices to manage
“The NxM Problem”
STANDARDS-BASED
MANAGEMENT
IT Pro Tool Developer Solution Provider
Storage Operating system DevicesDisk Managed
objects
IT Pro
Windows Management Framework
Tool Developer Solution Provider
DevicesOperating systemStorageDisk Managed
objects
Maximize the value of using the Windows Management Framework
STANDARDS-BASED
MANAGEMENT
Windows Management Framework
Standard models, protocols, and APIsMaximize the value of using the Windows Management Framework
STANDARDS-BASED
MANAGEMENT
Standard protocols: WS-Management, REST, HTTP, PSRP
Standard APIs: MI Client, Windows PowerShell, Open Data Protocol (OData)
Standard models: Common Information Model (CIM) schema, Storage Management Initiative Specification (SMI-S)
Windows Management Framework
IT Pro Tool Developer Solution Provider
DevicesOperating systemStorageDisk Managed
objects
• New WMI provider API (MI) with extended Windows PowerShell semantics.
• Open Management Infrastructure (OMI) for Linux and UNIX with the same MI provider API.
• Full implementation of WS-Man on Windows and Linux/UNIX.
• New MI client with integrated Windows PowerShell layer.
Open Managment Infrastructure
WS-Management
WS-Manprotocol handler
Windows PowerShell
MI client API
Microsoft .NET MI API
Native MI API
WS-Manprotocol handler
Open Management Infrastructure
WS-Manprotocol handler
Any device
Linux/UNIX
MI provider
WS-Manprotocol handler
Windows Management Instrumentation
Windows
MI provider
Classicprovider
STANDARDS-BASED
MANAGEMENT
Open source Windows Management Infrastructure server implemented by Microsoft.
Portable
Includes Windows Server Management protocol stack.Interacts with MI client and Windows PowerShell out of the box.
Small footprint
Scalable
Uses the same MI provider interface as Windows Management Infrastructure.Can share provider development tools with Windows Management Infrastructure.
One Management InfrastructureSTANDARDS-
BASED MANAGEMENT
Open Management Infrastructure vs. OpenPegasus
OpenPegasusOpen
Management Infrastructure
Factor
Requests per second(binary protocol) 260 20,000 76x
Image object size 8,000 KB 150 KB 53x
Trivial provider size 30 KB 3 KB 10x
Virtual memory size 54 MB 1.5 MB 36x
Resident set size 8,500 KB 500 KB 17x
STANDARDS-BASED
MANAGEMENT
Developing PowerShell cmdlets in native code, as CIM providers.
SMI-S service in the box for easier storage discovery.
OMI in the box for configuring network switch.
Instrumenting services and devices for Windows—through Windows Management Infrastructure (WMI) providers.
Standards-based way to access and manage storage.
Standards-based way to access and manage network switch.
Approach for Windows Server 2012 R2
Use SMI-S to manage external storage arrays:
Simplify and lower the cost of:
Use OMI to manage network switches:
STANDARDS-BASED
MANAGEMENT
Switch managementStandards based automation
PowerShell scripts for common switch management tasks.
SCVMM imports and validates port configuration from switch.
Logo Program: Server Certification for switch endors implementing CIM Schema.
Define mechanisms to auto generate PowerShell cmdlets for vendor extensions.
Easily deploy and operate network
switches in standards approach
Windows(PowerShel
l)
SCVMM
Non-Windows
WS-Man
Switch x
CIM
Switch y
CIM
Switch z
CIM
Windows Server 2012 ||
Global Settings• Computer System• Physical Computer System View• Global Ethernet Switch Settings• Features• …
Interfaces• Switch Service• Ethernet Port• VLANs• IP Protocol EndPoint• Link Aggregation• Switch Virtual Interface• ….
User Management• Role Based Authorization Service• Account Management Service• Accounts• Roles• Privileges• …..
Network Policy• ACL• Conditions• Actions• Rules• ….
Switch SchemaHigh level overview
Windows Server 2012 ||
$tors = "192.168.0.1", "192.168.0.2", "192.168.0.3" $so = New-CimSessionOption -UseSsl $s = New-CimSession -CN $tors -port 7779 -Auth Basic -Credential $cred -Sessionoption $so
#enable SSH Feature$ssh = Get-CimInstance -CimSession $s MSFT_Feature | ? FeatureName -eq 2 Set-CimInstance -CimSession $s $ssh -Property @{ IsEnabled = $true }
#Enable all ports$ports = Get-CimInstance -CimSession $s CIM_EthernetPort$ports | Invoke-CimMethod -Method RequestStateChange -Parameter @{ RequestedState = 2}
#Set a Port to trunk mode and specify list of VLANs $lanep = Get-CimAssociatedInstance $ports[5] -ResultClassName Cim_LanEndpoint$vlanep = Get-CimAssociatedInstance $lanep -ResultClassName Cim_VLanEndpoint$vlanepsd = Get-CimAssociatedInstance $vlanep -ResultClassName Cim_VLanEndpointSettingData #Set Port Mode to Trunk Set-CimInstance $vlanep -Property @{DesiredEndpointMode = 5} #Set list of trunk VLANs Set-CimInstance $vlanepsd -Property @{TrunkVlanList= “2,3,4”}
Sample PowerShell script
• Support multiple industry standards, schemas and protocols.
• PowerShell Cmdlets and WMI provider shipping in box to provide a common abstraction layer.
• Test scripts for validating hardware implementation.
Manage hardware in standards approach
Out-of-band hardware managementStandards based automation
Windows(PowerShell
)
PCSV
SMASH (WS-Man)
IPMI (RMCP+)
PCSV (WS-Man)
BMC x
SMASH
BMC y
IPMI
BMC z
PCSV
Windows Server 2012 ||
#### Currently customers have no easy way to automate hardware management . #### Different vendors support different protocols /mechanisms - and PowerShell coverage is low#### In Windows Server v.Next - customers will be able to consistently manage hardware from different vendors#### Key point to note here # - Simplicity and elegance# - Rich PowerShell experience
# Get data from the devices - In this demo we are managing three different BMCs $a = Get-PCSVDevice 10.20.30.111 -Credential admin -Auth Default -Protocol IPMI$b = Get-PCSVDevice 10.20.30.112 -Credential admin -Auth Digest -Protocol SMASH$c = Get-PCSVDevice 10.20.30.113 -Credential admin -Auth Digest -Protocol PCSV$hosts = $a,$b,$c
$hosts | Select Manufacturer, Model, FirmwareVersion # Show Manufacturer, Model and Firmware Version$hosts | Select PowerState # Show Current Power State$hosts | Set-PcsvDevice -NextBoot "Network“ # Set to PXE Boot from network$hosts | Restart-PcsvDevice # Restart the machines. This will prompt the user to # confirm because this is a "high impact action"$hosts | Restart-PcsvDevice –Force # Use force to suppress prompt and restart machine
Sample PowerShell script
Windows Server 2012 ||
Sample PowerShell script
$a = Get-PcsvDevice -TargetComputerName $ip -ManagementProtocol IPMI -Credential $cred # Switch ON the machine$a | Start-PcsvDevice $a | Stop-PcsvDevice
# Common automation scenario - set the machine to boot from network and restart the machine.# Let’s see how to do it using PCSV cmdlets in a pipeline# Step 1 - Set the machine to boot from network , but just for the next boot# Step 2 - Reboot the machine$bmc = Get-PcsvDevice -TargetComputerName $ip -ManagementProtocol IPMI -Credential $cred $bmc | Set-PcsvDeviceBootConfiguration -OneTimeBootSource "CIM:Network:1" -PassThru | Restart-PcsvDevice
PS C:\> $ip = "10.10.1.10"PS C:\> Get-PcsvDevice -TargetComputerName $ip -ManagementProtocol IPMI -Credential $credTargetComputerName Manufacturer Model SerialNumber EnabledState------------------ ------------ ----- ------------ ------------10.10.1.10 DELL PowerEdge R720 CN7123456700EH Disabled