oracle.oci.oci_compute_volume_attachment_facts – Fetches details about one or multiple VolumeAttachment 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_compute_volume_attachment_facts
.
New in version 2.9.0: of oracle.oci
Synopsis¶
Fetches details about one or multiple VolumeAttachment resources in Oracle Cloud Infrastructure
Lists the volume attachments in the specified compartment. You can filter the list by specifying an instance OCID, volume OCID, or both.
Currently, the only supported volume attachment type are IScsiVolumeAttachment and ParavirtualizedVolumeAttachment.
If volume_attachment_id is specified, the details of a single VolumeAttachment 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. |
availability_domain
string
|
The name of the availability domain.
Example: `Uocm:PHX-AD-1`
|
|
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.
Required to list multiple volume_attachments.
|
|
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 . |
|
display_name
string
|
Use display_name along with the other options to return only resources that match the given display name exactly.
|
|
instance_id
string
|
The OCID of the instance.
|
|
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. |
|
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 |
|
volume_attachment_id
string
|
The OCID of the volume attachment.
Required to get a specific volume_attachment.
aliases: id |
|
volume_id
string
|
The OCID of the volume.
|
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 volume_attachment
oci_compute_volume_attachment_facts:
# required
volume_attachment_id: "ocid1.volumeattachment.oc1..xxxxxxEXAMPLExxxxxx"
- name: List volume_attachments
oci_compute_volume_attachment_facts:
# required
compartment_id: "ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx"
# optional
availability_domain: Uocm:PHX-AD-1
instance_id: "ocid1.instance.oc1..xxxxxxEXAMPLExxxxxx"
volume_id: "ocid1.volume.oc1..xxxxxxEXAMPLExxxxxx"
Return Values¶
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description | ||
---|---|---|---|---|
volume_attachments
complex
|
on success |
List of VolumeAttachment resources
Sample:
[{'attachment_type': 'emulated', 'availability_domain': 'Uocm:PHX-AD-1', 'chap_secret': 'chap_secret_example', 'chap_username': 'chap_username_example', 'compartment_id': 'ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx', 'device': 'device_example', 'display_name': 'display_name_example', 'encryption_in_transit_type': 'NONE', 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'instance_id': 'ocid1.instance.oc1..xxxxxxEXAMPLExxxxxx', 'ipv4': 'ipv4_example', 'iqn': 'iqn_example', 'is_agent_auto_iscsi_login_enabled': True, 'is_multipath': True, 'is_pv_encryption_in_transit_enabled': True, 'is_read_only': True, 'is_shareable': True, 'iscsi_attach_commands': ['sudo iscsiadm -m node -o new -T IQN -p IP:PORT', 'sudo iscsiadm -m node -o update ...'], 'iscsi_detach_commands': ['sudo iscsiadm -m node -T IQN -p IP:PORT -u', 'sudo iscsiadm -m node -o delete -T IQN'], 'iscsi_login_state': 'UNKNOWN', 'lifecycle_state': 'ATTACHING', 'multipath_devices': [{'ipv4': 'ipv4_example', 'iqn': 'iqn_example', 'port': 56}], 'port': 56, 'time_created': '2013-10-20T19:20:30+01:00', 'volume_id': 'ocid1.volume.oc1..xxxxxxEXAMPLExxxxxx'}]
|
||
attachment_type
string
|
on success |
The type of volume attachment.
Sample:
emulated
|
||
availability_domain
string
|
on success |
The availability domain of an instance.
Example: `Uocm:PHX-AD-1`
Sample:
Uocm:PHX-AD-1
|
||
chap_secret
string
|
on success |
The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
Sample:
chap_secret_example
|
||
chap_username
string
|
on success |
The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP.
Example: `ocid1.volume.oc1.phx.<unique_ID>`
Sample:
chap_username_example
|
||
compartment_id
string
|
on success |
The OCID of the compartment.
Sample:
ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
|
||
device
string
|
on success |
The device name.
Sample:
device_example
|
||
display_name
string
|
on success |
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Sample:
display_name_example
|
||
encryption_in_transit_type
string
|
on success |
Refer the top-level definition of encryptionInTransitType. The default value is NONE.
Sample:
NONE
|
||
id
string
|
on success |
The OCID of the volume attachment.
Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
|
||
instance_id
string
|
on success |
The OCID of the instance the volume is attached to.
Sample:
ocid1.instance.oc1..xxxxxxEXAMPLExxxxxx
|
||
ipv4
string
|
on success |
The volume's iSCSI IP address.
Example: `169.254.0.2`
Sample:
ipv4_example
|
||
iqn
string
|
on success |
The target volume's iSCSI Qualified Name in the format defined by RFC 3720.
Example: `iqn.2015-12.us.oracle.com:<CHAP_username>`
Sample:
iqn_example
|
||
is_agent_auto_iscsi_login_enabled
boolean
|
on success |
Whether Oracle Cloud Agent is enabled perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
Sample:
True
|
||
is_multipath
boolean
|
on success |
Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
Sample:
True
|
||
is_pv_encryption_in_transit_enabled
boolean
|
on success |
Whether in-transit encryption for the data volume's paravirtualized attachment is enabled or not.
Sample:
True
|
||
is_read_only
boolean
|
on success |
Whether the attachment was created in read-only mode.
Sample:
True
|
||
is_shareable
boolean
|
on success |
Whether the attachment should be created in shareable mode. If an attachment is created in shareable mode, then other instances can attach the same volume, provided that they also create their attachments in shareable mode. Only certain volume types can be attached in shareable mode. Defaults to false if not specified.
Sample:
True
|
||
iscsi_attach_commands
list
/ elements=string
|
on success |
Commands to attach the iSCSI block volume. Empty if attachment_type is not iscsi.
Sample:
['sudo iscsiadm -m node -o new -T IQN -p IP:PORT', 'sudo iscsiadm -m node -o update ...']
|
||
iscsi_detach_commands
list
/ elements=string
|
on success |
Commands to detach the iSCSI block volume. Empty if attachment_type is not iscsi.
Sample:
['sudo iscsiadm -m node -T IQN -p IP:PORT -u', 'sudo iscsiadm -m node -o delete -T IQN']
|
||
iscsi_login_state
string
|
on success |
The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
Sample:
UNKNOWN
|
||
lifecycle_state
string
|
on success |
The current state of the volume attachment.
Sample:
ATTACHING
|
||
multipath_devices
complex
|
on success |
A list of secondary multipath devices
|
||
ipv4
string
|
on success |
The volume's iSCSI IP address.
Example: `169.254.2.2`
Sample:
ipv4_example
|
||
iqn
string
|
on success |
The target volume's iSCSI Qualified Name in the format defined by RFC 3720.
Example: `iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195`
Sample:
iqn_example
|
||
port
integer
|
on success |
The volume's iSCSI port, usually port 860 or 3260.
Example: `3260`
Sample:
56
|
||
port
integer
|
on success |
The volume's iSCSI port, usually port 860 or 3260.
Example: `3260`
Sample:
56
|
||
time_created
string
|
on success |
The date and time the volume was created, in the format defined by RFC3339.
Example: `2016-08-25T21:10:29.600Z`
Sample:
2013-10-20T19:20:30+01:00
|
||
volume_id
string
|
on success |
The OCID of the volume.
Sample:
ocid1.volume.oc1..xxxxxxEXAMPLExxxxxx
|
Authors¶
Oracle (@oracle)