1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
community.general/lib/ansible/modules/cloud/openstack
Sam Doran 38c0769abb Examples syntax batch5 (#5622)
* Change example syntax on supervisorctl module

* Change example syntax or _ec2_ami_search module

* Change example syntax on cloudformation module

* Change example syntax on ec2 module

* Change example syntax on ec2_facts module

* Change example syntax on ec2_eip module

* Change example syntax on rds module

* Change example syntax on route53 module

* Change example syntax on s3 module

* Change example syntax on digital_ocean module

* Change example syntax on docker_service module

* Change example syntax on cloudformation module

* Change example syntax on gc_storage module

* Change example syntax on gce module

* Change example syntax on gce_mig module

* Change example syntax on _glance_image module

* Change example syntax on _keystone_user module

* Change example syntax on _nova_keypair module

* Change example syntax on _quantum_floating module

* Change example syntax on _quantum_floating_ip_associate module

* Change example syntax on _quantum_network module

* Change example syntax on _quantum_router module

* Change example syntax on _quantum_router_gateway module

* Change example syntax on _quantum_router_interface module

* Change example syntax on _quantum_subnet module

* SQUASH _quantum_subnet

* Add missing quotes
2016-12-08 11:25:31 -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 Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_keystone_user.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_nova_compute.py nova_compute: indicate argument type (#4070) 2016-12-08 11:24:41 -05:00
_nova_keypair.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_quantum_floating_ip.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_quantum_floating_ip_associate.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_quantum_network.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_quantum_router.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_quantum_router_gateway.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
_quantum_router_interface.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
os_auth.py Fix OpenStack module failure output 2016-12-08 11:24:00 -05:00
os_client_config.py Wrap calls to main() with if check 2016-12-08 11:24:16 -05:00
os_floating_ip.py Expose internal_network in os_floating_ip (#5510) 2016-12-08 11:25:27 -05:00
os_image.py Wrap calls to main() with if check 2016-12-08 11:24:16 -05:00
os_image_facts.py s/plubic/public/in the doc 2016-12-08 11:24:14 -05:00
os_ironic.py Bulk spelling improvement to modules-core (#5225) 2016-12-08 11:25:20 -05:00
os_ironic_node.py Wrap calls to main() with if check 2016-12-08 11:24:16 -05:00
os_keypair.py Fix OpenStack module failure output 2016-12-08 11:24:00 -05:00
os_network.py Add uplink provider type (#5282) 2016-12-08 11:25:26 -05:00
os_networks_facts.py Remove version-added on name field. 2016-12-08 11:24:44 -05:00
os_nova_flavor.py Fix OpenStack module failure output 2016-12-08 11:24:00 -05:00
os_object.py Wrap calls to main() with if check 2016-12-08 11:24:16 -05:00
os_port.py Fix allowed_address_pairs and extra_dhcp_opts in os_port 2016-12-08 11:24:13 -05:00
os_router.py Fix bug in os_router.py when router is not actually updated. (#4107) 2016-12-08 11:24:43 -05:00
os_security_group.py Docs update for os_security_group (#5531) 2016-12-08 11:25:27 -05:00
os_security_group_rule.py Fix openstack security group rule vrrp choice apostrophe error (#4750) 2016-12-08 11:25:11 -05:00
os_server.py replace type() with isinstance() (#5541) 2016-12-08 11:25:27 -05:00
os_server_actions.py Add rebuild support to os_server_actions (#4289) 2016-12-08 11:25:25 -05:00
os_server_facts.py Fix OpenStack module failure output 2016-12-08 11:24:00 -05:00
os_server_volume.py Fix OpenStack module failure output 2016-12-08 11:24:00 -05:00
os_subnet.py Bulk spelling improvement to modules-core (#5225) 2016-12-08 11:25:20 -05:00
os_subnets_facts.py Fix parameters where type is assumed. 2016-12-08 11:24:05 -05:00
os_user.py Add update_password argument to os_user (#5219) 2016-12-08 11:25:26 -05:00
os_user_group.py Fix OpenStack module failure output 2016-12-08 11:24:00 -05:00
os_volume.py Fix size parameter documentation 2016-12-08 11:24:13 -05:00
quantum_subnet.py Examples syntax batch5 (#5622) 2016-12-08 11:25:31 -05:00
README.md Return resource objects from OpenStack modules 2016-12-08 11:23:09 -05:00

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 resouce, 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 noticable to ansible users.