cisco.aci.aci_l3out_extepg_to_contract – Bind Contracts to External End Point Groups (EPGs)
Note
This plugin is part of the cisco.aci collection (version 2.1.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 cisco.aci
.
To use it in a playbook, specify: cisco.aci.aci_l3out_extepg_to_contract
.
Parameters
Parameter |
Comments |
---|---|
User-defined string for annotating an object. If the value is not specified in the task, the value of environment variable |
|
The X.509 certificate name attached to the APIC AAA user used for signature-based authentication. If a If PEM-formatted content was provided for If the value is not specified in the task, the value of environment variable |
|
Name of the contract. |
|
The type of contract. Choices:
|
|
Name of the external end point group. |
|
IP Address or hostname of APIC resolvable by Ansible control host. If the value is not specified in the task, the value of environment variable |
|
Name of the l3out. |
|
Influence the output of this ACI module.
If the value is not specified in the task, the value of environment variable Choices:
|
|
Path to a file that will be used to dump the ACI JSON configuration objects generated by the module. If the value is not specified in the task, the value of environment variable |
|
User-defined string for the ownerKey attribute of an ACI object. This attribute represents a key for enabling clients to own their data for entity correlation. If the value is not specified in the task, the value of environment variable |
|
User-defined string for the ownerTag attribute of an ACI object. This attribute represents a tag for enabling clients to add their own data. For example, to indicate who created this object. If the value is not specified in the task, the value of environment variable |
|
The password to use for authentication. This option is mutual exclusive with If the value is not specified in the task, the value of environment variables |
|
Port number to be used for REST connection. The default value depends on parameter If the value is not specified in the task, the value of environment variable |
|
This has four levels of priority. Choices:
|
|
Either a PEM-formatted private key file or the private key content used for signature-based authentication. This value also influences the default This option is mutual exclusive with If the value is not specified in the task, the value of environment variable |
|
This is configurable for provided contracts. Choices:
|
|
Use Use Choices:
|
|
Name of existing tenant. |
|
The socket level timeout in seconds. If the value is not specified in the task, the value of environment variable Default: 30 |
|
If If the value is not specified in the task, the value of environment variable Choices:
|
|
If If the value is not specified in the task, the value of environment variable Choices:
|
|
The username to use for authentication. If the value is not specified in the task, the value of environment variables Default: “admin” |
|
If This should only set to If the value is not specified in the task, the value of environment variable Choices:
|
Notes
Note
The
tenant
,l3out
andextepg
must exist before using this module in your playbook. The cisco.aci.aci_tenant, cisco.aci.aci_l3out and cisco.aci.aci_l3out_extepg modules can be used for this.
See Also
See also
- APIC Management Information Model reference
More information about the internal APIC class fvtenant, l3extInstP and l3extOut.
- Cisco ACI Guide
Detailed information on how to manage your ACI infrastructure using Ansible.
- Developing Cisco ACI modules
Detailed guide on how to write your own Cisco ACI modules to contribute.
Examples
- name: Bind a contract to an external EPG
cisco.aci.aci_l3out_extepg_to_contract:
host: apic
username: admin
password: SomeSecretePassword
tenant: Auto-Demo
l3out: l3out
extepg : testEpg
contract: contract1
contract_type: provider
state: present
delegate_to: localhost
- name: Remove existing contract from an external EPG
cisco.aci.aci_l3out_extepg_to_contract:
host: apic
username: admin
password: SomeSecretePassword
tenant: Auto-Demo
l3out: l3out
extepg : testEpg
contract: contract1
contract_type: provider
state: absent
delegate_to: localhost
- name: Query a contract bound to an external EPG
cisco.aci.aci_l3out_extepg_to_contract:
host: apic
username: admin
password: SomeSecretePassword
tenant: ansible_tenant
l3out: ansible_l3out
extepg: ansible_extEpg
contract: ansible_contract
contract_type: provider
state: query
delegate_to: localhost
register: query_result
- name: Query all contracts relationships
cisco.aci.aci_l3out_extepg_to_contract:
host: apic
username: admin
password: SomeSecretePassword
contract_type: provider
state: query
delegate_to: localhost
register: query_result
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The existing configuration from the APIC after the module has finished Returned: success Sample: [{“fvTenant”: {“attributes”: {“descr”: “Production environment”, “dn”: “uni/tn-production”, “name”: “production”, “nameAlias”: “”, “ownerKey”: “”, “ownerTag”: “”}}}] |
|
The error information as returned from the APIC Returned: failure Sample: {“code”: “122”, “text”: “unknown managed object class foo”} |
|
The filter string used for the request Returned: failure or debug Sample: “?rsp-prop-include=config-only” |
|
The HTTP method used for the request to the APIC Returned: failure or debug Sample: “POST” |
|
The original configuration from the APIC before the module has started Returned: info Sample: [{“fvTenant”: {“attributes”: {“descr”: “Production”, “dn”: “uni/tn-production”, “name”: “production”, “nameAlias”: “”, “ownerKey”: “”, “ownerTag”: “”}}}] |
|
The assembled configuration from the user-provided parameters Returned: info Sample: {“fvTenant”: {“attributes”: {“descr”: “Production environment”, “name”: “production”}}} |
|
The raw output returned by the APIC REST API (xml or json) Returned: parse error Sample: “\u003c?xml version=\”1.0\” encoding=\”UTF-8\”?\u003e\u003cimdata totalCount=\”1\”\u003e\u003cerror code=\”122\” text=\”unknown managed object class \”/\u003e\u003c/imdata\u003e” |
|
The HTTP response from the APIC Returned: failure or debug Sample: “OK (30 bytes)” |
|
The actual/minimal configuration pushed to the APIC Returned: info Sample: {“fvTenant”: {“attributes”: {“descr”: “Production environment”}}} |
|
The HTTP status from the APIC Returned: failure or debug Sample: 200 |
|
The HTTP url used for the request to the APIC Returned: failure or debug |
Authors
Sudhakar Shet Kudtarkar (@kudtarkar1)
Shreyas Srish (@shrsr)