Re: [ovirt-users] http://www.ovirt.org/Features/ForemanIntegration

On 11.11.2014 16:09, ybronhei wrote: > On 11/11/2014 03:25 PM, Daniel Helgenberger wrote: >> >> >> On 11.11.2014 13:46, ybronhei wrote: >>> Hey Daniel, >>> Thanks for your comments. >>> First, I do mention the requirement for having ovirt_provision_plugin >>> installed in bullet 2: >>> """Add oVirt Provision Plugin: "yum install >>> ruby193-rubygem-ovirt_provision_plugin" \ "foreman-installer >>> --enable-foreman-plugin-ovirt-provision" (Not available yet) >>> """ >> Indeed, I read that. My reasoning at this point it might be too late in >> the text. Users (me included) already have tried this at this point >> using the pictured guide and failing because of the missing provider. >> >> This is the point witch was entirely unclear for me in my first attempt >> and it took me a while to find out. >> >> While the discovery plugin is needed (only) for Bare-Metal Provisioning, >> the ovirt provider is always needed for the integration to succeed. >> >> I did think about a hint early on describing the workflow briefly in the >> detailed description section: >> - Make sure Foreman is running at version X >> - Install RPMs in Foreman (see Bare-Metal Provisioning) >> - Go to engine, "Adding foreman provider" > I don't see why the current way we arrange the page is misleading. Sorry if this is unclear. But: For the "Test" button in "Add external provider" in Engine GUI to work, one *needs* do this on the Foreman host: # yum install ruby193-rubygem-ovirt_provision_plugin

If this this assumption is true (it was for me reproducible) Foreman/oVirt communication will fail.

Therefore I am still convinced it is reasonable to put this as the first step before ever trying to add the provider in oVirt.* The other things, like bare metal prov. and so on are optional. Installing the oVirt - provider on the Foreman host is not. > > We have under "Detailed Description" 3 levels which have different > prerequisites - > Adding installed Foreman hosts as oVirt hosts - which just requires > foreman setup, To make this clear, this is not correct since the default foreman setup does not have the oVirt provider module installed. There are some use cases where Foreman is added because of oVirt, and some will have Foreman already runningin their infra. In this case, foreman-installer was already run. * At least I was struggling with this requirement. Truth be told, Foreman was one point on a (very long) check list of mine; so I might not have paid proper attention to the details. OTOH the document suggested a strait forward approach with nice details and icons on how to do it oVirt. For instance, when I got to the section "Bare Metal Provisioning" I looked briefly over the requirements and decided to do this later on. Wrong here, since there is what I need to get it running in the first place! The other issue, having two different (one obsolete) ForemanIntegration docs, is solved now. > Bare-Metal Provisioning - which requires many things. starts with the > ovirt plugin, discovery plugin, configuration of hostgroups > computeresource medias and ends with setting the provisioning templates > accordingly for node installation. > > and last - Future Plans: VM provisioning which still in declaration phase. >> >> >>> >>> next foreman build foreman-installer will include the >>> --enable-foreman-plugin-ovirt-provision option which will make it >>> easier. its already merged. >> This is great to know! >> >>> >>> Second, about the openjdk issue, I don't think it worth to mention. I'll >>> add to the "Current Status" section that the integration is supported >>> over rhel6.6 and above. >> This will do here. >> >>> >>> Yaniv Bronhaim. >>> >>> On 11/11/2014 02:38 PM, Daniel Helgenberger wrote: >>>> Hello Yaniv, >>>> >>>> thank you! >>>> >>>> On 10.11.2014 10:04, ybronhei wrote: >>>>> For those who interested, I merged the pages ForemanIntegration and >>>>> AdvancedForemanIntegration to ease the search. >>>>> >>>>> The page includes full description about the current integration we have >>>>> with foreman [aka satellite\katello], the future plans, how to setup >>>>> environment for testing and production and more illustrations to make it >>>>> easier to follow >>>>> >>>>> feel free to comment about that (directly to me or to the list) and you >>>>> more than welcome to try that at home :) >>>> I think there might be still the issue I ran into: >>>> >>>> A prerequisite to adding Foreman external provider in oVirt is (at least >>>> for me) that Foreman has *ruby193-rubygem-ovirt_provision_plugin* rpm >>>> installed. Otherwise the test will fail with: >>>> "Failed with error PROVIDER_FAILURE and code 5050" >>>> >>>> Sp, on the foreman host one needs to do: >>>> yum install ruby193-rubygem-ovirt_provision_plugin >>>> >>>> Also, please note there is an issue users might run into at this step, >>>> so it may be worth noting. >>>> Foreman integration will fail altogether on Engines running =< El6.5 >>>> because of an too old jdk version not supporting DH keys larger then >>>> 1024 byte [1]. >>>> This is not an issue in oVirt and will never be resolved. Luckily, >>>> upgrading to the latest openjdk >>>> (java-1.7.0-openjdk-1.7.0.71-2.5.3.1.el6.x86_64) solves the issue (on >>>> the ENGINE!) >>>> >>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1157749 >>>>> >>>>> Thanks >>>>> >>>> >>> >>> >> > >