Enables self-provisioning (bootstrap to desired state) • Enables self-remediation (converges to desired state) • Has a resource/provider model • 12 resources out of the box
generating a document (MOF) consumed by PowerShell module or WMI (Windows Management Infrastructure) resource • Machines may converge manually by running Start-DscConfiguration cmdlet • Systems under management run Local Configuration Manager • Support push and pull model • Systems remain convergent by running Test- DscConfiguration via CIM (Common Information Model) session
party tools to automate Windows systems • Extend DSC concept to all devices in the data centre via open standards (Linux, Switches) • Make DSC a standard criteria for all Microsoft products
February 2012 August 2013 July 2014 ~ September 2014 KNIFE WINDOWS! PLUGIN POWERSHELL! IIS! SQL SERVER! WINDOWS! COOKBOOKS CHEF CLIENT! MSI REGISTRY_KEY! IN CORE CHEF POWERSHELL ! & ! BATCH SCRIPT IN CORE CHEF CHEF-CLIENT WINDOWS! SERVICE DSC PREVIEW! OPEN SOURCED DSC_SCRIPT! RESOURCE! IN CORE CHEF DESIRED STATE! SUPPORT! ANNOUNCED! (2014 DELIVERY)
to the name of the resource as a symbol, i.e. WindowsFeature in DSC becomes :windowsfeature. Case doesn’t matter. • For each property in the DSC resource for which you want to declare a desired value, use the syntax: property :property_name, value ! ! !
All product teams will support DSC and produce resources • Activity around OMI (Open Management Infrastructure) • Activitity around DAL (Datacentre Astraction Layer) • DSC on Linux • DSC for network switches • WMF 5.0 (OneGet, PowerShellGet, Network Switch cmdlets)
alone isn’t really sufficient • DSC provides an ecosystem and standard for automation and configuration • The Chef ecosystem adds testing, reporting/analytics • Chef + DSC = Win