[openFate 305631] vlan support in initrd
Feature added by: Bernhard Walle <bwalle@novell.com> Feature #305631, revision 1, last change by Title: vlan support in initrd openSUSE-11.2: New Requested by: Bernhard Walle (bwalle) Partner organization: openSUSE.org Description: Quoting from Bugzilla 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 complete. 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. Business case (Partner benefit): openSUSE.org: I don't see any business case here. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305631
Feature changed by: Andreas Jaeger (a_jaeger) Feature #305631, revision 5 Title: vlan support in initrd - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Desirable Requested by: Alexander Osthof (aosthof) Partner organization: openSUSE.org Description: Quoting from Bugzilla 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 complete. 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. Business case (Partner benefit): openSUSE.org: I don't see any business case here. Discussion: #1: Andreas Jaeger (a_jaeger) (2009-06-09 14:25:35) If that helps us with our own hardware in a significant way, I'm fine with doing it. Otherwise I propose to reject it. -- openSUSE Feature: https://features.opensuse.org/305631
Feature changed by: Andreas Jaeger (a_jaeger) Feature #305631, revision 4 Title: vlan support in initrd openSUSE-11.2: New Priority Requester: Desirable Requested by: Alexander Osthof (aosthof) Partner organization: openSUSE.org Description: Quoting from Bugzilla 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 complete. 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. Business case (Partner benefit): openSUSE.org: I don't see any business case here. + Discussion: + #1: Andreas Jaeger (a_jaeger) (2009-06-09 14:25:35) + If that helps us with our own hardware in a significant way, I'm fine + with doing it. Otherwise I propose to reject it. -- openSUSE Feature: https://features.opensuse.org/305631
Feature changed by: Alexander Osthof (aosthof) Feature #305631, revision 6 Title: vlan support in initrd openSUSE-11.2: Evaluation Priority Requester: Desirable Requested by: Alexander Osthof (aosthof) Partner organization: openSUSE.org Description: Quoting from Bugzilla 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 complete. 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. Business case (Partner benefit): openSUSE.org: I don't see any business case here. Discussion: #1: Andreas Jaeger (a_jaeger) (2009-06-09 14:25:35) If that helps us with our own hardware in a significant way, I'm fine with doing it. Otherwise I propose to reject it. + #2: Alexander Osthof (aosthof) (2009-06-15 10:47:19) + 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. -- openSUSE Feature: https://features.opensuse.org/305631
Feature changed by: Thorsten Kukuk (kukuk) Feature #305631, revision 7 Title: vlan support in initrd - openSUSE-11.2: Evaluation + openSUSE-11.2: Rejected by Thorsten Kukuk (kukuk) + reject date: 2009-09-15 13:14:13 + reject reason: Run out of time. Priority Requester: Desirable Requested by: Alexander Osthof (aosthof) Partner organization: openSUSE.org Description: Quoting from Bugzilla 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 complete. 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. Business case (Partner benefit): openSUSE.org: I don't see any business case here. Discussion: #1: Andreas Jaeger (a_jaeger) (2009-06-09 14:25:35) If that helps us with our own hardware in a significant way, I'm fine with doing it. Otherwise I propose to reject it. #2: Alexander Osthof (aosthof) (2009-06-15 10:47:19) 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. -- openSUSE Feature: https://features.opensuse.org/305631
participants (1)
-
fate_noreply＠suse.de