oracle.oci.oci_network_load_balancer_backend_set_facts – Fetches details about one or multiple BackendSet resources in Oracle Cloud Infrastructure

Note

This plugin is part of the oracle.oci collection (version 4.11.0).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install oracle.oci.

To use it in a playbook, specify: oracle.oci.oci_network_load_balancer_backend_set_facts.

New in version 2.9.0: of oracle.oci

Synopsis

  • Fetches details about one or multiple BackendSet resources in Oracle Cloud Infrastructure

  • Lists all backend sets associated with a given network load balancer.

  • If backend_set_name is specified, the details of a single BackendSet will be returned.

Requirements

The below requirements are needed on the host that executes this module.

Parameters

Parameter Choices/Defaults Comments
api_user
string
The OCID of the user, on whose behalf, OCI APIs are invoked. If not set, then the value of the OCI_USER_ID environment variable, if any, is used. This option is required if the user is not specified through a configuration file (See config_file_location). To get the user's OCID, please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm.
api_user_fingerprint
string
Fingerprint for the key pair being used. If not set, then the value of the OCI_USER_FINGERPRINT environment variable, if any, is used. This option is required if the key fingerprint is not specified through a configuration file (See config_file_location). To get the key pair's fingerprint value please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm.
api_user_key_file
string
Full path and filename of the private key (in PEM format). If not set, then the value of the OCI_USER_KEY_FILE variable, if any, is used. This option is required if the private key is not specified through a configuration file (See config_file_location). If the key is encrypted with a pass-phrase, the api_user_key_pass_phrase option must also be provided.
api_user_key_pass_phrase
string
Passphrase used by the key referenced in api_user_key_file, if it is encrypted. If not set, then the value of the OCI_USER_KEY_PASS_PHRASE variable, if any, is used. This option is required if the key passphrase is not specified through a configuration file (See config_file_location).
auth_purpose
string
    Choices:
  • service_principal
The auth purpose which can be used in conjunction with 'auth_type=instance_principal'. The default auth_purpose for instance_principal is None.
auth_type
string
    Choices:
  • api_key ←
  • instance_principal
  • instance_obo_user
  • resource_principal
The type of authentication to use for making API requests. By default auth_type="api_key" based authentication is performed and the API key (see api_user_key_file) in your config file will be used. If this 'auth_type' module option is not specified, the value of the OCI_ANSIBLE_AUTH_TYPE, if any, is used. Use auth_type="instance_principal" to use instance principal based authentication when running ansible playbooks within an OCI compute instance.
backend_set_name
string
The name of the backend set to retrieve.
Example: `example_backend_set`
Required to get a specific backend_set.

aliases: name
cert_bundle
string
The full path to a CA certificate bundle to be used for SSL verification. This will override the default CA certificate bundle. If not set, then the value of the OCI_ANSIBLE_CERT_BUNDLE variable, if any, is used.
config_file_location
string
Path to configuration file. If not set then the value of the OCI_CONFIG_FILE environment variable, if any, is used. Otherwise, defaults to ~/.oci/config.
config_profile_name
string
The profile to load from the config file referenced by config_file_location. If not set, then the value of the OCI_CONFIG_PROFILE environment variable, if any, is used. Otherwise, defaults to the "DEFAULT" profile in config_file_location.
network_load_balancer_id
string / required
The OCID of the network load balancer to update.

aliases: id
region
string
The Oracle Cloud Infrastructure region to use for all OCI API requests. If not set, then the value of the OCI_REGION variable, if any, is used. This option is required if the region is not specified through a configuration file (See config_file_location). Please refer to https://docs.us-phoenix-1.oraclecloud.com/Content/General/Concepts/regions.htm for more information on OCI regions.
sort_by
string
    Choices:
  • timeCreated
  • displayName
The field to sort by. Only one sort order can be provided. The default order for timeCreated is descending. The default order for displayName is ascending. If no value is specified, then timeCreated is the default.
sort_order
string
    Choices:
  • ASC
  • DESC
The sort order to use, either 'asc' (ascending) or 'desc' (descending).
tenancy
string
OCID of your tenancy. If not set, then the value of the OCI_TENANCY variable, if any, is used. This option is required if the tenancy OCID is not specified through a configuration file (See config_file_location). To get the tenancy OCID, please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm

Examples

- name: Get a specific backend_set
  oci_network_load_balancer_backend_set_facts:
    # required
    backend_set_name: backend_set_name_example
    network_load_balancer_id: "ocid1.networkloadbalancer.oc1..xxxxxxEXAMPLExxxxxx"

- name: List backend_sets
  oci_network_load_balancer_backend_set_facts:
    # required
    network_load_balancer_id: "ocid1.networkloadbalancer.oc1..xxxxxxEXAMPLExxxxxx"

    # optional
    sort_order: ASC
    sort_by: timeCreated

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key Returned Description
backend_sets
complex
on success
List of BackendSet resources

Sample:
[{'backends': [{'ip_address': 'ip_address_example', 'is_backup': True, 'is_drain': True, 'is_offline': True, 'name': 'name_example', 'port': 56, 'target_id': 'ocid1.target.oc1..xxxxxxEXAMPLExxxxxx', 'weight': 56}], 'health_checker': {'interval_in_millis': 56, 'port': 56, 'protocol': 'HTTP', 'request_data': None, 'response_body_regex': 'response_body_regex_example', 'response_data': None, 'retries': 56, 'return_code': 56, 'timeout_in_millis': 56, 'url_path': 'url_path_example'}, 'ip_version': 'IPV4', 'is_preserve_source': True, 'name': 'name_example', 'policy': 'TWO_TUPLE'}]
 
backends
complex
on success
Array of backends.

   
ip_address
string
on success
The IP address of the backend server. Example: `10.0.0.3`

Sample:
ip_address_example
   
is_backup
boolean
on success
Whether the network load balancer should treat this server as a backup unit. If `true`, then the network load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "isBackup" fail the health check policy.
Example: `false`

Sample:
True
   
is_drain
boolean
on success
Whether the network load balancer should drain this server. Servers marked "isDrain" receive no incoming traffic.
Example: `false`

Sample:
True
   
is_offline
boolean
on success
Whether the network load balancer should treat this server as offline. Offline servers receive no incoming traffic.
Example: `false`

Sample:
True
   
name
string
on success
A read-only field showing the IP address/IP OCID and port that uniquely identify this backend server in the backend set.
Example: `10.0.0.3:8080`, or `ocid1.privateip..oc1.<var>&lt;unique_ID&gt;</var>:443` or `10.0.0.3:0`

Sample:
name_example
   
port
integer
on success
The communication port for the backend server.
Example: `8080`

Sample:
56
   
target_id
string
on success
The IP OCID/Instance OCID associated with the backend server. Example: `ocid1.privateip..oc1.<var>&lt;unique_ID&gt;</var>`

Sample:
ocid1.target.oc1..xxxxxxEXAMPLExxxxxx
   
weight
integer
on success
The network load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives three times the number of new connections as a server weighted '1'. For more information about load balancing policies, see How Network Load Balancing Policies Work.
Example: `3`

Sample:
56
 
health_checker
complex
on success

   
interval_in_millis
integer
on success
The interval between health checks, in milliseconds. The default value is 10000 (10 seconds).
Example: `10000`

Sample:
56
   
port
integer
on success
The backend server port against which to run the health check. If the port is not specified, then the network load balancer uses the port information from the `Backend` object. The port must be specified if the backend port is 0.
Example: `8080`

Sample:
56
   
protocol
string
on success
The protocol the health check must use; either HTTP or HTTPS, or UDP or TCP.
Example: `HTTP`

Sample:
HTTP
   
request_data
string
on success
Base64 encoded pattern to be sent as UDP or TCP health check probe.

Sample:
null
   
response_body_regex
string
on success
A regular expression for parsing the response body from the backend server.
Example: `^((?!false).|\s)*$`

Sample:
response_body_regex_example
   
response_data
string
on success
Base64 encoded pattern to be validated as UDP or TCP health check probe response.

Sample:
null
   
retries
integer
on success
The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. The default value is 3.
Example: `3`

Sample:
56
   
return_code
integer
on success
The status code a healthy backend server should return. If you configure the health check policy to use the HTTP protocol, then you can use common HTTP status codes such as "200".
Example: `200`

Sample:
56
   
timeout_in_millis
integer
on success
The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. The default value is 3000 (3 seconds).
Example: `3000`

Sample:
56
   
url_path
string
on success
The path against which to run the health check.
Example: `/healthcheck`

Sample:
url_path_example
 
ip_version
string
on success
IP version associated with the backend set.

Sample:
IPV4
 
is_preserve_source
boolean
on success
If this parameter is enabled, then the network load balancer preserves the source IP of the packet when it is forwarded to backends. Backends see the original source IP. If the isPreserveSourceDestination parameter is enabled for the network load balancer resource, then this parameter cannot be disabled. The value is true by default.

Sample:
True
 
name
string
on success
A user-friendly name for the backend set that must be unique and cannot be changed.
Valid backend set names include only alphanumeric characters, dashes, and underscores. Backend set names cannot contain spaces. Avoid entering confidential information.
Example: `example_backend_set`

Sample:
name_example
 
policy
string
on success
The network load balancer policy for the backend set.
Example: `FIVE_TUPLE`

Sample:
TWO_TUPLE


Authors

  • Oracle (@oracle)