cmd-forwarder-vpp should apply changes for the datapath in case of changing connection proto on refresh

[denis-tingaikin]

Description

Client or Endpoint could change connection proto-state on refresh requests. For example, change Mac addresses or IP addresses or change routes, and so on.

The question is: Should forwarder-vpp apply the change?

Use-case

1. start basic NSM setup
2. start endpoint for service 'ns-1'
3. client requests service 'ns-1'
4. NSM serves the request (nsmgr, forwarder-vpp, endpoiont does work)
5. client gets connectivity
6. client does refresh
7. NSM serves the request
8. endpoint changes Src/Dst addresses for the client's request

Actual: client still have old IPs

Expected: ?

[denis-tingaikin]

/cc @edwarnicke

[edwarnicke]

@denis-tingaikin Do we know why the endpoint changed the Src/Dst IPs assigned?

[denis-tingaikin]

@edwarnicke At this moment we did not face something similar in our examples. The question is about to do we allow endpoints to change datapath config in general on refresh.

[edwarnicke]

@denis-tingaikin Ah... then yes, yes it should :)

[denis-tingaikin]

OK, then we should fix it.

[denis-tingaikin]

@edwarnicke Should this be considered before release v1.2.0?

[denis-tingaikin]

@edwarnicke confirmed internally that the issue should be considered.

Denis Tingaikin 15 hours ago
@edwarnicke Should we consider this before v1.2.0?

Ed Warnicke 15 hours ago
if possible yes… I suspect that we will need something like it to resolve issues with vL3