Service Graph Template

Location in GUI: Tenants » XXX » Services » L4-L7 » Service Graph Templates

Diagram

Classes

services (apic.tenants)

Name	Type	Constraint	Mandatory	Default Value
service_graph_templates	List	`[service_graph_templates]`	No

service_graph_templates (apic.tenants.services)

Name	Type	Constraint	Mandatory	Default Value
name	String	Regex: `^[a-zA-Z0-9_.:-]{1,64}$`	Yes
ndo_managed	Boolean	`true`, `false`	No	`false`
alias	String	Regex: `^[a-zA-Z0-9_.:-]{1,64}$`	No
description	String	Regex: `^[a-zA-Z0-9\\!#$%()*,-./:;@ _{\|}~?&+]{1,128}$`	No
template_type	Choice	`FW_TRANS`, `FW_ROUTED`, `ADC_ONE_ARM`, `ADC_TWO_ARM`, `OTHER`, `CLOUD_NATIVE_LB`, `CLOUD_VENDOR_LB`, `CLOUD_NATIVE_FW`, `CLOUD_VENDOR_FW`	No	`FW_ROUTED`
redirect	Boolean	`true`, `false`	No	`false`
share_encapsulation	Boolean	`true`, `false`	No	`false`
device	Class	`[device]`	Yes
consumer	Class	`[consumer]`	No
provider	Class	`[provider]`	No

device (apic.tenants.services.service_graph_templates)

Name	Type	Constraint	Mandatory
name	String	Regex: `^[a-zA-Z0-9_.:-]{1,64}$`	Yes
tenant	String	Regex: `^[a-zA-Z0-9_.:-]{1,64}$`	No
node_name	String	Regex: `^[a-zA-Z0-9_.:-]{1,64}$`	No

consumer (apic.tenants.services.service_graph_templates)

Name	Type	Constraint	Mandatory	Default Value
direct_connect	Boolean	`true`, `false`	No	`false`

Examples

Example 1: This example creates a Service Graph template that offers a high-level, reusable framework for defining and deploying service chains for L3 devices (also known as Routed mode). The service graph will be a Layer 3 graph towards as the type is defined as FW_ROUTED allowing traffic redirect (redirect: true). Also, it is not sharing encapsulation across all connectors for the function node (share_encapsulation: false).

A Device Selection Policy can be used to specify the particular instantiation details generated when the template is applied to a contract.

The data model can be applied as is; however, if the referenced L4-L7 Device is not included (listed as FW), the deployment will not function correctly. The FW device referenced in this example is located in the following module:

apic.tenants.services.l4l7_devices

apic:
  tenants:
    - name: PBR_ServGraph
      services:
        service_graph_templates:
          - name: PBR_SG_template
            description: This is a PBR SG template
            template_type: FW_ROUTED
            redirect: true
            share_encapsulation: false
            device:
              name: FW
              node_name: FW_Cluster

Simple example:

apic:
  tenants:
    - name: ABC
      services:
        service_graph_templates:
          - name: TEMPLATE1
            redirect: true
            device:
              name: DEV1

Full example:

apic:
  tenants:
    - name: ABC
      services:
        service_graph_templates:
          - name: TEMPLATE1
            alias: TEMPLATE1-ALIAS
            description: My Desc
            template_type: FW_ROUTED
            redirect: true
            share_encapsulation: false
            device:
              tenant: ABC
              name: DEV1
            consumer:
              direct_connect: false
            provider:
              direct_connect: true