From: "W. Michael Petullo" <mike@flyn.org>
To: xen-devel@lists.xensource.com
Subject: Proposal: vif-local
Date: Thu, 5 May 2011 12:15:43 -0500 [thread overview]
Message-ID: <20110505171542.GA17115@imp.local> (raw)
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..."
Would it be possible to modify vif-route, vif-bridge, etc. to operate
in this manner? This has been discussed briefly on the list before,
but I had not yet seen a solution.
--
Mike
:wq
next prev reply other threads:[~2011-05-05 17:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 7:04 New 4.0.2 and 4.1.1 release candidates Keir Fraser
2011-05-24 7:24 ` Keir Fraser
2011-05-05 17:15 ` W. Michael Petullo [this message]
2011-05-06 8:42 ` Proposal: vif-local Ian Campbell
2011-05-06 17:06 ` W. Michael Petullo
2011-05-09 8:45 ` Ian Campbell
2011-05-09 17:10 ` W. Michael Petullo
2011-05-10 8:02 ` Ian Campbell
2011-05-10 16:06 ` W. Michael Petullo
2011-05-10 16:12 ` Ian Campbell
2011-05-24 14:17 ` Re: New 4.0.2 and 4.1.1 release candidates W. Michael Petullo
2011-05-24 15:49 ` Keir Fraser
2011-05-24 17:31 ` Proposal: vif-local [and 1 more messages] Ian Jackson
2011-05-24 17:51 ` Ian Campbell
2011-05-25 9:45 ` Ian Jackson
2011-05-24 16:13 ` New 4.0.2 and 4.1.1 release candidates Olaf Hering
2011-05-24 17:58 ` Keir Fraser
2011-05-24 18:25 ` Olaf Hering
2011-05-24 20:04 ` Keir Fraser
2011-05-26 8:36 ` George Dunlap
2011-05-26 9:09 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110505171542.GA17115@imp.local \
--to=mike@flyn.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.