Description
Allow for forwarding all LVS port in Virtual Router (VR) in the static scenario.
Old implementation of VR was discarded in favor on LVS included in the Keepalived itself.
The current codebase does not take into account the case when there is necessity to load balance the whole traffic.
In new version of VR - ONEAPP_VNF_LB[0-9]_PORT is mandatory. So it's impossible to load balance the whole traffic.
According to Keepalived documentation it is possible to configure it without ports. The problem here is that this feature could be brought back only for statically-defined LBs, dynamically defined LBs (backends added via OneGate or user templates) require IP and PORT of the LB "endpoint" to be defined.
Use case
Allow for 1:1 mapping similar to SDNAT4 but implemented via LVS instead.
Interface Changes
In static scenario (and in static scenario only) LVS LB endpoint port should not be mandatory + should be conditionally removed from Keepalived configs.
Description Allow for forwarding all LVS port in Virtual Router (VR) in the static scenario. Old implementation of VR was discarded in favor on LVS included in the Keepalived itself. The current codebase does not take into account the case when there is necessity to load balance the whole traffic. In new version of VR - ONEAPP_VNF_LB[0-9]_PORT is mandatory. So it's impossible to load balance the whole traffic. According to Keepalived documentation it is possible to configure it without ports. The problem here is that this feature could be brought back only for statically-defined LBs, dynamically defined LBs (backends added via OneGate or user templates) require IP and PORT of the LB "endpoint" to be defined.
Use case Allow for 1:1 mapping similar to SDNAT4 but implemented via LVS instead.
Interface Changes In static scenario (and in static scenario only) LVS LB endpoint port should not be mandatory + should be conditionally removed from Keepalived configs.