On Monday 21 November 2011 19:12:36 Federico Simoncelli wrote: > ----- Original Message ----- > > From: "Doron Fediuck" <dfedi...@redhat.com> > > To: us...@ovirt.org > > Cc: "VDSM Project Development" <vdsm-devel@lists.fedorahosted.org> > > Sent: Monday, November 21, 2011 3:13:20 PM > > Subject: Re: [Users] ovirt-node on Gentoo > > > > On Monday 21 November 2011 16:00:26 Doron Fediuck wrote: > > > On Monday 21 November 2011 14:49:43 Mike Burns wrote: > > > > On Mon, 2011-11-21 at 07:42 -0500, Ayal Baron wrote: > > > > > > > > > > Actually we're thinking about NetworkManager, not netcf. > > > > > > > > Does NetworkManager have an api or library level package that > > > > doesn't > > > > pull in all the UI bits? ovirt-node does not currently include > > > > NetworkManager packages at all and we don't want to pull anything > > > > that > > > > is going to pull in X or another UI. > > > > > > > > Mike > > > > > > +1 > > > NetworkManager pulls in gnome, while it's net being used in many > > > cases, > > > especially in servers. > > > As for netcf in Gentoo, there's not substantial support which will > > > make > > > it easy to work with. > > > > > Clarifying my cryptic typos- netcf has no proper support in Gentoo. > > It will be helpful if vdsm takes a more generic approach. > > Configuring the network is a difficult task. Taking a more generic > approach means facing again the problems that NetworkManager found > and resolved in the past. > > Do you know any other (mature) project that is trying to fill in the > gaps between the network configurations in the various distro? > I'm worried that taking a generic approach we'll end up creating a > small NetworkManager clone with a smaller scope (usable only for the > vdsm tasks). > > We could use our effort to improve NetworkManager where it's lacking > of functionality/packaging. For example I've been waiting for the bridge > support for a long time, I hope to see it soon. > Federico, Since I personally know the one who wrote most of the vdsm-ovirt/rhel integration bugs (not the code, just the bugs...) I'm fully aware of network complexity, and the impact of supporting several distro's.
This is exactly why I asked for a /generic/ approach, which will not pull in numerous packages which are distro or desktop-env specific. Having said that, I can tell you that last night I did some more investigations in Gentoo, and I was pleasantly surprised to see the following: emerge -DuNavt --with-bdeps=y --keep-going net-misc/networkmanager These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild N ] net-misc/networkmanager-0.8.4.0-r2 USE="bluetooth ppp -avahi -connection-sharing -dhclient -dhcpcd -doc -gnutls -nss -resolvconf" 1,634 kB [ebuild N ] net-misc/modemmanager-0.4 USE="policykit -doc -test" 435 kB Total: 2 packages (2 new), Size of downloads: 2,069 kB This means that network manager no longer pulls gnome-related packages, which is very good news. If this is the case in other distro's I think we can converge on this solution. I guess we only need some input from Suse / Ubuntu people to see if it works for them as well. -- /d "This message will self destruct in the future. Or not." _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
