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:
It'll be a hustle to generate different configurations for all 4 roles.