Upload a Custom Service Design

You use a service design to add and provision a service in the network. Routing Director allows you to upload custom service designs and use them to provision corresponding services in the network.

Custom service designs can be created in two ways:

Create a new custom service design from scratch—A custom service design can be designed specifically for your use case and tailored for requirements that are not met by existing designs. You have flexibility in designing workflow, configuration, and user interface to suit your requirements.

Leverage and customize an existing service design—A leveraged custom service design, reuses an existing service design, inherits the workflow, configuration, and user interface of the base service design, and eliminates the need to build it from scratch. The existing service designs offered by Routing Director are L3VPN, E-LAN EVPN CSM, E-Line EVPN VPWS CSM, and E-Line L2 Circuit NSM, which can be customized and used to provision L3VPN, EVPN, EVPN-VPWS, and L2 circuit services, respectively.

To create and customize a service design, you must contact Juniper Networks Professional Services. The Juniper Networks Professional Services team provides you with a custom service design file in the .tgz format. Additionally, they will also provide you with common.tgz and network-resource.tgz files with corresponding configurations that map to the custom service design.

To upload the customized service design to the GUI (Orchestration > Service > Service Catalog), perform the following steps:

1. Log in to the Deployment Shell CLI as the root user.

2. Type exit to exit Deployment Shell to the Linux root shell.

3. Start a cMGD pod using the following command:

4. Launch the service orchestration cMGD CLI bash shell using the following command:

   You are now logged in to the service orchestration cMGD CLI bash shell.

5. Copy the custom service design file and the dependent files required to upload a custom service design to the /data-models/projects folder in the service orchestration cMGD CLI.

   In this topic, we refer to a custom service design file CSD.tgz .

   Copy the CSD.tgz file as well as the common.tgz and network-resource.tgz files to the /data-models/projects folder. The common.tgz and network-resource.tgz files are the dependency files.

6. Type cli and press Enter to launch the CLI mode.

7. View organizations available in Routing Director to add the custom service design.

   Where:

   Org-Name is the name of the organization created in Routing Director.

   Org-ID is the unique auto-generated alphanumeric ID assigned to the organization.

8. Enter the configuration mode.

9. Configure the organization ID to set the context of all tasks required to add the custom service design.

   Where:

   cd71dd08-72bb-4697-b516-655de87f69c6 is the unique Org-ID.

10. Commit the changes and exit the configuration mode.

11. Add projects to the service catalog for all organizations. Projects contain a service design and its dependency files required to provision a service.

    1. Add common files to the service catalog. Common files are reusable components required by multiple service designs.

       Where common.tgz file contains common files that includes standard YANG models, Jinja templates, third-party schemas, shared JQS, party files, standard ITEF templates, YANG models, and so on.

    2. Add network resource configuration files to the service catalog. The network resource file contains network resource service designs that acts as producers of shared resources and are consumed by service designs.

       Where network-resource.tgz file contains definitions of network elements such as IP address pools, VLAN IDs, VPN route distinguishers, and so on.

    3. Add your custom service design to the service catalog.

12. Verify the projects that you added to the service catalog using the following command:

    Where:
    Project Name displays the names of projects that you added to the service catalog.

    Project ID displays the unique ID assigned to different projects available in the service catalog.

13. Install all the files that you added to the service catalog using the following command:

14. This command may take some time to complete.

    A warning message confirms a successful update. Restart the CLI to complete installation of the new version. Confirm Yes, when prompted.

15. Now the customized service design is installed and must be available in the GUI.

    For customized service designs based on existing service designs, the user interface and workflow remain the same as those of the original service design.

    Log in again to the Routing Director GUI and the newly installed service design version 0.0.1 must be listed as Default under the Version column on the Service Designs page (Orchestration > Service Catalog). For more information, see About the Service Designs Page.

    You can create and provision a service based on the service design that you added. The Add drop-down on the Service Instances page (Orchestration > Service Instances) displays the name of the service design that you installed. Select the service design to create a corresponding service instance. For more information, see About the Service Instances Page.