leap_platform.git/puppet/manifests, branch 0.5.3

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.

Merge branch '2993_setup_subclass' into 0.6

2014-04-04T08:27:53+00:00

Move setup.pp to a subclass (site_config::setup) (Feature #2993)

2014-03-25T22:42:19+00:00

modules/site_static: part 1 - amber

2014-03-23T23:11:32+00:00

initial tapicero configuration

2013-11-27T19:48:00+00:00

Change-Id: Ie53b09df0758ba01b30ed658bee04682bc180b01

Possibility to include local puppet recipes (Feature #3976)

2013-10-20T18:59:22+00:00

vagrant: support other providers besides virtualbox (Bug #4158), Part 2

2013-10-16T19:30:16+00:00

took out the last remaining virtualbox references

move all resources that are applied on every node into site_config::default (#3782)

2013-09-20T17:02:02+00:00

in commit 338833, we established a relationship between all
resources that have a leap_service tag, that are called in site.pp.
But we had some resources as default on every node in site.pp
(apt::update, Package { require => Exec['apt_updated'] },
site_config::slow and stdlib), that were still lacking any
relationship to the leap_service tag.
By moving them into default.pp they automatically are executed
before resources with a leap_service tag.

include shorewall::interface{eth0} in setup.pp so packages can be installed during main puppetrun, even before shorewall is configured completly

2013-09-18T15:22:59+00:00