a-c-m
/
community.general
mirror of https://github.com/ansible-collections/community.general.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
community.general/lib/ansible/modules/cloud/openstack
History
Mohammed Naser ca9387dc0b Pop password from os_user params 
The password param conflicts with os-client-config's password grabbing.
The rest of the params really probably should also be popped - but
keeping this just to password for now. Will follow up with a change that
does an audit of all the os_ modules

This patch was previously contributed by @emonty to the former
ansible-modules-core repo however since the merge, it was closed
and not completed.  This patch includes the necessary changes cleaned
up to work with the latest release of Ansible.  This has been
tested to work internally
 		2017-01-14 08:32:27 -05:00
..
README.md minor spelling changes 2016-12-13 13:51:13 -05:00
__init__.py added __init__.py to new cloud subcategories so builds work again 2016-12-08 11:22:25 -05:00
_glance_image.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_keystone_user.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_nova_compute.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_nova_keypair.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_quantum_floating_ip.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_quantum_floating_ip_associate.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_quantum_network.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_quantum_router.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_quantum_router_gateway.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_quantum_router_interface.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
_quantum_subnet.py Use M() to link to the replacement module. (#19976) 2017-01-06 16:21:39 +00:00
os_auth.py Fix differences with devel. 2016-12-08 11:35:21 -05:00
os_client_config.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_flavor_facts.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_floating_ip.py Resolving differences in core modules post-merge 2016-12-08 11:25:36 -05:00
os_group.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_image.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_image_facts.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_ironic.py Some additional module cleanup of mistakes made during merging 2016-12-08 11:35:20 -05:00
os_ironic_inspect.py minor spelling changes 2016-12-13 13:51:13 -05:00
os_ironic_node.py Resolving differences in core modules post-merge 2016-12-08 11:25:36 -05:00
os_keypair.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_keystone_domain.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_keystone_domain_facts.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_keystone_role.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_keystone_service.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_network.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_networks_facts.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_nova_flavor.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_nova_host_aggregate.py added os_aggregate module (#19374) 2016-12-29 12:51:34 -05:00
os_object.py Resolving differences in core modules post-merge 2016-12-08 11:25:36 -05:00
os_port.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_port_facts.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_project.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_project_facts.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_quota.py Adding os_quota support to the OpenStack modules (#19590) 2017-01-08 18:55:12 +00:00
os_recordset.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_router.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_security_group.py Resolving differences in core modules post-merge 2016-12-08 11:25:36 -05:00
os_security_group_rule.py Resolving differences in core modules post-merge 2016-12-08 11:25:36 -05:00
os_server.py Verify image exists when passed for server creation 2016-12-22 22:37:59 +00:00
os_server_actions.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_server_facts.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_server_group.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_server_volume.py Resolving differences in core modules post-merge 2016-12-08 11:25:36 -05:00
os_stack.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_subnet.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_subnets_facts.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_user.py Pop password from os_user params 2017-01-14 08:32:27 -05:00
os_user_facts.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00
os_user_group.py Refreshed metadata for core modules 2016-12-08 11:25:35 -05:00
os_user_role.py minor spelling changes 2016-12-13 13:51:13 -05:00
os_volume.py Resolving differences in core modules post-merge 2016-12-08 11:25:36 -05:00
os_zone.py Relocating extras into lib/ansible/modules/ after merge 2016-12-08 11:35:18 -05:00

README.md

OpenStack Ansible Modules

These are a set of modules for interacting with OpenStack as either an admin or an end user. If the module does not begin with os_, it's either deprecated or soon to be. This document serves as developer coding guidelines for modules intended to be here.

Naming

  • All modules should start with os_
  • If the module is one that a cloud consumer would expect to use, it should be named after the logical resource it manages. Thus, os_server not os_nova. The reasoning for this is that there are more than one resource that are managed by more than one service and which one manages it is a deployment detail. A good example of this are floating IPs, which can come from either Nova or Neutron, but which one they come from is immaterial to an end user.
  • If the module is one that a cloud admin would expect to use, it should be be named with the service and the resource, such as os_keystone_domain.
  • If the module is one that a cloud admin and a cloud consumer could both use, the cloud consumer rules apply.

Interface

  • If the resource being managed has an id, it should be returned.
  • If the resource being managed has an associated object more complex than an id, it should also be returned.

Interoperability

  • It should be assumed that the cloud consumer does not know a bazillion details about the deployment choices their cloud provider made, and a best effort should be made to present one sane interface to the ansible user regardless of deployer insanity.
  • All modules should work appropriately against all existing known public OpenStack clouds.
  • It should be assumed that a user may have more than one cloud account that they wish to combine as part of a single ansible managed infrastructure.

Libraries

  • All modules should use openstack_full_argument_spec to pick up the standard input such as auth and ssl support.
  • All modules should extends_documentation_fragment: openstack to go along with openstack_full_argument_spec.
  • All complex cloud interaction or interoperability code should be housed in the shade library.
  • All OpenStack API interactions should happen via shade and not via OpenStack Client libraries. The OpenStack Client libraries do no have end users as a primary audience, they are for intra-server communication. The python-openstacksdk is the future there, and shade will migrate to it when its ready in a manner that is not noticeable to ansible users.

Testing