Page History

...

User Stories

Feature

Description

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1538

Create the Functional test case to validate VNFM Adapter NBI and SOL003-based SBI

Validate VNFM Adapter NBI and SOL003-based SBI

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1618

SVNFM Simulator

For integration testing in ONAP, vendor-neutral SVNFM is needed,

This SVNFM Simulator supports SOL003-based interfaces and message exchange sequences for interface verification.

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1619

Create SO VNFM Adapter Northbound Interface using Swagger

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1620

Create Shell Adapter

Deployable VNFM Adapter container in ONAP (including docker image and helm chart)
Register VNFM Adapter with MSB

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1621

Create placeholder implementation for create VNF (without SVNFM interaction)

Create Override YAML in OOM project
Define Create/instantiate VNF interface which log the request in SVNFM adapter
Create request to VNFM adapter for VNF creation

Note: manual database update to trigger new BB flow and no pre-load

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1622

Check for existing VNF (with SVNFM Interaction)

Update Override YAML to add A&AI basic auth and URL
Generate 003 APIs using swagger
Get the generic-vnf from A&AI
Select a VNFM from A&AI (if not already associated with a VNFM)
Check for existing VNF

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1623

Handle Create VNF request in VNFM adapter

Get VNFD Id from original csar
Send create request to the SVNFM
Set self-link based on result of create operation

User Stories
- TBD

Use Cases

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1624

Instantiate VNF (with SVNFM Interaction)

With pre-load data from SDNC based on model name and VNF-type
Get the flavor Id from the CSAR
Get the VIM info from A&AI
Send request to SVNFM
Update generic-vnf orchestration status A&AI

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1625

Handle Grant Request (Without Homing/OOF)

Reply to grant request based on given VIM info in request

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1626

Monitor Job Status

Adapter Store and return job Id ( job ids stored in cache)
Introduce Job monitoring handling in flow
Handle time out for Job monitoring ( hard coded/configure in yaml timeout)
Identify the VNFM and operation Id for the job
Send get operation status request to VNFM
Return status

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1627

Create relationship between esr-vnfm and generic-vnf in AAI

add a rule to AAI DBEdgeRule ESR

{ "from": "generic-vnf", "to": "esr-vnfm", "label": "tosca.relationships.DependsOn", "direction": "OUT", "multiplicity": "MANY2ONE", "contains-other-v": "NONE", "delete-other-v": "NONE", "prevent-delete": "NONE", "default": "true", "description":"" }

read the relationship in the SO VNFM Adapter Adapter

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1628

Handle Notification Subscription

Notification Subscription

Update generic-vnf status
Create vServers
Set OAM IP address - source of which needs to be configurable
Update Orch status in A&AI to completed

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1629

Notification Handling - Instantiate

Update generic-vnf status
Create vServers
Set OAM IP address - source of which needs to be configurable
Update Orch status in A&AI to completed

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1630

Monitor Node Status

Introduce Node monitoring handling in flow which periodically check orchestration status in A&AI
Handle time out for node status handling (hard coded/configurable timeout)

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1631

Handling Homing in Flow

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1632

Handle VNF delete and termination (without SVNFM integration)

Deleting/Terminating VNF (without SVNFM integration)

Define Terminate VNF interface in VNFM adapter
Update or introduce new building block which invoke VNFM adapter for termination

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1633

Terminate VNF (with SVNFM interaction)

Identify the SVNFM to use from A&AI
Send terminate request to SVNFM
Send delete request to SVNFM
Return a job Id
Check termination job status in flow

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1634

Notification Handling - Terminate

Delete vServers
Update generic-vnf orchestration status
Check node termination status in flow

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1635

Remove SDNC pre-load and introduce user_param handling

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1636

Handle Failure case where notification is missed (Query VNF)

VNFM Adapter expose interface to get of VNF info
Flow use VNF info to check status at timeout

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SO-1637

Spike - investigate OAM IP address handling for generic-vnf

Investigate OAM IP Address handling for generic-vnf

Use Cases

- Choose a use case for demonstrating the VNFM Adapter capabilities
- Ericsson Internal Test:
  - A vendor provides their VNF Package and SVNFM for managing the vendor-specific VNF package.
  - For the SO VNFM Adapter NBI and SOL003-SBI interface validation, Ericsson SVNFM is used for the internal testing
- Integration Test:
  - For the integration testing, generic/dummy VNF package and VNFM simulator are provided.
  - The generic/dummy VNF package is to test onboarding and SOL001 parameters extraction during SOL003-based API parameters, such as descriptor_id, flavor, etc.
  - VNFM simulator is a vendor-neutral SOL003-compliant VNFM, which supports SOL003 responses and message exchanges.
- Choose a use case for demonstrating the VNFM Adapter capabilities
- Under investigation (will determine soon)

VNFM Adapter Sub-components
- - SO VNFM Adapter component is a sub component of SO; utilizing docker image and container manged.
  - North Bound Interface (NBI)
    - RESTful APIs that support createVnf, instantiateVnf, queryVnf, grantVnf, TerminateVnf
    - Its APIs are SO specific; i.e., not SOL003-based ones
  - Business Logic layer
    - It is invoked by the NBI and provides business logic for createVnf, instantiateVnf, queryVnf, terminateVnf
    - SDNC and A&AI access to collect assignment and VimConnectionInfo
    - Accesses SdcPackageProvider for getting SOL003 package(s) and parameters
    - SdcPackageProvider
      - Supports SOL001/SOL004 package management
      - Provides getPackage, getVnfdId, getFlavorId, getVnfNodeProperty
      - Provides getPackage(s), getVnfd, getArtifactFile for SVNFM
      - Uses SDC Tosca Parser
    - GrantManager
      - Provides requestGrantForInstantiate REST API for SVNFM
      - Invokes OOF for homing decision; HPA support, and/or non-OOF decision
    - SOL003Lcn APIs
      - Supports VnfIdentifierCreationNotification, VnfIdentifierDeletionNotification, VnfLcmOperationOccurrenceNotification
  - SOL003 Communication Layer
    - It is a thin REST client layer, which sends SOL003-compliant requests to SVNFMs and receives responses/notifications from SVNFM.
    - For Grant, it provides the Grant REST endpoint for SVNFMs.

...

Space shortcuts

Page tree

Versions Compared

Old Version 87

New Version 88

Key

User Stories

Use Cases

Use Cases

VNFM Adapter Sub-components