TI API: Who routes to the Edge App?

[FabrizioMoggio]

For clarification on the TI API use case:

The common use case foresees standard and premium users for a certain service.

• A standard user generates a flow toward the Service FQDN (http://appservice.com:8080/)
• the user is attached to a central UPF
• the central UPF routes to Internet
• Internet DNS resolves the FQDN with the Cloud IP of the Service instance
• A premium users still generates a flow toward the Service FQDN (http://appservice.com:8080/)
• the TI API for the premium user attaches the premium user to an Edge UPF
• the Edge UPF is configured by the TI API to route http://appservice.com:8080/ to the Edge Data Network using Edge DNS resolving the FQDN with the IP of the Edge instance of the Application.

If the App Client doesn't use FQDN but generates flows to specific IPs, it is a task of the App client to change from Cloud IP to Edge IP.

Is there any doubt or comment?

[FabrizioMoggio]

A problem can raise if the App stores in the cache the DNS resolutions. This must be avoided and well explained in the every Edge related API. For sure in the Traffic Influence documentation.

[FabrizioMoggio]

@gunjald the valorization of the EDGE DNS is out of scope of the TI API, is it in scope of some API in the Edge Cloud family? When the EAS is instantiated at the Edge, maybe.

[FabrizioMoggio]

issue: #293

[FabrizioMoggio]

Closed according to the output of: issue: #293

A better documentation on the TI API must be done to explain that is a task of the Service Application to target the right flow destination.