Comment # 22 on bug 1182227 from Andrei Borzenkov

(In reply to Thomas Blume from comment #21)
> With ip=dhcp it still fails, I'm trying to find a workaround from within
> dracut.

wicked client (equivalent of ifup) requires per-interface configuration. That
is how wicked is designed. Wicked dracut parser is simply wrong.

The dracut legacy module basically implements hotplug - it runs ifup script
from within udev rule; ifup parses command line and picks up either
interface-specific config or generic one. It also waits for at least one
interface to come up. In addition its ifup can be called directly, is using the
same parser and works whether called from within udev rule or manually.

To add feature parity to wicked module there are two possibilities

1. Command line parser should generate policy instead of configuration; this
policy will be directly loaded into backend. This will move hotplug handling
into wicked. It won't allow running "wicked ifup" manually if needed.

2. Implement same wrapper for wicked ifup as legacy module does - generate
wicked configuration for specific interface and call wicked with it. It need
not really be xml, could be good ole ifcfg file. And add udev rules to call
this wrapper. And of cause name it ifup so it could be called explicitly. And
add same waiting for network being up.

Considering that a) there is exactly zero documentation for wicked policies and
b) running ifup/down manually still requires explicit configuration - I'd say 1
is pretty much unrealistic. For 2 one could actually simply copy legacy scripts
and only add ifcfg generation. But then it begs the question - why wicked at
all?

What exactly wicked module does that legacy module does not that justifies all
those efforts?