minor spelling changes

This commit is contained in:
Carlos E. Garcia
2016-12-10 21:50:09 -05:00
committed by Brian Coca
parent 054a3fccf8
commit 0b8011436d
114 changed files with 152 additions and 152 deletions

View File

@@ -17,7 +17,7 @@ Naming
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.
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.
@@ -53,7 +53,7 @@ Libraries
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.
its ready in a manner that is not noticeable to ansible users.
Testing
-------

View File

@@ -284,7 +284,7 @@ def ensure_user_role_exists(keystone, user_name, tenant_name, role_name,
Return (True, id) if a new role was created or if the role was newly
assigned to the user for the tenant. (False, id) if the role already
exists and was already assigned to the user ofr the tenant.
exists and was already assigned to the user for the tenant.
"""
# Check if the user has the role in the tenant

View File

@@ -153,7 +153,7 @@ def main():
if server:
cloud.inspect_machine(server['uuid'], module.params['wait'])
# TODO(TheJulia): diff properties, ?and ports? and determine
# if a change occured. In theory, the node is always changed
# if a change occurred. In theory, the node is always changed
# if introspection is able to update the record.
module.exit_json(changed=True,
ansible_facts=server['properties'])

View File

@@ -58,7 +58,7 @@ options:
default: null
project:
description:
- Name or ID of the project to scope the role assocation to.
- Name or ID of the project to scope the role association to.
If you are using keystone version 2, then this value is required.
required: false
default: null