VPN Service Operations

This section discusses operations for managing a tenant's VPN service through this extension.

Table 4.13. VPN Service Attributes
Attribute Type Required CRUD [a] Default Value Validation Constraints Notes
id uuid-str N/A R generated N/A Unique identifier for the VPN Service object.
tenant_id uuid-str Yes CR Derived from Authentication token valid tenant_id Owner of the VPN service. Only admin users can specify a tenant identifier other than their own.
name String No CRU None N/A Human readable name for the VPN service. Does not have to be unique.
description String No CRU None N/A Human readable description for the VPN service.
status String N/A R N/A N/A Indicates whether IPsec VPN service is currently operational. Possible values include: ACTIVE, DOWN, BUILD, ERROR, PENDING_CREATE, PENDING_UPDATE, or PENDING_DELETE.
admin_state_up Bool N/A CRU true {true | false } Administrative state of the vpnservice. If false (down), port does not forward packets.
subnet_id uuid-str Yes CR N/A valid subnet ID The subnet on which the tenant wants the VPN service. This may be extended in the future to support multiple subnets.
router_id uuid-str Yes CR N/A valid router ID Router ID to which the VPN service is inserted. This may change in the future, when router level insertion is available.

[a]

  • C. Use the attribute in create operations.

  • R. This attribute is returned in response to show and list operations.

  • U. You can update the value of this attribute.

  • D. You can delete the value of this attribute.

Questions? Discuss on ask.openstack.org
Found an error? Report a bug against this page


loading table of contents...