Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-09-02 | create all webapp databases so _security is set (fixes 3517) | Azul | |
2013-08-30 | create sessions db with puppet (Bug #3597) | varac | |
2013-08-27 | setup bigcouch logrotation (#3491) | Micah Anderson | |
Change-Id: Ia35cf7a9fc1d0fad6a57bbae73968ab6b8f0c847 | |||
2013-08-14 | require that the couchdb::query::setup has been run before any attempts are ↵ | Micah Anderson | |
made to create databases or add users as these would fail otherwise. Closes: #3466 Change-Id: Ifa8b3da5858ce858fd319c4a659e70d20a65d3e0 | |||
2013-05-23 | include site_couchdb::bigcouch::add_nodes in site_couchdb/manifests/init.pp | varac | |
2013-04-24 | take out plain couchdb setup, always deploy bigcouch (Feature #2176) | varac | |
2013-04-24 | Use pre-salted+hashed admin pw for couchdb (Feature #1941) | varac | |
2013-04-24 | updated needed couchdb users and DBs | varac | |
2013-04-24 | Use pre-salted+hashed user pw for couchdb (Feature #2324) | varac | |
2013-04-04 | pass $ca_name to stunnel::setup - this eliminates a dynamic scoped variable ↵ | Micah Anderson | |
lookup, and warning | |||
2013-04-04 | add Erlang Distributed Node Protocol Port json entry under bigcouch | Micah Anderson | |
setup ednp_server and ednp_client stunnels update couchdb puppet submodule to support configurable ednp_port parameter and general module cleanup pass ednp_port to couchdb setup so that it is configured in the vm.args template clarify in comments the difference between the epmd and ednp ports remove hard-coded erlang_vm_port variable and instead setup shorewall to allow for the stunnel connection only setup dnat rules for the ednp client connections | |||
2013-04-04 | remove the apache_ssl_proxy cleanup | Micah Anderson | |
2013-04-04 | rename the bigcouch_replication_[server,client] to be the more accurately, and | Micah Anderson | |
shorter named epmd (erlang port mapper daemon) | |||
2013-04-02 | switch to using stunnel_client and stunnel_server leap_cli macros | Micah Anderson | |
add bigcouch_replication_clients to couchdb.json change site_couchdb/manifests/stunnel to use stunnel_client and stunnel_server generated hiera values to setup the stunnels for the couch_server connections, and the bigcouch_replication_server and bigcouch_replication_clients tunnels instead of using hard-coded ips and ports. also change the pid names to be more consistent with what the tunnels are and are named | |||
2013-04-02 | replace long-form variables with shorter ones | Micah Anderson | |
remove unnecessary bigcouch_replication_client_default values (verify, rndfile, debuglevel) | |||
2013-04-02 | remove duplicate 'include site_stunnel' | Micah Anderson | |
this already exists in class site_stunnel::setup which is instantiated in this class | |||
2013-04-02 | fix bigcouch stunnel pid name | varac | |
2013-04-02 | decrease stunnel debug level | varac | |
2013-04-02 | couchdb hosts include site_shorewall::couchdb::bigcouch | varac | |
2013-04-02 | increase stunnel verbosity until everything is running smooth | varac | |
2013-04-02 | addded client side of bigcouch cluster protocol stunnel config | varac | |
2013-04-02 | added bigcouch.conf as incoming stunnel config for bigcouch clustering | varac | |
2013-04-02 | working on stunnel for bigcouch clustering | varac | |
2013-03-17 | fix webapp/couchdb stunnel certificate authority | Micah Anderson | |
2013-03-14 | add couchdb stunnel server | Micah Anderson | |
2013-03-14 | remove apache ssl proxy in preparation of replacing it with a stunnel setup | Micah Anderson | |
This presents us with an interesting problem of deprecation. We need to manage the removal of something that we previously installed in any released code. How long we carry the puppet code that removes raises some interesting questions: do we require that someone who deployed version 1 (where the apache ssl proxy was deployed) of the platform upgrade first to version 2 (where we remove the apache ssl proxy) before they upgrade to version 3 (where the apache ssl proxy removal is no longer present) -- or do we allow people to skip versions? | |||
2013-03-14 | include cloudant package repo for bigcouch server | varac | |
2013-03-10 | pass couchdb cookie to class couchdb | varac | |
2013-03-10 | use bigcouch in site_couchdb | varac | |
2013-03-10 | site_couchdb::configure moved to couchdb | varac | |
2013-03-10 | futon is enabled by default on bigcouch in default.ini | varac | |
we need to find another way to disable futon, it won't work disabling it here | |||
2013-03-09 | couchdb init file moved to couchdb module | varac | |
2013-02-09 | re-enabling futon (see #1121) | varac | |
2013-02-08 | couchdb: disable futon (Feature #1121) | varac | |
2013-02-06 | include shorewall config for webapp and couchdb | varac | |
2013-01-31 | tag 'base' is a bad idea because it invokes apache::base as well | varac | |
2013-01-31 | tag 'service' for all service classes | varac | |
2013-01-29 | eliminate dynamic lookup deprecation warnings for site_couchdb::apache_ssl_proxy | Micah Anderson | |
2012-12-19 | added ca_daemon initscript for later | varac | |
2012-12-10 | couchdb: use x509 module to deploy certs (fixes #1063) | varac | |
2012-12-07 | new names for couchdb DBs | varac | |
2012-12-07 | removed pinning couchdb to unstable because 1.2.0-3 is in wheezy, finally | varac | |
2012-12-04 | remove no longer needed removal of the ports.conf file | Micah Anderson | |
2012-12-04 | alphabetize the apache modules | Micah Anderson | |
2012-12-04 | Stop the [warn] NameVirtualHost *:443 has no VirtualHosts errors | Micah Anderson | |
When we include apache::ssl it ships the ssl.conf file which sets up the NameVirtualHost *:443, so we just do what that class does fixes: https://leap.se/code/issues/944 | |||
2012-11-22 | call refresh_apt before installing couchdb, solves ↵ | varac | |
https://leap.se/code/issues/994 | |||
2012-11-08 | = true | varac | |
2012-11-06 | adopt new hiera creditials | varac | |
2012-11-06 | sleep some more after couchdb restart, adopt new hiera creditials | varac | |
2012-11-04 | working resource relationships for deployment | varac | |