#4007 [RFE] Multihomed IPA client should register all IP address & hostname in IPA server
Opened 10 years ago by dpal. Modified 3 years ago

Ticket was cloned from Red Hat Bugzilla (product RHEL RFE): Bug 1014845

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Feature Request: Multihomed IPA client should register all IP address &
hostname in IPA server

ipa-client-install should have option to add secondary hostname & IP address.

# ipa-client-install --ntp-server=10.10.10.10 --hostname=client1.example.com
--realm=EXAMPLE.COM --domain=example.com -p admin -w XXXXX
--ainterface=dmz.example.com,www.example.com --aip=10.10.10.20,10.10.10.30

# ipa-client-install --ntp-server=10.10.10.10 --hostname=client1.example.com
--realm=EXAMPLE.COM --domain=example.com -p admin
Discovery was successful!
Hostname: client1.example.com
Realm: EXAMPLE.COM
DNS Domain: example.com
IPA Server: ipa01.example.com
BaseDN: dc=example,dc=com

Would you like to add additional interfaces? [no]: yes
Enter FQDN for the additional interface: dmz.example.com
Enter IP for additional interface: 10.10.10.20
Add more interfaces? [no]: yes
Enter FQDN for the additional interface: www.example.com
Enter IP for additional interface: 10.10.10.30
Add more interfaces? [no]: no

These additional interfaces will be added to IPA:
FQDN 1: dmz.example.com
IP 1: 10.10.10.20
FQDN 2: www.example.com
IP 2: 10.10.10.30


How to test:
By setting up a multihomed client & try to register it to IPA server with
command line argument to add additional IP address & hostnames.

Design is required before implementation.

Starting to shape next release

Will this be solved in #4249? Should we merge the tickets?

Ticket #4249 solves multiple IP addresses for client. But does not handle multiple hostnames. Assigning multiple hostnames and creating advanced mapping of names to IP addresses can be done in DNS configuration.

During processing of remaining tickets in 4.2 Backlog, this ticket was found as suitable to be fixed in the nearest bugfixing branch - which is 4.2.x.

Fixed in ticket #4249.

For multihomed support use --all-ip-address option or option --ip-address

We do not plan to support different hostname per interface, this should be done in DNS plugin.

Only a part is fixed, therefore not marking this ticket as fixed.

Per comment 9, moving to triage to propose won't fix for the hostname per interface part.

Deferring, additional use cases wanted.

Metadata Update from @dpal:
- Issue assigned to someone
- Issue set to the milestone: Future Releases

7 years ago

Our use case:

We have multiple internal networks:
- general network
- private nfs network with mtu=9000
- private infiniband network

Host on the different networks have dns entries with suffix 'g' for the nfs network, and suffix 'ib' for the infiniband network.

This allows us to specify at mount time which network we want the nfs traffic to occur over. For this to work with kerberos, we would need nfs principals for each dns name, preferably attached to the primary host.

Deferring, additional use cases wanted.

Having HPC system with two networks - Infiniband(IB) and Ethernet(Eth).
There are N storage servers exporting GPFS with NFS over IPoIB and IPoEth.

Physical servers and virtual servers with SR-IOV virtualized Infiniband use IP over IB,
Virtual servers go over Eth only.

IP over IB have hostnames ending with suffix "-ib0" - that allows us to select network to be used for NFS traffic. So same case as described by @orion above.

Login to comment on this ticket.

Metadata