Operations

Overview

The Operation views are available if the Network Infrastructure Management - Basic Management feature package is included in the deployment. To complete operations, NSP executes workflows. You can view the workflows in the Workflows, All Workflows view if needed.

Note: Before performing an operation on a group of NEs, you must define NE groups; see the NSP System Administrator Guide.

An operation is composed of a series of workflows, organized in phases, which are performed on a scope of NEs. Each phase of an operation is associated with a workflow. When the workflow for a phase is performed on an NE, it creates an execution within the operation, which is an instance of that phase’s workflow being performed on that NE. The workflows, phases, and other details for an operation are defined in an operation type.

You can create an operation to perform a task on large numbers of NEs concurrently; for example, upgrading all SR NEs in a network to the latest SR OS release. To complete the task, the NSP performs the actions that are defined in workflows; the specific workflows used can vary depending on the target NE, and each operation type contains a mapping profile which specifies which workflow to use on an NE for each phase in the operation. For example, an upgrade operation may contain a phase for copying files to the target NE; the specific workflow called may be different for a 7450 ESS and a 7950 XRS, but at the end of the phase the files are copied.

Operation types

An operation type is the blueprint used to create an operation. Each operation type is intended to perform a general task, such as upgrading software, and combines an operation model and a mapping profile, which are used to find the appropriate workflows to be performed on the NEs specified in the operation. The mapping profile matches workflows to NEs based on NE identifiers (for example, NE family or version). The operation model extends the base operation model defined in the NSP for each operation type.

Phases

Each operation is divided into phases, which are high-level steps in the process of the operation. Phases vary depending on the operation, and some operations have only a single phase. Some operations contain an Initial-Phase phase, which is performed against the NSP system to ensure the NSP is ready to proceed with the operation.

Phases which are waiting for your attention are noted in the Device Management, All Operations view.

Executions

An execution is the implementation of a phase on a specific NE. You can view the progress of individual phases by double-clicking on an operation in Device Management, All Operations view.

Executions can generate reports for you to review; report outputs are defined in the workflows used by the operation, so can vary between operations. Some operations generate reports in multiple phases, and provide an option for comparing reports - for example, an operation may have a pre-check phase and a post-check phase, with both phases generating reports that can be compared to highlight differences. Which reports are comparable is defined in the mapping profile for the operation. For assistance in developing workflows and operations that generate reports, please contact your support representative.

Creating and updating operation types

Operation types are stored in the NSP as artifacts and managed using Artifacts. Adding a new operation type or updating an existing one requires installing an artifact bundle. For information about installing an artifact bundle, see “How do I install an artifact bundle?” in the NSP Network Automation Guide. For information about creating artifact packages, contact your Nokia support representative.

Note: Before upgrading an operation type to a new major version by installing an updated artifact package, configure the lifecycle of the operation type to Withdrawn.

Operation models

An operation model is a .yang file which can be used to extend the base operation model of each operation type. For example, the operation model included in the default NE Backup operation type extends the model to include the backup-file parameter, which retrieves the name of the backup file created by the operation and includes it in the task result summary as a parameter.

Operation inputs can be stated in an operation model, and values for those inputs configured when the operation is created.

Mapping profiles

A mapping profile is a .yaml file that maps nodes to workflows, using node parameters such as node family and node software version. Qualifiers can be nested to produce more specific results, for example:

phases: 

  - phase: 'Backup'

    description: 'Single phase backup'

    concurrency_count: 20 

    ne_families:

       - family_type: 7750 SR, 7950 XRS

         ne_versions:

          - version: all

            workflow_name: LSO_7x50_Backup 

            workflow_inputs:

            backup_certificates: no

You can use a mapping profile to call different workflows for different nodes, or provide different inputs for the same workflow.

Model-driven and mixed-mode operations

For operations performed on nodes discovered through mixed-mode or model-driven management, CLI access management must be enabled on the node. The following types of CLI access must be enabled, in the order shown: md-cli, and classic-cli.

For SR OS device commissioning information, see the Management Interface Protocol Configuration section in the adaptor artifact guide. For additional information if needed, see the NE documentation.