NFS servers
| Line 6: | Line 6: | ||
=Exports= | =Exports= | ||
Each individual set of exports is self-contained, and ideally configured for an individual purpose. If a server pulls double duty, it should be entered into multiple classes and thus have multiple concatenated exports files. | Each individual set of exports is self-contained, and ideally configured for an individual purpose. If a server pulls double duty, it should be entered into multiple classes and thus have multiple concatenated exports files. | ||
| + | |||
| + | ==Keytab exports== | ||
| + | At the moment, the keytabs are generated separately (vis configurator). This will need to be automatically generated eventually. | ||
=Relevant files= | =Relevant files= | ||
Revision as of 02:24, 17 April 2010
UGCS has two main NFS servers: Apollo for shared files and keytabs, Demeter for cfengine. We would like to set up cfengine to automatically configure current (and future) NFS servers easily.
Contents |
Cfengine
All of the NFS servers will be put into a cfengine class that overwrites the /etc/exports file when cfrun is activated. This class will also restart nfs-kernel-server to take the new settings into effect. Then, each group of servers will have an separate class that concatenates the appropriate exports files to this blank file.
Exports
Each individual set of exports is self-contained, and ideally configured for an individual purpose. If a server pulls double duty, it should be entered into multiple classes and thus have multiple concatenated exports files.
Keytab exports
At the moment, the keytabs are generated separately (vis configurator). This will need to be automatically generated eventually.
Relevant files
- /afs/.../cfengine/global/inputs/cfagent.conf - contains class definitions
- /afs/.../cfengine/global/inputs/nfs.conf - NFS server commands
- /afs/.../cfengine/hosts/nfs/<exports> - export definitions imported by cfengine
