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 63908200B20 for ; Wed, 11 May 2016 23:46:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 62335160A18; Wed, 11 May 2016 21:46:26 +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 A3301160A17 for ; Wed, 11 May 2016 23:46:25 +0200 (CEST) Received: (qmail 23218 invoked by uid 500); 11 May 2016 21:46:24 -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 23191 invoked by uid 99); 11 May 2016 21:46:24 -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; Wed, 11 May 2016 21:46:24 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 5A1CFDFC71; Wed, 11 May 2016 21:46:24 +0000 (UTC) From: dmabry To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Apply static routes on change to master s... Content-Type: text/plain Message-Id: <20160511214624.5A1CFDFC71@git1-us-west.apache.org> Date: Wed, 11 May 2016 21:46:24 +0000 (UTC) archived-at: Wed, 11 May 2016 21:46:26 -0000 Github user dmabry commented on the pull request: https://github.com/apache/cloudstack/pull/1472#issuecomment-218600092 LGTM. We tested this in our Lab on HW and all static routes on each PG came up as expected. --- 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. ---