leap_platform.git/puppet/modules/site_couchdb, branch 0.7.0 [leap_platform] move rotated db creation to site_couchdb and fix rotated db tests 2015-04-08T20:58:41+00:00 elijah elijah@riseup.net 2015-04-08T20:58:41+00:00 e3cfc2e1e7055ce2640fcce5bf810d6bd7930d2f 






added support for rotating couchdb databases.
2015-03-31T05:33:05+00:00

elijah
elijah@riseup.net

2015-03-31T05:33:05+00:00

b64940c1de7cf42acef018ca2fbf5beff4f48e80












don't create dbs before couch cluster is settled
2015-02-03T20:45:52+00:00

varac
varacanero@zeromail.org

2015-02-03T20:45:52+00:00

46994b7a746ea9c89de74a2e8d4996c21c20af5c

Change-Id: Ifd665eb7efc06c1cf9e7b8fcfd5f42dbb34ac1b1





Change-Id: Ifd665eb7efc06c1cf9e7b8fcfd5f42dbb34ac1b1







Merge remote-tracking branch 'leap/develop' into check_dhcp
2014-12-04T11:09:10+00:00

Christoph Kluenter
ckluente@thoughtworks.com

2014-12-04T11:09:10+00:00

d063e35d3e29b3cedc810b8e5ca1855c841d8f9e












ship a modified runit config for bigcouch that raises the open file
2014-11-20T21:32:00+00:00

Micah Anderson
micah@leap.se

2014-11-20T21:27:35+00:00

503a316e67da2b4e0dbae7db28bbd0574fa3739f

descriptor limits to account for bigcouch sync spikes (#4935)

Change-Id: I242fba31f961b6139ec641e1708b170f5c0d009b





descriptor limits to account for bigcouch sync spikes (#4935)

Change-Id: I242fba31f961b6139ec641e1708b170f5c0d009b







change ordering hints to use refresh_stunnel exec instead of service (#6287)
2014-11-04T14:46:06+00:00

Micah Anderson
micah@leap.se

2014-11-03T02:47:36+00:00

18f5d6ea49446f214cbb764ea223f427aafd641e

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





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







Fix deprecated dynamic lookups of variables in site_couchdb (#6286)
2014-10-31T17:15:13+00:00

Micah Anderson
micah@leap.se

2014-10-31T17:15:13+00:00

84957fbd0f1e4aa26303b6488d9ec7df8af08ab7

Change-Id: I318944a6872a53ff9c533704514da339426d9401





Change-Id: I318944a6872a53ff9c533704514da339426d9401







ensure dhclicent and resolv.conf are configured before bigcouch
2014-09-29T12:33:56+00:00

Christoph Kluenter
ckluente@thoughtworks.com

2014-09-29T12:31:54+00:00

664dca31dec0c7935ee96359209d9dcefc03e38c












Increase wait-for-couch timeout (Bug #3735)
2014-09-17T09:44:17+00:00

varac
varacanero@zeromail.org

2014-09-17T09:44:17+00:00

d6c078f4beecefe42c971cc5802e79f42396ebab

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.





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.







lint site_couchdb
2014-06-26T06:10:29+00:00

elijah
elijah@riseup.net

2014-06-26T06:10:29+00:00

d6eabb09f978f1501b8b797d28e949a2e00ac82e