I used this approach detailed below in production for a large-ish
environment.
When used in conjunction with Nginx load balancing in AWS
(http://blog.mague.com/?p=286) it worked very well.
1) Route all certificate requests (explained above) to a pair of boxes that
have the sync setup listed bel
On Fri, Jul 18, 2014 at 1:37 AM, Dejan Golja wrote:
> We tried with yas3fs, but we abandoned that solution because was just not
> reliable enough. Also we considered GlusterFS, but again on some other
> projects the experience wasn't great.
>
> So my question is how you guys manage that ?
DRBD?
Not sure if it would work always, because if using unison you can get
conflicts on files such as serial, inventory.txt ,ca_crl.pem, etc and then
you need to merge them manually.
Quoting:
Unlike simple mirroring or backup utilities, Unison can deal with updates
to *both* replicas of a distribut
Hi
What about this approach? [1] Sync Puppet Certs between EC2 regions
It seems very easy to implement: unison + incron + scripts
Disclaimer: not tested yet. Hope to have a prof of concept next week.
Best regards
[1] http://blog.mague.com/?p=468
--
yas3fs is using s3 as a backend, but unfortunately did not work out.
On Friday, July 18, 2014 6:00:02 PM UTC+10, ankush grover wrote:
>
> Hi Dejan,
>
> You can try using S3 for this purpose. So keep all the data like SSL or
> CA on S3 and ask all the puppet masters to pickup the ssl or any oth
Hi Dejan,
You can try using S3 for this purpose. So keep all the data like SSL or CA
on S3 and ask all the puppet masters to pickup the ssl or any other data
from S3.
On Fri, Jul 18, 2014 at 12:07 PM, Dejan Golja wrote:
> Hello guys,
>
> so puppet community I seek some guidance. I am rebuil
