Update Icinga DB related docs #9423
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lippserd
previously approved these changes
Jun 29, 2022
We are using a central DB-Cluster, therefor Icinga2 got a database on this remote cluster. We used the icinga DB user, created during the step before, to import the DB schema. For this, the additional GRANT options `ALTER` and `CREATE` where needed to install the schema successfully via: ```bash mysql -u icinga -p icinga < /usr/share/icinga2-ido-mysql/schema/mysql.sql ``` Someone may find this a security problem. But I see two benefits: * these GRANT options are only set for the icinga.* database * this setup allows to execute also all later UPGRADE commands as the database user `icinga` - and not as the DB Administrator. Two additional notes: * I also included a small warning about the used default DB password * sadly, I have no way to change this also in the provided mariadb-centos7.png image, so this is left unchanged at the moment
Almost every Icinga 2 node setup requires the Icinga 2 API, as Icinga Web connects to it, Icinga DB requires it, and although it's not clearly mentioned anywhere in the documentation at the moment, it enables the cluster communication functionality.
That's useless.
There is a separate chapter, so why draw attention to installing even more things.
The Icinga DB docs will link to installing Icinga DB Web.
julianbrost
force-pushed
the
icingadb-docs-2.13
branch
from
5875195
to
c692066
Compare
Al2Klimov
approved these changes
Jun 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge conflicts were resolved by picking the version from the master. Therefore this also backports #9152. There are also some small differences with heading levels when comparing the two PRs, but the result looks fine (but feel free to double check).
backport of #9387