Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 97A27200BB4 for ; Tue, 1 Nov 2016 10:43:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 962AD160AF7; Tue, 1 Nov 2016 09:43:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D6E73160AE5 for ; Tue, 1 Nov 2016 10:42:59 +0100 (CET) Received: (qmail 96752 invoked by uid 500); 1 Nov 2016 09:42:59 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 96735 invoked by uid 99); 1 Nov 2016 09:42:58 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2016 09:42:58 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 8F250E0A05; Tue, 1 Nov 2016 09:42:58 +0000 (UTC) From: prashanthvarma To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1577: CLOUDSTACK-9321 : Multiple Internal LB rules (more t... Content-Type: text/plain Message-Id: <20161101094258.8F250E0A05@git1-us-west.apache.org> Date: Tue, 1 Nov 2016 09:42:58 +0000 (UTC) archived-at: Tue, 01 Nov 2016 09:43:00 -0000 Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1577 @jburwell @rhtyd Ok, we will rebase the PR, and let you know here. Moreover, we can re-run the added Marvin tests and share the results after the re-base. Generally, we have two commits in a PR, one for dev and one for test (Marvin). Let me know, if you want us to do this in a different way. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---