PolicyLbRule (schema)

Binding of a LbPoolAccess and Group to a PolicyLbVirtualServer

Binding of a LbPoolAccess and Group to a PolicyLbVirtualServer
used to route application traffic passing through load balancers.
PolicyLbRule uses match conditions to match application traffic passing
through a PolicyLbVirtualServer using HTTP or HTTPS. Can bind
multiple PolicyLbVirtualServers to a Group. Each PolicyLbRule
consists of two optional match conditions, each match contidion defines a
criterion for application traffic. If no match conditions are
specified, then the PolicyLbRule will always match and it is used
typically to define default rules. If more than one match condition is
specified, then matching strategy determines if all conditions should
match or any one condition should match for the PolicyLbRule to be
considered a match. A match indicates that the PolicyLbVirtualServer
should route the request to the Group (parent of PolicyLbRule).
Name Description Type Notes
_create_time Timestamp of resource creation EpochMsTimestamp Readonly
Sortable
_create_user ID of the user who created this resource string Readonly
_last_modified_time Timestamp of last modification EpochMsTimestamp Readonly
Sortable
_last_modified_user ID of the user who last modified this resource string Readonly
_links References related to this resource

The server will populate this field when returing the resource. Ignored on PUT and POST.
array of ResourceLink Readonly
_protection Indicates protection status of this resource

Protection status is one of the following:
PROTECTED - the client who retrieved the entity is not allowed
to modify it.
NOT_PROTECTED - the client who retrieved the entity is allowed
to modify it
REQUIRE_OVERRIDE - the client who retrieved the entity is a super
user and can modify it, but only when providing
the request header X-Allow-Overwrite=true.
UNKNOWN - the _protection field could not be determined for this
entity.
string Readonly
_revision Generation of this resource config

The _revision property describes the current revision of the resource. To prevent clients from overwriting each other's changes, PUT operations must include the current _revision of the resource, which clients should obtain by issuing a GET operation. If the _revision provided in a PUT request is missing or stale, the operation will be rejected.
int
_schema Schema for this resource string Readonly
_self Link to this resource SelfResourceLink Readonly
_system_owned Indicates system owned resource boolean Readonly
children subtree for this type within policy tree

subtree for this type within policy tree containing nested elements.
array of ChildPolicyConfigResource
Children are not allowed for this type
description Description of this resource string Maximum length: 1024
Sortable
display_name Identifier to use when displaying entity in logs or GUI

Defaults to ID if not set
string Maximum length: 255
Sortable
host_match Host HTTP header match condition

This condition is used to match HTTP request messages by the
specific HTTP header field, Host. The Host request header specifies
the domain name of the server. The supplied Host HTTP header match
condition will be matched as a regular expression.
The regular expressions in load balancer rules use the features
common to both Java regular expressions and Perl Compatible Regular
Expressions (PCREs) with some restrictions. Reference http://www.pcre
.org for PCRE and the NSX-T Administrator's Guide for the
restrictions. Please note, when regular expressions are used in JSON
(JavaScript Object Notation) string, every backslash character (\)
needs to be escaped by one additional backslash character.
string
id Unique identifier of this resource string Sortable
lb_virtual_server PolicyLbVirtualServer path

The path of PolicyLbVirtualServer to bind to this PolicyLbRule and its
Group
string
marked_for_delete Indicates whether the intent object is marked for deletion

Intent objects are not directly deleted from the system when a delete
is invoked on them. They are marked for deletion and only when all the
realized entities for that intent object gets deleted, the intent object
is deleted. Objects that are marked for deletion are not returned in
GET call. One can use the search API to get these objects.
boolean Readonly
Default: "False"
match_strategy Match strategy for determining match of multiple conditions

If more than one match condition is specified, then
matching strategy determines if all conditions should match or any
one condition should match for the LB Rule to be considered a match.
- ALL indicates that both host_match and path_match must match for
this PolicyLbRule to be considered a match
- ANY indicates that either host_match or patch match may match for
this PolicyLbRule to be considered a match
string Enum: ALL, ANY
Default: "ANY"
overridden Indicates whether this object is the overridden intent object

Global intent objects cannot be modified by the user.
However, certain global intent objects can be overridden locally by use
of this property. In such cases, the overridden local values take
precedence over the globally defined values for the properties.
boolean Readonly
Default: "False"
parent_path Path of its parent

Path of its parent
string Readonly
path Absolute path of this object

Absolute path of this object
string Readonly
path_match HTTP request uri match condition

This condition is used to match URIs(Uniform Resource Identifier) of
HTTP request messages. The URI field can be specified as a regluar
expression. If an HTTP request message is requesting an URI which
matches specified regular expression, it matches the condition. The
syntax of whole URI looks like this:
scheme:[//[user[:password]@]host[:port]][/path][?query][#fragment]
This condition matches only the path part of entire URI. The path_match
field is used as a regular expression to match URI path of HTTP
requests. For example, to match any URI that has "/image/" or
"/images/", uri field can be specified as: "/image[s]?/". The regular
expressions in load balancer rules use the features common to both
Java regular expressions and Perl Compatible Regular Expressions
(PCREs) with some restrictions. Reference http://www.pcre .org for
PCRE and the NSX-T Administrator's Guide for the restrictions.
Please note, when regular expressions are used in JSON (JavaScript
Object Notation) string, every backslash character (\) needs to be
escaped by one additional backslash character.
string
relative_path Relative path of this object

Path relative from its parent
string Readonly
resource_type Must be set to the value PolicyLbRule string
sequence_number Sequence number of the this PolicyLbRule

This field is used to resolve conflicts between multiple
PolicyLbRules associated with a single PolicyLbVirtualServer and will
be applied numerically or low to high
int
tags Opaque identifiers meaningful to the API user array of Tag Maximum items: 30
unique_id A unique identifier assigned by the system

This is a UUID generated by the GM/LM to uniquely identify
entites in a federated environment. For entities that are
stretched across multiple sites, the same ID will be used
on all the stretched sites.
string Readonly