- play_arrow Introduction
- play_arrow Overview
- play_arrow Access and Manage Paragon Automation Account
-
- play_arrow Administration
- play_arrow Introduction
- play_arrow Organization Management
- play_arrow Site Management
- play_arrow User Management
- play_arrow Inventory Management
- play_arrow Audit Logs
-
- play_arrow Device Life Cycle Management
- play_arrow Introduction
- play_arrow Day-Wise Activities for Device Life Cycle Management
- play_arrow Field Technician User Interface
- play_arrow Onboarding Profiles
- play_arrow Plan Device Onboarding
- play_arrow View Device Onboarding
- play_arrow Device Management
- Device Management Workflow
- Device Licenses Overview
- About the Features Tab
- About the Licenses Tab
- Manage Device Licenses
- About the Software Images Page
- Upload a Software Image
- Delete a Software Image
- About the Configuration Backups Page
- Configuration Templates Overview
- About the Configuration Templates Page
- Add a Configuration Template
- Edit and Delete a Configuration Template
- Preview a Configuration Template
- Deploy a Configuration Template to a Device
-
- play_arrow Observability
- play_arrow Introduction
- play_arrow Troubleshoot Devices
- play_arrow View Network Topology
-
- play_arrow Trust and Compliance
- play_arrow Introduction
- play_arrow Manage Trust Settings and Trust Scores
- Compliance Standards Overview
- About the Compliance Benchmarks Page
- About the Compliance Tailorings Page
- Example: Create a Tailoring Document for NTP Settings
- About the Compliance Checklist Page
- Add a Checklist Template
- Add Checklist for a Device
- Import Scans and Update Rule Results in a Checklist
- Trust Plans Overview
- About the Network Score Formula Page
- Trust Score Overview
- About the Network Score Page
- About the Snapshots Page
- Add a Snapshot for a Target
- play_arrow Manage Compliance Scans
- play_arrow Manage Vulnerabilities
- play_arrow Monitor Integrity
-
- play_arrow Active Assurance
- play_arrow Introduction
- play_arrow Test Agents
- play_arrow Tests and Monitors
-
- play_arrow Paragon Shell CLI Reference
- play_arrow Introduction
- play_arrow Operational Mode Commands
- file copy
- monitor
- request paragon backup
- request paragon cluster pods reset
- request paragon cluster upgrade
- request paragon config
- request paragon deploy
- request paragon deploy cluster
- request paragon destroy cluster
- request paragon fix-permission
- request paragon load
- request paragon repair-node
- request paragon replace-node
- request paragon restore
- request paragon running-config
- request paragon ssh
- request paragon ssh-key
- request paragon storage cleanup
- request paragon super-user password reset
- request system decrypt password
- request system reboot
- show configuration paragon cluster
- show host disk usage
- show paragon backup
- show paragon certificate expiry-date certificate-type
- show paragon cluster
- show paragon cluster details
- show paragon cluster namespaces
- show paragon cluster nodes
- show paragon cluster pods
- show paragon cluster pods namespace healthbot sort
- show paragon images version
- show paragon images version namespace
- show paragon pvc details
- show paragon version
- play_arrow Configuration Mode Commands
- delete paragon cluster
- load set
- set paragon cluster applications
- set paragon cluster common-services ingress
- set paragon cluster install
- set paragon cluster mail-server
- set paragon cluster nodes
- set paragon cluster ntp
- set paragon cluster papi
- set paragon cluster victoria-metrics
- set paragon monitoring
- set system login
- play_arrow Troubleshooting Commands
- Troubleshoot Using the Paragon Shell CLI Commands
- request support information
- request paragon troubleshooting information
- request paragon debug
- request paragon debug get-tsdb-data
- request paragon debug insights-kafka-data
- request paragon debug kafka
- request paragon debug logs
- request paragon debug logs namespace
- request paragon debug postgres
- request paragon debug redis
- play_arrow Service Orchestration
- About the Service Orchestration cMGD CLI
- set foghorn:core org-id
- set service design default version
- show service order status
- show service order as-json
- show service order as-yaml
- show service designs
- show device dependant configuration
- show insights configuration
- show configuration foghorn:customers
- request service project add
- request service orders sync
- request network resources load
- request service order upload
- request service order place
- request service order modify
- request service order delete
- request service order submit
- request service order provision
- request service design install
- request service design uninstall
-
ON THIS PAGE
About the Service Designs Page
The Service Designs page is an inventory of service designs that Paragon Automation provides for provisioning services. The page lists service designs for different services such as L3VPN, to be provisioned in a network. The service designs are listed by name, service type, version number, number of active instances, and so on. Paragon Automation allows you to provision up to three concurrent versions of a service design in a network. One of the three versions is set as the default version.
You must be a Super User to manage the service design catalog. Network Admins and Observers have read-only access to the inventory.
To access the Service Designs page, click Orchestration > Service Catalog on the navigation menu.
Tasks You Can Perform
You can perform the following tasks on the Service Designs page:
View service design details
To view details of a service design, do any of the following:
Hover over the service design and click the Details icon that appears next to the design name.
Select the design and click More > Show Detail.
The service-design-name pane appears on the right side of the Service Catalog page. On the service-design-name pane, you can view general information about the service design and details of other service designs that this service design depends on. See Table 2 and Table 3.
View the service instances associated with a service design.
To see details of the service instances of a service design, click the service-design-name hyperlink. You are directed to the Service Instances page, where the service design name is used as a filter to display the service instances associated with the design.
Set the default version of a service design
The Service Designs page lists up to three versions of a service design. One of the three versions is set as the default version and is marked as (Default) in the Service Designs table, next to the version number. Any service instance you create, modify, or delete is associated with the default service design. To change the default version for a service design:
Select the service design version you want to set as the default version.
Note:You must select a version that is not listed as default in the table.
Click the Set Default Version button and click Yes to confirm.
You see a message that the default version is successfully changed. The table automatically refreshes to display the updated service design default version.
Show or hide columns in the table or reset page preferences, using the vertical ellipsis menu.
Field Descriptions
Table 1 lists the fields on the Service Designs page.
Field | Description |
|---|---|
Name | Name of the service design. |
Service Type | The type of service that the service design provides guidelines for:
|
Version | Version number of the Service design. |
Created time | Date and time when the service design was created. |
Created by | Name of the user who created the service design. |
# Active Instances | Number of active service instances associated with the design. |
Description | Brief description about the service design, if any. |
Field | Description |
|---|---|
Name | Name of the service design. |
Service Type | Type of service for which the service design provides guidelines.
|
Version | Version of the service design. |
Release Notes | Summary of service design enhancements and bug fixes. Hover over the value of this field to view the summary of enhancements. |
Field | Description |
|---|---|
Name | Name of service design on which the current service design depends. For example, VPN service design on which the L3VPN service design depends. |
Service Type | Service type offered bythe service design on which the current service design depends. For example, network resource service type for VPN service design on which the L3VPN service design depends. |
Version | Version of the service design on which the current service design depends. |
