Page 1 of 2

question for the community

Posted: Mon Nov 24, 2014 10:55 am
by benhank
what open source Infrastructure Inventory solution do you use?

Re: question for the community

Posted: Mon Nov 24, 2014 12:59 pm
by abrist
Piles and Post-its.

Re: question for the community

Posted: Mon Nov 24, 2014 3:44 pm
by benhank
lol that would do it. job security guaranteed. "what?" fired? where my matches...

Re: question for the community

Posted: Mon Nov 24, 2014 5:52 pm
by slansing
Abrist needs a disclaimer for that haha, well, I hope others take interest in this thread and post their thoughts. Inventory management can vary from post-its, to SVN/Git controlled text files, to full on dedicated solutions, would be interesting to hear what others use.

Re: question for the community

Posted: Mon Nov 24, 2014 5:55 pm
by BanditBBS
I have worked for several large environments, not a single one had this figured out, LOL.

Re: question for the community

Posted: Tue Nov 25, 2014 9:17 am
by WillemDH
We use a SQL DB with access frontend at the moment and migrating to custom written ASP.net application.

Re: question for the community

Posted: Tue Nov 25, 2014 12:57 pm
by benhank
thanks for the reply will!

Re: question for the community

Posted: Tue Nov 25, 2014 4:14 pm
by tmcdonald
I tend to agree with Willem on this one. I always like the DIY route, so at my old job I had a MySQL DB with a queryable interface I threw together. It did everything I wanted and nothing I didn't. And in theory since I wrote it myself I could have integrated it with Nagios somehow.

Re: question for the community

Posted: Mon Dec 01, 2014 11:29 am
by benhank
Thanks fellas! Hey T, can you point me to how I would be able to make my own? and have you guys ever heard of nmap?

Re: question for the community

Posted: Mon Dec 01, 2014 11:40 am
by tmcdonald
To answer the nmap question first: Not only do we know of it, but we use it extensively in troubleshooting and it is even used on the backend in our Autodiscovery wizard.

To answer the DIY question: That is quite a tall order. I wrote the (extremely basic and not at all pretty) frontend and the (extremely small and lightweight) backend in PHP. The DB was MySQL and nothing special, just a few fields for the IP, OS, version, location, and notes. If I ever needed another field it was pretty trivial to add one, but planning ahead I never had to do that once I got the big points out of the way. I had a search bar that could search by any of the fields above, including keywords in the notes. Editing was simple since all the fields were displayed in a HTML form when I searched, and it was just a matter of changing what I wanted and hitting Update.

As for teaching you how to make your own, go forth and learn PHP ;)