Project

General

Profile

Feature #16173

Feature #16827: Update Puppet modules: 2019Q3 → 2019Q4 edition

Upgrade the icingaweb2 Puppet module

Added by intrigeri 8 months ago. Updated 28 days ago.

Status:
In Progress
Priority:
Elevated
Assignee:
-
Category:
Infrastructure
Target version:
Start date:
11/29/2018
Due date:
% Done:

0%

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

Related issues

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

History

#1 Updated by intrigeri 8 months ago

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

#2 Updated by intrigeri 8 months ago

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

#3 Updated by intrigeri 7 months ago

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

#4 Updated by intrigeri 5 months ago

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 4 months ago

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

#6 Updated by intrigeri 3 months ago

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

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

#7 Updated by intrigeri 3 months ago

  • Priority changed from Normal to Elevated

#8 Updated by intrigeri about 1 month ago

  • 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 28 days ago

  • Parent task changed from #15500 to #16827

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

#10 Updated by intrigeri 28 days ago

  • 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.

Also available in: Atom PDF