On 02/18/2012 06:03 AM, Itamar Heim wrote:
> I don't see how we'd have bandwidth to do this differently for oVirt on
> AS and rhev-m on eap. it's quite of an effort doing this once.
> it is also a deployment choice. for the point of argument, rhev may
> choose to use whichever version of jboss they want, it would still be
> the jboss rpm's, as-is, right?
> so why does it matter if they are part of software collections or not?
> the way i see it, software collections only allow to have multiple
> (mostly major) versions of same product (someone has to maintain all
> these version streams).
>
> I think more interesting is to solve allowing to easily create extend
> the jbossas service for pre/post steps of other products, and allow to
> launch multiple instances of it by creating a small wrapper service
> script re-using it (i.e., even if we decide we want ovirt to run jboss
> as ovirt-engine service, instead of jbossas service - I don't want to
> re-write and maintain the jbossas service as the ovirt service.
> I want the ovirt service to use the jbossas service implementation to do
> so with minimal code (make the script a library, or just re-useable and
> allow it to get a parameter of service name when i start it, etc.)
> _______________________________________________
> jboss-rpm mailing list
> jboss-rpm(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-rpm
The parameter you seek for multiple launches off 1 installation is
jboss.server.base.dir.
See also
https://issues.jboss.org/browse/AS7-1752
You can even have the main installation as one user and the ovirt
additional server base as another user.
but how would ovirt service re-use the jboss-as linux service and it's
logic without duplicating it?