SOL005 conformance testing

Proposers

• Gerardo García (Telefónica)
• Mark Beierl (Canonical)
• Silvia Almagia (ETSI)

Description

SOL005 conformance tests were run to identify the gaps between OSM NBI and SOL005 spec. A few issues were detected and are captured below:

• nsName not returned as output of nslcm/v1/ns_instances/{{nsInstanceId}}/instantiate
• OSM allows uploading NSD content to an NSD in a state other than 'CREATED'.
• The output of this request "GET /osm/nspm/v1/pm_jobs/1/reports/f54a3417-d357-481b-ab1d-6d6b85b14840" should include 'objectType' as a required property
• NS status query to NBI /nslcm/v1/ns_instances/{id} returns the creation time as "time-create" but for VNF the response uses "time-created". If there is a SOL005 parameter, it should be used.
• Last-modified-time should be exposed
• When a VNF is in scheduled state, vdur['status'] is not exposed from the /nslcm/v1/vnf_instances endpoint.
• The message POST /nslcm/v1/ns_instances uses InstantiateNSRequest instead of CreateNSRequest

Demo or definition of done

SOL005 conformance tests that were failing should pass now. There was a previous work to run conformance tests and could be used to test the feature: https://osm.etsi.org/gitlab/osm/projects/-/wikis/Projects/TST010

References:

• Bug 1123. NS Instantiate nsName as required property
• Bug 1188. Uploading NSD content of NSD in state 'ONBOARDED
• Bug 1454. OSM Performance Report missing Object descriptorType
• Bug 1622. Status report not consistent between NS and VNF
• Bug 1869. Endpoint - POST /nslcm/v1/ns_instances uses InstantiateNSRequest instead of CreateNSRequest
• Video TST010 in OSM CICD pipeline by Axel Velez
• Fix for 1188 Upload state conflict