From: Alex Gartrell <agartrell@fb.com>
To: <lvs-devel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Cc: <kernel-team@fb.com>
Subject: We've released a generic netlink python library -- gnlpy
Date: Wed, 20 May 2015 14:10:19 -0700 [thread overview]
Message-ID: <555CF83B.7040706@fb.com> (raw)
Hey everyone,
tl;dr; pure python generic netlink library with simple clients for ipvs
and taskstats here: https://github.com/facebook/gnlpy
At Facebook we rely upon ipvs for most of our layer-4 load balancing
needs. It's mostly worked pretty great for us. The standard way to
interact with ipvs is ipvsadm, which will use netlink sockets to make
rpc calls to the kernel (things like adding/remove services and real
servers). Because we run many, many instances of ipvs, we ended up
scripting this away with a separate program that shells out to ipvsadm.
The down side to this approach was that we had to format the arguments
and parse the result of the tool, which was kind of a pain.
Additionally, we'd sometimes get into a bad state where the exec would
fail or the binary wouldn't be there and the whole thing would kind of
break. To my knowledge this never caused any kind of large scale
incident, but it was an annoying thing to deal with.
At some point, we made some changes to ipvs (heterogenous pools) and we
were in the position of needing to roll a new ipvsadm binary to take
advantage of the functionality. That was fundamentally unappealing to
yours truly, so I hacked together gnlpy (Generic NetLink PYthon library)
instead. It's been in production for several months.
At some point thereafter, someone on the lvs-devel list mentioned
wanting to interact with ipvs through python and I made a vague
assurance that we'd open source this thing. Well here we are.
If you take a look at the code, you'll quickly notice that we haven't
gone through the trouble of implementing every RPC call for the families
we support and we certainly haven't gone through the trouble of
implementing every generic netlink family. We welcome your pull requests :)
--
Alex Gartrell <agartrell@fb.com>
next reply other threads:[~2015-05-20 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 21:10 Alex Gartrell [this message]
2015-05-20 23:33 ` We've released a generic netlink python library -- gnlpy Cong Wang
2015-05-21 14:52 ` Edward Cree
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=555CF83B.7040706@fb.com \
--to=agartrell@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox