Wicked A Network Manager Olaf Kirch

Transcription

1 Wicked A Network Manager Olaf Kirch Director SUSE Linux Enterprise [email protected]

2 2 Agenda Why Wicked!? What we want to achieve What Wicked can do today/tomorrow Architecture Wicked little intro

3 Why Wicked!?

4 4 Why Wicked? Basically because we went from this... Mail Usenet UUCP Expensive Modem

5 5 Why Wicked? to something like this. Converged Networks, Network Virtualization, Storage Networks,... systemd dracut libvirt openvswitch udev netfilter and bridge filtering dhcp zeroconf radvd ibft WPA IPv4 IPv6 LLDP Ether VLAN qeth WLAN bond pppoe bridge various kludges Modem x FCoE SRIOV PV NICs IB WiMax GSM

6 6 How Can I set up a bridge using two bonded NICs as one of its ports?

7 7 How Can I set up a bridge using two bonded NICs as one of its ports?... conveniently check routes, addresses, link-speed... and perhaps hardware offload settings on my Ethernet NIC?

8 8 How Can I set up a bridge using two bonded NICs as one of its... conveniently ports? check routes, addresses, link-speed... and perhaps hardware offload settings on my Ethernet NIC?... reconfigure a bonding device without bringing it down?

9 9 How Can I set up a bridge using two bonded NICs as one of its... conveniently ports? check routes, addresses, link-speed... and perhaps hardware offload settings on my Ethernet NIC?... reconfigure a bonding device without bringing it down?... configure a wireless connection with WPA2 and DHCP?

10 10 How Can I set up a bridge using two bonded NICs as one of its... conveniently ports? check routes, addresses,... configure a link-speed... wireless connection and perhaps with hardware offload WPA2 and DHCP? settings on my Ethernet NIC?... reconfigure a bonding device without bringing it down?... disable IPv6 on my DMZ Ethernet Interface?

11 11 Today's Networking Highly Dynamic Virtualized/Software-Defined Converged

12 That Was the Why...Now the What

13 13 What We Want To Achieve Goal Cope with increasingly complex configurations Target Audience Data Center and End Users Positioning Network configuration is a service Usability Make adoption as smooth as possible

14 14 What We Want To Achieve Technical Attributes Architecture-independent Extensible Needs small footprint (initrd use) React flexibly to network changes Broadcast event notifications interface comes up, IP address assigned, routing changed

15 15 Where Are We? Wicked is in SUSE Linux Enterprise 12 GA SUSE Linux Enterprise Server defaults to using wicked SUSE Linux Enterprise Desktop defaults to using NetworkManager

16 16 Smooth Transition What's Changed?! For end-users nothing really, so relax :D Sysconfig ifcfg-* style configuration In place for backward compatibility Converted to an internal format that is structured, extensible and more powerful Internal format to be exposed to administrators/users by SP1 /sbin/{ifup,ifdown,ifstatus,ifprobe} scripts wrap wicked commands Wicked supports the same functionality as SUSE Linux Enterprise Server 11 Invasive, yes Disruptive, no

17 17 What Wicked Can Do Today Device types Ethernet, VLAN, Bridging, Bonding, Infiniband, Loopback tun, tap, ipip, sit, gre, dummy macvlan, macvtap hsi, qeth, iucv wireless (one wpa-psk/eap network) Address configuration: static, dhcp4, dhcp6, IPv4 zeroconf Hot-plugging

18 18 What Wicked Will Do Tomorrow In implementation better tunneling (esp. IPv6 tunneling) On the roadmap: Documentation improvements pppoe (lower priority), ppp/umts [SP1] On the radar: Improve integration with openvswitch Network namespace awareness and virtual ethernet support Improve wireless support

19 19 Architecture External Helpers static config client (wicked) dhcp4 Config Policies Status dhcp6 policies policy engine master daemon (wickedd) auto4 Events Setup wpa Kernel...

20 A Wicked Little Intro

21 21 Network Service Wicked is a systemd thing! lots of systemd unit files network.service Start and stop The Network wicked.service Start and stop the networking the wicked way wickedd.service Control all wicked daemons Don't Mention the Interface Name War.

22 24 Restarting the Network systemctl restart network.service restarts the network interface configuration systemctl restart wickedd.service restarts wicked daemons without reconfiguring the network interfaces

23 25 Debugging Options Command line wicked --debug <all most help...> Enables debug level and sets filters by wicked facilities, e.g.: "all,-events,-socket,-objectmodel,-xpath,-xml,-dbus" Configuration file In /etc/wicked/common.xml, add <debug>true</debug>

24 26 Diagnosis Testing DHCP availability /usr/lib/wicked/bin/wickedd-dhcp4 --test $IFNAME /usr/lib/wicked/bin/wickedd-dhcp6 --test $IFNAME Things to watch out for in IPv6 setups If your router advertises Managed configuration, make sure you have a (working) DHCP6 server running :-) Verify the information distributed via DHCP6 Collecting logs journalctl: journalctl -b -o short-iso > wicked.log

25 27 Time for a Demo!

26 Summary

27 33 Today's Networking Highly Dynamic Virtualized/Software-Defined Converged

28 34 Wicked Network Configuration Configuration Tools matching the pace of evolution Network Configuration as a Service Supporting both Data Centers and End Users

29 35 Try it Now part of SLES 12! Clone it Your Questions!?

30 36 Corporate Headquarters Maxfeldstrasse Nuremberg Germany (Worldwide) Join us on:

31 Unpublished Work of SUSE. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

32 38 Backup Slides

33 39 Implementation Decisions Client / Server model DBus Service (provided by a daemon) Layered architecture providing separate DBus interfaces for hardware, netdev, address configuration, etc. Structured configuration files Sysconfig ifcfg- style for now, XML as internal representation Extensible Server can be extended with scripts NIS/dns/hostname updates