On 20/12/2012 16:58, Josh Galvez wrote: > This tool handle most of what you are asking for: > > http://www.nocproject.org/
hard to configure though. When it gets to the stage that it's relatively easy to configure and has good quality documentation, it will be awesome. Nick > -Josh > > On Thu, Dec 20, 2012 at 2:30 AM, Thilo Bangert <thilo.bang...@gmail.com>wrote: > >> On Thursday 20 December 2012 09:11:43 Saku Ytti wrote: >>> On (2012-12-20 03:24 +0000), Blake Pfankuch wrote: >>>> I actually was doing research on this today as well. Anyone have any >>>> experience with the solutions that implement VLAN management as well >> like >>>> Gestioip? >>> I'm not remotely interested in externally developed software for this >>> problem. >> >> what do you mean. i'd be fine with an opensource project providing this. >> >>> But it's fair question. Generally this tool should not be IP or >>> VLAN based but generic resource reservation tool, IP, VLAN, RD, RT, >>> VPLS-ID, site-id, pseudowireID what have you. >>> >>> For me, humans would not do much directly with the tool. They'd give it >>> large chunk of resource. Then maybe mine it to pools like 'coreLink', >>> 'coreLoop', 'custLink', 'custLAN' etc. >>> Then in your provisioning tools, you'd request resource from specific >> pool >>> via restful API. Humand would never manually write RD/RT/IP/VLAN in the >>> tool or in the configs. And this type of system is vastly simpler than >> the >>> IPAMs I see listed, once you get rid of all the UI candy, it gets rather >>> easy problem to solve. >> >> this is a pretty accurate description of our requirements, as well. off the >> top of my head we'd also manage phone numbers, key ids, and key box ids, >> with >> it, but that would almost be a minor detail. ;-) >> >> >> >>