Congratulations on choosing CSO for SD-WAN, Hybrid WAN, Cloud CPE, and NFV lifecycle management. This guide is designed to help you create:
The following types of configuration templates
Device templates, which offer stage 2 or post-initialization configuration settings for physical devices.
Templates that define the settings you can configure for a virtualized network function (VNF) in a network service.
Virtualized network function (VNF) packages with Resource Designer
Network services with Network Service Designer
Click the online Help (?) links for additional information, or refer to the Designer Tools Help Center.
You use Configuration Designer to create a configuration template. Before you design a configuration template, you create a request to track the requirements for the template.
To create a configuration template request:
A new configuration template request is created.
This task describes how to design a configuration template with a data model. You can alternatively design a configuration template with a working configuration.
To design a configuration template with your own data model:
The configuration template wizard appears with the Data Model Schema page displayed.
The data model schema defines the VNF.
The Jinja Template page is displayed.
The Jinja template is specific to the VNF and contains variables or expressions which are replaced with values when the template is rendered.
The configuration template wizard automatically generates a UI Builder page with view definitions based on your data model schema. The fields on this page map to the parameters in the configuration template and are read-only.
The Validate Template page appears.
A configuration template is generated using the values that you entered.
The Summary page is displayed.
To publish a configuration template:
The Designs page appears. All the configuration templates are displayed in a table.
The status of the template is Validated.
Your configuration template is published and available in Contrail Service Orchestration (CSO). Its status changes from Validated to Published.
If you are designing a device template, you can now view the template in Administration Portal.
If you are designing a VNF package, you can view the template in Resource Designer.
You create a VNF package with Resource Designer. Before you design a VNF package, you create a request to track the requirements for it.
To create a request for a VNF package:
A new VNF package request is created.
The information that you need to design a VNF package for a software application is specific to that application. You must use the documentation for the application to determine how it initializes and functions in the network. You specify that information when you design the VNF package.
To design a VNF package:
You see the requests that you have created.
The VNF package wizard appears with the Basic Information page displayed.
Note You must provide values for all the fields on this page.
Name of the VNF package that appears in Network Service Designer
VNF Manager
Name—Name of the VNF manager
Admin name—Username for logging in to the VNF manager
Password—Password for logging in to the VNF manager
Plug in—Type of plug-in that the VNF manager uses to manage the VNF
Built-in—CSO plug-in
External—Proprietary plug-in
Plug in name—Name of the plug-in
The deployment type:
vCPE—VNF is for use in a service provider cloud
uCPE—VNF is for use on a CPE device
Configuration templates specific to the VNF for
Basic—Information about the container in which the VNF resides.
Bootstrap—Information that the VNF uses when it initiates.
Networking—Information that enables the VNF to manage network traffic, such as information about interfaces or IP addresses..
The attributes that apply to the VNF—select all that apply. CSO uses these attributes to orchestrate the VNF..
SRIOV-DATA—Supports single-root I/O virtualization (SR-IOV) data interfaces for the container in which the VNF resides. This option works with the basic template that you specify.
SRIOV-MGMT—Supports SR-IOV management interfaces for the container in which the VNF resides. This option works with the basic template that you specify.
CDROM-Bootstrapping—Supports initialization of the VNF from a CD-ROM image. The CPE device treats the bootstrap configuration template as a CD-ROM image and initializes the VNF from that image.
UserData-Bootstrapping—Supports initialization of the VNF through Cloudinit. The CPE device treats the bootstrap configuration image as a Cloudinit image to initialize the VNF.
MGMT-VLAN-Tagged-Traffic—Supports VLAN tagged traffic and its management interfaces in conjunction with the networking configuration template that you specify.
DATA-VLAN-Tagged-Traffic—Supports VLAN tagged traffic and its data interfaces in conjunction with the networking configuration template that you specify.
Transparent-mode—Supports filtering of packets that traverse the VNF without modifying any of the source or destination information in the IP packet headers. This option works with the networking configuration template that you specify.
L3-mode—Enables Layer 3 networking for the VNF using the networking configuration template that you specify.
Direct-OAM-Reachability—Requires Operation, Administration, and Maintenance (OAM) access for management. You must select this option for any third-party VNF packages that you create.
One or more package flavors, which specify the required resources. A higher performance VNF package, such as a Gold flavor, typically uses more resources.
The Supported Function page is displayed.
The Supported Functions Chain page is displayed.
You specify a configuration template that you created in Configuration Designer for a particular VNF.
These values are displayed in Network Service Designer and used to evaluate the performance specification of a network service that you create for your customers.
The service chain is created and displayed in the same page.
The Summary page is displayed.
To publish a VNF package to the Network Service Designer.
The VNF Package Designs page appears. All the VNF packages are displayed in a table.
You can publish VNF packages with the state Validated.
Your VNF package is published and available in Network Service Designer. The status of the package changes from Validated to Published.
You use Network Service Designer to create network services and publish them to the network service catalog. When you publish a network service, you can see the service in Administration Portal.
To create a request for a network service:
The Network Service Designer Requests page is displayed.
The requests wizard appears with the Request Information page displayed.
The Service Chain and Design Goals page appears, displaying the Goals area, the Functional Service Design area, and the Function Palette.
For a centralized deployment, drag and drop the required functions in the required order for the service from the Function Palette to the Functional Service Design area.
For a distributed deployment, drag and drop the network functions from the Function Palette to the appropriate section on the service chain structure in the Functional Service Design area.
The Summary page appears, displaying the details you entered for the request.
The request for the network service design appears on the Requests page.
To design a service chain for a centralized deployment model:
The Requests page appears, displaying the open requests.
The Build page displays the requested network functions and the goals.
The VNF catalog at the bottom right of the page updates to show only the VNFs that provide this function.
The function appears inside the VNF image.
The Performance Goals pane updates to indicate how the network service design meets the customer goals.
The Vendor catalog at the bottom right of the page updates to show only the VNFs that provide this function, and, If a VNF in the Network Service Design workspace supports this function, a faded image of the function appears inside the VNF image.
To implement this function with the same VNF, click the faded image in the VNF image.
To implement this function with a different VNF, drag the VNF from the Vendor catalog to the Network Service Design workspace.
The Performance Goals pane again updates to indicate how the network service design meets the customer goals.
The network service is published to the network service catalog and you can see it in Administration Portal.
To design a service chain for a distributed deployment model:
The Requests page appears, displaying the open requests.
The Build page displays the service chain with the requested network functions, ingress and egress points, direction of traffic flow, and the goals for the network service.
The VNF catalog at the bottom right of the page updates to show only the VNFs that provide this function.
The function appears inside the VNF image, and the Performance Goals widget updates to indicate how the network service design meets the customer goals.
The network service is published to the network service catalog and you can see it in Administration Portal.
Creating Requests for Configuration Templates
Designing Templates with a Configuration
Publishing Configuration Templates
Creating Requests for VNF Packages
Designing VNF Packages
Publishing VNF Packages
Creating Requests for Network Services
Designing Network Services
Publishing Network Service Designs
Creating Requests for Configuration Templates
Designing Templates with a Configuration
Publishing Configuration Templates
Creating Requests for VNF Packages
Designing VNF Packages
Publishing VNF Packages
Creating Requests for Network Services
Designing Network Services
Publishing Network Service Designs