| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
missing.
|
|
permissions for replication
|
|
This only works with the latest patch to puppet_couchdb
|
|
|
|
|
|
adding warnings for when ACL is not being respected (which is currently always). closes #5445
|
|
|
|
|
|
|
|
|
|
|
|
|
|
add replication user
|
|
|
|
out into separate files.
|
|
|
|
needed shorewall will be automatically set up. requires new leap_cli
|
|
feature/couch
|
|
|
|
split out bigcouch and only apply if needed, initial code for replication
|
|
and bump the version number to 0.5.2.
Change-Id: Ie75018bf11583d14dab148732d58d6d50f88dd42
Note: this didn't make it into the tag
|
|
tagging 0.5.2 release
|
|
|
|
|
|
|
|
|
|
|
|
|
|
depending on the services.
|
|
|
|
the problem was following:
if a host has the webapp service, the template for /etc/hosts adds some stuff.
But setup.pp did not ask hiera about the services so
"/srv/leap/bin/puppet_command set_hostname" always resets the hostname.
Since that gets triggered every time you run "leap deploy" the
hostname changes, some services restart, then the hostname changes back and
the services restart again.
The solution is to get the hiera data before every run.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and were missing .conf suffix
|
|
for configuration (#3108)
Change-Id: I4f94a47d47a40bfc6835359e7781707f96e91db0
|
|
Change-Id: I3b6a87c9d6a2c349392e5bc98a68b800645fde92
|
