Mailing-List: contact notifications-help@libcloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@libcloud.apache.org
Date: Thu, 17 Jul 2014 20:07:05 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: notifications@libcloud.apache.org
Message-ID: <JIRA.12727372.1405442368521.65644.1405627625789@arcas>
In-Reply-To: <JIRA.12727372.1405442368521@arcas>
References: <JIRA.12727372.1405442368521@arcas>
Subject: [jira] [Commented] (LIBCLOUD-595) Support session affinity in GCE
 Load Balancer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LIBCLOUD-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065476#comment-14065476 ] 

ASF GitHub Bot commented on LIBCLOUD-595:
-----------------------------------------

GitHub user verb opened a pull request:

    https://github.com/apache/libcloud/pull/341

    [LIBCLOUD-595] Support GCE LB session affinity

    Add support for sessionAffinity to the GCE Load Balancer driver.
    sessionAffinity has the effect of causing clients to "stick" to a
    particular backend server.
    
    Also, trivial documentation fixes:
    
      * resolve ambiguous type specification in create_balancer
      * fix typo in development doc
    
    https://issues.apache.org/jira/browse/LIBCLOUD-595
    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/verb/libcloud LIBCLOUD-595_session_affinity

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/341.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #341
    
----
commit fc16778166442c68211bfeaccf12f1ada51cc6b4
Author: Lee Verberne <verb@google.com>
Date:   2014-07-10T20:31:34Z

    [LIBCLOUD-595] Support GCE LB session affinity
    
    Add support for sessionAffinity to the GCE Load Balancer driver.
    sessionAffinity has the effect of causing clients to "stick" to a
    particular backend server.
    
    Also, trivial documentation fixes:
    
      * resolve ambiguous type specification in create_balancer
      * fix typo in development doc

----


> Support session affinity in GCE Load Balancer
> ---------------------------------------------
>
>                 Key: LIBCLOUD-595
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-595
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: LoadBalancer
>            Reporter: Lee Verberne
>            Priority: Minor
>
> The Compute Engine network load balancer supports a sessionAffinity parameter that modifies the default algorithm to cause clients to prefer a particular member node.


--
This message was sent by Atlassian JIRA
(v6.2#6252)