Link to process-SC review record Graduation reviews
Project Technical Lead: Lokanath Padhu
Project Committers detail:
Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.
A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.
Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project.
Only Committers for a project are eligible to vote for a project’s Project Technical Lead.
Please see Akraino Technical Community Document section 3.1.3 for more detailed information.
|Committer Bio||Committer Picture|
Self Nominate for PTL (Y/N)
Use Case Attributes
Telco and carrier networks, enterprise networks, private networks, multi-access networks, edge cloud and verticals
|One of the key drivers of 5G Systems are ultra low latency and high reliability communications enabled by edge clouds. Services can be hosted close to the end users and new type pf services can be enabled by exposing contextual information to applications. In this framework the services can be enhanced with Machine Learning. Applications hosted in distributed cloud i.e. edge and central cloud, can consume services offered by service producers. Service consumers can discover the services that are available in that location via API framework. Similarly. the service producers can advertise their offerings via the same API framework. In addition to service discovery, the API framework allows authentication and authorization and can also provide communications transport to the service consumers and producers.|
Business use cases
Business Cost - Initial Build
|Depending on the deployment|
Business Cost - Operational
|Orchestration framework (such as ONAP) needs to enable applications in a distributed cloud discovering their local service registry for service discovery|
The solution should support granular access control and secure communications between service producer and service consumer
I see this in the description that its main functionality is related to service registration, service discovery and new service notifications and service availability.
All these functions and more (including Load balancing across multiple instances of the service, Mutual TLS, RBAC and many more) are taken care by service meshes such as ISTIO. Trying to understand using this framework instead of service meshes?