Release Notes

Version: 4.0.0

Release Date:2019-05-30

New major version v4 for the API, see Upgrade Notes

Dedicated Postman collection can be found in the integration project see test/postman

All tests suites have been re written in Karate, see src/test/resources/karatetest for inspiration.

New Features

Main new features are supports of

Main functional changes for BBS:

  • EXTAPI-98 - Service inventory notification`
  • EXTAPI-161 - New service specificationInputSchemas operation`

Main functional change for CCVPN

Many other changes and improvement are listed in JIRA:

Known Issues

Security Notes

NBI has been improved to reduce signs of vulnerabilities, especially by migrating from Springboot 1.x to Springboot 2 and using ONAP Parent pom.xml

Warning: NBI exposes non TLS API endpoint on port 30274, meaning full plain text exchange with NBI API. TLS configuration, with ONAP Root CA signed certificate will be proposed in El Alto.

As a workaround it is quite easy to add HTTPS support to NBI by configuring SSL and activating strict https. Presuming you have a valid JKS keystore, with private key and a signed certificate:

src/main/resources/application.properties
# tls/ssl
server.ssl.key-store-type=JKS
server.ssl.key-store=classpath:certificate/yourkeystore.jks
server.ssl.key-store-password=password
server.ssl.key-alias=youralias

# disable http and activate https
security.require-ssl=true

Quick Links:

Upgrade Notes

API is a new MAJOR v4 version due to the deletion of the ‘hasStarted’ attribute from getServiceById response GET /service/{id}

So don’t forget to use this new path:

/nbi/api/v4

before:

/nbi/api/v3

Deprecation Notes

API v3 is deprecated

Other


Version: 3.0.2

Release Date:2019-01-31

Part of Casablanca Maintenance Release tag - 3.0.1 January 31st, 2019

Fix

Detail of features described in the readTheDoc documentation.

Known Issues

No new issues

Security Notes

Quick Links:

https://wiki.onap.org/pages/viewpage.action?pageId=51282484


Version: 3.0.1

Release Date:2018-11-30

New Features

Main features are:

  • EXTAPI-96 - Add notification for serviceOrder API
  • EXTAPI-97 - Upgrade ServiceOrder API to manage modification UC
  • EXTAPI-100 - Improve ServiceInventory API
  • EXTAPI-101 - Integrate ExtAPI/NBI to MSB
  • EXTAPI-102 - Integrate ExtAPI/NBI to an E2E ONAP UC
  • EXTAPI-116 - Help NBI user to get information when Service order fails
  • EXTAPI-125 - Add support for progress percentage on ServiceOrder tracking

Detail of features described in the readTheDoc documentation.

Known Issues

No new issue (see Beijing ones)

Security Notes

Quick Links:

Upgrade Notes

No upgrade available from Beijing

Deprecation Notes

NA

Other


Version: 1.0.0

Release Date:2018-06-07

New Features

Main features are:

  • EXTAPI-39 - Retrieve SDC information (catalog information) for service level artifacts based on TMF633 open APIs - operation GET
  • EXTAPI-41 - Retrieve AAI information (inventory information) for service instance level artifacts based on TMF638 open APIs - operation GET
  • EXTAPI-42 - Create and retrieve SO service request for service level based on TMF641 open APIS - Operations POST & GET

Detail of features described in the readTheDoc documentation.

Bug Fixes

Not applicable - This is an initial release

Known Issues

For service catalog:

  • Find criteria are limited

For service inventory:

  • Customer information must be passed to get complete service representation.
  • Find criteria are limited.

For service order:

  • ServiceOrder will manage only ‘add’ and ‘delete’ operation (no change).
  • Only service level request is performed.
  • No request for VNF/VF and no call to SDNC.
  • EXTAPI-70 : links between customer/service instance and cloud/tenant not done (trigger VID issue).
  • Only active service state is considered to add a service.

Detail of limitations described in the readTheDoc documentation.

Security Notes

External API code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The External API open Critical security vulnerabilities and their risk assessment have been documented as part of the project. Authentication management and Data Access rights have not been implemented.

Quick Links:

Upgrade Notes

Not applicable - This is an initial release

Deprecation Notes

Not applicable - This is an initial release

Other


End of Release Notes