[sles-beta] Comments on wicked in today's presentations

[Joe Doupnik]

     The difficulties to which I refer below are two: the discussed 
interface naming and associated ifcfg-X contents, and then yesterday the 
peculiar problem of wireshark seeing no packets. The latter suggests 
wicked derived apparatus is not yet ready for packet captures.
     As for shell scripts, they at least work and are well proven in the 
field. Wicked exchanges them for its own scripts. So I think this is not 
a good argument on either side of the problem.
     What counts is the apparatus works as intended, is understood by 
owners and not least how it interfaces with human managers.
     Thanks,
     Joe D.

On 24/03/2014 21:36, Thorsten Kukuk wrote:
> On Mon, Mar 24, Joe Doupnik wrote:
>
>>       Further on what we know so far. Just what are those problems which
>> need solving (my place may not face them), and how would wicked go about
>> solving them? I dunno.
> Other question: which problems do you have caused by wicked and where
> do you come in contact with it?
> Up to now, I haven't seen any report here which where caused by
> wicked.
>
>> What does wicked do today in Beta 3?
> Making sure that your network interfaces will be setup and configured
> with an IP address.
> Which was done by a lot of shell scripts in SLES11 before.
>
>> I really don't  know, but its presence might contribute to our current
>> problems.
> Which problems?
> I only know about the interface renaming discussions, but this has
> nothing to do with wicked.
>
>> Do I need to take a training course to keep my Ethernet adapter and
>> IPtables script working?
> Do you had any issues in this regard with Beta1 - Beta3?
> Your interfaces are still the same as with SLES11: YaST2 and
> the config files in /etc/sysconfig/network.
>
> I have the feeling you are mixing up several things which
> are not connected.
>