This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Proposal: vif-local

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Proposal: vif-local
From: "W. Michael Petullo" <mike@xxxxxxxx>
Date: Fri, 6 May 2011 12:06:02 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 06 May 2011 10:07:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1304671321.26692.117.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110505171542.GA17115@xxxxxxxxx> <1304671321.26692.117.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
>> For site-specific reasons, I use the network-route/vif-route scripts. I
>> have found that we need to maintain a few custom firewall rules in order
>> to make things operate in an acceptable manner. I'd like to see a place
>> to put such scripts and any other site-specific setup related to bringing
>> up a vif. Keeping this separate from vif-route is useful so that the
>> installed scripts may be kept unmodified.
>> What I have come up with is vif-local, a script that lives in
>> /etc/xen/scripts. I modified vif-route to call vif-local right before
>> it logs "Successful..."
> I think it would be better to be more general and support a vif-post.d
> style directory which can contain scripts all of which are called (with
> a defined set of paramters/env variables).
> Not sure if we want vif-{route,bridge,etc}-post.d or not, perhaps that's
> overkill. Using -post.d leaves open the option to add -pre.d in the
> future as necessary.

I have attached a patch against Xen 4.1.0 that implements a vif-post.d
system. I only support the Linux hotplug case at this point.



Attachment: xen-4.1.0-local-vif-scripts.patch
Description: Text document

Xen-devel mailing list