Age | Commit message (Collapse) | Author |
|
work-around, use the couchdb admin/passwd
Change-Id: Ibb1cd8416d00552f8ca1716e42a08137a4b461aa
|
|
|
|
|
|
|
|
default to empty list.
|
|
|
|
|
|
|
|
|
|
by default.
|
|
Change-Id: I19e91887c3f8e90764b4baef8c5e29e25658e190
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
generating zone file).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(#2016)
|
|
|
|
included in the web app (#1978)
remove site_ca_daemon module and configuration in site.pp as well as the provider_base/services/ca.json
|
|
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
|
|
|
|
shorter named epmd (erlang port mapper daemon)
|
|
an email address contact.
|
|
|
|
|
|
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
|
|
|
|
cluster protocol
|
|
|