On Mon, Oct 2, 2017 at 8:52 AM, Simone Tiraboschi <[email protected]> wrote:
> > > On Mon, Oct 2, 2017 at 2:40 PM, Phillip Bailey <[email protected]> > wrote: > >> Yaniv, >> >> 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. >> >> 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. >> > > The current hosted-engine-setup is a noarch rpm but currently we don't > have any ppc engine-appliance to be deployed. > Ah, that makes more sense. Thanks! =) > > >> >> ----- >> >> Artyom, >> >> That project looks awesome and is very helpful. Thank you! >> >> -Phillip Bailey >> >> On Thu, Sep 28, 2017 at 1:37 AM, Artyom Lukianov <[email protected]> >> wrote: >> >>> Our infra team already deploy HE via ansible you can check their work >>> under https://github.com/fusor/ansible-ovirt >>> >>> Best Regards >>> >>> On Wed, Sep 27, 2017 at 6:16 PM, Yaniv Kaul <[email protected]> wrote: >>> >>>> >>>> >>>> On Wed, Sep 27, 2017 at 5:15 PM, Phillip Bailey <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> 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. >>>>> >>>>> 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. >>>>> >>>>> Thanks! >>>>> >>>>> 1. Verify provided storage settings for all allowable storage >>>>> types. >>>>> >>>>> >>>> I'm not sure I understand the requirement here. >>>> >>>> >>>>> >>>>> 1. >>>>> 2. Verify compatibility of selected CPU type for the engine VM >>>>> with the host's CPU >>>>> >>>>> >>>> This is easy. See [1] for a simple Python code. In bash: >>>> virsh -r capabilities |grep -m 1 "<model>" >>>> >>>> Y. >>>> [1] https://github.com/lago-project/lago/pull/323/files#diff >>>> -1b557418847a737490a95d4841c6a362R96 >>>> >>>> -Phillip Bailey >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> [email protected] >>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Devel mailing list >>>> [email protected] >>>> http://lists.ovirt.org/mailman/listinfo/devel >>>> >>> >>> >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/devel >> > >
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
