Opened 2 years ago

Closed 7 weeks ago

#3065 closed change (fixed)

Allow for host-specific Puppet guest OS configuration

Reported by: matze Assignee: matze
Priority: P2 Milestone:
Module: Infrastructure Keywords:
Cc: fred, paco, ferris Blocked By:
Blocking: #3064, #3576 Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

https://codereview.adblockplus.org/29367491/
https://codereview.adblockplus.org/29367494/
https://codereview.adblockplus.org/29367500/
https://codereview.adblockplus.org/29367524/
https://codereview.adblockplus.org/29367556/
https://codereview.adblockplus.org/29368560/
https://codereview.adblockplus.org/29370655/
https://codereview.adblockplus.org/29370651/
https://codereview.adblockplus.org/29370648/
https://codereview.adblockplus.org/29370645/

Description (last modified by matze)

Due to many optimizations in the context of i.e. #3576, we should now be able to implement a feature missed for quite a while now: The possibility to choose between (a pre-defined set of) guest operating systems, not only in order to allow for more flexibility, but to allow for iterative OS migration in the first place, even basic version upgrades, in the first place.

What to do

In order to prepare for continuous OS migration capability:

  • Introduce the concept of per-host OS to the infrastructure code-base
  • Introduce a Debian "jessie" / Puppet 3 master
  • Integrate a Debian "jessie" / Puppet 3 client
  • Ensure Legacy "precise" / Puppet 2 client compatibility

In the meantime:

  • Fix as many Puppet 2/3 incompatibility issues as possible
  • Ensure associated documentation, i.e. the README.md file, to be up-to-date

Minor patch-sets in that context may also use this very ticket as reference.

Change History (20)

comment:1 Changed 10 months ago by matze

  • Blocking 3576 added
  • Cc paco ferris added
  • Description modified (diff)
  • Summary changed from Allow for specifying the Vagrant box image to Allow for host-specific Puppet guest OS configuration
  • Type changed from defect to change

comment:2 Changed 10 months ago by abpbot

A commit referencing this issue has landed:
Issue 3065 - Ensure Puppet 3 compatibility in nrpe.cfg template

comment:3 Changed 10 months ago by matze

  • Owner set to matze

comment:4 Changed 10 months ago by matze

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:5 Changed 10 months ago by abpbot

A commit referencing this issue has landed:
Issue 3065 - Introduce support for host-specific operating systems

comment:6 Changed 10 months ago by matze

  • Review URL(s) modified (diff)

comment:7 Changed 10 months ago by abpbot

A commit referencing this issue has landed:
Issue 3065 - Introduce adblockplus::puppet module

comment:8 Changed 10 months ago by matze

  • Review URL(s) modified (diff)

comment:9 Changed 10 months ago by matze

  • Review URL(s) modified (diff)

comment:11 Changed 10 months ago by matze

  • Review URL(s) modified (diff)

comment:12 Changed 10 months ago by abpbot

A commit referencing this issue has landed:
Issue 3065 - Improve workaround for Puppet bug 3665

comment:13 Changed 10 months ago by abpbot

A commit referencing this issue has landed:
Issue 3065 - Improve workaround for Puppet bug 3665

comment:14 Changed 10 months ago by matze

  • Description modified (diff)

comment:15 Changed 10 months ago by matze

Test in production using a Debian "jessie" Puppet master with an existing Ubuntu "precise" filter-server worked like a charm. The following settings in puppet.conf required an update:

[main]
# Introduce to the master in proper fashion
certname = fqdn.example.com

[agent]
server = puppetmaster.example.com

For the tests a custom ssldir has been used, and for now the client configuration has been restored. Roll-out during migration should require prior deletion of the original SSL directory (/var/lib/puppet/ssl) on the agent only.

comment:16 Changed 10 months ago by matze

  • Description modified (diff)

comment:17 Changed 10 months ago by abpbot

A commit referencing this issue has landed:
Issue 3065 - Improve nginx::hostconfig Puppet 3 compatibility

comment:18 Changed 10 months ago by paco

  • Review URL(s) modified (diff)

comment:20 Changed 7 weeks ago by matze

  • Resolution set to fixed
  • Status changed from reviewing to closed
Note: See TracTickets for help on using tickets.