Age | Commit message (Collapse) | Author |
|
Change-Id: I4f53c3288df16aadf9d00f578cb36a135cf94335
|
|
Change-Id: I7214aa4334e3d817dd1b6d8dce43523e3d955b5d
|
|
Tag 0.5.4.1 hotfix release
|
|
Change-Id: I0d629c56b86cd4de5a6560d58715de7ec93dd4e3
|
|
|
|
Change-Id: Ia34388c5095301d3a72070737fdb9df758610581
|
|
Added a dependency on the couchdb "tapicero" user to get
created before starting the tapicero daemon.
|
|
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
|
|
Tagging 0.5.3 release
|
|
Due to how tapicero's initscript is made, it is not possible to check
for a valid exit code for the status (it returns a zero when it is not
running). So we disable the puppet 'hasstatus' parameter and instead
puppet will look in the process table for 'tapicero'
Change-Id: I9b017ea8055c0207e43876dd4e3bbc2619c0fd35
|
|
|
|
a wrong hostname on single node setup (Bug #5998)"
before, the ssh module added this check, resulting in a wrong
hostname and the port was always '22'.
manage_nagios parameter is boolean, so we use false instead of 'no'
manually add check_ssh to nagios (#5998)
|
|
Change-Id: I6be37c3c65c47e650c0e67bd43df8e2b1ac40dd6
|
|
need to be bumped each release
Change-Id: I3aabe1a713f4244cbbd607137e5d8e46d992a2bc
|
|
|
|
latest version, this is necessary to transition to the python-gnupg-ng
package, which will not otherwise be installed
Change-Id: I2ea631e15518fd40cb0ea4fe718498bdfba3c599
|
|
packages will be upgraded
Change-Id: Ic94be8b732d9d2202f87c0c2cdd2fd0d16cc9efc
|
|
now "hostname -f" results in the correct hostname.
Fixes #5835
|
|
and bump the version number to 0.5.2.
Change-Id: Ie75018bf11583d14dab148732d58d6d50f88dd42
Note: this didn't make it into the tag
|
|
tagging 0.5.2 release
|
|
depending on the services.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and were missing .conf suffix
|
|
for configuration (#3108)
Change-Id: I4f94a47d47a40bfc6835359e7781707f96e91db0
|
|
Change-Id: I3b6a87c9d6a2c349392e5bc98a68b800645fde92
|
|
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
|
|
Change-Id: I679dfe8dff90b7c86ab0ffff43e13958f1ec2c99
|
|
into develop
|
|
|
|
|
|
Change-Id: I4e9d845f9758232f4da0d4bfbf785e52982b825b
|
|
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
|
|
Change-Id: I3f6a4db26e064a520a08822cf23fc3288b31af62
|
|
Change-Id: Ie28de8d3f7a8c8cf52ce30365379a476d48dc88b
|
|
group it with the other preferences snippets
Change-Id: I83928c6b82cd6218a80c95475729cb57f146ff85
|
|
site_mx::haproxy and site_webapp::haproxy only
included site_haproxy. They didn't do anything else.
So just include site_haproxy in manifests/init.pp and
remove the unused classes
|
|
the problem was, that both site_mx::haproxy and site_webapp::haproxy
declared the same resource.
I fixed it by moving that resource to site_haproxy.
Since that gets included by both classes, everything works like
a charm
|
|
virtualbox sends the domain with the dhcp-answer.
If the wrong domain ends up in /etc/resolv.conf bigcouch fails.
|
|
latest leap_cli.
|
|
|
|
currently impossible to entirely overwrite the service.levels hash.
|
|
|