39 | | These templates are just provided as examples on how to use [source:templates/trunk/standard/filesystem/config.tpl standard/filesystem/config.tpl]. But this template can be used to handle many other layouts. The basic idea is to declare in this template all the possible file system that can be found on a system, most of them with zero size meaning they will not be created unless the variable used to define their size is explicitly set to a non-zero value. |
| 39 | These templates are just provided as examples on how to use [source:templates/trunk/standard/filesystem/config.tpl standard/filesystem/config.tpl]. But [source:templates/trunk/standard/filesystem/config.tpl standard/filesystem/config.tpl] can be used to handle many other layouts. You can build your own from scratch or mixing the examples provided (there is no restriction to use only LVM, logical partitions or raid volumes in one layout, this was done just for clarity of examples) or using other types of block devices like hardware raid. |
| 40 | |
| 41 | The basic idea is to declare in this base layout templates (like [source:templates/trunk/sites/example/site/filesystems/glite.tpl site/filesystems/glite.tpl], [source:templates/trunk/sites/example/site/filesystems/extended.tpl site/filesystems/extended.tpl], [source:templates/trunk/sites/example/site/filesystems/sw_raid.tpl site/filesystems/sw_raid.tpl]) all the possible file system that can be found on a system, most of them with zero size meaning they will not be created unless the variable used to define their size is explicitly set to a non-zero value in another template that include the basic layout (as [source:templates/trunk/sites/example/site/filesystems/ce_nfs_server.tpl site/filesystems/ce_nfs_server.tpl] does with [source:templates/trunk/sites/example/site/filesystems/glite.tpl site/filesystems/glite.tpl]). The main effort is to maintain the basic layout but it has the advantage to provide a central point for defining any potential configuration, avoiding a lot of duplication. |