----- Original Message ----- > From: "Doron Fediuck" <[email protected]> > To: "Alon Bar-Lev" <[email protected]> > Cc: "Juan Hernandez" <[email protected]>, [email protected] > Sent: Tuesday, January 1, 2013 10:30:29 AM > Subject: Re: [Engine-devel] Engine local configuration > > > All we are saying is DEVELOPMENT=1 is the default, since the code > > > is built differently for production, and installed accordingly. > > > Additionally you may have more than one devel setup, for example > > > for > > > different versions. So unless you override something (such as > > > keystore > > > pass, jboss location) mvn -Pdep should simply work, and make XXX > > > will > > > ensure whatever you need to override is done properly. > > > > > > > > > > No, you miss the point. > > I want to be able to have a full blown product installed for > > development as well. > > The only difference is the PREFIX and may be some other stuff I > > don't > > think of that are specific of development. > > I put the DEVELOPMENT=1 to focus the discussion. > > > > I should have written the following steps to be more clear: > > $ OEHOME=$HOME/ovirt-engine-root > > $ make PREFIX=$OEHOME > > $ make PREFIX=$OEHOME DEVELOPMENT=1 install > > $ cd ${OEHOME} > > $ . ./ovirt-engine.vars > > $ engine-setup > > <snip> > > $ sbin/engie-service.py start > > > > We probably need more vars on the make install, such as JBOSS_HOME, > > but the idea is that you have fully functional product in > > development mode, including PKI and support scripts. > > > > Regards, > > Alon > > Alon, > most universities today will not give you admin privileges. > We must be able to download the code and run it without additional > requirements. It is possible to run jboss with local configuration > (per user). So we should minimize the restrictions and not impose > new once. Running the installation script is nice to have, but > should be completely optional. Especially if you'd like to see it > being deployed in various distro's. So at least developers should > be able to git clone, compile and run. Everything else is packaging. >
You don't need any admin to install at PREFIX=$HOME/ovirt-engine-root We should make sure that we can run all components within PREFIX without root. As far as I can tell, we do not actually need root access for 99% of the implementation, one of the trivial differences is to replace systemctl start/stop with direct script execution in non-root mode. Alon _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
