Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

  1. 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

  1. New component capabilities for Dublin, functional enhancements

    1. Allow BSS or any other to receive service state update, by offering both dynamic event criteria notification subscription and event notification. REST base APIs. ( use DMaaP as source to read AAI events )

    2. Service Inventory improvement by adding few more information
    3. Application status enhancement, provide a query param to play basis integration test with other modules such aai, sdc, so, dmaap
  1. New or modified interfaces

    1. /service/{id}

    2. /serviceSpecification/{uuid}/specificationInputSchema retrieve the json shemas of the serviceSpec

    3. /status?viewAll=true
  2. Reference to the interfaces

    1. Latest documentation and swagger available on latest readthedoc here

  3. System limits


  4. Involved use cases, architectural capabilities or functional requirements

    1. BBS usecase

      1. service inventory notification

    2. CCVPN usecase

      1. Service inventory improvement, by retrieving a service instance by id, populating state and relatedParty attributes.

    3. Technical improvement

      1. Migrate from springboot 1.x to springboot 2.x

      2. Refactor API testing to resolve instability during jenkins jobs, facilitate test maintenance and new feature testing. Karate framework

  5. Listing of new or impacted models used by the project (for information only)

    1. None.

  • No labels