[HDDS-4819] Configuration property for OM to define bind address

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0, 1.1.0
• Component/s: OM
• Labels: pull-request-available
• Target Version/s: 1.5.0
• Assignee: UENISHI Kota
• Reporter: UENISHI Kota
• Created: 12/Feb/21 08:52
• Updated: 16/Dec/23 23:43

Description

Currently, "OZONE_OM_ADDRESS_KEY" (="ozone.om.address") is used both for client side and for server side. This is nice for unifying configuration files in both clients and servers, but in case where OM has multiple IP addresses and want to bind "0.0.0.0", the config file cannot be naively copied for clients' usage.

I would suggest adding another config key such as "ozone.om.bind-host" as well as "ozone.om.https-bind-host" .

I'm not sure there were any discussion on this topic, but I'd welcome a pointer to any past discussion.

Situation will be more complicated when OM HA is enabled. Say OM HA consists of om1, om2, om3 and service id is "sid". om1 config will be like:

ozone.om.address.sid.om1=0.0.0.0
ozone.om.address.sid.om2=om2
ozone.om.address.sid.om3=om3

om2:

ozone.om.address.sid.om1=om1
ozone.om.address.sid.om2=0.0.0.0
ozone.om.address.sid.om3=om3

om3:

ozone.om.address.sid.om1=om1
ozone.om.address.sid.om2=om2
ozone.om.address.sid.om3=0.0.0.0

clients:

ozone.om.address.sid.om1=om1
ozone.om.address.sid.om2=om2
ozone.om.address.sid.om3=om3

It'll be a hustle to generate different configurations for all 4 roles.

Issue Links

• links to: GitHub Pull Request #2602