[Voyage-linux] Patches welcome?

Tom Malcolmson (spam-protected)
Thu Oct 30 23:27:54 HKT 2008


Punky,

I followed your link and read about project dynamite.

I agree with most of what you have written, and I definitely agree with 
you about the importance of this.

You don't mention SNMP for the backend daemon.  How come?

Your 'large scale' point is very important.  I can easily manage a 
couple of Voyage nodes the ways things are.  It is when I get into 
bigger deployments that I need tools that are not currently available 
(as open source).

Kaboodle is an open source, cross platform, network management utility 
that has been abandoned.
http://www.kaboodle.org/
I think it would serve as a good starting point.  I quite like it's 
method of network discovery (using pcap/winpcap).  Perhaps the Kaboodle 
people could be convinced to make it dual licensed rather then just GPL?

Regarding programming language for the daemon.  I would have thought 
that writing it (or anything core) in Ruby or PHP would introduce new 
dependencies.  Whereas C/C++, Python, and shell wouldn't.

Tom.

Kim-man 'Punky' TSE wrote:
> Hi Jeff,
>
> I have listed out some requirements on the web UI.  See Project 
> Dynamite:    http://linux.voyage.hk/?q=project_dynamite
>
> Design philosophy and guidelines:
>   1. Small. It must be damn small in size as it runs on embedded system.
>   2. Extensible. It must be easily extensible to add support for 
> managing new services without code change so that 3rd party developer 
> (including OSS communities and commercial vendors) can enhance its 
> features and evolve it. Hence, the architecture design is the key.
>   3. Large Scale. It not only can work on single node but also can 
> manage multiple nodes. This is useful for enterprise-grade large scale 
> deployment.
>
> Unless some tools are available that closely match the requirement, 
> otherwise, they will not be in voyage.
> Regards,
> Punky
>
>
> Jeff R. Allen wrote:
>> Hello all,
>>
>> Just thought I'd introduce myself. I am just getting started with
>> Voyage, and I really like what I see so far. I'll be porting some
>> stuff I had working on OpenWRT over in the next few days.
>>
>> I'm trying to decide which direction to go to put a web-ui on the box.
>> Right now, I am headed towards Wifi-admin
>> (http://wifiadmin.sourceforge.net/). Anyone have success and/or horror
>> stories to tell?
>>
>> Finally, I'd really appreciate it if I could look at an example of
>> using the customization framework. I can generally see what it's
>> supposed to look like but a concrete example would be helpful.
>>
>> Thanks,
>>   -jeff
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux at list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>   
>
>




More information about the Voyage-linux mailing list