#1699 [RFE] Add Automount cross-location support
Closed: wontfix 5 years ago Opened 12 years ago by rcritten.

https://bugzilla.redhat.com/show_bug.cgi?id=732791

Description of problem:

IPA Automount configuration: Is it possible to reference an automount
 map from another location? E.g. under Policy -> Automount -> Add map
 -> Parent Map: <reference to other location>.auto.data

 Example: Let's say you have the following automount locations defined
 in IPA: NewYork, Washington, Miami. Each location has it's own
 auto.data map mounted under /data.

 Then making a common automount map in all the locations called
 auto.global, mounted at /global, each referencing the auto.data maps
 from the different IPA locations?

 /global/washington -> Washington's auto.data map
 /global/newyork -> NewYork's auto.data map
 /global/miami -> Miami's auto.data map

 I'm not looking for the configuration of the /global map to be
 automatic, a manual configuration for pointing to each locations
 auto.data map would do just fine.


Version-Release number of selected component (if applicable):
2.1

Check if automount supports multiple DNs.

I don't think this is possible without copying entries or using LDAP referrals.

The search base for autofs is set to the location which confines the autofs client. Storing entries outside this would make them unavailable.

I'm just not sure what impact performance, management or otherwise we would take on by creating a referral.

Metadata Update from @rcritten:
- Issue assigned to rcritten
- Issue set to the milestone: Ticket Backlog

7 years ago

I'm running into this as well - would be nice to have a shared common map area. Often one only needs a different auto.master for each location.

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given a priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata