Import Configuration Templates
In Administration Portal, users with the SP (Service Provider) Administrator role (on-premises installation only) or OpCo (Operating Company) Administrator role can import a configuration template by specifying the parameters using a configuration template file (Jinja template language), Yang model file (schema for the configuration), and the Viewdef file (configuration of the UI).
In CSO releases before Release 5.1.0, configuration templates are called stage-2 configuration templates.
To import a configuration template:
If the configuration template is imported successfully, you can validate the configuration template by using the Preview workflow and then assign the configuration template to a device template or deploy it on a device.
Setting |
Guideline |
---|---|
Template Name |
Enter a unique name that can only contain alphanumeric characters and hyphens; 64-character maximum. |
Description |
Enter a description for the configuration template. |
Output Config Format |
Select the output configuration format for the template:
|
Device Family |
Select the device family for which you are adding the template; for example, juniper-nfx. |
Configuration Template File |
Specify the file containing the configuration (in Jinja Template language syntax) by clicking the Browse button to navigate to the directory where the configuration template file is located and selecting the file. |
Yang Model File |
Specify the Yang data model (configuration schema) file by clicking the Browse button to navigate to the directory where the Yang model file is located and selecting the file. |
Viewdef File |
Specify the Viewdef file, which contains the configuration for the UI, by clicking the Browse button to navigate to the directory where the Viewdef file is located and selecting the file. |