ovirt-engine deployment method

[Itamar Heim]

On 04/17/2012 04:20 PM, Ofer Schreiber wrote:
> As decided earlier, oVirt next release (3.1) is targeted for Fedora 17.
> Since the engine uses JBoss, we have two deployment options:
> 1. Continue working with ovirt-engine-jbossas package
>     PROS: Single rpm. known upgrade method.
>     CONS: Maintaining un-natural zip based rpm. No official support. Can't be pushed into Fedora.
>
> 2. Move to JBoss F17 official packages:
>     PROS: Fully supported F17 rpms (including bug fixes, security fixes, etc). "The right thing to do".
>     CONS: Upgrade from first release (relaying on old jboss) will be almost impossible, Some open issues (will it work just as as normal service? or will we need to code a new one?), Might cause a delay to Feature Freeze.
>
> Thought? Comments?

we also want to push this version of ovirt into fedora (3.0 already in), 
which will require the native jboss rpms?

> Share them with us!
> ---
> Ofer Schreiber
> oVirt Release Manager
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch