Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
Expand All close
Expand All close
list Table of Contents
file_download PDF
{ "lCode": "en_US", "lName": "English", "folder": "en_US" }
English
 

Resource Designer Overview

date_range 18-Jun-18

Configuration Designer, Resource Designer, and Network Service Designer are visual designer tools used by the Juniper Networks Contrail Service Orchestration (CSO) for smooth onboarding. The designer tools offer network designers a convenient way of bringing virtualized network functions (VNFs) from Juniper Networks and third-party companies into the network services catalog using a graphical user interface (GUI).

Resource Designer provides an intuitive GUI-based workflow that guides administrators as they provide the required information to create a VNF package. Resource Designer also validates the created VNF package before it is published to Network Service Designer. Network Service Designer uses VNF packages to design customized network services that are published to the network services catalog, which contains a list of usable network services.

Service provider administrators access the network services catalog to assign a set of network services to their customers using the Administration Portal. Finally, customer administrators access the network services assigned to them using a Customer Portal to manage their sites and services. Figure 1 shows a Resource Designer workflow.

Figure 1: Resource Designer Workflow
Resource Designer
Workflow

As a system integrator or a service provider, you can use Resource Designer to create and onboard a VNF package that can be used for defining network services. A VNF package is a set of metadata or templates designed for a specific vendor’s VNF. Each VNF has its own combination of resources and performance characteristics. Having access to different levels of VNF packages can help you to design specific service-level agreements (SLAs) for your services. You can assign resources to VNFs using your vendor’s data sheets as a basis.

A typical VNF package might include:

  • VNF base configuration template—A configuration template can be created in Configuration Designer:

    • To ensure correct startup and ongoing manageability of the VNF

    • For management IP, SNMP, and system log configuration of the VNF

  • VNF descriptor (VNFD)—A deployment template that describes a VNF in terms of its deployment and operational behavior requirements. VNFD is mainly used during the instantiation of a VNF and for lifecycle management of a VNF instance. It includes the following properties:

    • Connection points—Represents the management interface, left interface, and right interface. Connections points are used to connect the virtual links.

    • Virtual links—Represents the management network link, left network link, and right network. Virtual links provide connectivity between VDUs.

    • Virtual deployment units (VDUs) and a topology showing how the VDUs are connected—VDUs are basic part of VNFs. VDUs are used to host the network function.

    • Allocated CPU and memory

    • Required storage

    • Names and types of VNF images

    • Deployment flavors—A differentiated option such as Gold, Silver, or Bronze with an appropriate SLA metric.

    • VNF auto-scale policies

  • VNF Manager plug-in—A plug-in type and name. For example, a VNF Manager for VNF lifecycle management.

  • Supported function chains—Sequences of network functions, such as firewall, NAT, or WAN optimization, that the VNF packages offers.

Some VNFs, like vSRX, support multiple functions and service chains. For example, vSRX can be deployed in the context of multiple functions such as firewalls, carrier-grade NAT, IDP, UTM, malware, and others.

footer-navigation