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

Compare with Current View Page History

« Previous Version 15 Next »

1. Scope


DESCRIPTION: This flow describes the the onboarding of resources into SDC. This can apply to a new resource or an upgraded resource. A resource can be a VNF or PNF. Resources are onboarded into the SDC catalog during design time. This flow will describe what happens when a resource is brought into SDC. A resource in the SDC catalog can then be used in design time to define a service.

WHEN EXECUTED: During Design Time (before Run Time). When SDC Service imports a Resource into the SDC catalog.

PURPOSE: To bring in a VNF or PNF resource into SDC during design time.

INFORMATION PASSED: Vendor provided PNF onboarding package.

ACTORS:

  • Service Designer
  • Operations Specialist
  • SDC (Deployment Studio)





2. Pre-Conditions

Vendors will prepare the Onboarding package:

  • MODELS IN SDC - SDC contains the verified service and resource descriptor (models).
  • CERTIFICATION STUDIO - The Certification Studio has certified the Package ready for distribution
  • ONAP SOFTWARE - Software images loaded in OpenStack installation, where instantiation will happen (since no S/W image repository). Need to be available in Target Cloud Instances.


The Onboarding Package Contains:


The following shows a diagram of the PNF Onboarding package which must be put together

A description of the things in the PNF Onboarding Package

  • PNF DESCRIPTORS (PNFD) - (Instantiation/Design Time) PNFD and VNFD have been mapped to ONAP platform data/information model. That is, the onboarded descriptor models (vendor provided) have been mapped onto ONAP platform data & information models that are useable and known to ONAP.
  • TOSCA METADATA - This file provided by the vendor describes the meta-information about the package. Notably it gives the key files in the package and their locations in the package as directory paths.
  • MANIFEST FILE - The Manifest file include basic information about the package itself.
  • VES EVENT REGISTRATION - This file describes all of the events that are supported by the PNF. It defines the possible events that the PNF can support, such as faults, heartbeating, Performance measurements. These are defined in the VES Event specification document available in the repository. The Event Registration also defines all of the fields that each of these events have also
  • PM DICTIONARY - Performance Measurements definitions.
  • ANSIBLE PLAYBOOKS - Ansible playbooks define the "scripts" that are used for remote ansible communications from ONAP towards a PNF.
  • NETCONF YANG MODELS - Defines the NetConf Yang Models that are used for NetConf communications between ONAP and the PNF.
  • CHEF COOKBOOKS - When Chef communications are supported between ONAP and the PNF, these define the communication playbooks that are used by Chef
  • MANUALS - Manuals can be included as informational artifacts in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time.
  • HELP FILES - Help files can be included as informational artifacts in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time.
  • CUSTOMER DOCUMENTATION PRODUCTS - Customer documentation products can be included as informational artifacts in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time.
  • TEST FILES - Manuals can be included as informational artifacts in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time.
  • LICENSING AGREEMENTS - Licensing agreements can be included as informational artifacts in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time.
  • RESOURCE CONFIGURATION INFORMATION - Resource Configuration Information can be included in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time.

3. Information Flow

The following diagram shows the PNF Pre-onboarding/Onboarding Flow:
 PNF Pre-onboarding/Onboarding USER USER VNFSDK VNFSDK SDC SDC PNF PACKAGE DELIVERY Onboarding API Vendor Delivery 1PNF Package Delivery PACKAGE VALIDATION VNF SDK Package Validation 2License File Check 3Certificate File Check 4Manifest file & destination cross-check 5Manifest file tag Validation 6TOSCA Metadata file validation Certification Studio 7User checks validation SDC PACKAGE ONBOARDING xNF Resources, Service ID 8UUID Metadata added 9TOSCA MetaData added 10TOSCA Descriptor Added 11X License Model Files Added 12Additional Artifacts Added (Manual/Optional)

PNF PACKAGE DELIVERY

1. PNF PACKAGE DELIVERY – Vendor Delivers the Package.

PACKAGE VALIDATION (VNF-SDK)

2. LICENSE FILE CHECK – VNF-SDK performs a license file check within the vendor-delivered PNF package.

3. CERTIFICATE FILE CHECK – VNF-SDK performs a certificate file check within the vendor-delivered PNF package.

4. FILE AND DESTINATION CHECK – VNF-SDK examines the MainServiceTemplate.mf (Manifest file) and performs a cross-check of the files & pathway directories specified within the manifest faile against the actual files within the vendor-delivered PNF package. It checks that the files that have been specified in the manifest file are actually in the given destination (directories).

5. MANIFEST FILE TAG VALIDATION – VNF-SDK performs a check of the PNF keywords in the MainServiceTemplate.mf (Manifest file). The tags are pnf_product_name, pnf_provider_id, pnf_package_version, pnf_release_data_time, and non-mano_artifact_sets.

6. TOSCA METADATA FILE VALIDATION – VNF checks the Meta Data file (TOSCA.meta) in the PNF package with the ETSI SOL004 validation tags. The checks performed are the Entry definition, Entry-manifest, Entry-change-log, Entry-tests, Entry certificates.=.

7. USER CHECKS VALIDATION – The end user may then inspect that the PNF package has been appropriately verified in the Certification studio.

SDC PACKAGE ONBOARDING

8. UUID IDENTIFIER – SDC adds a UUID identifier.

9. TOSCA METADATA – SDC adds additional TOSCA Meta-data.

10. TOSCA DESCRIPTOR – SDC may add a TOSCA Descriptor

11. LICENSE MODEL FILE – SDC can add a license model file.

12. ADDITIONAL ARTIFACTS – The User may optionally manually add additional artifacts.


4. Post Condition

The post-conditions for this flow are:

  • PNF ONBOARDED - Service has an A&AI Service Record Entry.
  • PNFD MODEL LOADED - Resources associated with the Service have been successfully instantiated.
  • SDC INTERNAL MODEL - Cloud resources have been successfully assigned necessary to support the service
  • PACKAGE VALIDATED - Network assignments have been assigned for the service
  • ADDITIONAL ARTIFACTS - Security assignments have been su


  • No labels