Product SiteDocumentation Site

Chapter 9. Policy: Using Automount

9.1. About Automount and FreeIPA
9.2. Configuring Automount
9.2.1. Configuring autofs on Fedora
9.2.2. Configuring Automount on Solaris
9.3. Setting up a Kerberized NFS Server
9.3.1. Setting up a Kerberized NFS Server
9.3.2. Setting up a Kerberized NFS Client
9.4. Configuring Locations
9.4.1. Configuring Locations through the Web UI
9.4.2. Configuring Locations through the Command Line
9.5. Configuring Maps
9.5.1. Configuring Direct Maps
9.5.2. Configuring Indirect Maps
9.5.3. Importing Automount Maps
Automount is a way of making directories on different servers available, automatically, when requested by a user. This works exceptionally well within an FreeIPA domain since it allows directories on clients within the domain to be shared easily. This is especially important with user home directories (Section 5.1, “Setting up User Home Directories”).
In FreeIPA, automount works with the internal LDAP directory and, if it is configured, DNS services.

9.1. About Automount and FreeIPA

Automount is a way to manage, organize, and access directories across multiple systems. Automount automatically mounts a directory whenever that resource is requested. Automount also provides a coherent structure to the way that these directories are organized. Every single directory, or mount point is called a key. Multiple keys that are grouped together are a map, and maps are associated according to their physical or conceptual location.
The base configuration file for autofs is the auto.master file in the /etc/ directory. There can be multiple auto.master configuration files in separate server locations, if necessary.
When autofs is configured on a server and that server is a client in a FreeIPA domain, then all of the configuration information for automount is stored in the FreeIPA directory. Rather than being stored in separate text files, the autofs configuration — maps, locations, and keys — are stored as LDAP entries. For example, the default map file, auto.master, is stored as:
dn: automountmapname=auto.master,cn=default,cn=automount,dc=example,dc=com
objectClass: automountMap
objectClass: top
automountMapName: auto.master


FreeIPA does not set up or configure autofs. That must be done separately. FreeIPA works with an existing autofs deployment.
Each new location is added as a container entry under cn=automount,dc=example,dc=com, and each map and each key are stored beneath that location.
As with other FreeIPA domain services, automount works with FreeIPA natively. The automount configuration can be managed by FreeIPA tools:
  • Locations, using ipa automountlocation* commands
  • Both direct and indirect maps, using ipa automountmap* commands
  • Keys, using ipa automountkey* commands
For automount to work within the FreeIPA domain, the NFS server must be configured as a FreeIPA client. Configuring NFS itself is covered in the Red Hat Enterprise Linux Storage Administration Guide.