Customer presently makes use of veth in their deployment. These veths are made persistent across reboots by the manual creation of systemctl units that execute during boot. A cleaner and more manageable way of dealing with this would be if the veth could have an ifcfg script as other interfaces do which could then get deployed in an advanced network config manner with director.
*** Bug 1304021 has been marked as a duplicate of this bug. ***
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
(In reply to Freddy Wissing from comment #0) > Customer presently makes use of veth in their deployment. > > These veths are made persistent across reboots by the manual creation of > systemctl units that execute during boot. > > A cleaner and more manageable way of dealing with this would be if the veth > could have an ifcfg script as other interfaces do which could then get > deployed in an advanced network config manner with director. Hello Freddy, I'm taking a look at this bug, and I don't actually understand the ask. Perhaps if you included an example of what the user is doing with the sysctl files, I could examine whether we could have the os-net-config utility generate ifcfg files. Without knowing what the purpose of the veth is, I'm not sure I can imagine how this feature would work. Can you please describe in more detail how the veth interfaces are used?
Hi Dan, The customer isn't pursuing this anymore due to some internal decisions so we can go ahead and close the bug. Thanks, /Freddy