opentelekomcloud.cloud.vpc_peering module -- Add/Update/Delete vpc peering connection from OpenTelekomCloud¶
Note
This module is part of the opentelekomcloud.cloud collection (version 0.14.6).
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.
New in opentelekomcloud.cloud 0.13.1
Synopsis¶
Add or Remove vpc peering 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 |
|---|---|
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. |
|
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. |
|
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. |
|
A path to a CA Cert bundle that can be used as part of verifying SSL API requests. |
|
A path to a client certificate to use as part of the SSL transaction. |
|
A path to a client key to use as part of the SSL transaction. |
|
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. |
|
Provides supplementary information about the VPC peering connection. |
|
Endpoint URL type to fetch from the service catalog. Choices:
|
|
Specifies the ID of the project to which a local VPC belongs. Can not be updated. |
|
Name or ID of the local router. Can not be updated. |
|
Name or ID of the vpc peering connection. Mandatory for creating. Can be updated. |
|
Name of the region. |
|
Specifies the ID of the project to which a peer VPC belongs. Can not be updated. |
|
ID of the remote router. Can not be updated. |
|
Log level of the OpenStackSDK Choices:
|
|
Path to the logfile of the OpenStackSDK. If empty no log is written |
|
Should the resource be present or absent. Choices:
|
|
How long should ansible wait for the requested resource. Default: |
|
Whether or not SSL API requests should be verified. Before Ansible 2.3 this defaulted to Choices:
|
|
Should ansible wait until the requested resource is complete. Choices:
|
Notes¶
Note
The standard OpenStack environment variables, such as
OS_USERNAMEmay 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¶
# Create a vpc peering.
- opentelekomcloud.cloud.vpc_peering:
name: "peering1"
local_router: "local-router"
local_project: "959db9b6017d4a1fa1c6fd17b6820f55"
remote_router: "peer-router"
remote_project: "959db9b6017d4a1fa1c6fd17b6820f55"
# Update vpc perring
- opentelekomcloud.cloud.vpc_peering:
name: "peering1"
description: "new description"
local_router: "local-router"
local_project: "959db9b6017d4a1fa1c6fd17b6820f55"
remote_router: "peer-router"
remote_project: "959db9b6017d4a1fa1c6fd17b6820f55"
# Delete a load balancer(and all its related resources)
- opentelekomcloud.cloud.vpc_peering:
name: "peering2"
state: absent
Return Values¶
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
Dictionary describing VPC peering instance. Returned: On Success. |
|
Dictionary describing the local vpc. Returned: On success when |
|
Specifies the ID of the project to which a VPC involved in the VPC peering connection belongs. Returned: success Sample: |
|
Specifies the ID of a VPC involved in a VPC peering connection. Returned: success Sample: |
|
Specifies the time (UTC) when the VPC peering connection is created. Returned: On success when Sample: |
|
Provides supplementary information about the VPC peering connection. Returned: On success when Sample: |
|
Specifies the VPC peering connection ID. Returned: On success when Sample: |
|
Specifies the VPC peering connection name. Returned: On success when Sample: |
|
Dictionary describing the local vpc. Returned: On success when |
|
Specifies the ID of the project to which a VPC involved in the VPC peering connection belongs. Returned: success Sample: |
|
Specifies the ID of a VPC involved in a VPC peering connection. Returned: success Sample: |
|
Specifies the VPC peering connection status. Returned: On success when Sample: |
|
Specifies the time (UTC) when the VPC peering connection is updated. Returned: On success when Sample: |