Monday, March 17, 2008

YaST2 network, driver options

I've added support for driver options for openSUSE-11.0.
This is feature I don't really use, but some of openSUSE or SLES users does. Maybe I'll need it when I will play more with bonding devices.

Hm, feature ...
In fact it brings back functionality that there was already there. But it was done in "hwcfg" files - deprecated configuration files for hardware devices. Now that configuration is stored in /etc/modprobe.d/network. But it's probably not final solution.

Why? because all that options are stored "on one place" but options packaged by driver rpms are stored in /etc/modprobe.d/$driver_name.

Maybe in future I'll change that place or enhance functionality to work on whole directory, but I need some feedback or opinions. Are there any?

Sunday, March 16, 2008

YaST2 network, bridge devices

this is my first (and very short) blog about YaST2 development.
I put some screenshots here: new features::bridge.

What is bridged network good for? Mostly for network used with virtualisation (Xen, VirtualBox, Vmware, etc.). For this purpose all virtualisation products has their own tools, configurations and scripts.
This (per-virtualisation-application) has some disadvantages:
- possible conflict between sysconfig
- not unified way how to configure
- network configuration can't be clone by AutoYaST
That's why it makes sense to be implemented in YaST

Briefed introduction : when you want for any of your hosted machine to be seen from network, create bridge attached with physical network interface and some tun device. TUN device will be attached into your virtual machine and it makes virtual hosted machine be directly connected to real LAN.

The plan is (together with bridge) to implement also support for tun/tap devices (this should be done in sysconfig first) and Xen networking to confgure all this staff in one place.

Do you like this feature? If you have any feedback, comment or enhancement request - please let me know.