leap_platform.git/puppet/manifests, branch master [leap_platform] Feat: Refactor tor services 2017-10-05T23:24:50+00:00 Micah Anderson micah@riseup.net 2017-09-19T19:36:06+00:00 5b10def43d134e5735bfcec1237c04cf66e8610b In order to refactor the tor services, we need to split them out into three different services. This adds the hidden service class that is necessary to support the previous commits. Fixes #8864. 
In order to refactor the tor services, we need to split them out into three
different services. This adds the hidden service class that is necessary to
support the previous commits. Fixes #8864.
Feat: split tor service into three 2017-10-05T23:24:34+00:00 elijah elijah@riseup.net 2017-09-19T18:54:27+00:00 96f8af37b4a3bbd9a15651e27f588073c0601299 The 'tor' service is now three separate services, 'tor_exit', 'tor_relay', or 'hidden_service'. 
The 'tor' service is now three separate services, 'tor_exit', 'tor_relay', or 'hidden_service'.
Restructure site_tor to be more clear and re-usable (fixes #8784). 2017-05-06T16:51:51+00:00 Micah Anderson micah@riseup.net 2017-05-02T20:23:20+00:00 68e9a28da2db4cb494bc19a1aeaa0663cb286414 This makes a more clear site_tor::relay class that the leap service includes, and a more generic site_tor class that other classes can depend on for setting up the initial install. 
This makes a more clear site_tor::relay class that the leap service
includes, and a more generic site_tor class that other classes can
depend on for setting up the initial install.
[bug] Fix site_obfsproxy services variable lookup 2016-06-14T18:48:34+00:00 varac varacanero@zeromail.org 2016-06-14T18:46:38+00:00 96ef4273241d79427bb0b252fb759affec85db14 After including everything into a `node default` scope in puppet/manifests/site.pp to make puppet-catalog-test happy (see commit 62ea45d47), we get this error: Error: member(): Requires array to work with at /srv/leap/puppet/modules/site_obfsproxy/manifests/init.pp:14 Moving the `services` hiera avaluation out of the node scope back to top level scope will solve this. 
After including everything into a `node default` scope
in puppet/manifests/site.pp to make puppet-catalog-test happy
(see commit 62ea45d47), we get this error:

    Error: member(): Requires array to work with at
    /srv/leap/puppet/modules/site_obfsproxy/manifests/init.pp:14

Moving the `services` hiera avaluation out of the node scope back
to top level scope will solve this.
use node default {} in site.pp for catalog test 2016-06-11T13:23:11+00:00 varac varacanero@zeromail.org 2016-06-11T13:23:11+00:00 62ea45d47cbed1a7fc8c7b1284087d7bb9be4235 






[feat] Dont install recommended packages
2016-03-31T08:54:43+00:00

varac
varacanero@zeromail.org

2016-03-17T19:43:11+00:00

bdba3c13d48960e275ddd208527b8736fa518e23

By default, Puppet installs recommended packages.
We turn this off for all apt Package resources.





By default, Puppet installs recommended packages.
We turn this off for all apt Package resources.







Revert "[feat] Use systemd as service provider"
2016-03-15T19:21:51+00:00

varac
varacanero@zeromail.org

2016-03-15T19:21:51+00:00

9b50224e6409d433e1074a218cbca594bd822608

This reverts commit 0aebb4c41f96f6ad7a7e8a3b07eaffa1f9075f51.

We enabled systemd as puppet service default provider, but this results
in these services falsely detected as not running, and restarted on
every deploy.
We need to indivually configure systemd as service provider only for
those services that ship a systed unit file.

see #7966 for details





This reverts commit 0aebb4c41f96f6ad7a7e8a3b07eaffa1f9075f51.

We enabled systemd as puppet service default provider, but this results
in these services falsely detected as not running, and restarted on
every deploy.
We need to indivually configure systemd as service provider only for
those services that ship a systed unit file.

see #7966 for details







[feat] Use systemd as service provider
2016-03-08T19:26:56+00:00

varac
varacanero@zeromail.org

2016-03-08T17:38:22+00:00

0aebb4c41f96f6ad7a7e8a3b07eaffa1f9075f51

Even when the service provider defaults to systemd in
latest puppet, it still defaults to 'debian' in puppet
3.7.2 (jessie version).

We dropped wheezy support so we should use the systemd provider
for now.

https://docs.puppetlabs.com/puppet/latest/reference/type.html#service-provider-systemd





Even when the service provider defaults to systemd in
latest puppet, it still defaults to 'debian' in puppet
3.7.2 (jessie version).

We dropped wheezy support so we should use the systemd provider
for now.

https://docs.puppetlabs.com/puppet/latest/reference/type.html#service-provider-systemd







[feat] Fix fast deploy using 'leap deploy --fast'
2016-01-28T22:52:41+00:00

varac
varacanero@zeromail.org

2016-01-27T23:04:10+00:00

a8343508a6ced1dcbca621ad4c6f3ac39676326b

This worked before, but somehow stopped working.

We need to include 'site_config::slow' top-level scope instead
of including it in 'site_config::default', because otherwise it
would get tagged with 'leap_base', and would be included always.

This way 'site_config::slow' gets included by default, but can be
excluded by using 'leap deploy --fast'.
See https://leap.se/en/docs/platform/details/under-the-hood#tags

- Resolves: #7844





This worked before, but somehow stopped working.

We need to include 'site_config::slow' top-level scope instead
of including it in 'site_config::default', because otherwise it
would get tagged with 'leap_base', and would be included always.

This way 'site_config::slow' gets included by default, but can be
excluded by using 'leap deploy --fast'.
See https://leap.se/en/docs/platform/details/under-the-hood#tags

- Resolves: #7844







restructured site.pp, now only one class gets included in site.pp per service (Bug #6851)
2016-01-22T08:50:33+00:00

varac
varacanero@zeromail.org

2015-04-13T21:16:00+00:00

150579fb14716892cc3e4d7d9c0f81b30d56f03a

Also, moved global Exec{} defaults to site.pp

Change-Id: I9ae91b77afde944d2f1312613b9d9030e32239dd





Also, moved global Exec{} defaults to site.pp

Change-Id: I9ae91b77afde944d2f1312613b9d9030e32239dd