Hi Nate,

Thanks very much for using this Zenpack and for providing the feedback.

I've added your suggestions to the documenation page http://mwallraf.github.io/ZenPacks.TwoNMS.Rancid/

Perhaps I can implement them in the next version.

The modeler plugin is something I took for granted because that's a general way of working with Zenoss but indeed it's needed in order to integrate the Rancid results into the Zenoss GUI. By the way, not sure how you're using this, but personally I never check the configs inside Rancid because it's a bit slow but do I use the direct links to redirect the device configs to my ViewVC page using the zRancidViewerPath zproperty.

The zenpack uses the zenoss device id andindeed these have to resolve to IP addresses for Rancid to work. I always make sure that my host is known in DNS or in /etc/hosts and then I add devices to Zenoss based on that hostname. But another method is to automatically sync the Zenoss devices to /etc/hosts. This can be easily done and I think there are some example scripts available in the Zenoss forums. The Zenrancid script cannot do this because it runs as the zenoss user and by default the /etc/hosts file requires root permissions to change.

Using IP addresses would indeed be an option but I prefer to see the hostnames in ViewVC or in the Rancid config folders (via command line) so that's why I decided not to use ip addresses. Perhaps I can make this an option in the next release

Thanks again for the suggestions!

Maarten