...
ONAP components need to talk with external systems such as VIM/VNFM/vendor SDNC/EMS to orchestrate a network service, for example, VF-C need to talk with VIM to allocate resource and VNFM to deploy a VNF. So they should get the information of available external systems from a registry before call the Interfaces of these external systems. ESR provides a service to centralized management of the information (name, vendor, version, acess end point, etc.) of external systems. So the ONAP components can get the system information with unified API from a logical single point.
Note: This project is proposed to be a sub-project of A&AI.
...
- How does this project fit into the rest of the ONAP Architecture?
...
- What other ONAP projects does this project depend on?
- A&AI (store the external system data and status to A&AI)
- MSB
- What other ONAP projects will call the API from ESR?
- Multi-Vim
- VF-C
- ONAP SDN-C ?
- Are there dependencies with other open source projects?
...
- Primary Contact Person: Zi Li
- Names, gerrit IDs, and company affiliations of the committers
- Contributors
Zi Li li.zi30@zte.com.cn
Qi Sun sun.qi310@zte.com.cn
Liang Qin qin.liang13@zte.com.cn Project Roles (include RACI chart, if applicable)
Role First Name Last Name Linux Foundation ID Email Address Location Primary Contact Zi Linancylizi li.zi30@zte.com.cn Committers Zi Li
nancylizi li.zi30@zte.com.cn Qi Sun
sunqi310 sun.qi310@zte.com.cn Contributors Zi Li
li.zi30@zte.com.cn Qi Sun sun.qi310@zte.com.cn Liang Qin qin.liang13@zte.com.cn
Other Information:
- link to seed code (if applicable)
https://gerrit.open-o.org/r/#/admin/projects/common-services-external-system-registration (seed code for service end)
https://gerrit.open-o.org/r/#/admin/projects/client-gui (seed code for portal) - Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- Meets Board policy (including IPR)
...