Bug 1510243

Summary: [Docs][Admin] Updates to Ansible Documentation
Product: Red Hat Enterprise Virtualization Manager Reporter: Byron Gravenorst <bgraveno>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED NOTABUG QA Contact: rhev-docs <rhev-docs>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1.7CC: apinnick, lbopf, lsurette, mgoldboi, srevivo
Target Milestone: ovirt-4.1.11Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-28 08:24:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1475678    

Description Byron Gravenorst 2017-11-07 01:21:17 UTC
Updates to Ansible documentation.

1) Advise customers about the best topology to use for running Ansible on RHV.

---email conversation (mgoldboi & omachace)---

> one thing i think we should do, is advising the customers on the best
> topology to perform it with.
> as far as i see it, we have 3 options
> -remote execution on the manager machine - major downside is that it's
> requires the RHVM root password, and will do copy all the playbooks to the
> engine.
> -remote execution on a machine that will execute the tasks against RHVM -
> downside here is the complexity of the env (additional machine) and
> playbooks needs to be copied over the wire, for translation and execution on
> the remote machine - less performent and more complicated from my POV
> -local execution which translates to api calls to the engine - that's
> probably the recommended way to do it security and performance wise.
>
> any thoughts or comments around this approach?

I completely agree. The best use case is to use localhost, but still
users don't have
to use it like that. So if we recommend them to use it like that, it
would be nice.

-------

2) Additionally, document that the SDK must be installed on the machines,
where the tasks will run, not necessarily where the playbook is executed.

3) Consider adding details on how to obtain the engine certificate (download link from the console client resources) to enable secured operation.

4) Consider updating the example to use the supplied ovirt_infra_var.yml in the ansible examples directory, and show the command line of the playbook.