Merge pull request #1753 from rwellon/RW-IAE-Providers2

General markdown edits for provider topics

Author: agrare

managing_providers/_topics/adding_ansible_galaxy_roles.md

@@ -1,18 +1,10 @@
 ## Installing Roles on an Embedded Ansible Appliance
 
-Roles are ways of automatically loading certain variable files, tasks,
-and handlers based on a known file structure. Grouping content by roles
-also allows easy sharing of roles with other users. Install roles on a
-{{ site.data.product.title_short }} appliance with the Embedded Ansible server role
-activated to optimize playbooks.
+Roles are ways of automatically loading certain variable files, tasks, and handlers based on a known file structure. Grouping content by roles also allows for easy sharing of roles with other users. Install roles on a {{ site.data.product.title_short }} appliance with the Embedded Ansible server role activated to optimize playbooks.
 
-When using this role in a playbook on a {{ site.data.product.title_short }}
-appliance, add an empty `roles` directory at the root of the playbook.
-In the `roles` directory, include a `requirements.yml` file with the
-following contents:
+When using this role in a playbook on a {{ site.data.product.title_short }} appliance, add an empty `roles` directory at the root of the playbook. In the `roles` directory, include a `requirements.yml` file with the following contents:
 
     ---
     - src: <ansible-galaxy-role>
 
-{{ site.data.product.title_short }} will automatically install the role once it sees
-the `requirements.yml` file in the playbook.
+{{ site.data.product.title_short }} automatically installs the role once it sees the `requirements.yml` file in the playbook.

managing_providers/_topics/ansible_credentials.md

@@ -1,217 +1,149 @@
 # Credentials
 
-Credentials are utilized by {{ site.data.product.title_short }} for authentication when
-running Ansible playbooks against machines, synchronizing with inventory
-sources, and importing project content from a version control system.
+Credentials are utilized by {{ site.data.product.title_short }} for authentication when running Ansible playbooks against machines, synchronizing with inventory sources, and importing project content from a version control system.
 
 ## Adding Credentials
 
-{{ site.data.product.title_short }} can store credentials used by playbooks. Credentials
-saved in {{ site.data.product.title_short }} are matched and executed with a playbook
-when run.
+{{ site.data.product.title_short }} can store credentials used by playbooks. Credentials saved in {{ site.data.product.title_short }} are matched and executed with a playbook when run.
 
 1.  Browse to menu: **Automation > Ansible > Credentials**.
 
-2.  Click **Configuration**, then
-    ![Add New Credential](../images/1862.png) (**Add New
-    Credential**).
+2.  Click **Configuration**, then ![Add New Credential](../images/1862.png) (**Add New Credential**).
 
 3.  Provide a **Name** for the credential.
 
-4.  Select the **Credential Type**. Additional fields will appear
-    depending on the type chosen.
+4.  Select the **Credential Type**. Additional fields will appear depending on the type chosen.
 
-    - **Vault Password**: Ansible Vault credentials have only the **Vault
-    Password** attribute that may be configured. For more information on Ansible Vault, see [Using Vault in playbooks](http://docs.ansible.com/ansible/latest/playbooks_vault.html).
+    - **Vault Password**: Ansible Vault credentials have only the **Vault Password** attribute that may be configured. For more information on Ansible Vault, see [Using Vault in playbooks](http://docs.ansible.com/ansible/latest/playbooks_vault.html).
 
 5.  Click **Add**.
 
 ## Credential Types
 
-Each credential type used by {{ site.data.product.title_short }} is detailed in the
-following sections.
+Each credential type used by {{ site.data.product.title_short }} is detailed in the following sections.
 
 ### Machine
 
-Machine credentials enable {{ site.data.product.title_short }} to invoke Ansible on
-hosts under your management. Just like using Ansible on the command
-line, you can specify the SSH username, optionally provide a password,
-an SSH key, or a key password. They define SSH and user-level privilege
-escalation access for playbooks, and are used when running playbooks on
-a remote host.
+Machine credentials enable {{ site.data.product.title_short }} to invoke Ansible on hosts under your management. Just like using Ansible on the command line, you can specify the SSH username, optionally provide a password, an SSH key, or a key password. They define SSH and user-level privilege escalation access for playbooks, and are used when running playbooks on a remote host.
 
-  - **Username**: The username to be used for SSH authentication.
+- **Username**: The username to be used for SSH authentication.
 
-  - **Password**: The actual password to be used for SSH authentication.
+- **Password**: The actual password to be used for SSH authentication.
 
-  - **SSH Private Key**: Copy or drag-and-drop the SSH private key for
-    the machine credential.
+- **SSH Private Key**: Copy or drag-and-drop the SSH private key for the machine credential.
 
-  - **Private Key Passphrase**: If the SSH Private Key used is protected
-    by a password, you can configure a Key Password for the private key.
+- **Private Key Passphrase**: If the SSH Private Key used is protected by a password, you can configure a Key Password for the private key.
 
-  - **Privilege Escalation**: Specifies the type of escalation privilege
-    to assign to specific users. Options include **sudo**, **su**,
-    **pbrun**, **pfexec**.
+- **Privilege Escalation**: Specifies the type of escalation privilege to assign to specific users. Options include **sudo**, **su**, **pbrun**, **pfexec**.
 
-  - **Privilege Escalation Username**: Enter the username to use with
-    escalation privileges on the remote system.
+- **Privilege Escalation Username**: Enter the username to use with escalation privileges on the remote system.
 
-  - **Privilege Escalation Password**: Enter the actual password to be
-    used to authenticate the user via the selected privilege escalation
-    type on the remote system.
+- **Privilege Escalation Password**: Enter the actual password to be used to authenticate the user via the selected privilege escalation type on the remote system.
 
 ### Network
 
-Network credentials are used by Ansible networking modules to connect to
-and manage networking devices.
+Network credentials are used by Ansible networking modules to connect to and manage networking devices.
 
 Network credentials have several attributes that may be configured:
 
-  - **Username**: The username to use in conjunction with the network
-    device.
+- **Username**: The username to use in conjunction with the network device.
 
-  - **Password**: The password to use in conjunction with the network
-    device.
+- **Password**: The password to use in conjunction with the network device.
 
-  - **Authorize**: Select this from the Options field to add an
-    Authorize password which signs the RSA key with a password.
+- **Authorize**: Select this from the Options field to add an Authorize password which signs the RSA key with a password.
 
-  - **Authorize password**: If **Authorize** is checked, enter a
-    password in the **Authorize Password** field.
+- **Authorize password**: If **Authorize** is checked, enter a password in the **Authorize Password** field.
 
-  - **SSH Key**: Copy or drag-and-drop the actual SSH Private Key to be
-    used to authenticate the user to the network via SSH.
+- **SSH Key**: Copy or drag-and-drop the actual SSH Private Key to be used to authenticate the user to the network via SSH.
 
-  - **Private key passphrase**: The actual passphrase for the private
-    key to be used to authenticate the user to the network via SSH.
+- **Private key passphrase**: The actual passphrase for the private key to be used to authenticate the user to the network via SSH.
 
 ### SCM
 
-SCM (source control) credentials are used with Projects to clone and
-update local source code repositories from a remote revision control
-system such as Git, Subversion, or Mercurial.
+SCM (source control) credentials are used with Projects to clone and update local source code repositories from a remote revision control system such as Git, Subversion, or Mercurial.
 
-Source Control credentials have several attributes that may be
-configured:
+Source Control credentials have several attributes that may be configured:
 
-  - **Username**: The username to use in conjunction with the source
-    control system.
+- **Username**: The username to use in conjunction with the source control system.
 
-  - **Password**: The password to use in conjunction with the source
-    control system.
+- **Password**: The password to use in conjunction with the source control system.
 
-  - **Private key passphrase**: If the SSH private key used is protected
-    by a passphrase, you may configure a key passphrase for the private
-    key.
+- **Private key passphrase**: If the SSH private key used is protected by a passphrase, you may configure a key passphrase for the private key.
 
-  - **Private Key**: Copy or drag-and-drop the actual SSH Private Key to
-    be used to authenticate the user to the source control system via
-    SSH.
+- **Private Key**: Copy or drag-and-drop the actual SSH Private Key to be used to authenticate the user to the source control system via SSH.
 
 ### Amazon
 
-Selecting this credential type enables synchronization of cloud
-inventory with Amazon Web Services.
+Selecting this credential type enables synchronization of cloud inventory with Amazon Web Services.
 
-  - **Access Key**: User credentials that allow for programmatic calls
-    to Amazon Web Services.
+- **Access Key**: User credentials that allow for programmatic calls to Amazon Web Services.
 
-  - **Secret Key**: The secret key that corresponds to the user access
-    key.
+- **Secret Key**: The secret key that corresponds to the user access key.
 
-  - **STS Token**: Token generated by Amazon Web Services Security Token
-    Service.
+- **STS Token**: Token generated by Amazon Web Services Security Token Service.
 
 ### Azure
 
-Selecting this credential type enables synchronization of cloud
-inventory with Microsoft Azure.
+Selecting this credential type enables synchronization of cloud inventory with Microsoft Azure.
 
 Microsoft Azure credentials have several attributes to configure:
 
-  - **Username**: The username to use to connect to the Microsoft Azure
-    account.
+- **Username**: The username to use to connect to the Microsoft Azure account.
 
-  - **Password**: The password to use to connect to the Microsoft Azure
-    account.
+- **Password**: The password to use to connect to the Microsoft Azure account.
 
-  - **Subscription ID**: The Subscription UUID for the Microsoft Azure
-    account.
+- **Subscription ID**: The Subscription UUID for the Microsoft Azure account.
 
-  - **Tenant ID**: The Tenant ID for the Microsoft Azure account.
+- **Tenant ID**: The Tenant ID for the Microsoft Azure account.
 
-  - **Client Secret**: The Client Secret for the Microsoft Azure
-    account.
+- **Client Secret**: The Client Secret for the Microsoft Azure account.
 
-  - **Client ID**: The Client ID for the Microsoft Azure account.
+- **Client ID**: The Client ID for the Microsoft Azure account.
 
 ### OpenStack
 
-Selecting this credential type enables synchronization of cloud
-inventory with Red Hat OpenStack Platform.
+Selecting this credential type enables synchronization of cloud inventory with Red Hat OpenStack Platform.
 
 OpenStack credentials have several attributes that may be configured:
 
-  - **Username**: The username to use to connect to OpenStack.
+- **Username**: The username to use to connect to OpenStack.
 
-  - **Password (API Key)**: The password or API key to use to connect to
-    OpenStack.
+- **Password (API Key)**: The password or API key to use to connect to OpenStack.
 
-  - **Host (Authentication URL)**: The host to be used for
-    authentication.
+- **Host (Authentication URL)**: The host to be used for authentication.
 
-  - **Project (Tenant Name)**: The Tenant name or Tenant ID used for
-    OpenStack. This value is usually the same as the username.
+- **Project (Tenant Name)**: The Tenant name or Tenant ID used for OpenStack. This value is usually the same as the username.
 
-  - **Domain name**: The FQDN to be used to connect to OpenStack.
+- **Domain name**: The FQDN to be used to connect to OpenStack.
 
 ### Red Hat Virtualization
 
-Selecting this credential type enables synchronization of cloud
-inventory with Red Hat Virtualization.
+Selecting this credential type enables synchronization of cloud inventory with Red Hat Virtualization.
 
-Red Hat Virtualization credentials have several attributes that may be
-configured:
+Red Hat Virtualization credentials have several attributes that may be configured:
 
-  - **Username**: The username to use to connect to Red Hat
-    Virtualization.
+- **Username**: The username to use to connect to Red Hat Virtualization.
 
-  - **Password**: The password to use to connect to Red Hat
-    Virtualization.
+- **Password**: The password to use to connect to Red Hat Virtualization.
 
-  - **Host (Authentication URL)**: The host to be used for
-    authentication.
+- **Host (Authentication URL)**: The host to be used for authentication.
 
-    <div class="important">
+   **Important**: Enter in **Host** the Red Hat Virtualization provider URL, followed by the path `/ovirt_engine/api`. Example: `https://your.rhv.com/ovirt_engine/api`
 
-      - Enter in **Host** the Red Hat Virtualization provider URL,
-        followed by the path `/ovirt_engine/api`. Example:
-        `https://your.rhv.com/ovirt_engine/api`
-
-      - See [Ansible Roles](https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/chap-automating_rhv_configuration_using_ansible#Ansible_Roles)
-        for more information on Ansible Roles available for Red Hat
-        Virtualization.
-
-    </div>
+   For more information on the Ansible Roles that are available for Red Hat Virtualization, see [Ansible Roles](https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/chap-automating_rhv_configuration_using_ansible#Ansible_Roles).
 
 ### VMware
 
-Selecting this credential type enables synchronization of inventory with
-VMware vCenter.
+Selecting this credential type enables synchronization of inventory with VMware vCenter.
 
-**Important:**
-
-If both {{ site.data.product.title_short }} and a VMware provider are located in the same IPv6-only network, use a DNS-resolvable hostname for the VMware provider in the **vCenter Host** field when adding credentials.
+**Important:** If both {{ site.data.product.title_short }} and a VMware provider are located in the same IPv6-only network, use a DNS-resolvable hostname for the VMware provider in the **vCenter Host** field when adding credentials.
 
 VMware credentials have several attributes that may be configured:
 
-  - **Username**: The username to use to connect to vCenter.
-
-  - **Password**: The password to use to connect to vCenter.
+- **Username**: The username to use to connect to vCenter.
 
-  - **vCenter Host**: The vCenter hostname or IP address to connect to.
+- **Password**: The password to use to connect to vCenter.
 
-**Note:**
+- **vCenter Host**: The vCenter hostname or IP address to connect to.
 
-If the VMware guest tools are not running on the instance, VMware inventory sync may not return an IP address for that instance.
+**Note:** If the VMware guest tools are not running on the instance, VMware inventory sync may not return an IP address for that instance.