eoly / puppet-rancid Goto Github PK

I don't think this module is using any specific functions from this version of stdlib.

How do you feel about me making it 'puppetlabs-stdlib' (>= 3.2.0) ?

Hi @eoly

Could you add me as a collaborator to this repo? This would let me push changes to it. When pushing new changes, I would tag and release them in accordance to my other modules and those of Ericsson.

@nhemingway I see you are giving this module some needed attention :) You might look to update the metadata.json to support newer puppet versions and the .travis.yml to test them. Ideally this would support Puppet 6 and 7.

Originally posted by @ghoneycutt in #30 (comment)

I had recently to re-install one of our rancid servers and I noticed that all routers were reported as down.
After a bit of digging I am still unclear where the problem lies.
I noticed that /usr/libexec/rancid/control_rancid changes the logic/format of temporary files, but the original router.db has still the same format.

Did anyone successfully use this module with rancid 3.X?

It is currently hard-coded to cvs. I'd like to use git

@eoly Thank you for merging in the updates we did at Ericsson. Travis is all setup, though you need to turn it on. I think you just need to sign in on Travis-ci.org and enable the service hook for this repo.

http://about.travis-ci.org/docs/user/getting-started/

Setting up rancid to use git is ok. Getting it to automatically push commits to a network repo, whilst easy enough, is a PITA to remember when you add a new group. It would be helpful if this module could be told where the remotes are for groups, and then all the config is in one place.

Hi @eoly,
it would be helpfull for us if you could create new releases/tags when updating your module. With this it's easier to explicit choose which version to use :)

Thanks & have phun
Phil

We are not using hiera with our puppet install and I am struggling to define the device config given that the only example in the README is in hiera, not in the site.pp node config syntax.
Can someone provide an example config that can be included in site.pp?

Permit the user to specify how many days logs to keep:

class { 'rancid':
    log_retention => '30d',  # or '1w', 'or '3m' for days, weeks, months.
}