[rancid] Reporting subsets of Rancid data.

[Dan Anderson]

If you created an additional set of groups, you could do a group per campus and send the reports/diffs for each group or groups to different e-mail addresses based on the entries in your /etc/aliases file. That's 100% supported and wouldn't change during upgrades. People who wanted to see all of the reports/diffs would be in all of the group aliases and those who didn't would only be in a subset.


Something along the lines of

campus1_switches: boss_person, campus1_people
campus2_switches: boss_person, campus2_people, campus1_people

-- Dan
On Apr 8, 2021, 12:11 PM -0400, Chris Davis <Chris.Davis at principia.edu>, wrote:
> We have 2 major campuses, and we've always reported our config diffs and pretty much everything else to all members of our small network team.  All the switch configs are co-located in the same directory, etc.  But now, one campus is complaining that they don't want to see all the config diffs from the other because it's difficult to know if they have data in the config diff report.  I was asked if it was possible to split the report into 2, one for each campus.  The IP addresses are such that it would be possible to identify them easily.  But rancid just seems to be focused on reporting what is in the directory.  I'm not sure I'd want to go to great effort to make this kind of thing happen, just to have it break every time I update Rancid.  Our boss is keen on network knowing everything on either campus (we back one another up to a high level of degree).  Is it easy to carve up the reporting based on IP ranges and provide different email addresses for each set of reports without impacting the future upgrading process?   I just want to be able to say I investigated it, but I think the boss would be against it anyway.
>
> Thanks.
> Chris
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at www.shrubbery.net
> https://www.shrubbery.net/mailman/listinfo/rancid-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20210408/2e666208/attachment.htm>