Bug#347569: VDE2 package
On Thu, Dec 14, 2006 at 05:38:03PM +0100, Piotr Roszatycki wrote: Hi Piotr! :) I added you to the alioth pkg-vsquare project, and we'll be glad for you to join the mailing lists and discuss with us how we can integrate our efforts best, in order to comaintain vde, and the other vsquare projects, if you want! ;) You already have commit access to our svn repository! I'm personally not completely familiar with all the vsquare tools and was mostly involved on the debian specific part, to help with the actual packaging and uploading them... I'm sure together with ludovico we can sort everything out and also quickly include the relevant patches upstream! As far as etch goes I agree with you that vde2 and the other vsquare packages have no chance to get in (bad timing, unfortunately) and wouldn't remove vde 1.x... We can still provide the transitional package and we'll upload everything to backports.org after etch is released, to support vde2 for stable, while making a complete support available for lenny! :) > I hope you will accept my patches and /etc/network scripts :) > We certainly will! :) And also the group related things seems ok to me and if nobody has any objection I think should be included... > I see there is no need to modify the packages heavly, so I think there is no > need to inform the ftp-master just now. He probably will ask if the VDE2 > package was hijacked. I hope we can work together on VDE2 project so the > situation would be clear. :) > The package was approved, no problem adding you to the Uploaders: field as well to make it clear we are all working on this! Thanks! Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347569: VDE2 package
Piotr, I think there has been a lack of communication (from both sides). We needed vde-2 to release (soon) umview and we have seen (nor heard of) any further evolution of vde-2 from you. Unfortunately ftpmaster has already included our vde-2 (afaik) so my proposal is to make a merge of both efforts as soon as possible (I think that Ludovico is working on that), and then we will decide together for the final maintainer of the packets. Your work on vde-1 has been perfect and everybody here appreciate your professional management of Debian issues, but the delay on vde-2 was a bit painful for us. So, my wish for the future is to increase the level of communication from both sides to avoid any further doubling of efforts. Ludovico is working on the whole View-OS project (including VDE), he is younger and just a bit less busy than me, so I think he is a valuable resource for keeping the suitable level of communication needed. Thank you Piotr, renzo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347569: VDE2 package
Thank you very much for fast reponse :) On Thursday 14 December 2006 13:19, Ludovico Gardenghi wrote: > Hi. Renzo Davoli, the main VDE author, asked Guido and me to create a > new package for VDE2. There was no recent activity on the vde package so > we went on with the packaging. Yes, there was a problem with VDE 2.0.x version and it didn't work correctly if the separate programs was started with different privileges. I.e. the vde_switch as root, the slirpvde as user. My modifications allow to start VDE components with anybody who are in vde2-net group. The trick is to start each components' sockets with 660 mode. If some user belongs to vde2-net group, it can connect to the socket. I needed some additional modifications for upstream (the 070-mode_for_comm_socket.patch file). I'll be glad if the patch will be applied to the upstream. I didn't want to release the vde2 package which doesn't support group-based privileges, so I delayed my work... > We have no problems in leaving the maintenance of VDE packages to you > and, if needed, in adding you to the members of pkg-vsquare. I think the better way is to put my patches to upstream. I see the pkg-vsquare project is very reasonable, and I think our work can be merged. > > * Does the vde2 package interfere with vde package? > > As for now, yes. Binaries have the same names and places in vde and > vde2; in fact we added a Conflict in vde2 against vde. We don't see this > as a problem, because vde2 has complete backwards compatibility with vde > and it't much more reliable and bug-free. 1.x series of VDE should not > be used anymore. The real question is: should we remove vde package from etch or not? Unfortunately, the etch is frozen now, so at least we can leave the VDE 1.x in Debian stable... I've provided the transitioning package: Package: vde Architecture: all Depends: vde2 Description: transitional dummy package which can be safely removed Dummy package to upgrade to the new vde2 package. I think it might be a smooth way for upgrade VDE 1.x to the 2.x, but as far as etch is frozen, I'm afraid that the upgrade shouldn't be forced. > > * Does it contain some additional patches? > > Being the authors of VDE we decided to put everything in the main CVS > tree: we see no point in having debian-specific patches. So I'd like to list my patches and explain why I created them: 010-fhs_compatibility.patch: vdetap.c prints the path to shared library as /usr/local/lib/libvdetap.so. It should be /usr/lib/vde2/libvdetap.so 030-rtld_next.patch: The libvdetap shouldn't call syscalls! Instead of this, it should call next function in dynamic library symbol list. It is only way to make libvdetap compatible with other dynamic library wrappers, like fakeroot or fakechroot. Worse, using pure syscalls makes VDE not portable to other systems than Linux! 040-missing_includes.patch: I think it is not necessary now. 050-sigs_on_non_i386_archs.patch: The VDE is not portable to non-i386 architectures! This patch is necessary for alpha and arm, AFAIR. 060-vdeqemu_cleanup_after_error.patch: The vdeq does not clean up after some errors. 070-mode_for_comm_socket.patch: The patch for allowing to use group-based privileges. The patch also provides "-m" option for vdeq and vdetap. 080-daemonize_with_detach.patch: The vde_switch and slirpvde don't detach from terminal. It is the must for daemons, because it hangs the start up scripts otherwise. 090-slirpvde_pidfile.patch: The slirpvde doesn't create pidfile. > > * Does it provide /etc/network/interfaces support? > > No. I took a quick look to your support and it seems complete and > useful. I think it should be included in the official vde2 package. The hints how to use this interface are in README.Debian file. > > * Does it support non-root users? > > I'm not sure I've fully understood this question. Strictly speaking, > vde2 never needs root access. The only case it may be needed is when you > want to connect a vde_switch to a tap interface (I agree that's often > the case, but not always) and nobody created a persistent tap interfaces > for you. But also in this case you can create a persistent tap interface > with tunctl with the correct owner and let a non-root user start the > vde_switch. I meant starting the vde_switch with root privileges (i.e. as tap0 interface) and allowing to connect to the socket for users who belongs to specific group (i.e. vde2-net for Debian system). I.e.: The global system interface is started as: iface tap0 inet static address 10.0.2.1 netmask 255.255.255.0 vde2-slirp -dhcp It means that the vde_switch is started as root user and vde2-net group (needed for kernel >2.6.18) and slirpvde is started as vde2-net user and vde2-net group. Just now it is possible to add some user to vde2-net group, i.e.: # adduser dexter vde2-net and the user can connect to the switch with his own application: dexter$ vdeq qemu -m 660 -net nic -net vde,sock=/var/run
Bug#347569: VDE2 package
On Thu, Dec 14, 2006 at 11:21:50AM +0100, Piotr Roszatycki wrote: > Hi. I've found that you uploaded new vde2 package. I didn't find the source > for the package, so I'd like to ask: Hi. Renzo Davoli, the main VDE author, asked Guido and me to create a new package for VDE2. There was no recent activity on the vde package so we went on with the packaging. I'm sure we should and can join our efforts for a better vde2 package :-) so I'll try to answer all your questions. First of all, we keep the source code for VDE on SourceForge (project name VDE) and it's updated to the latest version (currently 2.1.5 which I released a few days ago). The Debian-related files are hosted on alioth under the "pkg-vsquare" project. It includes Debian files for other software written by Renzo, me and others. All this software is linked to virtual machines and networks (see http://www.virtualsquare.org) and our intention is to create Debian packages for other projects as well. We have no problems in leaving the maintenance of VDE packages to you and, if needed, in adding you to the members of pkg-vsquare. And now, your questions. > * Does the vde2 package interfere with vde package? As for now, yes. Binaries have the same names and places in vde and vde2; in fact we added a Conflict in vde2 against vde. We don't see this as a problem, because vde2 has complete backwards compatibility with vde and it't much more reliable and bug-free. 1.x series of VDE should not be used anymore. > * Does it contain some additional patches? Being the authors of VDE we decided to put everything in the main CVS tree: we see no point in having debian-specific patches. > * Does it provide /etc/network/interfaces support? No. I took a quick look to your support and it seems complete and useful. I think it should be included in the official vde2 package. > * Does it support non-root users? I'm not sure I've fully understood this question. Strictly speaking, vde2 never needs root access. The only case it may be needed is when you want to connect a vde_switch to a tap interface (I agree that's often the case, but not always) and nobody created a persistent tap interfaces for you. But also in this case you can create a persistent tap interface with tunctl with the correct owner and let a non-root user start the vde_switch. > * Is it uploaded to experimental or sid? I think it's uploaded to Sid, but Guido is the Debian expert of this group. :-) I don't know if this is the best solution for release times, but I want to stress the fact that vde2 is *much* more stable than vde. Lots of bugs have been fixed in the vde2 branch and not in vde 1.x. > * Your package is splitted on 3 different binary packages. Why? I think the > vde2 package should provide all files. We did this splitting for a good reason, or at least we think so. :-) Let me try to explain: - libvdeplug is a library that everyone can use to write his own vde-compatible application (e.g. qemu or vdetelweb - that's a web interface to vde that hasn't been packaged yet). This wants to be a quite stable package with a well defined API and we don't want a program to depend on the whole VDE package just for a little library that allows it to connect to a switch (maybe on a different host) - vde_cryptcab has been splitted from the main package because of specific requests from many users. The main point is "we don't want to be forced to install OpenSSL libraries if we don't need the SSL part of VDE." vde_cryptcab (sort of a vde_plug over an encrypted UDP channel) is the only tool that depends on SSL and it's not vital to VDE. > * New vde2 package doesn't provide upgrade path for users of old vde package. I suppose the only upgrade that may be needed is in your /etc/network/interfaces part (but I'm not sure -- I haven't checked it very well). vde2 aims to substitute vde in a quite painless way. The control socket (i.e. /var/run/vde.ctl) now is a directory containing various sockets, but usually nobody notices this in the everyday use, unless one tries to connect a vde_plug from vde 1.x to a vde_switch from vde2. In that case he must specify the socket name /var/run/vde.ctl/ctl instead of the dir name, but that's all. > I would like to offer my help and patches. My vde2 package is available at > http://people.debian.org/~dexter/vde2 > The SVN source is available at > svn://svn.debian.org/cvsdebuild/trunk/debian/dists/vde2 We'll take a look and, if you have no objections, we could try to merge your additions to the main tree. Do you have specific advices or anything? > Please reconsider the package splitting. Please let the ftp-master know, that > he should remove currently uploaded vde2 package from NEW queue. Please, > review my patches and /etc/network scritps. I explained you the reasons that pushed us towards the splitting and, if you find them reasonable, we'd like to keep them in this way. Of course we're open to suggestions. We'll notify the ftp-mas
Bug#347569: VDE2 package
Hi. I've found that you uploaded new vde2 package. I didn't find the source for the package, so I'd like to ask: * Does the vde2 package interfere with vde package? * Does it contain some additional patches? * Does it provide /etc/network/interfaces support? * Does it support non-root users? * Is it uploaded to experimental or sid? For last two weeks I worked on vde2 package. I didn't uploaded it yet because the etch was freezed. I've noticed that your package is slightly different that mine: * Your package is splitted on 3 different binary packages. Why? I think the vde2 package should provide all files. * New vde2 package doesn't provide upgrade path for users of old vde package. I would like to offer my help and patches. My vde2 package is available at http://people.debian.org/~dexter/vde2 The SVN source is available at svn://svn.debian.org/cvsdebuild/trunk/debian/dists/vde2 My proposition is: Please reconsider the package splitting. Please let the ftp-master know, that he should remove currently uploaded vde2 package from NEW queue. Please, review my patches and /etc/network scritps. I think we could join the forces to make a better vde2 package. Greets, -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
