Re: [Users] Migrating engine-setup to otopi
Hi Jiri
----- Original Message -----
From: "Jiri Belka" <jbelka(a)redhat.com>
To: "Alex Lourie" <alourie(a)redhat.com>
Cc: engine-devel(a)ovirt.org, users(a)ovirt.org
Sent: Thursday, March 14, 2013 12:38:46 PM
Subject: Re: [Users] Migrating engine-setup to otopi
On Thu, 14 Mar 2013 06:13:39 -0400 (EDT)
Alex Lourie <alourie(a)redhat.com> wrote:
> Hi All
>
> Recent development of the otopi [1] framework allows us to migrate
> the engine-setup,
> upgrade and cleanup (and potentially other) utilities to
> implementation as an otopi
> plugin.
>
> Potential benefits of such a move are:
>
> 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...
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.
Anyway, everything what is not RPM/YUM specific and more portable
is good way...
Thanks!
jbelka
--
Best regards,
Alex Lourie
Software Developer in Integration
Red Hat