4848652c7a
Start using this to construct shade OpenStack Cloud objects in a
consistent manner. This will let us centralize things like dealing with
password arguments and whatnot. It also allows us to introduce the
ability to pass a fully formed config dict directly to the module.
Migrate all OpenStack modules to use openstack_cloud_from_module.
Have it return the shade library since it's responsible for
importing shade and shade is needed for the exceptions.
Only pull specific OpenStack arguments for the constructor
Rather than passing **module.params to the shade constructor, pull out
only the values that make sense. This should prevent the issues with
module parameters stepping on shade parameters.
Replace module.params.pop with module.params.get
We don't need to pop these anymore since the shade constructor is now
using opt-in values.
Using real urls is ungood. Use example.com domains. Also, get rid of the
antiquated port numbers.
(cherry picked from commit 0f893027c4)
24 lines
568 B
YAML
24 lines
568 B
YAML
clouds:
|
|
vexxhost:
|
|
profile: vexxhost
|
|
auth:
|
|
project_name: 39e296b2-fc96-42bf-8091-cb742fa13da9
|
|
username: fb886a9b-c37b-442a-9be3-964bed961e04
|
|
password: fantastic-password1
|
|
rax:
|
|
cloud: rackspace
|
|
auth:
|
|
username: example
|
|
password: spectacular-password
|
|
project_id: 2352426
|
|
region_name: DFW,ORD,IAD
|
|
devstack:
|
|
auth:
|
|
auth_url: https://devstack.example.com
|
|
username: stack
|
|
password: stack
|
|
project_name: stack
|
|
ansible:
|
|
use_hostnames: True
|
|
expand_hostvars: False
|
|
fail_on_errors: True
|