From issues-return-12037-apmail-airavata-issues-archive=airavata.apache.org@airavata.apache.org Fri Sep 15 00:37:04 2017 Return-Path: X-Original-To: apmail-airavata-issues-archive@minotaur.apache.org Delivered-To: apmail-airavata-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4C4AE1AB16 for ; Fri, 15 Sep 2017 00:37:04 +0000 (UTC) Received: (qmail 62058 invoked by uid 500); 15 Sep 2017 00:37:04 -0000 Delivered-To: apmail-airavata-issues-archive@airavata.apache.org Received: (qmail 61993 invoked by uid 500); 15 Sep 2017 00:37:04 -0000 Mailing-List: contact issues-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@airavata.apache.org Received: (qmail 61975 invoked by uid 99); 15 Sep 2017 00:37:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Sep 2017 00:37:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 452B7C5A31 for ; Fri, 15 Sep 2017 00:37:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Qe6KIntlEYbM for ; Fri, 15 Sep 2017 00:37:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 680265FCB9 for ; Fri, 15 Sep 2017 00:37:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C08C1E0EF4 for ; Fri, 15 Sep 2017 00:37:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4723225387 for ; Fri, 15 Sep 2017 00:37:00 +0000 (UTC) Date: Fri, 15 Sep 2017 00:37:00 +0000 (UTC) From: "Eroma (JIRA)" To: issues@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRAVATA-2518) Gateway usage reporting is set to gateway ID but it need to have an extension MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2518: ---------------------------- Description: When gateway usage reporting is enabled in the SciGaP portal for each resource, in individual gateway need to add the "Gateway Id for Usage Reporting" gateways have added the gateway ID for each but just the gateway ID is not sufficient for correct reporting. It need to have an extension. We should provide the gateway admins with a comment to mention that a extension is required. If not this will be forgotten and there is no way to validate either. It would be ideal if a check can be enforced to check the existing of an extension. similar to checking email format. was: 1. When gateway usage reporting is enabled in the SciGaP portal for each resource, in individual gateway need to add the "Gateway Id for Usage Reporting" gateways have added the gateway ID for each but just the gateway ID is not sufficient for correct reporting. It need to have an extension. We should provide the gateway admins with a comment to mention that a extension is required. If not this will be forgotten and there is no way to validate either. It would be ideal if a check can be enforced to check the existing of an extension. similar to checking email format. > Gateway usage reporting is set to gateway ID but it need to have an extension > ----------------------------------------------------------------------------- > > Key: AIRAVATA-2518 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2518 > Project: Airavata > Issue Type: Bug > Components: Airavata System > Affects Versions: 0.18 > Reporter: Eroma > Assignee: Marcus Christie > > When gateway usage reporting is enabled in the SciGaP portal for each resource, in individual gateway need to add the "Gateway Id for Usage Reporting" > gateways have added the gateway ID for each but just the gateway ID is not sufficient for correct reporting. It need to have an extension. We should provide the gateway admins with a comment to mention that a extension is required. If not this will be forgotten and there is no way to validate either. > It would be ideal if a check can be enforced to check the existing of an extension. similar to checking email format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)