oracle.oci.oci_network_load_balancer_health_facts – Fetches details about one or multiple NetworkLoadBalancerHealth resources in Oracle Cloud Infrastructure¶
Note
This plugin is part of the oracle.oci collection (version 5.0.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_health_facts
.
New in version 2.9.0: of oracle.oci
Synopsis¶
Fetches details about one or multiple NetworkLoadBalancerHealth resources in Oracle Cloud Infrastructure
Lists the summary health statuses for all network load balancers in the specified compartment.
If network_load_balancer_id is specified, the details of a single NetworkLoadBalancerHealth will be returned.
Requirements¶
The below requirements are needed on the host that executes this module.
python >= 3.6
Python SDK for Oracle Cloud Infrastructure https://oracle-cloud-infrastructure-python-sdk.readthedocs.io
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
|
|
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
|
|
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. |
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.
|
|
compartment_id
string
|
The OCID of the compartment containing the network load balancers to list.
Required to list multiple network_load_balancer_healths.
|
|
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
|
The OCID of the network load balancer to update.
Required to get a specific network_load_balancer_health.
aliases: id |
|
realm_specific_endpoint_template_enabled
boolean
|
|
Enable/Disable realm specific endpoint template for service client. By Default, realm specific endpoint template is disabled. If not set, then the value of the OCI_REALM_SPECIFIC_SERVICE_ENDPOINT_TEMPLATE_ENABLED variable, if any, is used.
|
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
|
|
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
|
|
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 |
Notes¶
Note
For OCI python sdk configuration, please refer to https://oracle-cloud-infrastructure-python-sdk.readthedocs.io/en/latest/configuration.html
Examples¶
- name: Get a specific network_load_balancer_health
oci_network_load_balancer_health_facts:
# required
network_load_balancer_id: "ocid1.networkloadbalancer.oc1..xxxxxxEXAMPLExxxxxx"
- name: List network_load_balancer_healths
oci_network_load_balancer_health_facts:
# required
compartment_id: "ocid1.compartment.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 | |
---|---|---|---|
network_load_balancer_healths
complex
|
on success |
List of NetworkLoadBalancerHealth resources
Sample:
[{'critical_state_backend_set_names': [], 'network_load_balancer_id': 'ocid1.networkloadbalancer.oc1..xxxxxxEXAMPLExxxxxx', 'status': 'OK', 'total_backend_set_count': 56, 'unknown_state_backend_set_names': [], 'warning_state_backend_set_names': []}]
|
|
critical_state_backend_set_names
list
/ elements=string
|
on success |
A list of backend sets that are currently in the `CRITICAL` health state. The list identifies each backend set by the user-friendly name you assigned when you created the backend set.
Example: `example_backend_set`
Returned for get operation
|
|
network_load_balancer_id
string
|
on success |
The OCID of the network load balancer with which the health status is associated.
Returned for list operation
Sample:
ocid1.networkloadbalancer.oc1..xxxxxxEXAMPLExxxxxx
|
|
status
string
|
on success |
The overall health status of the network load balancer.
* **OK:** All backend sets associated with the network load balancer return a status of `OK`.
* **WARNING:** At least one of the backend sets associated with the network load balancer returns a status of `WARNING`, no backend sets return a status of `CRITICAL`, and the network load balancer life cycle state is `ACTIVE`.
* **CRITICAL:** One or more of the backend sets associated with the network load balancer return a status of `CRITICAL`.
* **UNKNOWN:** If any one of the following conditions is true:
* The network load balancer life cycle state is not `ACTIVE`.
* No backend sets are defined for the network load balancer.
* More than half of the backend sets associated with the network load balancer return a status of `UNKNOWN`, none of the backend sets return a status of `WARNING` or `CRITICAL`, and the network load balancer life cycle state is `ACTIVE`.
* The system could not retrieve metrics for any reason.
Sample:
OK
|
|
total_backend_set_count
integer
|
on success |
The total number of backend sets associated with this network load balancer.
Example: `4`
Returned for get operation
Sample:
56
|
|
unknown_state_backend_set_names
list
/ elements=string
|
on success |
A list of backend sets that are currently in the `UNKNOWN` health state. The list identifies each backend set by the user-friendly name you assigned when you created the backend set.
Example: `example_backend_set2`
Returned for get operation
|
|
warning_state_backend_set_names
list
/ elements=string
|
on success |
A list of backend sets that are currently in the `WARNING` health state. The list identifies each backend set by the user-friendly name you assigned when you created the backend set.
Example: `example_backend_set3`
Returned for get operation
|
Authors¶
Oracle (@oracle)