[Nodeshot] Not reinventing the wheel and Helping out

[Fabio Capriati]

Hi frederico,
i think that's a good software ... it can be useful for massive setup
for all devices. For example if we have a new public IP, we have to add
a policy route on all devices in the network and have to do it manually
(ask for the people to do that on own node is impossible) ... with that
framework we can retrive the information and do massive setup by
nodoshot (future feature)...

Beautiful! :D   


Il giorno dom, 05/01/2014 alle 18.52 +0100, nemesis ha scritto:
> On Sun, 05 Jan 2014 11:13:37 -0600, "Charles N. Wyble" 
>  <charles at knownelement.com> wrote:
> > On 1/5/2014 10:39 AM, nemesis wrote:
> >> On Sun, 05 Jan 2014 10:39:50 -0600, "Charles N. Wyble" 
> >> <charles at knownelement.com> wrote:
> >>>>
> >>>> I found this approach so good that I decided to extract a feature 
> >>>> of nodeshot into a separate pure-python repository:
> >>>> https://github.com/nemesisdesign/netengine
> >>>
> >>>
> >>> Please embrace/extend/use trigger:
> >>>
> >>> http://trigger.readthedocs.org/en/latest/
> >>>
> >>> Adding OpenWRT support to that package would be a HUGE win.
> >>
> >>
> >> That would be interesting. But we should get in touch with the 
> >> authors of that library before proceeding.
> >
> > Why?
> >
> > http://trigger.readthedocs.org/en/latest/new_vendors.html
> >
> > Just start hacking and send a pull request.
> 
>  It's not guaranteed a pull request will be accepted. Few years ago a 
>  Google Summer of Code student here in ninux developed a feature for 
>  diaspora, the open source federated social network, after he was done he 
>  sent the pull request and was not merged because they changed some 
>  internals and were not interested in making effort to guarantee backward 
>  compatibility for his feature. That was quite a turn down indeed.
> 
> >>
> >> Our main need is to have a common API to extract information from 
> >> devices.
> >
> > That is precisely what trigger is for. It also supports writing to
> > the devices.
> 
>  The docs say:
> 
>  "Trigger is a Python framework and suite of tools for interfacing with 
>  network devices and managing network configuration and security policy. 
>  Trigger was designed to increase the speed and efficiency of network 
>  configuration management."
> 
>  Not exactly the same thing.
> 
>  I'm analyzing the documentation.
> 
> >> We have to understand if some features we need are compatible with 
> >> the goals of that library and if authors are willing to let us 
> >> contribute. If they're positive about it that would be awsome :)
> >
> > They are. They want to support all vendors (according to the site).
> > I'm starting work on adding a few vendors I use (h3c/hp/3com).
> 
> 
>  Basically, what we need is a method that outputs a dictionary/json with 
>  all the data, like this:
>  https://github.com/nemesisdesign/netengine/blob/master/netengine/backends/dummy.py#L24
> _______________________________________________
> Nodeshot mailing list
> Nodeshot at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/nodeshot

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://ml.ninux.org/pipermail/nodeshot/attachments/20140105/8e260c52/attachment-0001.sig>