| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Ruby itself is a parameterized class, and parameters cannot get
overridden (see https://projects.puppetlabs.com/issues/9259).
The webapp node didn't install the ruby-dev package (we never
noticed because our vagrant images as probably other debian images
had ruby-dev preinstalled).
We now use the ruby::devel class to install ruby-dev.
- Tested: [citest-jessie]
- Resolves: #7838
|
|
I merged immerda's changes to the `rubygems` module, which
remove the installation of the `rubygems` package from jessie
on, because it's a dependency of the `ruby2.1` package, which is
a dep of puppet, and therefore installed on every node.
- Tested: [local singlenode]
- Resolves: #7619
|
|
|
|
otherwise, machines will be out-of-mememory on deploy
|
|
Vagrant uses portmap and nfs-common for mounting shared folders using
nfs.
|
|
In certain node setups, the webapp gems cannot get built
because `build-essential` and dependent packages were not
present.
I refactored the `site_config::packages::build_essential` class,
which now inherits `site_config::packages`. The latter class removes
all unneccessary (development) packages, but when the
`site_config::packages::build_essential` class is included, some
dev packages are overridden to be installed.
- Tested: [local]
- Resolves: #7834
|
|
|
|
After restructuring site.pp to only include site_config::default and
the service-specific classes, we got this:
Duplicate declaration: X509::Cert[undef] is already declared in file
/srv/leap/puppet/modules/site_config/manifests/x509/commercial/cert.pp
at line 8; cannot redeclare at
/srv/leap/puppet/modules/site_config/manifests/x509/cert.pp:8 on node
rewcitestweb1.rewire.org
So i included site_config::params in all site_config::x509 clases.
Change-Id: Ib8387abfdc68b36c73a45fd2dd1f3a159eaec4a5
|
|
service (Bug #6851)
Also, moved global Exec{} defaults to site.pp
Change-Id: I9ae91b77afde944d2f1312613b9d9030e32239dd
|
|
ensuring the satellite hosts are setup properly (#7611)
Change-Id: I9dce57c305a6fd6a39596a941174fe1879af5e4f
|
|
forward port to pixelated
|
|
pixelated needs to be accessible when running inside vagrant
problem is, that we can't add the forwarding anywhere else because
vagrant always overwrites virtualbox settings.
|
|
leap redirects port 80 to an invalid url
|
|
on vagrant, we use example.org as domain and all
requests to http are redirected to https://example.org
thats why this does not work on vagrant. we connect to
localhost:8080 and get redirected to https://example.org
thats why we do not need this port forwarded
|
|
|
|
failed to parse template tor/torrc.exit_policy.erb, undefined method
`each' for "*:*":String
Change-Id: I2b7b444187376dbc2f3cc5095391ae54bf8321b3
|
|
|
|
|
|
This will output node debug information by calling the
bin/debug.sh script.
|
|
fall-back to an OpenNIC resolver that does not log (#7781)
Change-Id: I290321927c8188c82e95e2cd4b93cd01bd2258c2
|
|
|
|
without getting blocked by the rbl (#7819)
Change-Id: Ib7a00f810b6c49528e5f99a1d83296553a81e65e
|
|
Change-Id: Iedd464a397e9944159991241cd84caad6a2a40d6
|
|
otherwise, machines will be out-of-mememory on deploy
|
|
- Tested: [unstable.bitmask.net]
- Resolves: #7798
|
|
- Resolves: #7802
|
|
|
|
|
|
Run git as user, not root
|
|
|
|
Under jessie, leap-mx is started by systemd now, not as a forked
proc by twistd anymore. Therefore leap-mx (the user the mx proc runs
as) needs direct access to it's config file under /etc/leap/mx.conf.
Before, twistd would start as root, read the config and then fork an mx
proc as unprivileged leap-mx user.
- Tested: [quetzal]
- Resolves: #7782
|
|
|
|
|
|
|
|
|
|
Change-Id: I101e4c9791102123d4334e1b84a48dacea99ac52
|
|
|
|
|
|
|
|
|
|
|
|
|
|
leap_cli could not get installed from source on jessie
|
|
jessie is now the default box
|
|
|
|
debconf selections, are set correctly (#7478)
Change-Id: I3bd261fd6fe27bbf10b8994ffff9f8b7be5b9de0
|
|
|
|
ensure that the key/value are only split on the first colon
|
|
|
