From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>
Subject: Re: [GIT PULL v2 00/15] Second Round of IPVS Updates for v3.18
Date: Thu, 18 Sep 2014 11:03:31 +0200 [thread overview]
Message-ID: <20140918090331.GA24111@salvia> (raw)
In-Reply-To: <1410999961-7975-1-git-send-email-horms@verge.net.au>
On Thu, Sep 18, 2014 at 09:25:46AM +0900, Simon Horman wrote:
> Hi Pablo,
>
> please consider these IPVS updates for v3.18.
>
> I hope that v2 of this pull request addresses the issues you raised
> in v1. In particular "ipvs: use correct address family in scheduler logs"
> patch consolidates what was previously 7 patches. And I have provided
> a longer description: I hope the tone is closer to what you need.
>
> This pull requests makes the following changes:
>
> * Add simple weighted fail-over scheduler.
> - Unlike other IPVS schedulers this offers fail-over rather than load
> balancing. Connections are directed to the appropriate server based
> solely on highest weight value and server availability.
> - Thanks to Kenny Mathis
>
> * Support IPv6 real servers in IPv4 virtual-services and vice versa
> - This feature is supported in conjunction with the tunnel (IPIP)
> forwarding mechanism. That is, IPv4 may be forwarded in IPv6 and
> vice versa.
> - The motivation for this is to allow more flexibility in the
> choice of IP version offered by both virtual-servers and
> real-servers as they no longer need to match: An IPv4 connection from an
> end-user may be forwarded to a real-server using IPv6 and vice versa.
> - Further work need to be done to support this feature in conjunction
> with connection synchronisation. For now such configurations are
> not allowed.
> - This change includes update to netlink protocol, adding a new
> destination address family attribute. And the necessary changes
> to plumb this information throughout IPVS.
> - Thanks to Alex Gartrell and Julian Anastasov
>
> The following changes since commit 0bbe80e571c7b866afd92a98edd32a969467a7a9:
>
> netfilter: masquerading needs to be independent of x_tables in Kconfig (2014-09-12 09:40:18 +0200)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git tags/ipvs2-for-v3.18
Pulled, thanks a lot Simon.
prev parent reply other threads:[~2014-09-18 9:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 0:25 [GIT PULL v2 00/15] Second Round of IPVS Updates for v3.18 Simon Horman
2014-09-18 0:25 ` [PATCH 01/15] ipvs: Add simple weighted failover scheduler Simon Horman
2014-09-18 0:25 ` [PATCH 02/15] ipvs: Add destination address family to netlink interface Simon Horman
2014-09-18 0:25 ` [PATCH 03/15] ipvs: Supply destination addr family to ip_vs_{lookup_dest,find_dest} Simon Horman
2014-09-18 0:25 ` [PATCH 04/15] ipvs: Pass destination address family to ip_vs_trash_get_dest Simon Horman
2014-09-18 0:25 ` [PATCH 05/15] ipvs: Supply destination address family to ip_vs_conn_new Simon Horman
2014-09-18 0:25 ` [PATCH 06/15] ipvs: prevent mixing heterogeneous pools and synchronization Simon Horman
2014-09-18 0:25 ` [PATCH 07/15] ipvs: Pull out crosses_local_route_boundary logic Simon Horman
2014-09-18 0:25 ` [PATCH 08/15] ipvs: Pull out update_pmtu code Simon Horman
2014-09-18 0:25 ` [PATCH 09/15] ipvs: Add generic ensure_mtu_is_adequate to handle mixed pools Simon Horman
2014-09-18 0:25 ` [PATCH 10/15] ipvs: support ipv4 in ipv6 and ipv6 in ipv4 tunnel forwarding Simon Horman
2014-09-18 0:25 ` [PATCH 11/15] ipvs: address family of LBLC entry depends on svc family Simon Horman
2014-09-18 0:25 ` [PATCH 12/15] ipvs: address family of LBLCR " Simon Horman
2014-09-18 0:25 ` [PATCH 13/15] ipvs: use correct address family in scheduler logs Simon Horman
2014-09-18 0:26 ` [PATCH 14/15] ipvs: use the new dest addr family field Simon Horman
2014-09-18 0:26 ` [PATCH 15/15] ipvs: Allow heterogeneous pools now that we support them Simon Horman
2014-09-18 9:03 ` Pablo Neira Ayuso [this message]
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=20140918090331.GA24111@salvia \
--to=pablo@netfilter.org \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=wensong@linux-vs.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;
as well as URLs for NNTP newsgroup(s).