Opened on 09/12/2015 at 02:29:45 PM
Closed on 09/04/2017 at 10:05:24 AM
#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/ |
||
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-baseIntroduce 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.
Attachments (0)
Change History (20)
comment:1 Changed on 12/14/2016 at 02:57:11 PM 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 on 12/14/2016 at 03:11:05 PM by abpbot
comment:3 Changed on 12/14/2016 at 03:11:48 PM by matze
- Owner set to matze
comment:4 Changed on 12/14/2016 at 03:35:36 PM by matze
- Review URL(s) modified (diff)
- Status changed from new to reviewing
comment:5 Changed on 12/14/2016 at 03:37:04 PM by abpbot
A commit referencing this issue has landed:
Issue 3065 - Introduce support for host-specific operating systems
comment:7 Changed on 12/15/2016 at 08:00:27 AM by abpbot
A commit referencing this issue has landed:
Issue 3065 - Introduce adblockplus::puppet module
comment:10 Changed on 12/15/2016 at 11:59:23 AM by abpbot
A commit referencing this issue has landed:
Issue 3065 - Refactor adblockplus::puppet module to include Puppet patches
comment:11 Changed on 12/15/2016 at 12:12:17 PM by matze
- Review URL(s) modified (diff)
comment:12 Changed on 12/15/2016 at 12:14:52 PM by abpbot
A commit referencing this issue has landed:
Issue 3065 - Improve workaround for Puppet bug 3665
comment:13 Changed on 12/15/2016 at 12:18:10 PM by abpbot
A commit referencing this issue has landed:
Issue 3065 - Improve workaround for Puppet bug 3665
comment:14 Changed on 12/15/2016 at 12:24:26 PM by matze
- Description modified (diff)
comment:15 Changed on 12/15/2016 at 12:43:23 PM 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 on 12/15/2016 at 12:45:20 PM by matze
- Description modified (diff)
comment:17 Changed on 12/15/2016 at 01:23:22 PM by abpbot
A commit referencing this issue has landed:
Issue 3065 - Improve nginx::hostconfig Puppet 3 compatibility
comment:18 Changed on 01/03/2017 at 04:23:34 AM by paco
- Review URL(s) modified (diff)
comment:19 Changed on 01/04/2017 at 09:03:08 PM by abpbot
Some commits referencing this issue have landed:
comment:20 Changed on 09/04/2017 at 10:05:24 AM by matze
- Resolution set to fixed
- Status changed from reviewing to closed
A commit referencing this issue has landed:
Issue 3065 - Ensure Puppet 3 compatibility in nrpe.cfg template