[Nodeshot] Networking features in nodeshot

[Nemesis]

Hi Renaud, yes you are completely right.

Initially my goal was to get out something people could start using
asap, now we are there finally and I have to refine it.

You can disable the networking apps just by editing your project
settings file, I have a few instances where I do that, and in my
settings I have:

# ------ All settings customizations must go here ------ #

INSTALLED_APPS.remove('nodeshot.networking.connectors')
INSTALLED_APPS.remove('nodeshot.networking.hardware')
INSTALLED_APPS.remove('nodeshot.networking.links')
INSTALLED_APPS.remove('nodeshot.networking.net')

Ideally all these apps will live in a separate repo dedicated to mesh
networks, and some of those modules will live in their own projects (eg:
links will be django-netjsongraph).

Did you do this or did you do something different?

Federico


On 11/30/2015 07:43 PM, Renaud wrote:
> Hi Federico,
>
> I completely agree with your point of view. As I told to the list
> previously I'm working on a project based on nodeshot for the
> frontend. And one of my recent challenges were to remove all the
> networking part of nodeshot without hacking nodeshot itself.
>
> It'd be cool to have only the core exempt of nodeshot without the
> business logic link to the original goal of the project (WiFi/Networks).
>
> My 2 cents,
> Renaud
>
>> Nemesis <mailto:nemesis at ninux.org>
>> lundi 30 novembre 2015 18:48
>> Hi everyone,
>>
>> In the latest months I've been working a lot in order to extract some
>> nodeshot modules that would be more successful in separate
>> projectsthat can be included into nodeshot.
>>
>> In the process of extraction I have also been working on adding new
>> features that will beavailable in nodeshot in the near future.
>>
>> These features are all related to community networks, which is the
>> main use cases from which nodeshot is born.
>>
>> I'm talking about these projects:
>>
>>   * netdiff, pure python library that is in charge of analyzing
>>     network topology: https://github.com/ninuxorg/netdiff
>>   * django-netjsongraph, django app that is built on top of netdiff:
>>     https://github.com/interop-dev/django-netjsongraph
>>   * netjsongraph.js, javascript library (based on d3):
>>     https://github.com/interop-dev/netjsongraph.js
>>   * netjsonconfig, pure python library that generates OpenWRT
>>     configurations: https://github.com/openwisp/netjsonconfig
>>
>> The good news isI'm very satisfied with the results I'm obtaining!
>> The bad news is that it will take longer than expected to finish the
>> process and release the 1.0.
>> The truth is I was not satisfied with the quality of the current
>> architecture in nodeshot. I would especially like to separate
>> completely the nodeshot core from the networking features, simplify
>> some modules and remove afew cumbersome hacks.
>>
>> I want to finish this process before releasing the 1.0, because 1.0
>> is meant to be a stable release, after the 1.0 is out I won't be able
>> to do drastic changesanymore, so I think it's better to solve these
>> problems right now, I'm sure that the benefits in the long term will
>> be long lasting.
>>
>> I've talked a lot about the reasons that led me to these decisionsat
>> different events, eg at the Battlemesh v8 in Sloveniawhichison
>> youtube https://www.youtube.com/watch?v=mFQKtIWL8vk. 
>>
>> Pheraphs we could just release a 0.10 somewhen soon ...
>>
>> Federico
>> _______________________________________________
>> Nodeshot mailing list
>> Nodeshot at ml.ninux.org
>> http://ml.ninux.org/mailman/listinfo/nodeshot
>
>
>
> _______________________________________________
> Nodeshot mailing list
> Nodeshot at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/nodeshot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/nodeshot/attachments/20151201/384789ba/attachment-0001.html>