Vins wrote:In the configstore_poller.php at line 170 and 183 there's a hard-coded reference to
'<ahref="http://net10/cacti/plugins/configstore/ ... _status=-1&...
it is correct?
No. That will be fixed in the next release. I am very close, but if you provide a patch, I will patch the existing one and post it to the forum. Otherwise, just keep an eye out. On a related note, I am close to a point with the next release that I could release it, but have a ways to go on my actual goal. If anyone would like to get the new one a little early, let me know. If I have enough interest, I will post another working release. Here is a short list of the changes done now:
- Inventory management.
- Separation of Inventory and backups.
- Config Search - search for a string in the latest backups. i.e. how many switches have a particular command in their configs.
- Ability to keep Cacti devices and MacTrack devices in sync with ConfigStore.
- Location awareness. Everything has to be entered into inventory, and assigned a location. Management, Cacti/Mactrack integration, Backups, etc. is an option.
- API (never written an API, so I am sure that criticism will make it better
- Abstraction of backup server into the accounts area instead of global settings. This was so that you can have multiple backup servers. This is so that you if you have a device behind a firewall, which is NATting for the device, you can tell the device to backup to the NAT IP. I am sure their are other uses, but that was mine.
- Ability to send a config from a particular context, or VRF on a device.
- Read only mode for most areas of ConfigStore.
Things that need to be done before official release:
- Tagging. Ability to tag inventory items to each other in a parent child relationship. (switch belongs to a stack who's master has an IP/hostname etc.)
- Documentation management. Ability to upload and tag documents to anything in inventory. i.e. Attach a floor plan to a floor in inventory, etc. Use your imagination..
- Contact/Contract man agent with tagging of course. This is primarily for vendor contract management. It is not a intended to be a replacement for a GAO - though it would be nice
- Crypto Store. This is for keeping encrypted information i.e. username/passwords, etc.
- VPN manager. This may be worked into the Contact manager, but haven't thought it though completely yet. The purpose is provide an internal portal for people to update, and view VPN documentation. Everyone has their own VPN form they ask other companies to fill out when creating a site-to-site VPN that establishes encryption, PSK, contact info, peer addresses, etc. This will be that, in a web form to start with.
Any questions or comments welcome.
-chadd.