Doc Text:
|
With previous versions, hosted-engine deployment didn't configure grafana, and so users had to manually configure it later, which was inconvenient.
With this version, hosted-engine deployment does configure grafana automatically by default.
doc team: Some more details and background:
1. I am writing doc text only for this bug, because that's enough IMO, although the actual needed changes are tracked also in other bugs - 1985927 and 1986393.
2. The current behavior (before fixing this bug) was introduced in 4.4.2, for bug 1866780. That one was about upgrade from 4.3 with dwh on a separate machine. To make the fix for current but not introduce that one, the change is slightly more complex: For new deployments, grafana is always configured (by default), but when restoring from backup (and also as part of upgrade from 4.3, which involves backup/restore), we configure grafana only if dwh was local to the engine machine.
So you might want to mention this in the doc text, if you want - something like "When using hosted-engine with --restore-from-file, grafana is configured only if dwh was configured locally, on the engine machine".
3. I now also filed a doc bug 1987193, for removing this from the documentation.
|