This document provides information about using configuration management tools Puppet and Chef on Microsoft Azure. It discusses the Puppet agent process, how Puppet modules are used to compile and apply configurations. It provides timelines of Chef releases and integrations with Windows. It describes why Chef is useful on Azure, the architecture for using Chef on Azure, and examples of common Chef resources for Windows configuration including registry_key and powershell_script. Links are provided to learn more about Puppet, Chef community and tools for using them on Azure.

6. OPSDEV

7. https://puppetlabs.com/

9. Configuration Alerting
Monitor

11. Virtual Machine
management

12. Virtual Machine
management
http://aka.ms/devops_oss_ms

13. 1. The Puppet agent process collects
information about the host it is
running on, which it passes to the
server.
2. The parser uses that system
information and Puppet modules
on local disk to compile a
configuration for that particular
host and returns it to the agent.
3. The agent applies that
configuration locally, thus affecting
the local state of the host, and files
the resulting report with the server.

14. OPERATERELEASE
SQL DBPuppet Master VM
cspkg

15. Chef and Windows Timeline
• May 2011 – Knife plugin for Windows announced
• Oct 2011 – PowerShell, IIS, SQL Server, and Windows cookbooks
• Dec 2011 – Chef Client Installer MSI for Microsoft Windows
• Feb 2012 – Integration of the registry_key resource into core Chef from the
Windows cookbook
• Aug 2013 – Chef 11.6.0 release. PowerShell and Batch scripting integrated into
core Chef. Chef Client released as Windows service
• Feb 2014 – knife Azure release 1.2.2

16. Why Chef on Azure
• Chef Community - community.opscode.com
– +25,000 registered users
– 1,300 individual contributors
– 200 corporate contributors
– 900 cookbooks
• Support for on-Premise Windows and Windows Azure in
the Cloud

17. Chef on Azure - Architecture
• Github – knife-azure
• Chef Server - .pem files and
Cookbooks
• Windows Azure – endorsed
Linux packages
• New VM – loads
workstation
• New workstation – loads
client and recipes

18. Overview of Chef Resources on
Windows

19. Same as UNIX/Linux
• file, remote_file, cookbook_file, template
• directory, remote_directory
• user, group
• mount (can take CIFS paths)
• env
• service
• execute
• ruby_block
• many others...

20. Unique to Windows
• registry_key (new in Chef 11.0.0)
• powershell_script (new in Chef 11.6.0)
• batch (new in Chef 11.6.0)
• Automatic architecture handling (:i386 vs. :x86_64)
• Automatic Windows filesystem redirector handling (Wow64)
• Long-term roadmap: move more resources to core and out of ‘windows’
cookbook

21. Windows-Only Cookbooks
• By Chef:
– 7-zip
– iis
– powershell
– sql_server
– webpi
– windows
– wix

22. Windows Community Cookbooks
• ms_dotnet2 / 4 / 45
• windows_ad (by TAMU)
• msoffice
• azure

23. # Set system’s proxy settings to be the same as used for Chef
proxy = URI.parse(Chef::Config[:http_proxy])
registry_key 'HKCUSoftwareMicrosoftWindowsCurrentVersionInternet Settings'
do
values [{:name => 'ProxyEnable', :type => :reg_dword, :data => 1},
{:name => 'ProxyServer', :data => "#{proxy.host}:#{proxy.port}"},
{:name => 'ProxyOverride', :type => :reg_string, :data => '<local>'}]
action :create
end
registry_key example

24. powershell_script "rename hostname" do
code <<-EOH
$computer_name = Get-Content env:computername
$new_name = 'test-hostname'
$sysInfo = Get-WmiObject -Class Win32_ComputerSystem
$sysInfo.Rename($new_name)
EOH
end
powershell_script example

25. github.com/opscode/knife-azure

26. http://msopentech.com/blog/project-categories/devops/

29. http://aka.ms/devops_oss_ms
Microsoft Virtual Academyhttp://azure.Microsoft.com
Puppet and Chef on Azure