ansible/contrib/inventory/openstack.yml

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
Add documentation for the new OpenStack Inventory 2015-02-26 17:59:00 +01:00			`clouds:`
Add a module_utils OpenStack Cloud constructor (#20974) 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. 2018-02-15 15:20:49 +01:00			`vexxhost:`
			`profile: vexxhost`
Add documentation for the new OpenStack Inventory 2015-02-26 17:59:00 +01:00			`auth:`
Add a module_utils OpenStack Cloud constructor (#20974) 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. 2018-02-15 15:20:49 +01:00			`project_name: 39e296b2-fc96-42bf-8091-cb742fa13da9`
			`username: fb886a9b-c37b-442a-9be3-964bed961e04`
			`password: fantastic-password1`
Add documentation for the new OpenStack Inventory 2015-02-26 17:59:00 +01:00			`rax:`
			`cloud: rackspace`
			`auth:`
			`username: example`
			`password: spectacular-password`
			`project_id: 2352426`
			`region_name: DFW,ORD,IAD`
			`devstack:`
			`auth:`
Add a module_utils OpenStack Cloud constructor (#20974) 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. 2018-02-15 15:20:49 +01:00			`auth_url: https://devstack.example.com`
Add documentation for the new OpenStack Inventory 2015-02-26 17:59:00 +01:00			`username: stack`
			`password: stack`
			`project_name: stack`
Optionally only use UUIDs for openstack hosts on duplicates The OpenStack inventory lists hostnames as the UUIDs because hostsnames are not guarnateed to be unique on OpenStack. However, for the common case, this is just confusing. The new behavior is a visible change, so make it an opt-in via config. Only turn the hostnames to UUIDs if there are duplicate hostnames. 2015-12-03 16:04:24 +01:00			`ansible:`
			`use_hostnames: True`
			`expand_hostvars: False`
Allow fail_on_errors in openstack inventory Add support for a new option to the openstack inventory. This is so should one cloud be unavailable you can still list hosts from any other openstack clouds you have configured. This is exposed as an option under the extra config part of ansible in the openstack clouds.yaml. 2016-02-29 05:21:42 +01:00			`fail_on_errors: True`