Changes between Version 8 and Version 9 of AnnotatedExamples
- Timestamp:
- 06/01/10 05:51:21 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnnotatedExamples
v8 v9 16 16 Our example starts with the bare minimum configuration setup. We have a client, a profile group, a list of packages, and a base configuration. 17 17 18 ==== Metadata/clients.xml ==== 19 18 20 {{{ 19 # cat Metadata/clients.xml21 #!text/xml 20 22 <Clients version='3.0'> 21 23 <Client profile='fedora' pingable='N' pingtime='0' name='foo.bar.com'/> 22 24 </Clients> 25 }}} 23 26 24 # cat Metadata/groups.xml 27 ==== Metadata/groups.xml ==== 28 {{{ 29 #!text/xml 25 30 <Groups version='3.0'> 26 31 <Group profile='true' name='fedora' toolset='rh'/> 27 32 </Groups> 33 }}} 28 34 29 # cat Base/base.xml 35 ==== Base/base.xml ==== 36 37 {{{ 38 #!text/xml 30 39 <Base> 31 40 <Group name='fedora'> … … 33 42 </Group> 34 43 </Base> 35 36 # cat Pkgmgr/packages.xml 44 }}} 45 ==== Pkgmgr/packages.xml ==== 46 {{{ 47 #!text/xml 37 48 <PackageList type='rpm' priority='0'> 38 49 <Package name='ntp' version='4.2.0.a.20050816-11.FC5'/> … … 42 53 === Add service === 43 54 44 Configure the service, and add it to the base. 55 Configure the service, and add it to the base. Add the content below to the `Svcmgr/services.xml` file. 56 45 57 {{{ 46 # cat Svcmgr/services.xml 58 #!text/xml 47 59 <Services priority='0'> 48 60 <Service name='ntpd' status='on'/> 49 61 </Services> 62 }}} 50 63 51 # cat Base/base.xml 64 To the `Base/base.xml` file 65 {{{ 66 #!text/xml 52 67 <Base> 53 68 <Group name='fedora'> … … 64 79 # cat Cfg/etc/ntp.conf/ntp.conf 65 80 server ntp1.utexas.edu 81 }}} 66 82 67 # cat Base/base.xml 83 And the `Base/base.xml` file 84 85 {{{ 86 #!text/xml 68 87 <Base> 69 88 <Group name='fedora'> … … 75 94 }}} 76 95 77 === C create a bundle ===96 === Create a bundle === 78 97 79 98 The above configuration layout works fine for a single service, but that method of organization would quickly become a nightmare as you approach the number of packages, services, and config files required to represent a fully configured host. Bundles allow the grouping of related configuration entries that are used to provide a single service. This is done for several reasons: … … 83 102 * Services associated with a bundle get restarted whenever any entity in that bundle is modified. This ensures that new configuration files and software are used after installation. 84 103 85 The config file, package, and service are really all related components describing the idea of an ntp client, so they should be logically grouped together. We use a bundle to accomplish this. 86 104 The config file, package, and service are really all related components describing the idea of an ntp client, so they should be logically grouped together. We use a bundle to accomplish this. The bundle is located at `Bundler/ntp.xml` 87 105 {{{ 88 # cat Bundler/ntp.xml106 #!text/xml 89 107 <Bundle name='ntp' version='2.0'> 90 108 <Package name='ntp'/> … … 96 114 After this bundle is created, it must be associated with a group (or groups). Add a bundle child element to the group(s) which should install this bundle. 97 115 116 The `Metadata/groups.xml` file 117 98 118 {{{ 99 # cat Metadata/groups.xml119 #!text/xml 100 120 <Groups> 101 121 ...
