Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Distributed Applications: Telco world is known to have requirement to support ‘network services’ whose components (VNFs today) spread across multiple computing regions (Openstack based regions).  Hence, the need for central orchestrator that orchestrates various VNFs of the network service in multiple openstack based computing regions.  With edge-computing,  even normal applications are becoming distributed, where a few microservices of the application are deployed across multiple edges & a few in network edges and public clouds. Essentially, applications are becoming more like network services.
  2. Convergence of applications and network functions due to Edges : Edge world can’t afford to have two computing environments – One for normal applications and another one for network functions. This is due to resource constraints. Since many edge-computing efforts in Industry adopted K8s, it is natural to think about supporting network functions and use same K8s cluster for both. It appears that a few MEC applications even require some network functions to be deployed along with them (Example include MEC applications with network security functions).
  3. Network function deployments and life cycle management are more complex than the applications due to need for supporting multiple interfaces, provider networks,  service function chaining. ONAP is solving many of these challenges.
  4. Support for Multiple Cloud technologies :  Supporting legacy Openstack deployments with greenfield  K8s deployments are needed.  ONAP solves these multi-cloud challenges.
  5. Support for Telco infrastructure such as OSS/BSS – ONAP is already in the path to support various MEF standards on its north side to support standardization between OSS/BSS and Orchestrators.
  6. Support for monitoring of distributed applications and closed loops :  Monitoring distributed applications that are deployed across multiple edges/clouds is complex.  There is need for showing the comprehensive status at the application level instead of at each resource level.  ONAP monitors the services/distributed-apps and not only provides simpler view of the status, but also can run through various analytics engines and even act on the actionable insights.

...

#5 VNFREQS => CNFSREQS - Certification CNF requirements - need to align with the ONAP Architcture + ONAP SECCOM regardng regarding Cloud Native.

 

Features/Capabilities - How We complement each other?

...