Project Name:
- Proposed name for the project:
External System Register - Proposed name for the repository: esr
Project description:
ONAP components need to talk with external systems such as VIM/VNFM/SDNC/EMS to orchestrate a network service, for example, SO/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.
Scope:
- Register/query/update/delete function of VIM
- Register/query/update/delete function of VNFM
- Register/query/update/delete function of SDN Controller
- Register/query/update/delete function of EMS.
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- How does this align with external standards/specifications?
- Are there dependencies with other open source projects?
- APIs/Interfaces
- Mysql
- Microservice Bus
- Integration Testing
- APIs/Interfaces
Resources:
- Primary Contact Person
- Names, gerrit IDs, and company affiliations of the committers
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
https://gerrit.open-o.org/r/#/admin/projects/common-services-external-system-registration - 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)
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name: esr
- JIRA project prefix: esr
...