Description of problem: From bug 847833#c13 "Another thing that I just noticed, after looking at the logs again, was that we're exporting /usr/local/exports/iso as r/w. IMHO exporting anything in /usr as r/w is a bad idea. If the installer is going to set up an export for /usr it should be 'read' only and not r/w. R/W should be in /var or something." Expected results: Create the export according best practice
if doing this, need to consider upgrade implications
This is just the default value that we suggest during installation, before that we didn't suggest anything. So from the upgrade point of view there shouldn't be any additional implication: the upgrade must support any directory, as the user can choose any directory. I agree that we should suggest something outside of /usr and that something under /var makes more sense. What about /var/lib/ovirt-engine/exports? We already put other variable data under /var/lib/ovirt-engine, and we create and track that directory as part of the RPMs.
I don't think this should be under /var/lib/ovirt-engine, too sensitive. Better /var/lib/exports/XXXX.
If we all agree that /var/lib/exports is better than /usr/local/exports then the following change can fix it: http://gerrit.ovirt.org/7563
(In reply to comment #4) > If we all agree that /var/lib/exports is better than /usr/local/exports then > the following change can fix it: > > http://gerrit.ovirt.org/7563 +1
The proposed change has been merged upstream: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=dcd746d6e4faf9fac5cf1894ab6896aef4541b48
ok - si18