Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
The user or group.
The Role granted to the grantee.
The Type of AccessGrant.
Used in:
Used in:
Used in:
The name of the group.
The members of the group.
Used in:
Used in:
The local ASN for BGP peering.
The remote ASN for BGP peering. If unset, BGP will not be used.
The BGP peers. If empty, BGP will not be used.
The service VIPs hosted by this cluster, excluding those that are misconfigured (see the misconfigured_vserver attribute).
The list of vservers that have broken configurations.
Metadata about this Cluster configuration.
The dedicated VIP subnet(s) for this cluster, in CIDR notation.
The access groups that are referenced by the vservers.
High-Availability states for a Seesaw Node.
State of the node could not be determined.
Node is in a ready but non-serving state.
Node is disabled, will not serve traffic.
Node is in a failure state.
Node is in an active and serving state.
Node is in shutdown state and will stop serving requests.
TODO(angusc): Use different message types for the different healthcheck types.
Used in:
,Healthcheck interval in seconds.
Healthcheck timeout in seconds.
Healthcheck port. For Vserver healthchecks, this field is required. For VserverEntry healthchecks, it is optional and uses the VserverEntry port by default.
String to send for UDP/TCP/HTTP(S) healthcheck.
Expected response for UDP/TCP/HTTP(S) healthcheck.
Expected response code for healthcheck.
The Mode of this healthcheck.
The HTTP request method to use for an HTTP(S) healthcheck.
Perform a healthcheck against an HTTP proxy.
Do TLS verification.
Number of retries before a healthcheck is considered to have failed.
Used in:
Used in:
Used in:
, , ,Fully qualified hostname.
An IPv4 address and prefix length in CIDR format.
An IPv6 address and prefix length in CIDR format.
Host status.
Servicedb statuses
Used in:
Used in:
The UNIX timestamp at which the Cluster configuration was last updated.
Miscellaneous details about the Cluster configuration (info on upstream source data, etc) go here.
Used in:
Used in:
Used in:
Used in:
The name of this vserver.
VIP hostname and IP(s).
Contact info for Responsible Party.
Use firewall mark instead of individual service configurations.
The healthchecks to perform on the backends, in addition to those that are VserverEntry specific.
The access grants for this vserver.
Warning messages about this Vserver (such as misconfigured backends) to be displayed on operator consoles.
The list of backends for this vserver.
Used in:
See --persisent in man ipvsadm(8).
Continue sending packets for existing connections to the same backend, even when that backend is failing healthchecks.
The minimum fraction of backends that must be healthy for the vserver to be active. If the number of backends falls below this watermark, the vserver is considered unhealthy. Valid values are 0.0 to 1.0. If unset, the value of server_high_watermark is used.
The minimum fraction of backends that must be healthy for vserver to become active. Default is 0.0 .
--l-threshold per man ipvsadm(8).
--u-threshold per man ipvsadm(8).
The healthchecks to perform on the backends.
Use "one packet" load balancing.
Used in:
See --gatewaying in man ipvsadm(8).
See --masquerding in man ipvsadm(8).
See --ipip in man ipvsadm(8).
See --scheduler in man ipvsadm(8).
Used in:
NOTE: MH scheduler option is available after Kernel 4.18. It is typically used without conntrack sync. Additional sysctl settings such as `net.ipv4.vs.sloppy_tcp` is required when operating in that mode to allow seamless failover. However, turning off conntrack sync could break other services on other scheduler settings. Ref: https://www.kernel.org/doc/Documentation/networking/ipvs-sysctl.txt