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

[ybronhei]

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)
"""

next foreman build foreman-installer will include the 
--enable-foreman-plugin-ovirt-provision option which will make it 
easier. its already merged.

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.

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
>>
>


-- 
Yaniv Bronhaim.