| Age | Commit message (Collapse) | Author |
|---|
|
Soledad is now taking care of the design of said database.
Closes #8428
|
|
- Resolves: #8693
|
|
|
|
When the soledad couch user is not present, soledad-server
refuses to start, so we need to ensure that couch is setup correctly
before starting soledad-server.
see https://leap.se/code/issues/8535
|
|
|
|
Mochiweb in couchdb by default sets the TCP socket option SO_NODELAY to
false. This means that small data sent to the TCP socket, like the reply
to a document write request (or reading a very small document), will not
be sent immediately to the network - TCP will buffer it for a while
hoping that it will be asked to send more data through the same socket
and then send all the data at once for increased performance.
Setting this increases the couchdb speed significantly.
Change-Id: Ib493ef061ff62c9bdee501e44ce2b55990fe14b7
|
|
|
|
Latest shorewall module does `shorewall check` (executed
by `Exec[shorewall_check]`) so every related resource change
must notify this Exec instead of `Service[shorewall]` as before.
|
|
Change-Id: I0c6e27298c63bd37de1410985d054799818c22a4
|
|
Automatic background couchdb db compaction frees a huge
amount of diskspace.
- Resolves: #8118
|
|
|
|
I used `puppet-lint -f FILE` to fix most issues, while
finishing with manual intervention.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Conflicts:
# puppet/modules/site_couchdb/manifests/plain.pp
|
|
- Resolves: #7418
|
|
We now include "site_config::remove::bigcouch" in class
"site_couchdb::master", which sets up plain couchdb.
|
|
service (Bug #6851)
Also, moved global Exec{} defaults to site.pp
Change-Id: I9ae91b77afde944d2f1312613b9d9030e32239dd
|
|
This reverts commit 02b1b484ad9a5d065ceac72b8263b7bcc112c923.
Now that we have a proper couchdb jessie package we don't need to
install it from Debian unstable.
|
|
|
|
- Related: #6920
|
|
When migrating from bigcouch to couchdb, we need to remove leftover nagios
tests for bigcouch.
- Added new classes: site_check_mk::agent::couchdb::bigcouch and
site_check_mk::agent::couchdb::master
- Tested: unstable.pixelated-project.org
- Resolves: https://github.com/pixelated/pixelated-platform/issues/126
|
|
- Resolves: #7514
|
|
Soledad now creates user-dbs, which has been done by tapicero
in the past. we need to remove any leftovers from tapicero.
|
|
|
|
- create soledad-admin user
- deploy netrc file for userdb creation
- Move soledad-server.conf from /etc/leap to /etc/soledad
- make soledad-server.conf group-accessible for the soledad group, so
the soledad-admin user can read it
- Resolves: #7502
|
|
|
|
|
|
The bigcouch specific class ordering from site_couchdb::create_dbs
needed to move to site_couchdb::bigcouch, otherwise a plain couchdb
setup would try to include bigcouch classes and fail.
Change-Id: I06742d4a12c5b40c9c9faa90441734e6926d422d
|
|
Change-Id: I9e46286c402adc06f3f815f8a1eea11fe82c7c39
|
|
use this to run a single, plain couchdb node, using couchdb 1.6
from the leap repo:
"couch": {
"master": true,
"pwhash_alg": "pbkdf2"
}
Change-Id: Ie4f34c2c5cb9feca7a10450bcf0bc260c8aa9d33
|
|
|
|
|
|
Change-Id: Ifd665eb7efc06c1cf9e7b8fcfd5f42dbb34ac1b1
|
|
|
|
descriptor limits to account for bigcouch sync spikes (#4935)
Change-Id: I242fba31f961b6139ec641e1708b170f5c0d009b
|
|
In a multi-node couch deployment, it was observed that the Service['stunnel']
would be activated, and then later a stunnel::client was created which would
trigger an Exec['refresh_stunnel']. Because of this, and the ordering hints
that were in place, the service would get started, and then the couchdb
databases, users, designs, etc. were being put into place and then a stunnel
client was created, triggering the refresh_stunnel exec, which would cause
an interruption in the connectivity and result in failures.
This change replaces the Service['stunnel'] hint with the the
Exec['refresh_stunnel'] to make sure that the stunnels are fully setup before
attempting couch operations.
Change-Id: I33ddd24884b3c23a1df5555ca53ca65cd703da50
|
|
Change-Id: I318944a6872a53ff9c533704514da339426d9401
|
|
|
|
Site_couchdb::Bigcouch::Settle_cluster/Exec[wait_for_couch_nodes] waits
60s for all nodes to be member of the cluster. Because we deploy to
multiple nodes in parallel, not all nodes are ready at the same time,
so we increased the timeout from 60s to 120s.
|
|
|
|
This only works with the latest patch to puppet_couchdb
|
|
|
|
|
|
out into separate files.
|
