OpenNESS has many features such as

• Secure on-boarding of MEC host
• Service registry & service discovery
• Traffic interception and redirection

As part of integration with OpenNESS, ICN 3.0 will focus on the third feature (Traffic interception and redirection) as we feel that this is the most important problem that is not solved by other means.   Service registry & discovery is not needed as K8s based service mechanism is good enough for many use cases. Secure onboarding  of MEC host can be done at later time as many treat this optional, mainly in Enterprise edges.

As part of integration, following tasks are identified:

• Identifying the subset of OpenNESS that satisfies traffic interception & redirection and making it available in ICN.
• Ensuring that client connection to cloud services are redirected to local replicated service.\
• Development of controller in ONAp4K8s to auto configure traffic rules when the workloads are deployed.

Please see the file section on conceptual description.

Files