From mboxrd@z Thu Jan  1 00:00:00 1970
From: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Subject: Re: a work for lxc monitor network interface
Date: Wed, 18 Dec 2013 14:16:22 -0600
Message-ID: <20131218201622.GA25926@tp>
References: <52B15E7B.8080009@huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Content-Disposition: inline
In-Reply-To: <52B15E7B.8080009-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/containers>,
	<mailto:containers-request-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/containers/>
List-Post: <mailto:containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
List-Help: <mailto:containers-request-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/containers>,
	<mailto:containers-request-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org?subject=subscribe>
Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
To: Libo Chen <clbchenlibo.chen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: hadi-fAAogVwAN2Kw5LPnMra/2Q@public.gmane.org, containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, karma-sWkBwLop/e8RbODiWk9XIg@public.gmane.org, takano-ryousei-XSdjUN4cZ6fPDbFq/vQRIQ@public.gmane.org, caglar-mM0DFpta8ko@public.gmane.org, dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org, "zhangwei(Jovi)" <jovi.zhangwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>, stgraber-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org, james.hunt-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org
List-Id: containers.vger.kernel.org

Quoting Libo Chen (clbchenlibo.chen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org):
> Hello LXC experts,
> 
> 	lxc tool can set network interface by config, but it is static.
> In some scene, the network interface will be dynamic created on the host
> and need be shared to container, but it is not suitable to do by hand,
> so lxc can not work for it.
> 
> 	I also know lxc_user_nic() can only do a part of work, but we have
> two more work:
> 1. grasp the netlink/uevent message about network interface online
> 2. config interface attached to container ip address .
> 
> so it can not fully meet my requirements.
> 
> 	I want there is a monitor can work for network interface hotplug.
> 
> 1. read config form config file, it describe monitor which network interface
>    and what's the network configuration
> 2. grasp the netlink/uevent message about network interface online on the host
> 3. create veth pair, put veth attach to container and bridge
> 4. config the veth attached to container ipaddr
> 
> 			
>          	          netlink  create veth pair
> monitor ---> read config  -------> veth0 attach to container --> config ipaddr
> 				   veth1 attach to bridge
> 
> monitor may be the lxc-start or a child forked by lxc-start.
> 
> 
>  Is this reasonable?  If so, I'd like to do it.

I'm not quite clear on what you're trying to do, but it sounds like you
could use a udev rule, triggered on the nic creation, and use lxc-device
from inside that rule to attach the nic to the container.