search

quattor / configuration-modules-core

Node Configuration Manager Components for Everyone
www.quattor.org
Other
6 stars 54 forks source link

ncm-network: checking of device name should be extended to allow for gre tunnel #1090

Open StephaneGerardVUB opened 7 years ago

StephaneGerardVUB commented 7 years ago

The device name of a gre tunnel is usually 'gre[i]', but this is not allowed with the current $dev_regexp.

stdweird commented 7 years ago

do you want support for gre tunnels like https://www.linickx.com/gre-example-for-centosrhel? because that requires also some schema changes

StephaneGerardVUB commented 7 years ago

I need support for GRE tunnels like this : http://docs.openvswitch.org/en/latest/howto/tunneling/?highlight=gre

stdweird commented 7 years ago

that's a tunnel mamanged by openvswitch. maybe i'm missing something here, but i don't think these have ifcfg- files. (and if they have, you can call them whatever you want, incl eth)

StephaneGerardVUB commented 7 years ago

We create openvswitch bridges and GRE endpoints with ifcfg- files generated by ncm-network. Here are a few examples : `cat /etc/sysconfig/network-scripts/ifcfg-br2

ONBOOT=yes NM_CONTROLLED='no' DEVICE=br2 TYPE=OVSBridge DEVICETYPE='ovs' MTU=1462 BOOTPROTO=none

cat /etc/sysconfig/network-scripts/ifcfg-gre0

ONBOOT=yes NM_CONTROLLED='no' DEVICE=gre0 TYPE=OVSTunnel DEVICETYPE='ovs' OVS_BRIDGE='br2' OVS_TUNNEL_TYPE='gre' OVS_TUNNEL_OPTIONS='options:remote_ip=192.168.10.145' BOOTPROTO=none ` You are right, we can call these ifcfg- files whatever we want since the name of the interface is actually defined by DEVICE. But it is a bit confusing.