[Users] Migrating engine-setup to otopi

[Alon Bar-Lev]

----- Original Message -----
> From: "Jiri Belka" <jbelka at redhat.com>
> To: "Alex Lourie" <alourie at redhat.com>
> Cc: engine-devel at ovirt.org, users at ovirt.org
> Sent: Thursday, March 14, 2013 1:47:12 PM
> Subject: Re: [Users] Migrating engine-setup to otopi
> 
> On Thu, 14 Mar 2013 07:06:04 -0400 (EDT)
> Alex Lourie <alourie at redhat.com> wrote:
> 
> > > > 1. Be able to port engine to other distributions.
> > > 
> > > Really? Beside this topic I see hardcoded usernames in scripts...
> > > 
> > > http://gerrit.ovirt.org/#/c/12551/2/backend/manager/dbscripts/dbfunctions.sh,unified
> > 
> > These usernames are not hard-coded. There are default values
> > present which are kept for
> > local installations, but with remote DB setup the user is prompted
> > to provide a username
> > of her/his own.
> 
> Not everywhere are postgresql dirs owned by postgres, on some BSDs it
> is
> _postgresql.

Right, as I said this is going away.

I am porting this first to Gentoo, which is the most complex, then I will be able to provide debian based.

For the postgres issue, I am against assuming local database and the configuration of the database it-self (hba, etc).

Like in other products, the dba will create a user and a database with the user as an owner and provide us the user/password and database name, this method does not require privileged database user for product installation and working locally or remotely, and is portable.

We will keep the functionality of system provisioning as an optional component exists in some distribution.

Regards,
Alon Bar-Lev