rax_network – create / delete an isolated network in Rackspace Public Cloud¶
New in version 1.4.
Requirements¶
The below requirements are needed on the host that executes this module.
- python >= 2.6
- pyrax
Parameters¶
Parameter | Choices/Defaults | Comments |
---|---|---|
api_key
-
|
Rackspace API key, overrides credentials.
aliases: password |
|
auth_endpoint
-
added in 1.5 |
Default: "https://identity.api.rackspacecloud.com/v2.0/"
|
The URI of the authentication service.
|
cidr
-
|
cidr of the network being created
|
|
credentials
-
|
File to find the Rackspace credentials in. Ignored if api_key and username are provided.
aliases: creds_file |
|
env
-
added in 1.5 |
Environment as configured in ~/.pyrax.cfg, see https://github.com/rackspace/pyrax/blob/master/docs/getting_started.md#pyrax-configuration.
|
|
identity_type
-
added in 1.5 |
Default: "rackspace"
|
Authentication mechanism to use, such as rackspace or keystone.
|
label
-
|
Label (name) to give the network
|
|
region
-
|
Default: "DFW"
|
Region to create an instance in.
|
state
-
|
|
Indicate desired state of the resource
|
tenant_id
-
added in 1.5 |
The tenant ID used for authentication.
|
|
tenant_name
-
added in 1.5 |
The tenant name used for authentication.
|
|
username
-
|
Rackspace username, overrides credentials.
|
|
verify_ssl
-
added in 1.5 |
Whether or not to require SSL validation of API endpoints.
|
Notes¶
Note
- The following environment variables can be used,
RAX_USERNAME
,RAX_API_KEY
,RAX_CREDS_FILE
,RAX_CREDENTIALS
,RAX_REGION
. RAX_CREDENTIALS
andRAX_CREDS_FILE
points to a credentials file appropriate for pyrax. See https://github.com/rackspace/pyrax/blob/master/docs/getting_started.md#authenticatingRAX_USERNAME
andRAX_API_KEY
obviate the use of a credentials fileRAX_REGION
defines a Rackspace Public Cloud region (DFW, ORD, LON, …)
Examples¶
- name: Build an Isolated Network
gather_facts: False
tasks:
- name: Network create request
local_action:
module: rax_network
credentials: ~/.raxpub
label: my-net
cidr: 192.168.3.0/24
state: present
Status¶
- This module is not guaranteed to have a backwards compatible interface. [preview]
- This module is maintained by the Ansible Community. [community]
Authors¶
- Christopher H. Laco (@claco)
- Jesse Keating (@omgjlk)
Hint
If you notice any issues in this documentation you can edit this document to improve it.