Project Overview
NBI stands for NorthBound Interface. It brings to ONAP a set of APIs that can be used by external systems such BSS for example. These APIs are based on TMForum APIs
New component capabilities for Frankfurt, functional enhancements
Security https and Java 11 upgrades
- Improvement to external swagger documentation with reference to ONAP API style guidelines
New or modified interfaces
- None
Reference to the interfaces
Latest documentation and swagger available on latest readthedoc here
System limits
Involved use cases, architectural capabilities or functional requirements
BBS usecase
service inventory notification ( allowing eventType=ServiceCreationNotification,ServiceAttributeValueChangeNotification, ServiceRemoveNotification to be registered for subscription by external systems )
CCVPN usecase
Service inventory improvement, by retrieving a service instance by id, populating state and relatedParty attributes.
Adding Service Order forwarding capaibility with External API Framework acting as an API Proxy for external communication originating internally from ONAP Service Orchestrator
Technical improvement
Migrate from springboot 1.x to springboot 2.x
Refactor API testing to resolve instability during jenkins jobs, facilitate test maintenance and new feature testing. Karate framework
Listing of new or impacted models used by the project (for information only)
None.
Diagram
- CCVPN, east-west interaction of ONAP instances through External API