ProPuppet2nd-第四章-扩展资源-CSDN文库

需积分: 6 30 浏览量 2014-10-23 15:47:50 上传评论收藏 5.08MB PDF 举报

资源详情

资源评论

资源推荐

CHAPTER

4

Scaling

Puppet

You've

seen

that

the

Puppet

agent

and

master

require

very

little

work

to

gel

up

and

running

on

a

handful

of

nudes

using

the

default

configuration.

It

is,

however,

a

significantly

more

involved

undertaking

to

scale

Puppet

to

handle

hundreds

of

nodes.

Yet

many

installations

are

successfully

using

Puppet

to

manage

hundreds,

thousands,

and

tens

of

thousands

of

nudes.

In

this

chapter,

we

cover

a

number

of

proven

strategies

that

are

employed

to

scale

Puppet.

•

You'll

see

how

to

enable

a

single

Puppet

master

system

to

handle

hundreds

[if

nodes

using

the

Apache

web

server.

*

We

also

demonstrate

how

to

configure

more

than

one

Puppet

master

system

to

handle

thousands

of

nodes

using

a

load

balancer.

*

Throughout,

we

make

a

number

of

recommendations

to

help

you

avoid

the

common

pitfalls

related

to

performance

and

scalahility,

*

We

will

demonstrate

a

masterless

Puppet

configuration,

In

which

each

node

has

a

full

checkout

of

the

puppet

code

and

runs

puppet

apply

locally,

usually

via

cron.

Thi$

approach

enables

infinite

scalability

and

redundancy;

the

nodes

no

longer

share

any

single

bottleneck.

*

Finally,

you’ll

learn

how

to

measure

the

performance

of

the

Puppet

master

infrastructure

in

order

to

determine

when

it's

time

to

add

more

capacity.

We

also

provide

two

small

scripts

to

avoid

the

"thundering-

herd

effect*'

and

to

measure

catalog

compilation

Lime.

together

with

the

transport

mechanism

between

the

agent

and

master,

we'll

explore

the

two

main

options

of

handling

SSL

certificates

in

a

scalable

Puppet

deployment:

*

Using

a

single

Certificate

Authority

(CA)

Puppet

master

*

Distributing

the

same

CA

across

multiple

Puppet

masters

Running

the

Puppet

Master

with

Apache

and

Passenger

The

first

scaling

example

wTere

going

to

demonstrate

is

the

combination

of

the

Apache

web

server

with

a

module

called

Phusion

Passenger,

which

is

also

known

as

mod_rails,

mod_pa55enger,

or

just

Passenger.

Passenger

is

an

Apache

module

that

allows

the

embedding

of

Ruby

applications,

much

as

mod

php

or

mod_perl

allow

the

embedding

of

THr

and

Perl

applications.

The

Passenger

module

is

not

a

standard

module

that

ships

with

Apache

web

server

and,

as

a

result,

must

be

installed

separately.

Passenger

Is

available

as

a

RubyGem

package,

or

it

may

be

downloaded

and

installed

from

http:

//www.modrails.

com/.

In

some

distributions,

Passenger

maybe

available

from

packages.

We

will

discuss

installing

Passenger

In

depth.

For

networks

of

one

10

two

thousand

Puppet-

managed

nodes,

a

single

Puppet

master

system

running

inside

Apache

with

Passenger

is

often

sufficient

Later

in

this

chapter,

we

will

examine

how

to

run

multiple

Puppet

master

systems

to

provide

high

availability

or

support

for

an

even

larger

number

of

Puppet-

managed

nodes.

These

more

complex

configurations

will

all

build

on

the

baste

Apache

and

Passenger

configuration

we

introduce

tO

yOU

here.

We

will

also

build

upon

the

Puppet

master

configuration

w

e

created

in

Chapter

2

and

the

environment

structure

we

introduced

in

Chapter

3.

First,

you

need

to

install

Apache

and

Passenger,

and

then

configure

Apache

to

handle

the

SSL

authentication

and

verification

of

the

Puppet

agent,

and

finally

connect

Apache

to

the

Tuppet

master

and

ensure

that

everything

is

working

as

expected.

As

we

scale

Puppet

up,

it

is

important

to

draw*

the

distinction

between

the

idea

of

a

front-end

HTTP

request

handler

and

a

back-end

Puppet

master

worker

process.

The

front-

end

request

handler

is

responsible

for

accepting

the

TCP

connection

from

the

Puppet

agent,

selecting

an

appropriate

hack-

end

worker,

muting

the

request

to

the

worker,

accepting

the

response,

and

finally

serving

it

back

to

the

Puppet

agent.

This

distinction

between

a

front-end

request

handler

and

a

back-end

worker

process

is

a

common

concept

when

scaling

web

services.

Installing

Apache

and

Passenger

To

get

started,

you

need

to

install

Apache

and

Passenger.

Both

are

relatively

simple

and

easy

to

set

up.

Installing

Apache

and

Passenger

on

Debian/Ubuntu

LTS

剩余69页未读，继续阅读

评论0

内容反馈

duohejia

粉丝: 3
资源: 4

最新资源

资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！点击此处反馈

feedback-tip