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 931FC200C3F for ; Wed, 8 Mar 2017 05:59:28 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9174C160B74; Wed, 8 Mar 2017 04:59:28 +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 CF894160B68 for ; Wed, 8 Mar 2017 05:59:27 +0100 (CET) Received: (qmail 75295 invoked by uid 500); 8 Mar 2017 04:59:26 -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 75284 invoked by uid 99); 8 Mar 2017 04:59:26 -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, 08 Mar 2017 04:59:26 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7ED34DFD9E; Wed, 8 Mar 2017 04:59:26 +0000 (UTC) From: anshul1886 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1278: CLOUDSTACK-9198: Virtual router gets deployed in dis... Content-Type: text/plain Message-Id: <20170308045926.7ED34DFD9E@git1-us-west.apache.org> Date: Wed, 8 Mar 2017 04:59:26 +0000 (UTC) archived-at: Wed, 08 Mar 2017 04:59:28 -0000 Github user anshul1886 commented on the issue: https://github.com/apache/cloudstack/pull/1278 @rafaelweingartner, Yes we can agree on those changes. But with additional description when the CallContext.current().getCallingAccount() call is made then it is setting the proper context which is global in nature and passed automatically to next method calls. --- 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. ---