[opensuse-factory] Introducing wicked
Presenting wicked network configuration ======================================= This is the first public release of wicked, an experimental framework for network configuration. You may ask, don't we have enough of those already? Don't we have NetworkManager, connman, netcf, and a few more? The point I started from was the desire to unify what is usually provided through the traditional ifup script kudzu, with some of the more desktop oriented services provided by facilities like NetworkManager. I also wanted to move towards a more powerful set of functionality written in C, which is able to subsume functionality provided by ifconfig, ip(8), brctl, vconfig, ethtool, etc, and be able to drive these through an extensible XML representation of the network configuration. Kind of the Grand Unified Theory of network configuration :-) Right now, this implementation uses a daemon service and a command line utility. These two communicate securely via a local UNIX socket, allowing the server to validate the client's user id. The server offers a REST interface to various aspects of network configuration. The client application uses REST calls to retrieve interface configuration and status, or to reconfigure interfaces. The path space used by the API can be extended to cover other aspects of network configuration as well, such as reading, writing and restoring the resolv.conf file. After having hacked on this for a while, I want to release this to the community for feedback. If you're interested in finding out more, you will find a README and several manpages in the source code, which is available from http://gitorious.org/wicked Regards, Olaf Kirch <okir@suse.de> -- Neo didn't bring down the Matrix. SOA did. (soafacts.com) -------------------------------------------- Olaf Kirch - Director Server (okir@novell.com) SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, 25 Nov 2010, Olaf Kirch wrote:
Presenting wicked network configuration =======================================
This is the first public release of wicked, an experimental framework for network configuration.
You may ask, don't we have enough of those already? Don't we have NetworkManager, connman, netcf, and a few more?
The point I started from was the desire to unify what is usually provided through the traditional ifup script kudzu, with some of the more desktop oriented services provided by facilities like NetworkManager. I also wanted to move towards a more powerful set of functionality written in C, which is able to subsume functionality provided by ifconfig, ip(8), brctl, vconfig, ethtool, etc, and be able to drive these through an extensible XML representation of the network configuration.
Kind of the Grand Unified Theory of network configuration :-)
Right now, this implementation uses a daemon service and a command line utility. These two communicate securely via a local UNIX socket, allowing the server to validate the client's user id.
The server offers a REST interface to various aspects of network configuration. The client application uses REST calls to retrieve interface configuration and status, or to reconfigure interfaces. The path space used by the API can be extended to cover other aspects of network configuration as well, such as reading, writing and restoring the resolv.conf file.
After having hacked on this for a while, I want to release this to the community for feedback.
If you're interested in finding out more, you will find a README and several manpages in the source code, which is available from http://gitorious.org/wicked
And you provide packages in the open build service project home:okir:XXXX or elsewhere? Richard. -- Richard Guenther <rguenther@suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 25 November 2010 17:31:28 Richard Guenther wrote:
And you provide packages in the open build service project home:okir:XXXX or elsewhere?
So far, I have built neither. MGE was kind enough to contribute a spec file, so that is coming soon as well... Olaf -- Neo didn't bring down the Matrix. SOA did. (soafacts.com) -------------------------------------------- Olaf Kirch - Director Server (okir@novell.com) SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2010-11-25 T 17:56 +0100 Olaf Kirch wrote:
On Thursday 25 November 2010 Richard Guenther wrote:
And you provide packages in the open build service project home:okir:XXXX or elsewhere?
So far, I have built neither. MGE was kind enough to contribute a spec file, so that is coming soon as well...
First shot is at: home:mge1512:tools/wicked Currently building, ... Feel free to copy elsewhere:-) so long MgE -- Matthias G. Eckermann Senior Product Manager - SUSE® Linux Enterprise - Server Product Line Phone: +49 30 44315731 - Mobile: +49 179 2949448 - E-Mail: mge@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* Olaf Kirch <okir@suse.de> [2010-11-25 17:26]:
Presenting wicked network configuration =======================================
This is the first public release of wicked, an experimental framework for network configuration.
You may ask, don't we have enough of those already? Don't we have NetworkManager, connman, netcf, and a few more?
The point I started from was the desire to unify what is usually provided through the traditional ifup script kudzu, with some of the more desktop oriented services provided by facilities like NetworkManager. I also wanted to move towards a more powerful set of functionality written in C, which is able to subsume functionality provided by ifconfig, ip(8), brctl, vconfig, ethtool, etc, and be able to drive these through an extensible XML representation of the network configuration.
Kind of the Grand Unified Theory of network configuration :-)
Right now, this implementation uses a daemon service and a command line utility. These two communicate securely via a local UNIX socket, allowing the server to validate the client's user id.
The server offers a REST interface to various aspects of network configuration. The client application uses REST calls to retrieve interface configuration and status, or to reconfigure interfaces. The path space used by the API can be extended to cover other aspects of network configuration as well, such as reading, writing and restoring the resolv.conf file.
After having hacked on this for a while, I want to release this to the community for feedback.
If you're interested in finding out more, you will find a README and several manpages in the source code, which is available from http://gitorious.org/wicked
Will the server interface be public and stable allowing for different client implementations e.g. a GUI? Why are you using a sever-client design rather than a library? It looks a bit similar in scope to http://hub.opensolaris.org/bin/view/Project+brussels/ which has made network configuration (and interfacing with it) much more pleasant on the Solaris platform. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
El 25/11/10 14:05, Guido Berhoerster escribió:
Why are you using a sever-client design rather than a library?
not having to provide an stable API/ABI might be a good reason ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Donnerstag, 25. November 2010 17:25:58 schrieb Olaf Kirch:
Presenting wicked network configuration =======================================
This is the first public release of wicked, an experimental framework for network configuration.
You may ask, don't we have enough of those already? Don't we have NetworkManager, connman, netcf, and a few more?
Hi Olaf, there exists a network management tool called wicd. To avoid confusion I suggest to choose another name for the new project. Some suggestions: ned ncd netcond okid ;-) -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG, Putzbrunner Str. 71, 81739 München, Germany Tel: +49 89 99 34 110, Fax: +49 89 99 34 1199 mhilzinger@linuxnewmedia.de - http://www.linuxnewmedia.de ---------------------------------------------------------- Linux New Media, the Pulse of Open Source: Lawrence, KS - Málaga Manchester - München - São Paulo - Warszawa ---------------------------------------------------------- Sitz der Gesellschaft: Putzbrunner Str. 71, 81739 München Amtsgericht München: HRB 129161 Vorstand: Brian Osborn, Hermann Plank Aufsichtsratsvorsitzender: Rudolf Strobl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Cristian Rodríguez -
Guido Berhoerster -
Marcel Hilzinger -
Matthias G. Eckermann -
Olaf Kirch -
Richard Guenther