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

[Simon Knight]

I think the hard bit is representing a network in an abstract way,
that can handle the majority of use cases. Once you have that you can
push data from the current network into it, run analysis on it, and
generate configurations from it. There's been bits and pieces from
research on the topic, but no complete solution yet.

On 27 July 2012 19:55, Christopher Pollock <chris at ionetworks.com.au> wrote:
> 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.
>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>