...
There are multiple options that CSPs should consider while thinking to integrating ONAP into their existing environments, some such considerations are : ( >>Lei : These cosideration options may need specify and more descriptions)
- Integrated solutions with carrier-grade versions of individual ONAP modules
- Service models, applications and micro-services built to run in ONAP environments
- Compliant networking infrastructure (physical/virtual), including PNFs, VNFs, domain controllers, etc. that can plug into ONAP
- Operational changes which are required to run and manage ONAP
- Set of developers, testers and designers required to deliver & operate services though ONAP
- Ensuring ONAP is a secure product by design and striking a fine balance between services they want on ONAP while keeping ONAP on the current version of release
- and many such unknowns
...
Imagining various service providers set up scenarios, if we can define ONAP's integration evolution to address this integration conundrum, this should address inter-operability across EMS, NMS, OSS as well as the BSS; and this is the path of least resistance to increase the adoption and presence of ONAP platform.
( >>Lei : We think SDO is not very relevant to production environment, maybe we could consider move this content into other charpter. LFN white paper have some info about ONAP and SDOs , which could be a reference. )
Several CSPs have a strong dependency on standard solutions and it is usually a common strategy for a collaborative network (Ex - 3GPP compliant solutions or GSMA aligned specifications); SDOs can assist with architecture, quality and inter-operability of Open Source projects, as well as enhance the overall vitality of the mobile value chain.
...