Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 3 ■ MONITORING AND UPDATINGYou can also have configurations that differ for each machine. Or you can set up base configurationsand then either inherit from or include them in the node configuration.You may have a basic server config that differs from your desktop config, and both may inherit froma base or default config. This could look like this:class base {# Various basic thingsinclude autofsinclude croninclude puppetinclude ssh# and so on}class desktop inherits base {# Everything in the base class will automatically be included here# Then you can alsoinclude latexinclude gnome# and so on}class server inherits base {# Again, everything from the base class will automatically be included# Then some other server-only thingsinclude nfs# and so on}Classes can be specified either in a single file or in a file per class. So here, you could have all theprevious setup in a single file classes.pp, or you could separate it into base.pp, desktop.pp, andserver.pp (see the suggested directory structure in Figure 3-3). I recommend the latter to makeconfiguration management easier, because it means that you can easily find the node or applicationwhose configuration you want to edit.3-15. Defining Your Puppet Nodes in LDAPInstead of defining your nodes in site.pp, you can keep them in LDAP as the puppetclass attribute. Thisenables you to automatically set up the type of Puppet node that a machine should be set up as whenyou first add it to the directory. You can have as many of these puppetclass attributes per host as youlike—for example, my web server has webserver, ftpserver, and server as puppetclass attributes.site.pp therefore has only import statements, not node definitions. Your class definitions are set in/etc/puppet/manifests/classes, as described in the previous recipe, and you import them in site.pp(again, as in the previous recipe).86Download at WoweBook.Com
CHAPTER 3 ■ MONITORING AND UPDATING■ Note Find more information about this at http://reductivelabs.com/trac/puppet/wiki/LDAPNodes or inDeploying OpenLDAP by Tom Jackiewicz (Apress, 2004).A reasonable setup to start with is to have the base.pp, desktop.pp, and server.pp classes, asmentioned in the previous recipe (with server.pp and desktop.pp inheriting from base.pp). You can thenadd further puppetclass attributes (for example, webserver and nfsserver) as required for your setup.Install libldap-ruby1.8 on the Puppet server (Debian package).Add the Puppet schema to your LDAP schema directory (/etc/ldap/schema/). See recipe 2-12 for adiscussion of LDAP schemas and object identifiers (OIDs). Or just put the following in as/etc/ldap/schema/puppet.schema:# These OIDs are all fake. No guarantees there won't be conflicts.# $Id$attributetype ( 1.1.3.10 NAME 'puppetclass'DESC 'Puppet Node Class'EQUALITY caseIgnoreIA5MatchSYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )attributetype ( 1.1.3.9 NAME 'parentnode'DESC 'Puppet Parent Node'EQUALITY caseIgnoreIA5MatchSYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )objectclass ( 1.1.1.2 NAME 'puppetClient' SUP top AUXILIARYDESC 'Puppet Client objectclass'MAY ( puppetclass $ parentnode ))Add a schema line to /etc/ldap/slapd.conf:include/etc/ldap/schema/puppet.schemaRestart slapd:/etc/init.d/slapd restartYour server.pp and desktop.pp classes will now correspond to a puppetclass attribute in the LDAPtables. To modify a host, you can use an LDIF file that looks like this (this one updates the server server1and the desktop desktop1):87Download at WoweBook.Com
Page 2:
Download at WoweBook.Com
Page 5 and 6:
Download at WoweBook.Comiii
Page 7 and 8:
Contents■About the Author .......
Page 9 and 10:
■ CONTENTS3-7. Writing a Nagios P
Page 11 and 12:
■ CONTENTS■Chapter 8: Using the
Page 13 and 14:
■ CONTENTSAbout the Author■Juli
Page 15 and 16:
■ CONTENTSAcknowledgmentsMany tha
Page 17 and 18:
■ CONTENTSIntroductionThis book i
Page 19 and 20:
■ INTRODUCTIONDownloading the Cod
Page 21 and 22:
C H A P T E R 1■ ■ ■Saving Yo
Page 23 and 24:
CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44:
CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 83 and 84: C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86: CHAPTER 3 ■ MONITORING AND UPDATI
Page 105: CHAPTER 3 ■ MONITORING AND UPDATI
Page 115 and 116: C H A P T E R 4■ ■ ■Taking Ba
Page 117 and 118: CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 139 and 140: C H A P T E R 5■ ■ ■Working w
Page 141 and 142: CHAPTER 5 ■ WORKING WITH FILESYST
Page 155 and 156: C H A P T E R 6■ ■ ■Securing
Page 157 and 158:
CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
C H A P T E R 7■ ■ ■Working w
Page 179 and 180:
CHAPTER 7 ■ WORKING WITH APACHEOn
Page 181 and 182:
CHAPTER 7 ■ WORKING WITH APACHEdi
Page 183 and 184:
CHAPTER 7 ■ WORKING WITH APACHE4.
Page 185 and 186:
CHAPTER 7 ■ WORKING WITH APACHE
Page 187 and 188:
CHAPTER 7 ■ WORKING WITH APACHEAl
Page 189 and 190:
CHAPTER 7 ■ WORKING WITH APACHE
Page 191 and 192:
C H A P T E R 8■ ■ ■Making Be
Page 193 and 194:
CHAPTER 8 ■ USING THE COMMAND LIN
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
C H A P T E R 9■ ■ ■Working w
Page 207 and 208:
CHAPTER 9 ■ WORKING WITH TEXT IN
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
C H A P T E R 10■ ■ ■Things G
Page 225 and 226:
CHAPTER 10 ■ THINGS GO IN, THINGS
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
C H A P T E R 11■ ■ ■Tracking
Page 235 and 236:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 237 and 238:
CHAPTER 11 ■ TRACKING DOWN BUGS01
Page 239 and 240:
CHAPTER 11 ■ TRACKING DOWN BUGS
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 247 and 248:
CHAPTER 11 ■ TRACKING DOWN BUGSAn
Page 249 and 250:
CHAPTER 11 ■ TRACKING DOWN BUGS#
Page 251 and 252:
C H A P T E R 12■ ■ ■Managing
Page 253 and 254:
CHAPTER 12 ■ MANAGING TIME AND PE
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
APPENDIX■ ■ ■Perl TipsSee rec
Page 269 and 270:
APPENDIX ■ PERL TIPS• Date::Par
Page 271 and 272:
APPENDIX ■ PERL TIPSPerl Syntax N
Page 273 and 274:
■ ■ ■Index■Symbols$CDPATH,
Page 275 and 276:
■ INDEXenscript option (printing)
Page 277 and 278:
■ INDEX■NNagiosadding hosts to,
Page 279 and 280:
■ INDEXsyslogcentralized logging
Page 281 and 282:
Download at WoweBook.Com
show all

Linux System Administration Recipes A Problem-Solution Approach

Create successful ePaper yourself

Delete template?

Save as template?