Changes between Version 7 and Version 8 of TracNav
- Timestamp:
- 12/11/08 16:29:50 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracNav
v7 v8 50 50 Package 51 51 A package for the given system (RPM. Deb, ebuild, etc) 52 ConfigFile52 !ConfigFile 53 53 A config file 54 54 Service … … 56 56 Directory 57 57 A directory that should be present 58 SymLink58 !SymLink 59 59 A symbolic link that should be present 60 60 … … 76 76 77 77 Here we can see that for the Group rhel, the syslog Bundle contains a 78 ConfigFile element /etc/syslog.conf, a Package element sysklogd, and78 !ConfigFile element /etc/syslog.conf, a Package element sysklogd, and 79 79 a Service element syslog. This defines a relationship between all 80 80 these elements, so that if one of these changes, examination of all … … 150 150 file, but it could easily be automated. Enter Generators. 151 151 With a Generator you can have it so the it takes care of the 152 management of the particular ConfigFile elements such as /etc/ssh/152 management of the particular !ConfigFile elements such as /etc/ssh/ 153 153 known_hosts and the host keys. What would happen is when a client 154 contacts the Bcfg2 server and requests those ConfigFile elements154 contacts the Bcfg2 server and requests those !ConfigFile elements 155 155 handled by the Generator, the Generator will take care of auto- 156 156 generation of new host keys for a host or giving a host the host key … … 275 275 }}} 276 276 277 Here you can see that the data is encapsulated in a PackageList which277 Here you can see that the data is encapsulated in a !PackageList which 278 278 describes the URI of the files described, the type of package, and a 279 279 priority of the files. The priority is used to decide which specific … … 317 317 The Base directory is responsible for defining the base config for 318 318 all hosts of a given Group. The majority of the elements are 319 Packages, but you can have Services, ConfigFiles, Directories, and320 SymLinks as well. Here's an example:319 Packages, but you can have Services, !ConfigFiles, Directories, and 320 !SymLinks as well. Here's an example: 321 321 322 322 {{{ … … 351 351 ==== Cfg/ Directory ==== 352 352 353 The Cfg is where all the actual ConfigFiles are kept. If you have a354 ConfigFile element listed in a Bundle you need to provide Bcfg with353 The Cfg is where all the actual !ConfigFiles are kept. If you have a 354 !ConfigFile element listed in a Bundle you need to provide Bcfg with 355 355 the actual configuration file to give to the host. The directory 356 356 structure under the Cfg/ directory defines where the configuration … … 436 436 }}} 437 437 438 The + at the beg gining of the file tells Bcfg2 that the line should438 The + at the begining of the file tells Bcfg2 that the line should 439 439 be appended to end of the file. You can also start a line with - to 440 440 tell Bcfg2 to remove that exact line wherever it might be in the file.
