On Wed, Sep 19, 2012 at 07:22:59PM +0200, Andi wrote: > >>We have installed openvswitch in netkit(a user-mode linux front-end > >>let's say) after cross-compiling it for UML. During the startup of > >>the virtual machines we use a script to install openvswitch using > >>the commands reported in section 7 of INSTALL.Linux. The various > >>environment variables are exported in the script but as it turns out > >>they are not permanent after booting. After chroot-ing in the file > >>system of the virtual machines I have added the export of this > >>variables values in .bashrc. > >Is the script something that might be useful to others? If so, please > >consider posting it. If it's general-purpose enough, then perhaps it > >might be useful to include it in the Open vSwitch repository. > > > >Thanks, > > > >Ben. > Hi Ben, > > I think it(btw it is a makefile with different targets such as boot, > start, stop ...) could be useful for those who are using openvswitch > on netkit. If generalized only a little it can be used even for > other environments. So could you point me where to exactly put it?
If it's a reasonable size, you could post it here, to the mailing list. > Btw we have also written a guide about installing openvswitch in > DD-WRT. We have reported the guide here: > http://www.openflow.org/wk/index.php/UoR_:_Openflow_Kernel_space_on_DD-WRT > If you think it's the case that this should be added even in some > openvswitch wiki or repository let us know and we will add it. Maybe. Perhaps the decision should depend on what is more likely to need changing: the Open vSwitch parts or the DD-WRT parts. We can maintain the Open vSwitch parts well, if the file is our tree, but we are likely to not notice if the DD-WRT parts need to be updated, which could frustrate users. My guess, off-hand, is that it's better to keep this in the openflow wiki. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
