No description
3e7b240696
* Add os_keystone_service_endpoint This patch adds a new Ansible module which allows a user to create an endpoint to a service with Keystone. Fixes #23909 * os_keystone_endpoint: Fix style and messages Fix comments, pep8, version, metadata, license header and imports according to the Contributing Modules Checklist Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> * os_keystone_endpoint: Fix return values - Change type of 'endpoint' return value from dictionary to complex in order to get validate_module checks passed. - Remove 'id' from the return data since it is included inside the 'endpoint' value wich is already being returned. - Rename 'service' field to 'service_id' which is the correct name for the service id field returned in json. Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> * os_keystone_endpoint: Update shade version Update minimum shade version to 1.11.0 Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> * os_keystone_endpoint: Make region optional Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> * os_keystone_endpoint: Validate service exists before using service.id Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> * os_keystone_endpoint: Fix documentation for service to accept name or id Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> * os_keystone_endpoint: Pass the full service object to create_endpoint() We already have the service object retrieved in code, by passing service.id to create_endpoint, the shade librarie queries the api again to get the full service object. By Passing the already rerieved service object to create_endpoint() we save one request to the API. Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> * os_keystone_endpoint: Make type explicit in module arguments. Althoug type is default to str when not specified in module arguments this commit explicitly defines type='str' for better readability. Signed-off-by: Alberto Murillo <albertomurillosilva@gmail.com> |
||
|---|---|---|
| .github | ||
| bin | ||
| contrib | ||
| docs | ||
| examples | ||
| hacking | ||
| lib/ansible | ||
| packaging | ||
| test | ||
| ticket_stubs | ||
| .coveragerc | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .yamllint | ||
| ansible-core-sitemap.xml | ||
| CHANGELOG.md | ||
| CODING_GUIDELINES.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| docsite_requirements.txt | ||
| Makefile | ||
| MANIFEST.in | ||
| MODULE_GUIDELINES.md | ||
| README.md | ||
| RELEASES.txt | ||
| requirements.txt | ||
| ROADMAP.rst | ||
| setup.py | ||
| shippable.yml | ||
| tox.ini | ||
| VERSION | ||
Ansible
Ansible is a radically simple IT automation system. It handles configuration-management, application deployment, cloud provisioning, ad-hoc task-execution, and multinode orchestration - including trivializing things like zero downtime rolling updates with load balancers.
Read the documentation and more at https://ansible.com/
You can find installation instructions here for a variety of platforms. Most users should probably install a released version of Ansible from pip, a package manager or our release repository. Officially supported builds of Ansible are also available. Some power users run directly from the development branch - while significant efforts are made to ensure that devel is reasonably stable, you're more likely to encounter breaking changes when running Ansible this way.
Design Principles
- Have a dead simple setup process and a minimal learning curve
- Manage machines very quickly and in parallel
- Avoid custom-agents and additional open ports, be agentless by leveraging the existing SSH daemon
- Describe infrastructure in a language that is both machine and human friendly
- Focus on security and easy auditability/review/rewriting of content
- Manage new remote machines instantly, without bootstrapping any software
- Allow module development in any dynamic language, not just Python
- Be usable as non-root
- Be the easiest IT automation system to use, ever.
Get Involved
- Read Community Information for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
- All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use
git rebasevsgit mergefor this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed. - Users list: ansible-project
- Development list: ansible-devel
- Announcement list: ansible-announce - read only
- irc.freenode.net: #ansible
Branch Info
- Releases are named after Led Zeppelin songs. (Releases prior to 2.0 were named after Van Halen songs.)
- The devel branch corresponds to the release actively under development.
- Various release-X.Y branches exist for previous releases.
- We'd love to have your contributions, read Community Information for notes on how to get started.
Authors
Ansible was created by Michael DeHaan (michael.dehaan/gmail/com) and has contributions from over 1000 users (and growing). Thanks everyone!
Ansible is sponsored by Ansible, Inc
License
GNU General Public License v3.0
See COPYING to see the full text.