[ovirt-users] [ovirt-devel] oVirt 3.5 test day 2 results

[Simone Tiraboschi]

----- Original Message -----
> From: "Jiri Belka" <jbelka at redhat.com>
> To: "Simone Tiraboschi" <stirabos at redhat.com>
> Cc: "users" <users at ovirt.org>, devel at ovirt.org
> Sent: Thursday, July 31, 2014 8:26:20 AM
> Subject: Re: [ovirt-users] [ovirt-devel] oVirt 3.5 test day 2 results
> 
> > > '...no so usable', this is joke. It's real design failure. Do not take
> > > this personally but whoever approved this did bad job.
> > 
> > No, of course: I'm not so proud of it too. :-)
> > 
> > A previous attempt used ssh and scp to do all automatically but it was
> > rejected being judged not so secure.
> > Avoiding to use ssh and scp so seams a strong requirement; if you have any
> > better idea feel free to propose it.
> 
> I will not repeat myself again in details, all setup should be done from
> Admin portal, same was one adds a host.
> 
> Anyway, job spent time on this work is useless. I hope it will be moved
> to trash bin, this is ridiculous.
> 
> What is obvious is that who designed this is not UNIX sysadmin oriented
> junkie.
> 
> j.
> 

The big part of this task was indeed to properly complete the modularization of engine setup: now you can run engine-setup only for the websocket-proxy stuff and it don't try anymore to setup jboss AS and DBMS stuff as it did in the past. We need that in any case.
The work on the console UI for websocket proxy cert was quite small since the 'interface' is really simple.

Of course we can do better, but I'm not so sure we really need it now.

Actual solution can be judged cumbersome but I think that only a few sysadmin are really going to install the websocket proxy on a separate host; I'm almost sure that they aren't going to move it one day on an host and one day on another so a bit of manual work on my opinion can be acceptable on that.

Simone