Dear Shesha
you are right, you have not had any answer from me yet.
In these three months I have carefully examined your proposal.
Many features you suggest are interesting but I think I will
reimplement them in the mainstream version of VDE.
* the use of IP sockets for VDEplug connections could be useful
in situations like the ones you illustrated (thousands of VM in
a data center).
Your implementation is not flexible: depending on a command line
option all the ports use IP sockets or all the ports use UNIX sockets.
It is not possible to mix the two possibilities.
Moreover, your implementation of IP sockets is not safe,
everyone who can access the IP node can join the VDE switch as there are
no authentication nor authorization controls.
* the idea of trunk switches is interesting, too.
I do not like your implementation as it requires a lot of useless data
structures. In fact, to use the existing code, you allocate all the
possible VLANS. I think I'll implement that feature using a different
search policy in the hash table (all the VLANS will be recognized as
valid).
* last but not least there is a problem about the license. The code
you sent me includes a copyright notice of your company.
I am glad to acknowledge your contribution but I do not want to share
the copyright of the project.
Thank you very much for your suggestions that will help us to evolve
VDE.
All the best.
renzo
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
vde-users mailing list
vde-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vde-users
