Feature #12451

Update icingaweb2 DB initialization code wrt. upstream changes

Added by intrigeri 2017-04-16 10:13:03 . Updated 2019-02-10 13:22:47 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2017-04-16
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I’ve upgraded the Puppet module and manifests/initialize.pp seems to now do stuff we used to do ourselves with puppet-tails:files/monitoring/icingaweb2/scripts/install_icingaweb2_database. Likely we can drop some of our custom code :)

Subtasks

Related issues

Related to Tails - Feature #16173: Upgrade the icingaweb2 Puppet module Confirmed 2018-11-29

History

#1 Updated by intrigeri 2018-11-29 22:06:26

  • related to Feature #16173: Upgrade the icingaweb2 Puppet module added

#2 Updated by intrigeri 2019-02-10 09:12:28

  • Assignee deleted (bertagaz)

(There’s no reason why bertagaz has to do this work, so assigning to him was somewhat unfair: the improvement suggested here was not possible when he delivered our monitoring infra. Still, it would be nice to have :)

#3 Updated by intrigeri 2019-02-10 13:22:47

There are a few possible ways to handle this:

  • mysql::db’s sql parameter, once Feature #15513 is done for ecours; but it needs to first concatenate the schema file with a template-generated custom one
  • use upstream’s icingaweb2::initialize, as suggested initially here
  • Only create an empty database and let Icingaweb2 do the rest (https://bugs.debian.org/831532): we don’t seem to manage our admin users with Puppet anyway, so if all our custom code is doing is creating a default “icingaadmin” user that we won’t use, maybe it’s not worth the hassle.