ETHTOOL_OPTS in cobbler

[Tom Kleiberg]

Hello all,

I am trying to force the ethernet-card settings on my FC8 machines.  
One way of doing this is to use the ifcfg-ethX scripts
(see http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-per...)

.
This requires that an extra parameter is added to these scripts,  
namely ETHTOOL_OPTS.
My question is now whether it is possible to add this line to the  
script during installation and (possibly) different for each  
interface, e.g.:

cobbler system edit --name=foo --interface=eth1 -- 
mac=AA:BB:CC:DD:EE:A1 --ip=x.x.x.x --ethopts="speed 100 duplex full  
autoneg off"

if not, what would be a good way to do this?

thnx

tom

[Tom Brown]

Tom Kleiberg wrote:
>  Hello all,
>
>  I am trying to force the ethernet-card settings on my FC8 machines.  
>  One way of doing this is to use the ifcfg-ethX scripts
>  (see
> http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-per...) 
>  .
>  This requires that an extra parameter is added to these scripts,  
>  namely ETHTOOL_OPTS.
>  My question is now whether it is possible to add this line to the  
>  script during installation and (possibly) different for each  
>  interface, e.g.:
>
>  cobbler system edit --name=foo --interface=eth1 -- 
>  mac=AA:BB:CC:DD:EE:A1 --ip=x.x.x.x --ethopts="speed 100 duplex full  
>  autoneg off"
>
>  if not, what would be a good way to do this?
>     
i do it in %post but yeah its a pain

[Christian Horn]

On Wed, Jun 03, 2009 at 12:31:40PM +0200, Tom Kleiberg wrote:
>  
>  I am trying to force the ethernet-card settings on my FC8 machines.  
>  One way of doing this is to use the ifcfg-ethX scripts
>  (see
> http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-per...) 
>  .
>  This requires that an extra parameter is added to these scripts,  
>  namely ETHTOOL_OPTS. 
For this i use ksmeta-vars eth0force100full, eth1force100full
etc. which are checked by a snippet and appropriate line is
inserted into the network-device configfile.

Not optimal solution, also i am checking for each ethX-inter-
face literally and couldnt get a 'for i in ethXforce100full'-
line to work.


Christian

[Tom Kleiberg]

Thanks for your quick reply!

Your fix brought me to another idea. I was thinking of, instead of  
using the ksmeta-vars parameter as you say, to use the bonding-opts  
parameter. This parameter you can set for each interface. i guess this  
should not make much fuss, as long as you are not using the interface  
in bonding mode. By means of some snippet, i can then parse the  
parameter and set ETHTOOL_OPTS.
This may however only work when the bonding options are not placed  
inside /etc/modprobe,conf but in ifcfg-ethX  ("BONDING_OPTS"). The  
snippet could then be as simple as just replacing BONDING_OPTS with  
ETHTOOL_OPTS. Would you agree with this quick-n-dirty fix?

thanks

tom




On Jun 3, 2009, at 12:44 PM, Christian Horn wrote:

>  On Wed, Jun 03, 2009 at 12:31:40PM +0200, Tom Kleiberg wrote:
> >
> > I am trying to force the ethernet-card settings on my FC8 machines.
> > One way of doing this is to use the ifcfg-ethX scripts
> > (see
> http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-per...)
> > .
> > This requires that an extra parameter is added to these scripts,
> > namely ETHTOOL_OPTS.
>
>  For this i use ksmeta-vars eth0force100full, eth1force100full
>  etc. which are checked by a snippet and appropriate line is
>  inserted into the network-device configfile.
>
>  Not optimal solution, also i am checking for each ethX-inter-
>  face literally and couldnt get a 'for i in ethXforce100full'-
>  line to work.
>
>
>  Christian
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler

[Christian Horn]

On Wed, Jun 03, 2009 at 01:14:11PM +0200, Tom Kleiberg wrote:
>  
>  Your fix brought me to another idea. I was thinking of, instead of  
>  using the ksmeta-vars parameter as you say, to use the bonding-opts  
>  parameter. This parameter you can set for each interface. i guess this  
>  should not make much fuss, as long as you are not using the interface  
>  in bonding mode. By means of some snippet, i can then parse the  
>  parameter and set ETHTOOL_OPTS.
>  This may however only work when the bonding options are not placed  
>  inside /etc/modprobe,conf but in ifcfg-ethX  ("BONDING_OPTS"). The  
>  snippet could then be as simple as just replacing BONDING_OPTS with  
>  ETHTOOL_OPTS. Would you agree with this quick-n-dirty fix? 
Was also thinking on that.  Reminds me of an internal feature-
request i have to work on of a collegue asking for the flexibility to
explicitly choose the interface-mode like static, dhcp or none.
Havent looked deeper, for now this is done implicitly;
none for bond-slaves, static/dhcp switched by static-boolean.

I think he cant state a valid usecase so i will just push him into 
writing a custom snippet doing what he wants.
If many of such interface-based requests/needs come up a free-text
line could be interesting, kind of ksmeta-per-interface.
But right now i cant think of more possible per-interface-settings
so a proper solution for the ethtool parameters would be enough.


Christian

[Tom Kleiberg]

Hello all,

In reply to my own earlier e-mail, i now just use the following dirty  
fix. It uses the bonding-opts parameter (which can be set per  
interface) to set the ETHTOOL_OPTS. It is not ideal, but as long as  
you do not need bonding on that interface, it should not matter (I  
guess). Here is the patch for post_install_network_config:

[naslab@panoramix snippets]$ diff -aNr post_install_network_config  
post_install_network_config_tjk
118a119,124
>              # TJK fix: use bonding_opts for ethtoolops
>              #if $bonding_opts != "" and $bonding.lower() == ""
>  cat >> $devfile << EOF
>  ETHTOOL_OPTS="$bonding_opts"
>  EOF
>              #end if 
I can now set the options via:

  /usr/bin/cobbler system edit --name=node11 --interface=eth1 -- 
mac=00:0A:E4:14:0E:A3 --ip=10.0.0.55 --netmask=255.255.255.252 -- 
static=1 --bonding-opts="speed 100 duplex full autoneg off"

Perhaps, the maintainers of cobbler want to consider to add  
ETHTOOL_OPTS as new feature in future releases.

Kind regards,

Tom





On Jun 3, 2009, at 12:44 PM, Christian Horn wrote:

>  On Wed, Jun 03, 2009 at 12:31:40PM +0200, Tom Kleiberg wrote:
> >
> > I am trying to force the ethernet-card settings on my FC8 machines.
> > One way of doing this is to use the ifcfg-ethX scripts
> > (see
> http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-per...)
> > .
> > This requires that an extra parameter is added to these scripts,
> > namely ETHTOOL_OPTS.
>
>  For this i use ksmeta-vars eth0force100full, eth1force100full
>  etc. which are checked by a snippet and appropriate line is
>  inserted into the network-device configfile.
>
>  Not optimal solution, also i am checking for each ethX-inter-
>  face literally and couldnt get a 'for i in ethXforce100full'-
>  line to work.
>
>
>  Christian
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler

[Michael DeHaan]

Tom Kleiberg wrote:
>  Hello all,
>
>  I am trying to force the ethernet-card settings on my FC8 machines.  
>  One way of doing this is to use the ifcfg-ethX scripts
>  (see
> http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-per...) 
>  .
>  This requires that an extra parameter is added to these scripts,  
>  namely ETHTOOL_OPTS.
>  My question is now whether it is possible to add this line to the  
>  script during installation and (possibly) different for each  
>  interface, e.g.:
>
>  cobbler system edit --name=foo --interface=eth1 -- 
>  mac=AA:BB:CC:DD:EE:A1 --ip=x.x.x.x --ethopts="speed 100 duplex full  
>  autoneg off"
>
>  if not, what would be a good way to do this?
>
>  thnx
>
>  tom
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
Seeing the network snippets are complex (understatement!) I think that 
(if it's something folks are interested in), might be a nice parameter 
to have, that way
folks would not have to modify their own Snippets. (Asking users to 
understand how to tweak the network snippet is a bit much, I think, and 
it's better that
we do things in ways that save everyone work).

Would someone want to add this?

Adding that parameter on a per-interface basis, defaulting to "", does 
not seem to be a bad idea to me.

(We'd want this done on the "master" development branch of course, 
rather than applied to 1.6, since it is a new feature)

--Michael

[Dave Hatton]

Michael DeHaan wrote:
>  Tom Kleiberg wrote:
>    
> > Hello all,
> >
> > I am trying to force the ethernet-card settings on my FC8 machines.  
> > One way of doing this is to use the ifcfg-ethX scripts
> > (see
> http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-per...) 
> > .
> > This requires that an extra parameter is added to these scripts,  
> > namely ETHTOOL_OPTS.
> > My question is now whether it is possible to add this line to the  
> > script during installation and (possibly) different for each  
> > interface, e.g.:
> >
> > cobbler system edit --name=foo --interface=eth1 -- 
> > mac=AA:BB:CC:DD:EE:A1 --ip=x.x.x.x --ethopts="speed 100 duplex full  
> > autoneg off"
> >
> > if not, what would be a good way to do this?
> >
> > thnx
> >
> > tom
> >
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/cobbler
> >   
> >     
>
>  Seeing the network snippets are complex (understatement!) I think that 
>  (if it's something folks are interested in), might be a nice parameter 
>  to have, that way
>  folks would not have to modify their own Snippets. (Asking users to 
>  understand how to tweak the network snippet is a bit much, I think, and 
>  it's better that
>  we do things in ways that save everyone work).
>
>  Would someone want to add this?
>
>  Adding that parameter on a per-interface basis, defaulting to "", does 
>  not seem to be a bad idea to me.
>
>  (We'd want this done on the "master" development branch of course, 
>  rather than applied to 1.6, since it is a new feature)
>
>     
Hi Michael,

Been away for a while finishing off a long term project

This feature has been on my personal list for a while.

I'll add this next week, unless someone else is already doing it.

Dave Hatton