leap_platform.git/puppet/modules/site_config/manifests, branch 0.6.0rc3

implement custom puppet support (#6201, #6226)

2014-10-21T20:43:30+00:00

change puppet command to include in the --modulepath
/srv/leap/files/puppet/modules

If a provider places puppet code under files/puppet it will
be sync'd over to all the nodes, once leap cli #6225 is merged.

The custom puppet entry point is in class 'custom' which can
be put into files/puppet/modules/custom/manifests/init.pp

Change-Id: I74879c6ee056b03cd4691aa81a7668b60383bdad

FQDN should come first in /etc/hosts

2014-08-22T20:10:06+00:00

fixes /etc/hosts: wrong order (Bug #5835) (now for real)

before, /etc/hosts contained i.e.

  127.0.1.1    plain1 plain1.bitmask.net plain1.bitmask.i

which resulted in no fqdn reported both by "hostname -f"
and "facter fqdn"

this fix produces this order which is needed to report a fqdn:

  127.0.1.1    plain1.bitmask.net plain1 plain1.bitmask.i

reorder /etc/hosts

2014-06-27T14:53:16+00:00

now "hostname -f" results in the correct hostname.
Fixes #5835

clean up how /etc/hosts is generated so it doesn't require custom behavior depending on the services.

2014-06-04T21:19:55+00:00

bugfix: actually apply modules based on $services

2014-06-04T20:05:56+00:00

move hiera from site.pp to site_config::setup

2014-06-03T13:48:35+00:00

the problem was following:

if a host has the webapp service, the template for /etc/hosts adds some stuff.
But setup.pp did not ask hiera about the services so
"/srv/leap/bin/puppet_command set_hostname" always resets the hostname.
Since that gets triggered every time you run "leap deploy" the
hostname changes, some services restart, then the hostname changes back and
the services restart again.

The solution is to get the hiera data before every run.

Switch away from site_config::sshd and instead just include site_sshd

2014-05-27T23:55:32+00:00

The existing site_config::sshd had a non-functioning 'include sshd' line
in it that was not doing what was expected (this was supposed to include
the sshd module, but due to scoping was including itself).

It seemed better to eliminate some of the unused pieces and consolidate
into one config location.

Change-Id: I79dd904e696ca646180a09abbb03b5361dfc8ab9

Implement #2328: unbound.conf: content changed on every puppetrun

2014-05-22T19:50:02+00:00

This is done by using the include glob capability that is in the
wheezy-backports and newer unbound to include the
/etc/unbound/unbound.conf.d/* config files.

To do this, we need to transition from our /etc/unbound/conf.d directory
structure to use the one that the debian package uses.

This allows us to clean up the rather ugly way we were configuring the
resolver before.

Change-Id: I68347922f265bbd0ddf11d59d8574a612a7bd82c

lint cleanup of site_config::caching_resolver

2014-05-22T17:11:54+00:00

Change-Id: I3f6a4db26e064a520a08822cf23fc3288b31af62

Install wheezy-backports version of unbound, this is necessary to solve #2328

2014-05-22T16:19:04+00:00

Change-Id: Ie28de8d3f7a8c8cf52ce30365379a476d48dc88b