Description of problem: In order to avoid conflict with the current ports of proxy (54323) and daemon (54322), the ports should be replaced and registered according to IANA availability: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt Additional info: * See bug 1517764 * Same issue and solution should be applicable for vdsm.
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
ok, closing. Please reopen if still relevant/you want to work on it.
I submitted application for registering 2 ports: - imageio-data: https://tools.iana.org/public-view/viewticket/1166971 - imageio-control: https://tools.iana.org/public-view/viewticket/1166973 The public data port of the daemon and proxy would be hard to change in oVirt setup, since this affects existing setups (administrator already opened ports 54322 and 54323). But imageio default port can use proper registered ports, and the new control port is used only locally on engine so it does not affect any user.
This request is not currently committed to 4.4.z, moving it to 4.5
Nir, thank you. I see the tickets are closed now, can you please check the status?
This bug/RFE is more than 2 years old and it didn't get enough attention so far, and is now flagged as pending close. Please review if it is still relevant and provide additional details/justification/patches if you believe it should get more attention for the next oVirt release.
The response from IANA was that we should use the default HTTP port since this is basically HTTP application. So is is very unlikely that we can get a registered port for imageio ports.