What is artifact support in NSP?

Artifacts overview

NSP may require artifacts, as defined in What is an artifact?, to be installed in order to perform specific functions. For example, the NE upgrade operation requires a series of workflows. The functional area within NSP that the artifact is designed to support is called the target application, or simply, target.

NSP facilitates the tracking and management of NSP artifacts and artifact bundles by providing one location and one method for managing artifacts and artifact bundles in your system.

Adaptor artifacts

NSP supports a variety of multi-vendor devices via pluggable artifacts and adaptors, which are grouped by vendor and type/use case and bundled together for delivery.  

Some artifacts are generic, supporting multiple NE releases. Other artifacts are specifically targeted to a single NE release.

Certain artifacts can be installed from the Artifacts, Artifact Bundles view, as shown in Table 2-1, Artifacts supported for installation using the NSP Artifacts views, while other artifacts must be installed using legacy tools.

Obtaining artifacts

Depending on your feature packages, a set of artifacts and bundles is included with your NSP installation. Additional or updated artifact bundles can be downloaded from the Nokia NSP software delivery site:

Artifacts can be delivered or updated outside the NSP release cycle.

Compatible artifacts

The following table shows the artifact types that can be imported via NSP’s Artifacts views.

Table 2-1: Artifacts supported for installation using the NSP Artifacts views

Artifact type

Target application

Device mappings for MDM Server telemetry

MDM Telemetry Mappings

Resync device mappings for MDM managed NEs

MDM Resync Mappings

Resync device mappings for classically managed NEs

NFM-P Resync Mappings

YANG to YANG mappings for IETF

YANG-to-YANG Mappings

JSON ACT alarm rules mapping

NSP ACT Framework

Operation types

Device Management -  Operations

Cloud native telemetry resources

Telemetry

Workflows, actions, and Jinja2 templates

workflow-manager

These artifacts are found in the Workflows views after installation.

Intent types

intent-manager

All intent types are found in the Network Intents views after installation. To use intent types in other views, such as Service Fulfillment, you need to import them from the view they will be used in.

Service Management metadata files for data sync

service-fulfillment

Model-driven adaptor artifacts 1

MDM

Notes:
  1. Some adaptor artifacts may not be supported for installation using the Artifacts views. See the artifact guide for the adaptor bundle to verify compatibility. If the adaptor bundle is not installable from the Artifacts view, see “How do I install adaptor artifacts that are not supported in the Artifacts view?” in the NSP System Administrator Guide for information about installing it.

Developer mode

If developer mode is disabled in the NSP, user actions are limited. Importing artifacts using the Artifacts views is supported for signed artifacts only.

See the NSP Installation and Upgrade Guide for more information.

Access control

Depending on your assigned role, some operations in the Artifacts views may not be available to you. Contact your system administrator if you can't access certain network resources or information.

Note: Disabling developer mode overrides access control settings. If developer mode is disabled, restricted functions are restricted for all users.