Book Image

Managing Windows Servers with Chef

By : John Ewart
Book Image

Managing Windows Servers with Chef

By: John Ewart

Overview of this book

<p>This book begins with an introduction to the functionality and benefits of using Chef to manage Windows systems. From there, you are shown an overview of the Chef architecture and how to prepare a Windows host so that it can be managed by Chef, followed by an example of writing code to install a popular .NET application with Chef.<br /><br />This book looks at how Windows system administrators can effectively leverage Chef as an automated system management tool to simplify their lives through managed infrastructure. Included are practical examples that will help you to understand how to take advantage of Chef when managing your infrastructure.<br /><br />By the end of the book, you will be able to deploy software, provision hosts (including cloud servers), develop and test recipes for multiple platforms, and manage Windows hosts using the powerful tools that Chef provides.</p>
Table of Contents (13 chapters)

ZIP files


There is not a consistent way to natively manage packing or unpacking of ZIP files on all Windows platforms. To work around this, the windows_zipfile resource provides a pure Ruby implementation for manipulating ZIP files on the Windows platform.

The following table lists the actions and parameters available for the windows_zipfile resource:

windows_zipfile

Action

Description

unzip

This decompresses a specified ZIP file at the source into the destination.

zip

This creates a ZIP file at the destination from the source.

Parameter

Description

path

This is the resource name attribute specifying the path—unzipping this designates where the unzipped files go, while zipping the path specifies where the ZIP file is to be created.

source

This indicates the ZIP file location to uncompress when unzipping, or the directory containing files to be compressed when zipping.

checksum

This is the optional checksum that verifies whether the ZIP file is the expected...