In preparation for the transition to the future parser first, and puppet 4 later, we will be able to do things more easily if we allow ourselves to have the possibility to define separated environments.
So we need to add support for directory environments to our puppet classes as well as enabling them in production.
Instructuions for how to configure environments is here
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | aborrero | T178717 Upgrade wmcs instances and masters to puppet 4.8 | |||
| Resolved | None | T177254 Upgrade to puppet 4 (4.8 or newer) | |||
| Resolved | None | T169548 Prepare for Puppet 4 | |||
| Resolved | Joe | T169485 Add support for directory environments to our puppet classes, production puppetmaster | |||
| Declined | None | T169493 Test restarting puppetmaster workers for every code deploy | |||
| Resolved | Joe | T169546 Add results of compilation with the future parser to the puppet compiler |
First hurdle: puppetlabs advises to set the variable environment_timeout to unlimited and to restart the puppetmaster at every code deploy, for performance reasons.
I'm not sure it's feasible for us - the only way to do it would be to leverage passenger's rolling restart capability within puppet-merge.
I'm opening a subtask for that.
Change 363790 had a related patch set uploaded (by Giuseppe Lavagetto; owner: Giuseppe Lavagetto):
[operations/puppet@production] puppetmaster: add environment for the future parser
Change 363790 merged by Giuseppe Lavagetto:
[operations/puppet@production] puppetmaster: add environment for the future parser
Change 363797 had a related patch set uploaded (by Giuseppe Lavagetto; owner: Giuseppe Lavagetto):
[operations/puppet@production] profile::base: allow setting a puppet environment
Change 363797 merged by Giuseppe Lavagetto:
[operations/puppet@production] profile::base: allow setting a puppet environment