Feature #16173

Upgrade the icingaweb2 Puppet module

Added by intrigeri 2018-11-29 22:06:18 . Updated 2020-04-01 08:45:21 .

Status:
Confirmed
Priority:
Elevated
Assignee:
Sysadmins
Category:
Infrastructure
Target version:
2020
Start date:
2018-11-29
Due date:
% Done:

0%

Feature Branch:
puppet-lizard-manifests:feature16173, puppet-tails:feature16173, puppet-icingaweb2:feature16173
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Related to Tails - Feature #12451: Update icingaweb2 DB initialization code wrt. upstream changes Confirmed 2017-04-16
Blocks Tails - Feature #13284: Core work: Sysadmin (Adapt our infrastructure) Confirmed 2017-06-30

History

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

  • related to Feature #12451: Update icingaweb2 DB initialization code wrt. upstream changes added

#2 Updated by intrigeri 2018-11-29 22:12:40

  • blocks Feature #13284: Core work: Sysadmin (Adapt our infrastructure) added

#3 Updated by intrigeri 2019-01-02 05:00:51

  • Target version changed from Tails_3.12 to Tails_3.13

#4 Updated by intrigeri 2019-02-10 09:18:17

Note to myself, it’s going to be a big one:

$ git diff --stat ...v2.2.0 -- files/ manifests/ templates/ | tail -n1
 48 files changed, 2010 insertions(+), 1495 deletions(-)

#5 Updated by intrigeri 2019-03-11 09:34:36

  • Target version changed from Tails_3.13 to Tails_3.14

#6 Updated by intrigeri 2019-05-02 17:23:31

  • Target version changed from Tails_3.14 to Tails_3.15

I’ll focus on Feature #15510 first and I doubt I’ll have time to handle this one too during this cycle.

#7 Updated by intrigeri 2019-05-02 17:24:18

  • Priority changed from Normal to Elevated

#8 Updated by intrigeri 2019-06-11 18:24:09

  • Status changed from Confirmed to In Progress
  • Feature Branch set to puppet-lizard-manifests:feature16173, puppet-tails:feature16173, puppet-icingaweb2:feature16173

I checked a bit v2.0.3. Significant changes include:

  • s/mod/module/ in icingaweb2::module::monitoring
  • the $ido_db* and $web_db* params are gone; instead there are $db_* params that I think replace the $web_db* ones; and icingaweb2::module::monitoring now has $ido* params so that’s probably where those ones are gone
  • there’s a new icingaweb2::config::resource defined resource (“Resources are used for the internal authentication mechanism and by modules”) + icingaweb2::config::authmethod, but some examples suggest that a simpler config is doable
  • $admin_users is gone; instead, the module configures a default icingaadmin admin user and provide facilities to manage more roles & users

All this is pretty scary and given we run code that’s never been released officially (some kind of development snapshot from 2 years ago, if I got it right), it’s not clear whether upgrading can work without too many headaches. I’m tempted to drop our existing icingaweb2 setup + DB and let the new module set it up from scratch but I don’t know if we have customizations that live only in our DB and are not tracked anywhere else. I guess I’ll try the upgrade anyway and if it’s too painful, I’ll reconsider.

#9 Updated by intrigeri 2019-06-19 10:40:19

I doubt I’ll manage to do this by the end of Q2.

#10 Updated by intrigeri 2019-06-19 10:44:48

  • Assignee deleted (intrigeri)
  • Target version changed from Tails_3.15 to 2019

I’d rather see @bertagaz handle this one: you know this area of our infra & codebase way better than me.

#11 Updated by groente 2019-08-01 09:33:29

  • Assignee set to Sysadmins

#12 Updated by intrigeri 2020-03-17 08:40:36

  • Status changed from In Progress to Confirmed

#13 Updated by intrigeri 2020-04-01 08:45:22