opentelekomcloud.cloud.vpc_peering_info module – Get information about vpc peerings

Note

This module is part of the opentelekomcloud.cloud collection (version 0.14.5).

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 opentelekomcloud.cloud. You need further requirements to be able to use this module, see Requirements for details.

To use it in a playbook, specify: opentelekomcloud.cloud.vpc_peering_info.

New in opentelekomcloud.cloud 0.0.4

Synopsis

  • Get a generator of vpc peerings info from the OTC.

Requirements

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

  • openstacksdk

  • openstacksdk >= 0.36.0

  • otcextensions

  • python >= 3.6

Parameters

Parameter

Comments

api_timeout

integer

How long should the socket layer wait before timing out for API calls. If this is omitted, nothing will be passed to the requests library.

auth

dictionary

Dictionary containing auth information as needed by the cloud’s auth plugin strategy. For the default password plugin, this would contain auth_url, username, password, project_name and any information about domains (for example, os_user_domain_name or os_project_domain_name) if the cloud supports them. For other plugins, this param will need to contain whatever parameters that auth plugin requires. This parameter is not needed if a named cloud is provided or OpenStack OS_* environment variables are present.

auth_type

string

Name of the auth plugin to use. If the cloud uses something other than password authentication, the name of the plugin should be indicated here and the contents of the auth parameter should be updated accordingly.

ca_cert

aliases: cacert

string

A path to a CA Cert bundle that can be used as part of verifying SSL API requests.

client_cert

aliases: cert

string

A path to a client certificate to use as part of the SSL transaction.

client_key

aliases: key

string

A path to a client key to use as part of the SSL transaction.

cloud

any

Named cloud or cloud config to operate against. If cloud is a string, it references a named cloud config as defined in an OpenStack clouds.yaml file. Provides default values for auth and auth_type. This parameter is not needed if auth is provided or if OpenStack OS_* environment variables are present. If cloud is a dict, it contains a complete cloud configuration like would be in a section of clouds.yaml.

interface

aliases: endpoint_type

string

Endpoint URL type to fetch from the service catalog.

Choices:

  • "admin"

  • "internal"

  • "public" ← (default)

name

string

Peering connection name.

project_id

string

Project ID.

region_name

string

Name of the region.

router

string

Router name or id.

sdk_log_level

string

Log level of the OpenStackSDK

Choices:

  • "ERROR"

  • "WARN" ← (default)

  • "INFO"

  • "DEBUG"

sdk_log_path

string

Path to the logfile of the OpenStackSDK. If empty no log is written

status

string

Peering connection status.

Choices:

  • "pending_acceptance"

  • "rejected"

  • "expired"

  • "deleted"

  • "active"

timeout

integer

How long should ansible wait for the requested resource.

Default: 180

validate_certs

aliases: verify

boolean

Whether or not SSL API requests should be verified.

Before Ansible 2.3 this defaulted to yes.

Choices:

  • false

  • true

wait

boolean

Should ansible wait until the requested resource is complete.

Choices:

  • false

  • true ← (default)

Notes

Note

  • The standard OpenStack environment variables, such as OS_USERNAME may be used instead of providing explicit values.

  • Auth information is driven by openstacksdk, which means that values can come from a yaml config file in /etc/ansible/openstack.yaml, /etc/openstack/clouds.yaml or ~/.config/openstack/clouds.yaml, then from standard environment variables, then finally by explicit parameters in plays. More information can be found at https://docs.openstack.org/openstacksdk/

Examples

# Get configs versions.
- vpc_peering_info:
    name: vpc_peering1
  register: vpc_peering
- vpc_peering_info:
    router: "76889f64a23945ab887012be95acf"
  register: vpc_peering

Return Values

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

Key

Description

vpc_peerings

complex

The VPC peering connection object list.

Returned: On Success.

accept_vpc_info

dictionary

Information about the peer VPC.

Returned: success

Sample: "{tenant_id: 968u64a23945ab887012be95acf, vpc_id: 7dau5bac-0925-4d5b-add8-cb6667b8}"

created_at

string

The time (UTC) when the VPC peering connection is created.

Returned: success

Sample: "2020-09-13T20:37:01"

description

string

Provides supplementary information about the VPC peering connection.

Returned: success

Sample: ""

id

string

The VPC peering connection ID.

Returned: success

Sample: "4dae5bac-0925-4d5b-add8-cb6667b8"

name

string

The VPC peering connection name.

Returned: success

Sample: "vpc-peering1"

request_vpc_info

dictionary

Information about the local VPC.

Returned: success

Sample: "{tenant_id: 76889f64a23945ab887012be95acf, vpc_id: 4dae5bac-0925-4d5b-add8-cb6667b8}"

status

string

The VPC peering connection status.

Returned: success

Sample: "ACTIVE"

updated_at

string

Specifies the time (UTC) when the VPC peering connection is updated.

Returned: success

Sample: "2020-09-13T20:38:02"

Authors

  • Polina Gubina (@polina-gubina)

last updated: UTC - commit: