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 function, 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 install 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 that can be installed using the Artifacts import functions in the NSP UI are located in the NSP/<release>/Artifacts hierarchy. See How do I install an artifact bundle?.
-
Production adaptors and their associated artifacts can be obtained from the NSP/<release>/Adaptors folder. For installation of adaptors and other artifacts that cannot be installed using the Artifacts views, see “How do I install adaptor artifacts that are not supported in the Artifacts view?” in the NSP System Administrator Guide
Artifact guides are provided with the adaptors for each NE family and NSP release. For example, the Nokia SR OS Artifact Guide for Release 23.11 lists and describes the adaptor suites delivered to support management of Nokia SR OS devices by NSP Release 23.11 over model-driven interfaces. The artifact guides also contain information about the NSP functionality supported by the adaptors, NE compatibility with those NSP functions, NE commissioning information and a view of active issues.
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 install using the NSP Artifacts views
|
Artifact type |
Target |
|---|---|
|
Device mappings for MDM Server telemetry |
telemetry-mappings |
|
Resync device mappings for MDM managed NEs |
resync-mappings |
|
Resync device mappings for classically managed NEs |
nfmp-resync-mappings |
|
YANG to YANG mappings for IETF |
yang-mappings |
|
JSON ACT alarm rules mapping |
nsp-act |
|
Large scale operation-types |
Device Management - Operations |
|
Cloud native telemetry resources |
cn-telemetry |
|
Workflows, actions, and Jinja2 templates |
workflow-manager |
|
Intent types |
intent-manager |
|
Service Management metadata files for data sync |
service-fulfillment |
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.