User documentation for yang module vlr.yang

module rw-project                                                            1
  rw-project data                                                          1.1
    list rw-project:project                                              1.1.1
      container rw-project:project-config                              1.1.1.1
        list rw-project:user                                         1.1.1.1.1
          list rw-project:role                                     1.1.1.1.1.1
      container rw-project:project-state                               1.1.1.2
        list rw-project:user                                         1.1.1.2.1
          list rw-project:role                                     1.1.1.2.1.1
        list rw-project:role                                         1.1.1.2.2
      container vlr:vlr-catalog                                        1.1.1.3
        list vlr:vlr                                                 1.1.1.3.1
          container vlr:provider-network                           1.1.1.3.1.1
          container vlr:ip-profile-params                          1.1.1.3.1.2
            list vlr:dns-server                                  1.1.1.3.1.2.1
            container vlr:dhcp-params                            1.1.1.3.1.2.2
module vlr                                                                   2


1  module rw-project

1.1  rw-project data
  Description
    This yang module defines project-based tenancy for RIFT.ware.
    Authorization for project access is defined in terms of RIFT.ware's
    Role-Based Access Control (RBAC) model.

1.1.1  list rw-project:project
  Description
    Configuration and state for individual projects.  RIFT.ware
    applications and projects are expected to augment this list in
    order to add configuration for projects that is specific to the
    product or application.  As such, this list contains minimal
    data defined in this yang module.

    When augmenting this element, other yang modules should prefer to
    define containers with the same name as the augmenting module.
    (Augmenting RIFT.ware modules should prefer to augment without
    the rw prefix [for new features], or should prefer to augment the
    augmented container of an existing augment, to ease future
    adoption and/or standardization.)
  Leaves
    name: name, type: STRING, description: Name of the project.
    name: description, type: STRING, description: Information about project
  XPath Path
    /rw-project:project
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']
  RW.REST URI Path
    /rw-project:project/STRING
  JSON Config Sample
    [
      {
        "name": "STRING",
        "description": "STRING",
        "project-config": {
          "user": [ { ... }, { ... } ]
        }
      }, {
        ...
      }
    ]
  JSON Sample
    [
      {
        "name": "STRING",
        "description": "STRING",
        "project-config": {
          "user": [ { ... }, { ... } ]
        },
        "project-state": {
          "user": [ { ... }, { ... } ],
          "role": [ { ... }, { ... } ]
        },
        "vlr:vlr-catalog": {
          "schema-version": "v3.0",
          "vlr": [ { ... }, { ... } ]
        }
      }, {
        ...
      }
    ]
  XML Config Sample
    <rw-project:project xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:name>STRING</rw-project:name>
      <rw-project:description>STRING</rw-project:description>
      <rw-project:project-config>
        <rw-project:user>...</rw-project:user>
      </rw-project:project-config>
    </rw-project:project>
  XML Sample
    <rw-project:project xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:name>STRING</rw-project:name>
      <rw-project:description>STRING</rw-project:description>
      <rw-project:project-config>
        <rw-project:user>...</rw-project:user>
      </rw-project:project-config>
      <rw-project:project-state>
        <rw-project:user>...</rw-project:user>
        <rw-project:role>...</rw-project:role>
      </rw-project:project-state>
      <vlr:vlr-catalog xmlns:vlr="urn:ietf:params:xml:ns:yang:nfvo:vlr">
        <vlr:schema-version>v3.0</vlr:schema-version>
        <vlr:vlr>...</vlr:vlr>
      </vlr:vlr-catalog>
    </rw-project:project>

1.1.1.1  container rw-project:project-config
  Description
    General Project configuration supported by all products.
  XPath Path
    /rw-project:project/rw-project:project-config
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/rw-project:project-config
  RW.REST URI Path
    /rw-project:project/STRING/project-config
  JSON Config Sample
    {
      "user": [
        {
          "user-domain": "STRING",
          "user-name": "STRING",
          "role": [ { ... }, { ... } ]
        }, {
          ...
        }
      ]
    }
  JSON Sample
    {
      "user": [
        {
          "user-domain": "STRING",
          "user-name": "STRING",
          "role": [ { ... }, { ... } ]
        }, {
          ...
        }
      ]
    }
  XML Config Sample
    <rw-project:project-config xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:user>
        <rw-project:user-name>STRING</rw-project:user-name>
        <rw-project:user-domain>STRING</rw-project:user-domain>
        <rw-project:role>...</rw-project:role>
      </rw-project:user>
    </rw-project:project-config>
  XML Sample
    <rw-project:project-config xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:user>
        <rw-project:user-name>STRING</rw-project:user-name>
        <rw-project:user-domain>STRING</rw-project:user-domain>
        <rw-project:role>...</rw-project:role>
      </rw-project:user>
    </rw-project:project-config>

1.1.1.1.1  list rw-project:user
  Description
    The list of Users who have been assigned Roles within this
    Project.
  Leaves
    name: user-domain, type: LEAFREF, description: The user domain.  This is the source of the user identity.
    Different domains may duplicate a user-name, but such users
    would be considered distinct by RIFT.ware.
    name: user-name, type: LEAFREF, description: The user name.  The syntax of this name depends on the domain.
    For example, if the domain is a login name, it might be limited
    to alphanumeric characters.  However, if the domain is email address,
    the syntax could include additional characters, such as the at(@) sign.
  XPath Path
    /rw-project:project/rw-project:project-config/rw-project:user
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/rw-project:project-config/rw-project:user[rw-project:user-name='STRING'][rw-project:user-domain='STRING']
  RW.REST URI Path
    /rw-project:project/STRING/project-config/user/STRING,STRING
  JSON Config Sample
    [
      {
        "user-domain": "STRING",
        "user-name": "STRING",
        "role": [
          {
            "role": "STRING"
          }, {
            ...
          }
        ]
      }, {
        ...
      }
    ]
  JSON Sample
    [
      {
        "user-domain": "STRING",
        "user-name": "STRING",
        "role": [
          {
            "role": "STRING"
          }, {
            ...
          }
        ]
      }, {
        ...
      }
    ]
  XML Config Sample
    <rw-project:user xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:user-name>STRING</rw-project:user-name>
      <rw-project:user-domain>STRING</rw-project:user-domain>
      <rw-project:role>
        <rw-project:role>STRING</rw-project:role>
      </rw-project:role>
    </rw-project:user>
  XML Sample
    <rw-project:user xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:user-name>STRING</rw-project:user-name>
      <rw-project:user-domain>STRING</rw-project:user-domain>
      <rw-project:role>
        <rw-project:role>STRING</rw-project:role>
      </rw-project:role>
    </rw-project:user>

1.1.1.1.1.1  list rw-project:role
  Description
    The list of Roles the User has been assigned.
  Leaves
    name: role, type: STRING, description: The Role, independent of Keys.
  XPath Path
    /rw-project:project/rw-project:project-config/rw-project:user/rw-project:role
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/rw-project:project-config/rw-project:user[rw-project:user-name='STRING'][rw-project:user-domain='STRING']/rw-project:role[rw-project:role='STRING']
  RW.REST URI Path
    /rw-project:project/STRING/project-config/user/STRING,STRING/role/STRING
  JSON Config Sample
    [
      {
        "role": "STRING"
      }, {
        ...
      }
    ]
  JSON Sample
    [
      {
        "role": "STRING"
      }, {
        ...
      }
    ]
  XML Config Sample
    <rw-project:role xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:role>STRING</rw-project:role>
    </rw-project:role>
  XML Sample
    <rw-project:role xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:role>STRING</rw-project:role>
    </rw-project:role>

1.1.1.2  container rw-project:project-state
  Description
    General Project operational state supported by all products.
  XPath Path
    /rw-project:project/rw-project:project-state
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/rw-project:project-state
  RW.REST URI Path
    /rw-project:project/STRING/project-state
  JSON Sample
    {
      "user": [
        {
          "user-domain": "STRING",
          "user-name": "STRING",
          "role": [ { ... }, { ... } ]
        }, {
          ...
        }
      ],
      "role": [
        {
          "role": "STRING",
          "description": "STRING"
        }, {
          ...
        }
      ]
    }
  XML Sample
    <rw-project:project-state xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:user>
        <rw-project:user-name>STRING</rw-project:user-name>
        <rw-project:user-domain>STRING</rw-project:user-domain>
        <rw-project:role>...</rw-project:role>
      </rw-project:user>
      <rw-project:role>
        <rw-project:role>STRING</rw-project:role>
        <rw-project:description>STRING</rw-project:description>
      </rw-project:role>
    </rw-project:project-state>

1.1.1.2.1  list rw-project:user
  Description
    The state of Users who have been assigned Roles within
    this Project.
  Leaves
    name: user-domain, type: STRING, description: The user domain.  This is the source of the user identity.
    Different domains may duplicate a user-name, but such users
    would be considered distinct by RIFT.ware.
    name: user-name, type: STRING, description: The user name.  The syntax of this name depends on the domain.
    For example, if the domain is a login name, it might be limited
    to alphanumeric characters.  However, if the domain is some
    kind of email address, the syntax could include assitional
    characters, such as the at sign.
  XPath Path
    /rw-project:project/rw-project:project-state/rw-project:user
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/rw-project:project-state/rw-project:user[rw-project:user-name='STRING'][rw-project:user-domain='STRING']
  RW.REST URI Path
    /rw-project:project/STRING/project-state/user/STRING,STRING
  JSON Sample
    [
      {
        "user-domain": "STRING",
        "user-name": "STRING",
        "role": [
          {
            "role": "STRING",
            "state": "STRING"
          }, {
            ...
          }
        ]
      }, {
        ...
      }
    ]
  XML Sample
    <rw-project:user xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:user-name>STRING</rw-project:user-name>
      <rw-project:user-domain>STRING</rw-project:user-domain>
      <rw-project:role>
        <rw-project:role>STRING</rw-project:role>
        <rw-project:state>STRING</rw-project:state>
      </rw-project:role>
    </rw-project:user>

1.1.1.2.1.1  list rw-project:role
  Description
    The state of the Roles the User has been assigned.
  Leaves
    name: role, type: STRING, description: The Role, independent of Keys.
    name: state, type: STRING, description: The assignment of a User to a Role may be an asynchronous
    operation.  This value indicates whether the Role
    assignment is active.  If the value is 'active', then the
    assignment is complete and active.  Any other value
    indicates that Role assignment is in a transitional or
    failed state, as described in the value.
  XPath Path
    /rw-project:project/rw-project:project-state/rw-project:user/rw-project:role
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/rw-project:project-state/rw-project:user[rw-project:user-name='STRING'][rw-project:user-domain='STRING']/rw-project:role[rw-project:role='STRING']
  RW.REST URI Path
    /rw-project:project/STRING/project-state/user/STRING,STRING/role/STRING
  JSON Sample
    [
      {
        "role": "STRING",
        "state": "STRING"
      }, {
        ...
      }
    ]
  XML Sample
    <rw-project:role xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:role>STRING</rw-project:role>
      <rw-project:state>STRING</rw-project:state>
    </rw-project:role>

1.1.1.2.2  list rw-project:role
  Description
    The set of Roles that may be configured into
    /rw-project:project/rw-project:config/rw-project:user/
    rw-project:role.
  Leaves
    name: role, type: STRING, description: The Role, independent of Keys.
    name: description, type: STRING, description: A description of the Role.
  XPath Path
    /rw-project:project/rw-project:project-state/rw-project:role
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/rw-project:project-state/rw-project:role[rw-project:role='STRING']
  RW.REST URI Path
    /rw-project:project/STRING/project-state/role/STRING
  JSON Sample
    [
      {
        "role": "STRING",
        "description": "STRING"
      }, {
        ...
      }
    ]
  XML Sample
    <rw-project:role xmlns:rw-project="http://riftio.com/ns/riftware-1.0/rw-project">
      <rw-project:role>STRING</rw-project:role>
      <rw-project:description>STRING</rw-project:description>
    </rw-project:role>

1.1.1.3  container vlr:vlr-catalog
  Leaves
    name: schema-version, type: STRING, description: Schema version for the VLR. If unspecified, it assumes v3.0
  XPath Path
    /rw-project:project/vlr:vlr-catalog
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/vlr:vlr-catalog
  RW.REST URI Path
    /rw-project:project/STRING/vlr:vlr-catalog
  JSON Sample
    {
      "schema-version": "v3.0",
      "vlr": [
        {
          "id": "STRING",
          "name": "STRING",
          "nsr-id-ref": "STRING",
          "vld-ref": "STRING",
          "res-id": "STRING",
          "short-name": "STRING",
          "vendor": "STRING",
          "description": "STRING",
          "version": "STRING",
          "type": "ELAN",
          "root-bandwidth": 0,
          "leaf-bandwidth": 0,
          "create-time": 0,
          "uptime": 0,
          "network-id": "STRING",
          "vim-network-name": "STRING",
          "provider-network": { ... },
          "ip-profile-params": { ... },
          "status": "LINK_UP",
          "operational-status": "init"
        }, {
          ...
        }
      ]
    }
  XML Sample
    <vlr:vlr-catalog xmlns:vlr="urn:ietf:params:xml:ns:yang:nfvo:vlr">
      <vlr:schema-version>v3.0</vlr:schema-version>
      <vlr:vlr>
        <vlr:id>STRING</vlr:id>
        <vlr:name>STRING</vlr:name>
        <vlr:nsr-id-ref>STRING</vlr:nsr-id-ref>
        <vlr:vld-ref>STRING</vlr:vld-ref>
        <vlr:res-id>STRING</vlr:res-id>
        <vlr:short-name>STRING</vlr:short-name>
        <vlr:vendor>STRING</vlr:vendor>
        <vlr:description>STRING</vlr:description>
        <vlr:version>STRING</vlr:version>
        <vlr:type>ELAN</vlr:type>
        <vlr:root-bandwidth>0</vlr:root-bandwidth>
        <vlr:leaf-bandwidth>0</vlr:leaf-bandwidth>
        <vlr:create-time>0</vlr:create-time>
        <vlr:uptime>0</vlr:uptime>
        <vlr:network-id>STRING</vlr:network-id>
        <vlr:vim-network-name>STRING</vlr:vim-network-name>
        <vlr:provider-network>...</vlr:provider-network>
        <vlr:ip-profile-params>...</vlr:ip-profile-params>
        <vlr:status>LINK_UP</vlr:status>
        <vlr:operational-status>init</vlr:operational-status>
      </vlr:vlr>
    </vlr:vlr-catalog>

1.1.1.3.1  list vlr:vlr
  Leaves
    name: id, type: STRING, description: Identifier for the VLR.
    name: name, type: STRING, description: VLR name.
    name: nsr-id-ref, type: STRING, description: NS instance identifier.
    This is a leafref /rw-project:project/nsr:ns-instance-config/nsr:nsr/nsr:id
    name: vld-ref, type: STRING, description: Reference to VLD
    /rw-project:project/nsr:ns-instance-config/nsr:nsr[nsr:id=../nsr-id-ref]
    /nsd/vld:vld/vld:id
    name: res-id, type: STRING, description: Identifier for resmgr id mapping
    name: short-name, type: STRING, description: Short name to appear as label in the UI
    name: vendor, type: STRING, description: Provider of the VLR.
    name: description, type: STRING, description: Description of the VLR.
    name: version, type: STRING, description: Version of the VLR
    name: type, type: ENUM
    name: root-bandwidth, type: UINT64, description: For ELAN this is the aggregate bandwidth.
    name: leaf-bandwidth, type: UINT64, description: For ELAN this is the bandwidth of branches.
    name: create-time, type: UINT32, description: Creation timestamp of this Virtual Link.
    The timestamp is expressed as seconds
    since unix epoch - 1970-01-01T00:00:00Z
    name: uptime, type: UINT32, description: Active period of this Virtual Link.
    Uptime is expressed in seconds
    name: network-id, type: STRING, description: Identifier for the allocated network resource.
    name: vim-network-name, type: STRING, description: Name of network in VIM account. This is used to indicate
    pre-provisioned network name in cloud account.
    name: status, type: ENUM, description: Status of the virtual link record.
    name: operational-status, type: ENUM, description: The operational status of the Virtual Link
    init                 : The VL is in init stat.
    vl-alloc-pending     : The VL alloc is pending in VIM
    running              : The VL is up  and running in VM
    vl-terminate-pending : The VL is being terminated in VIM.
    terminated           : The VL is terminated in the VM.
    failed               : The VL instantiation failed in VIM.
  XPath Path
    /rw-project:project/vlr:vlr-catalog/vlr:vlr
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/vlr:vlr-catalog/vlr:vlr[vlr:id='STRING']
  RW.REST URI Path
    /rw-project:project/STRING/vlr:vlr-catalog/vlr/STRING
  JSON Sample
    [
      {
        "id": "STRING",
        "name": "STRING",
        "nsr-id-ref": "STRING",
        "vld-ref": "STRING",
        "res-id": "STRING",
        "short-name": "STRING",
        "vendor": "STRING",
        "description": "STRING",
        "version": "STRING",
        "type": "ELAN",
        "root-bandwidth": 0,
        "leaf-bandwidth": 0,
        "create-time": 0,
        "uptime": 0,
        "network-id": "STRING",
        "vim-network-name": "STRING",
        "provider-network": {
          "physical-network": "STRING",
          "segmentation_id": 0
        },
        "ip-profile-params": {
          "ip-version": "ipv4",
          "subnet-address": "UNION_VALUE",
          "gateway-address": "UNION_VALUE",
          "security-group": "STRING",
          "dns-server": [ { ... }, { ... } ],
          "dhcp-params": { ... },
          "subnet-prefix-pool": "STRING"
        },
        "status": "LINK_UP",
        "operational-status": "init"
      }, {
        ...
      }
    ]
  XML Sample
    <vlr:vlr xmlns:vlr="urn:ietf:params:xml:ns:yang:nfvo:vlr">
      <vlr:id>STRING</vlr:id>
      <vlr:name>STRING</vlr:name>
      <vlr:nsr-id-ref>STRING</vlr:nsr-id-ref>
      <vlr:vld-ref>STRING</vlr:vld-ref>
      <vlr:res-id>STRING</vlr:res-id>
      <vlr:short-name>STRING</vlr:short-name>
      <vlr:vendor>STRING</vlr:vendor>
      <vlr:description>STRING</vlr:description>
      <vlr:version>STRING</vlr:version>
      <vlr:type>ELAN</vlr:type>
      <vlr:root-bandwidth>0</vlr:root-bandwidth>
      <vlr:leaf-bandwidth>0</vlr:leaf-bandwidth>
      <vlr:create-time>0</vlr:create-time>
      <vlr:uptime>0</vlr:uptime>
      <vlr:network-id>STRING</vlr:network-id>
      <vlr:vim-network-name>STRING</vlr:vim-network-name>
      <vlr:provider-network>
        <vlr:physical-network>STRING</vlr:physical-network>
        <vlr:segmentation_id>0</vlr:segmentation_id>
      </vlr:provider-network>
      <vlr:ip-profile-params>
        <vlr:ip-version>ipv4</vlr:ip-version>
        <vlr:subnet-address>UNION_VALUE</vlr:subnet-address>
        <vlr:gateway-address>UNION_VALUE</vlr:gateway-address>
        <vlr:security-group>STRING</vlr:security-group>
        <vlr:dns-server>...</vlr:dns-server>
        <vlr:dhcp-params>...</vlr:dhcp-params>
        <vlr:subnet-prefix-pool>STRING</vlr:subnet-prefix-pool>
      </vlr:ip-profile-params>
      <vlr:status>LINK_UP</vlr:status>
      <vlr:operational-status>init</vlr:operational-status>
    </vlr:vlr>

1.1.1.3.1.1  container vlr:provider-network
  Description
    Container for the provider network.
  Leaves
    name: physical-network, type: STRING, description: Name of the physical network on which the provider
    network is built.
    name: segmentation_id, type: UINT32, description: ID of segregated virtual networks
  XPath Path
    /rw-project:project/vlr:vlr-catalog/vlr:vlr/vlr:provider-network
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/vlr:vlr-catalog/vlr:vlr[vlr:id='STRING']/vlr:provider-network
  RW.REST URI Path
    /rw-project:project/STRING/vlr:vlr-catalog/vlr/STRING/provider-network
  JSON Sample
    {
      "physical-network": "STRING",
      "segmentation_id": 0
    }
  XML Sample
    <vlr:provider-network xmlns:vlr="urn:ietf:params:xml:ns:yang:nfvo:vlr">
      <vlr:physical-network>STRING</vlr:physical-network>
      <vlr:segmentation_id>0</vlr:segmentation_id>
    </vlr:provider-network>

1.1.1.3.1.2  container vlr:ip-profile-params
  Leaves
    name: ip-version, type: ENUM
    name: subnet-address, type: UNION, description: Subnet IP prefix associated with IP Profile
    name: gateway-address, type: UNION, description: IP Address of the default gateway associated with IP Profile
    name: security-group, type: STRING, description: Name of the security group
    name: subnet-prefix-pool, type: STRING, description: VIM Specific reference to pre-created subnet prefix
  XPath Path
    /rw-project:project/vlr:vlr-catalog/vlr:vlr/vlr:ip-profile-params
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/vlr:vlr-catalog/vlr:vlr[vlr:id='STRING']/vlr:ip-profile-params
  RW.REST URI Path
    /rw-project:project/STRING/vlr:vlr-catalog/vlr/STRING/ip-profile-params
  JSON Sample
    {
      "ip-version": "ipv4",
      "subnet-address": "UNION_VALUE",
      "gateway-address": "UNION_VALUE",
      "security-group": "STRING",
      "dns-server": [
        {
          "address": "UNION_VALUE"
        }, {
          ...
        }
      ],
      "dhcp-params": {
        "enabled": true,
        "start-address": "UNION_VALUE",
        "count": 0
      },
      "subnet-prefix-pool": "STRING"
    }
  XML Sample
    <vlr:ip-profile-params xmlns:vlr="urn:ietf:params:xml:ns:yang:nfvo:vlr">
      <vlr:ip-version>ipv4</vlr:ip-version>
      <vlr:subnet-address>UNION_VALUE</vlr:subnet-address>
      <vlr:gateway-address>UNION_VALUE</vlr:gateway-address>
      <vlr:security-group>STRING</vlr:security-group>
      <vlr:dns-server>
        <vlr:address>UNION_VALUE</vlr:address>
      </vlr:dns-server>
      <vlr:dhcp-params>
        <vlr:enabled>true</vlr:enabled>
        <vlr:start-address>UNION_VALUE</vlr:start-address>
        <vlr:count>0</vlr:count>
      </vlr:dhcp-params>
      <vlr:subnet-prefix-pool>STRING</vlr:subnet-prefix-pool>
    </vlr:ip-profile-params>

1.1.1.3.1.2.1  list vlr:dns-server
  Leaves
    name: address, type: UNION, description: List of DNS Servers associated with IP Profile
  XPath Path
    /rw-project:project/vlr:vlr-catalog/vlr:vlr/vlr:ip-profile-params/vlr:dns-server
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/vlr:vlr-catalog/vlr:vlr[vlr:id='STRING']/vlr:ip-profile-params/vlr:dns-server[vlr:address='UNION_VALUE']
  RW.REST URI Path
    /rw-project:project/STRING/vlr:vlr-catalog/vlr/STRING/ip-profile-params/dns-server/UNION_VALUE
  JSON Sample
    [
      {
        "address": "UNION_VALUE"
      }, {
        ...
      }
    ]
  XML Sample
    <vlr:dns-server xmlns:vlr="urn:ietf:params:xml:ns:yang:nfvo:vlr">
      <vlr:address>UNION_VALUE</vlr:address>
    </vlr:dns-server>

1.1.1.3.1.2.2  container vlr:dhcp-params
  Leaves
    name: enabled, type: BOOLEAN, description: This flag indicates if DHCP is enabled or not
    name: start-address, type: UNION, description: Start IP address of the IP-Address range associated with DHCP domain
    name: count, type: UINT32, description: Size of the DHCP pool associated with DHCP domain
  XPath Path
    /rw-project:project/vlr:vlr-catalog/vlr:vlr/vlr:ip-profile-params/vlr:dhcp-params
  XPath Keyed Path
    /rw-project:project[rw-project:name='STRING']/vlr:vlr-catalog/vlr:vlr[vlr:id='STRING']/vlr:ip-profile-params/vlr:dhcp-params
  RW.REST URI Path
    /rw-project:project/STRING/vlr:vlr-catalog/vlr/STRING/ip-profile-params/dhcp-params
  JSON Sample
    {
      "enabled": true,
      "start-address": "UNION_VALUE",
      "count": 0
    }
  XML Sample
    <vlr:dhcp-params xmlns:vlr="urn:ietf:params:xml:ns:yang:nfvo:vlr">
      <vlr:enabled>true</vlr:enabled>
      <vlr:start-address>UNION_VALUE</vlr:start-address>
      <vlr:count>0</vlr:count>
    </vlr:dhcp-params>

2  module vlr

