[AusNOG] (Semi/Somewhat/Paritially)-automated network configuration management

Christopher Pollock chris at ionetworks.com.au
Fri Jul 27 20:25:42 EST 2012


Exactly, which was why my first suggestion was "take someone else's tool
and modify it to pull the data you want".  OpenNMS, for example, keeps data
and configuration in XML.  Not hard to get at if you want it.

--
Christopher Pollock,
io Networks Pty Ltd.
e. chris at ionetworks.com.au
p. 1300 1 2 4 8 16
d. 07 3188 7588
m. 0410 747 765
skype: christopherpollock
twitter.com/chrisionetworks
http://www.ionetworks.com.au
In-house, Outsourced.



On Fri, Jul 27, 2012 at 7:29 PM, Simon Knight <simon.knight at gmail.com>wrote:

> > I suppose network configuration is such a wide and varied thing that it's
> > difficult to model all useful configuration so it's really up to us to
> > decide what we need to capture and model it ourselves.
>
> There's always going to be custom requirements, but there's also a
> strong argument for not reinventing the wheel.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20120727/699e3372/attachment.html>


More information about the AusNOG mailing list