Default gateway support

[gentooboontoo]

Hello Walter,

If you're ok with the change, please pull this (Fix default gateway) in your repository... If quite ok, you could pull and fix.

Julien

[Don't mind and pull also our other former 5 commits; it will not change anything... I suppose when you forked you perhaps make some git-related mistakes which changed commit ids?]

[globalcitizen]

This change assumes that the user wishes to have a certain kind of network configuration - ie: non-DHCP.

In fact, we should support many types of network configuration, including DHCP.

The reason that DHCP is important is as follows.

When migrating certain types of guests (such as lxc-isolated server components, eg: database servers or web servers) between hosts, or managing a large number of guests, it makes sense to push (virtual) network configuration from the host in order to better facilitate migration and maintain config in one place. In contrast, throwing part of the config in to the guest and part of the config on to the host makes migration a real pain.

Some of the current features of the script (eth0 null config in /etc/conf.d/net) are designed to support this.

However, since we don't have any proper documentation or information on network setup yet, and I am not properly familiar with the strategy that lxc-create (and associated configuration files), libvirt, and other tools in the area are taking, I'm happy to make this change and revisit the network configuration at a later stage.

However, this is definitely only a preliminary change and needs to be revisited.

[globalcitizen]

Can't seem to make it merge ... I get # git pull https://github.com/gentooboontoo/lxc-gentoo.git b2273a05f447883d08842ee421308e48f8ce58a fatal: Couldn't find remote ref b2273a05f447883d08842ee421308e48f8ce58a

Let's leave it for now.

[globalcitizen]

There is some forward-looking info around network configuration stuff here: https://wiki.ubuntu.com/UDSProceedings/N/CloudInfrastructure#Make%20LXC%20ready%20for%20production

There's going to be a meeting on Skype next Thursday with the IBM kernel engineers on lxc and Ubuntu people - they are looking to see the remaining issues sorted in to a list and finalised for inclusion in to Ubuntu 'natty'. I have asked to eavesdrop on the meeting to learn what the direction of networking will be.

[gentooboontoo]

I agree with you but it was a temporary fix otherwise networking does not work at all without manual fix afterward. This change supported dhcp in some sense because we can directly set IP prompt with 'dhcp' instead of an IP but it is not sufficient (dhcpcd still missing). It was just a progressive (but not perfect I agree) enhancement of the current script while waiting lxc supports whole net configuration.

To sum up, for my work, I need DHCP but:

• we need to emerge dhcpcd but we can't if no network (circular issue!)
• When I manually emerge dhcp, dhcpcd does not work (Staling with "Waiting for carrier...")

At last, I think, we should support and use by default openrc and baselayout2 by considering them as stable. They are lxc-aware and some issues could be naturally resolved by them.

Problem? how to properly do all of that ... and with a neutral or gentoo way... (I hope lxc future developement will not be too ubuntu biased)

PS: I think your git command was wrong To merge a pull request, (see http://help.github.com/pull-requests/ , "Merging a Pull Request" at bottom) You could add locally my repository with:

git remote add gentooboontoo https://gentooboontoo@github.com/gentooboontoo/lxc-gentoo.git then to add my branch in local branch called gentooboontoo: git fetch gentooboontoo master:gentooboontoo

then you can make merges as usual.