Home_greyopenFATE - openSUSE feature tracking > #305631
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

vlan support in initrd

Feature state

Rejected Information


Quoting from Bug #415389 (because external reporters are not able to create a FATE entry):

It would be very useful to be able to create vlan network interfaces in initrd
via kernel command line parameters. This makes network support in initrd more

In our case we need vlan support because all servers have two physical network
interfaces. eth0 is connected to the default vlan, which is internet in our
case. eth1 is a trunk interface connected to several internal vlans.
We need the vlans to seperate traffic from different virtual machines. Only one
vlan supports nfs, other vlans are more restricted or private to a customer
owning a virtual machine.

Because a xen dom0 server doesn't need much diskspace, we boot them from the
network. This requires the initrd to login to the nfs server, which requires
vlan support.

User benefit:

I don't see any business case here.


icons/user_comment.png A. J. wrote: (9 years ago)

If that helps us with our own hardware in a significant way, I'm fine with doing it. Otherwise I propose to reject it.

icons/user_comment.png A. O. wrote: (9 years ago)

This feature was entered in a time when Bernhard Walle was still with us and maintainer of mkinitrd. As he's gone I was (automatically?) entered as requester, but I don't have the technical background. Now, Milan is the new maintainer and should be able to judge the effort and feasibility of this feature. Also, I'm adding Libor as responsible engineering manager.

Last change: 9 years ago
Score: 0
  • Negative: 1
  • Neutral: 0
  • Positive: 1
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint