Configuration Templates Overview

Contrail Service Orchestration (CSO) offers a fully automated, end-to-end provisioning of customer premises equipment (CPE) devices. CSO utilizes configuration templates to provision parameters to enable the onboarding and configuration of Juniper Networks devices throughout the device lifecycle. Configuration templates (referred to as stage-2 templates in releases before CSO Release 5.1.0) also enable you to deploy customized configurations on devices that are managed by CSO. In short, configuration templates enable you to make configuration changes to Juniper devices by using the CSO GUI.

Configuration changes can be of two types:

• Global, which refers to configurations are common to all devices; for example, syslog or SNMP settings.

• Device-specific, which refers to configurations are unique for each device; for example, BGP configuration.

You can use configuration templates to push global (common) configurations to all devices or to specific devices.

By default, CSO provides predefined configuration templates that are pre-assigned to device templates. You can also create your own templates by importing a template, cloning a template and modifying its settings, or adding a template. Templates can be created by users with different roles. The availability of the templates is determined by the role of the user who created the template:

• Templates created by the SP Administrator (CSO on-premises version) users, are available to operating companies (OpCos), the OpCo’s tenants, and the SP Administrator’s tenants.

• Templates created by the OpCo Administrator users are available only to the OpCo and the OpCo’s tenants.

• Templates created by the Tenant Administrator users are available only to the tenant.

You can either attach (assign) a configuration template to a device template, which enables the configuration to be deployed on devices which use that device template, or you can deploy a configuration template directly on a device.