More feedback from Didi in regards to the data warehouse and reports topics.
========================
8.4.1 Prerequisites 1.: Not exactly. You can also set them up all at once.
Not that important.
8.4.2 Prerequisites 2.: I'd phrase the last two a bit more generally,
perhaps:
- Access to the database of the engine.
If it was set up automatically, (then the existing text), otherwise
you'll also need to provide access on the database machine to the
dwh/reports machine (including pg_hba.conf, firewall, etc., up to you how
much to detail).
Similarly with the other procedures.
Procedure 8.2. step 6 and 8: Do not install the package 'rhevm'. If for any
reason you do, in step 8 you are asked whether to configure the engine.
Reply 'No'.
A reason why you might need/want to install rhevm on this machine:
Currently engine-backup is in rhevm-tools, which requires rhevm. If you
want to use it to backup dwh/reports, you are in above flow.
Similarly with the other procedures.
8.4.3 Prerequisites 3.: (in addition to notes above) last point should be:
allow access to the _dwh_ machine pg port 5432.
We specifically do not require access to the engine db. We used to, at some
point, and dropped this. This is mainly to allow separating the network:
Have one network with the engine and one with the dwh db. Users might want
other software/systems access dwh db (for analysis, billing, whatever) and
still not expose the engine.
8.4.4 Prerequisites: Again, engine+dwh can be done in a single run.
Procedure 8.8 step 1.: This one is different. Here, you can't do
engine+reports in a single run, because you still do not have dwh. If you
did install both, and reply 'yes' to both, you are stuck when asked about
dwh db. If you reply 'no' to Reports, install dwh, then run again
'engine-setup', you'll not be asked again about Reports. If you want to be
asked again, you can do this with 'engine-setup
--reconfigure-optional-components'. This option was added in 3.5.0, you
might want to add it here.
========================