Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add a Resource Instance

You can create a resource instance based on the corresponding resource design and configure the resources available in the resource pool to provision a service. After you add a resource instance and configure the resource pool for the instance, you can save and commit the instance. When you save and commit a resource instance, Paragon Automation activates a workflow run to upload the resource instance to the database. You can monitor the workflow execution state by viewing the workflow run details.

To add a resource instance:

  1. Click Orchestration > Resource Instances.
    The Resource Instances page appears.
  2. Click the add (+) icon above the Resource Instances table.
    The Add New Resource Instance page appears.
  3. Enter the values for instance name and customer name, and select a resource design by referring to Table 1.
  4. Do one of the following:
    • Click Create.

      A template of the resource instance based on the corresponding resource design is created. The instance name is listed in the Resource Instances table. You are directed to the Modify Resource-Instance-Name page, which displays the following panes:

      • The Resource Editor on the left pane.

      • The resource Inventory in JSON format on the right pane.

        The inventory lists all network resources associated with the current resource instance, that are available in the Paragon Automation database. You can expand or collapse the sections to view resource configuration details.

    • Click Close to discard your changes and exit the page. To restart the process, go to 1.

  5. Configure the network resource pools as described in Configure Resource Pools for Resource Instances.
  6. Click Proceed to save the resource instance configuration.
    The Compare Resource Definition page appears.
  7. Click Save and Commit.
    A service order is created and the Monitor order status page appears and displays the execution status of the service order. The resource instance is first saved and then committed.
  8. (Optional) If the service order commit fails, you can navigate to the workflow-ID page to debug and fix the issue.
  9. Click OK.
    The Resource Instances page appears and displays the newly added resource instance,
Table 1: Fields on the Add New Resource Instance Page

Field

Description

Instance Name

The name of the resource instance. For example, vpn1.

Customer

The name of the customer for whom you are creating the resource instance.

A resource instance is created for a customer to define the available network resources and to allocate these resources when provisioning a VPN service for the customer.

To add a new customer, click the Add Customer link. See Add a Customer.

Note:

The default customer name is set as network-operator.

Resource Design

Paragon Automation provides the following resource designs:

  • Topology—The topology resource design provides guidelines to create topology resource pools for L3VPN or EVPN services.

  • VPN—The VPN resource design provides guidelines to create VPN resource pools for L3VPN, EVPN, or L2 Circuit services.

  • Routing—The routing resource design provides guidelines to create routing resource pools for infrastructure service.

  • L3-Addr—The Layer 3 resource design provides guidelines to create Layer 3 resource pools for infrastructure service.

  • L2-Addr—The Layer 2 resource design provides guidelines to create Layer 2 resource pools for infrastructure service.