<div dir="ltr">Yaniv,<br><br>The goal with the storage requirement is to verify connectivity of the storage information provided by the user, as the input is being gathered prior to running the setup process. The intent is to be able to provide warnings to the user during the data collection process.<br><br>Thanks for the CPU-related information. I was already pulling the CPU model from the Ansible setup module. I needed help with verifying that the model selected for the HE VM is compatible with the host's model. The link you provided had the list available there, which helps tremendously. The only issue I can see is that PPC models aren't included in that list.<br><br>-----<br><br>Artyom,<br><br>That project looks awesome and is very helpful. Thank you!</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">-Phillip Bailey</div></div></div>
<br><div class="gmail_quote">On Thu, Sep 28, 2017 at 1:37 AM, Artyom Lukianov <span dir="ltr"><<a href="mailto:alukiano@redhat.com" target="_blank">alukiano@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Our infra team already deploy HE via ansible you can check their work under <a href="https://github.com/fusor/ansible-ovirt" target="_blank">https://github.com/<wbr>fusor/ansible-ovirt</a><div><br></div><div>Best Regards</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 27, 2017 at 6:16 PM, Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Sep 27, 2017 at 5:15 PM, Phillip Bailey <span dir="ltr"><<a href="mailto:phbailey@redhat.com" target="_blank">phbailey@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi all,</div><div><br></div><div>I'm working on the new Cockpit hosted engine wizard and could use some input from all of you. One goal of this project is to move away from reliance on the existing OTOPI-based tools and towards an ansible-based approach.<br><br>The items below are things we'd like to do using ansible, if possible. If any of you have existing plays or suggestions for the best way to use ansible to solve these problems, please let me know.</div><div><br></div><div>Thanks!<br><div><ol><li>Verify provided storage settings for all allowable storage types.<br></li></ol></div></div></div></blockquote><div><br></div></span><div>I'm not sure I understand the requirement here.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><ol><li></li><li>Verify compatibility of selected CPU type for the engine VM with the host's CPU</li></ol></div></div></div></blockquote><div><br></div></span><div>This is easy. See [1] for a simple Python code. In bash:</div><div>virsh -r capabilities |grep -m 1 "<model>"<br></div><div><br></div><div>Y.</div><div>[1] <a href="https://github.com/lago-project/lago/pull/323/files#diff-1b557418847a737490a95d4841c6a362R96" target="_blank">https://github.com/lago-pr<wbr>oject/lago/pull/323/files#diff<wbr>-1b557418847a737490a95d4841c6a<wbr>362R96</a></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span class="m_-952283575778939718m_-7970173915109618878gmail-HOEnZb"><font color="#888888"><div><div><div class="m_-952283575778939718m_-7970173915109618878gmail-m_9169472778476895952gmail_signature"><div dir="ltr">-Phillip Bailey</div></div></div>
</div></font></span></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></blockquote></div><br></div></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>