自动化云端管理：《使用Chef与微软Azure》实战指南

需积分: 10 21 浏览量更新于2024-07-20 收藏 12.62MB PDF 举报

"《使用Chef与微软Azure》(Using Chef with Microsoft Azure, Apress, 2016) 是一本实战指南，专为在云计算环境中利用Chef开源工具进行基础设施配置管理和自动化提供深入指导。随着微软Azure云平台每周吸引超过10,000名新客户，并且其使用率持续增长，对自动化方法的需求变得空前迫切。本书旨在帮助读者理解和应用这两种技术的结合，以提升效率和可靠性。书中详细介绍了如何通过编写Chef '菜谱'（recipe），将基础设施作为代码（Infrastructure as Code）来描述，从而简化配置管理流程。读者将学习如何使用Chef工具在Microsoft Azure中自动部署和管理整个环境，包括虚拟机和其他资源。作者Stuart Preston以其专家视角，探讨了在Azure中多种资源部署策略，比如使用不同的工具和技术，如PowerShell、ARM模板等，以及它们各自的优缺点。每章都包含实践练习，这些练习展示了Chef和Azure自动化功能在Windows、Mac和Linux平台上的应用，让读者能够亲手体验并理解自动化过程。本书不仅提供了具体的实例，还涵盖了建立可靠的、可重复和健壮的资源配置管道的策略，这对于企业在Azure中实现持续集成和持续部署(CI/CD)至关重要。版权信息表明，这本书享有法律保护，所有权利归Stuart Preston所有。尽管如此，为了学术研究或个人计算机系统的特定用途，如短篇摘录或电子适应性使用，部分材料是可以使用的。《Using Chef with Microsoft Azure》是一本实用的资源，对于那些寻求在云计算时代有效管理Azure资源的IT专业人员来说，是一本不可或缺的参考书籍。"

Introduction

One of the challenges of working in technology today is the relentless pace of change. As practices evolve

and new tools are introduced, documentation either does not exist or becomes rapidly out of date, which is

part of the reason there were very few resources available to me when I started my journey of using Chef with

the Microsoft Azure platform. I struggled to find the information I needed in one place but instead gathered

nuggets of knowledge that were scattered far and wide, eventually learning the hard way how to accomplish

the results I wanted. This book aims to bring the most important points into one place - and be the book I

wish I had on my desk when I started out.

Automating your infrastructure in the cloud has many benefits. Clicking around in an online portal

certainly feels easy from a usability point of view but you may be missing out on some of the great

advantages of the cloud that can be realized when you adopt an Infrastructure-as-Code approach. Using

Chef, you can version your infrastructure configuration, introduce quality tooling into your infrastructure

pipeline, and integrate the provisioning of new environments into your continuous delivery process.

Leveraging the flexibility of the cloud to pay for only what you need can reduce infrastructure spend

considerably and maintaining your platform as code allows for testing that protects the system against

human error, reducing failures and unforeseen issues.

If you are new to Chef, Microsoft Azure, or both this book should give you an overview of the best

practices for managing your platform alongside some detailed examples that help to step you through the

process. I’ve tried to keep things simple, while ensuring real-world considerations are not omitted.

A small word of warning. Releases to both Chef and Microsoft Azure happen at an alarming pace

(thanks, Continuous Delivery!) and so I expect aspects of this book will soon become out of date, or

superseded by the new thinking. To ensure the book remains a useful resource as both Chef and Azure

evolve I will try and keep track of any significant changes via the book’s home page at

http://bit.ly/

chefazure

My aim for this book is to give you the raw materials and guidance required to get started using Chef

with the Microsoft Azure toolset - first of all, setting out the tools you can use individually and then in the

later chapters using continuous provisioning approaches. I look forward to hearing about the solutions you

create using the tools.

www.it-ebooks.info

S. Preston, Using Chef with Microsoft Azure, DOI 10.1007/978-1-4842-1476-3_1

CHAPTER 1

Configuration Management

using Chef

The automation of configuration management is not a particularly new practice in the world of

software delivery. However, scripted approaches of the past suffered from a lack of common standards,

documentation, and understanding. A team member would select a preferred scripting language, adopt

their own patterns, and implement it in their own unique way. This approach required an in-depth

knowledge of the dependencies for all the software to be installed and configured on a machine and often

made assumptions about the initial state of the machine before applying changes. Upgrades to software

were rarely considered, and because the knowledge was invested in a single person it was difficult to support

and maintain. Not everything would or could be automated, and so there would also generally be an amount

of manual tweaking required to achieve the desired state, so it wasn’t entirely automated and left scope for

human error.

Modern configuration management tools such as Chef aim to solve these problems by abstracting

away the actions to be taken on a target resource from their actual implementation. We utilize a common

domain-specific language (DSL) across all resources to describe the desired state of the system, and behind

the scenes Chef takes care of the rest.

Chef has enjoyed enormous success and adoption since its creation in 2008, with companies such as

Facebook and Microsoft using the product to manage their infrastructure. At the heart of this success is the

global community it has built. By open sourcing the core product and working hard on the cross-platform

story, Chef has enlisted thousands of potential contributors to help drive innovation and to support each

other with the challenges of automating infrastructure at scale. The culture and community permeate

through all aspects of the Chef offering and draws yet more contributions into the ecosystem, making it a

powerful force in the world of automation.

In this chapter we will discuss the principles and purpose of automated provisioning and configuration

management, walk through an overview of Chef, and go through the steps required to set up a Chef

workstation environment that can be used to automate configuration management in the cloud.

Electronic supplementary material The online version of this chapter (doi: 10.1007/978-1-4842-1476-3_1 )

contains supplementary material, which is available to authorized users.

www.it-ebooks.info

CHAPTER 1 ■ CONFIGURATION MANAGEMENT USING CHEF

The Purpose and Principles of Automated Provisioning and

Configuration Management

It would be remiss of me not to mention the DevOps movement early on in this book. While there are many

definitions, I tend to go along with the definition of DevOps being a cultural and technical movement that

focuses on building organizations that are able to operate with stability at high velocity. The term itself

targets the silos that these groups have traditionally found themselves in.

Automation is one of the pillars of the DevOps movement because it can provide quality assurance,

consistency, and repeatability across the realms of both development and operations. This is especially

true in the case of infrastructure automation where manually building individual servers, configuring their

base applications, applying their updates, and patching them was not only a time-consuming task but

also complex and prone to human error. Minor deviations would occur between resources that should be

configured identically, causing unforeseen issues and brittle setups that were hard to reproduce. The term

snowflake server is often used to reflect the uniqueness of those systems.

Many large enterprises have met with challenges scaling their on-premises infrastructure, teams,

and processes to meet the demands of the high-velocity, agile development teams they now service.

Organizational structures would introduce multiple hand-offs into the process with a set of project

requirements being agreed upon up front (generally by a designated architect before the development team

is even assembled). The environments would be designed and scheduled into the pipeline of work across

a large team of disparate skillsets to complete their relevant tasks and then hand over to the development

team on the scheduled date, sometimes weeks and months after the initial requirements were agreed upon.

In the initial days and weeks of using the environment the development team, struggling to run their

application on the delivered environment, would identify new requirements or issues in configuration. After

an indisputable root cause had been established the correcting actions would be scheduled again through

the same waterfall process, elongating the feedback loop, preventing QA activities in the environments, and

often delaying the project launch.

A more incremental, automated approach to provisioning can drastically reduce the feedback loop

on configuration changes and allow development teams to operate at velocity without environment

impediments. By describing your infrastructure platform as code it can be updated frequently as the

requirements of the application evolve over time and because Chef recipes are idempotent , once the

desired state is achieved, future executions of the recipe will result in a no-op (i.e., no changes will be made).

Automation also removes the opportunity for human error to introduce unwanted deviations between

environments and “configuration drift” over time into an unknown state.

Many organizations are moving away from on-premises infrastructure into a cloud environment;

and as they do so, the opportunities to leverage Infrastructure as Code practices greatly increase. Using

a cross-platform provisioning and configuration management tool such as Chef you can now provision

an application architecture consisting of IaaS, PaaS, and SaaS services across a global distribution of data

centers using a common language and framework. Although many examples in this book will focus on IaaS

scenarios, I encourage you not to overlook the many PaaS and SaaS options available in Azure, some of

which may prevent you from reinventing the wheel.

Figure

1-1 shows the separation of Provisioning from Configuration Management from Release

Management. Often in the cloud sense, these terms are used interchangeably whereas I prefer to draw out

the separation of each area as a separate concern. This is because different tooling and artifacts are involved

for each layer of the architecture:

• Provisioning is concerned with the specification of the guest and operating system

on top of a host. The host could be a virtualization layer such as a hypervisor or

a cloud platform such as Microsoft Azure. The point is that in this layer we know

nothing about the application that is going to run on top of it.

www.it-ebooks.info

CHAPTER 1 ■ CONFIGURATION MANAGEMENT USING CHEF

• Configuration Management is concerned with the configuration of the Operating

System after it has been provisioned, as well as any applications and their

configuration that sit on top of that Operating System.

• Release Management is concerned with the releasing of an application payload on

top of the application that has been deployed.

One other huge advantage of using Infrastructure as Code practices in a cloud environment is the ability

to provide ephemeral environments in a fast, repeatable, and consistent way. With the right automation in

place you could potentially spin up a new environment for a day, or even for a few minutes, at a minimal

cost and with a negligible lead time. Compare this to the increased complexity and overhead you would

experience if trying to achieve the same in an on-premises, manual setup, and it becomes clear that the

cloud was made for automation.

Chef Architecture

Let’s quickly cover some of the core terminology of Chef as (hopefully) a refresher for you.

■ Note If this isn’t a refresher for you, I highly recommend you spend a couple of days going through the

excellent resources and hands-on labs available at http://learn.chef.io to familiarize yourself with the Chef

platform and terminology.

Chef is built around the concepts of converging toward desired state and modeling Infrastructure as

Code via resources that are building blocks. Simply put, a cookbook is made up from a collection of recipes ,

which in turn are an ordered set of instructions you would like to perform on a node (a node being defined

as any server or device capable of running a Chef client). Recipes themselves are written in the Chef domain-

specific language (DSL) built on top of the Ruby language. Cookbooks can also contain Resources, which do

Figure 1-1. Provisioning vs. Configuration Management vs. Release Management

www.it-ebooks.info

剩余238页未读，继续阅读

vanridin

粉丝: 108
资源: 1187

自动化云端管理：《使用Chef与微软Azure》实战指南

microsoft_azure：Chef的Windows Azure食谱

微软Azure Stack产品介绍.pdf

a-taste-of-chef-with-azure:使用 Azure 配置 Chef

源码编译安装chef-solo

DevOps - 配置管理 - Chef

./tools/chef_deploy_quick.sh chef_json_common.json | tee -a deploy.out，这条命令什么意思

创建windows server服务器50台，使用什么技术可以让该需求快速实现

36岁的网络工程师怎么转行云计算运维

java部署有几种方式

这条命令什么意思./tools/chef_deploy_quick.sh | tee -a deploy.out

最新资源