From dev-return-112567-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Tue Feb 26 18:49:16 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 28C4218062C for ; Tue, 26 Feb 2019 19:49:15 +0100 (CET) Received: (qmail 661 invoked by uid 500); 26 Feb 2019 18:49:14 -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 629 invoked by uid 99); 26 Feb 2019 18:49:13 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2019 18:49:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 83CC31822C3 for ; Tue, 26 Feb 2019 18:49:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.798 X-Spam-Level: * X-Spam-Status: No, score=1.798 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id AQOwrVBnTbX7 for ; Tue, 26 Feb 2019 18:49:12 +0000 (UTC) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 706BB623FF for ; Tue, 26 Feb 2019 18:41:40 +0000 (UTC) Received: by mail-wr1-f41.google.com with SMTP id w2so15099638wrt.11 for ; Tue, 26 Feb 2019 10:41:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=O4Fq0wULSAdlbP4C6IAd32i2S3cTT+VPIqzS0KRfy3U=; b=Gq6EqBoaGkW101D3o93izWPoJTNZlFCHwbP7n4B8mYc5nPc/hBrYPOypO+W7pk47WM k/UvAhILy2T6XuzVxJ+CFvfSRQw67doLGlz+jQWWA8/h8n4bn+tUJVggRijxAVoPwHuS dKDUCj+6G5HR6Gp3UI8yiLXXBsmMXp1+cSKXFn0LraLeAD/LtlATXa0Xs2un5diyboxv /03E72CzfVSsuU4mHq2H3mkUxVrHAwalTwPNX5IW1aaP0a5OazaOXOldLOWdXWQx0HD0 waqR2EDhzcMtIGj3OZnSKL3MdLI36BEh0+F2LY9wtaBjb0//nXk6o/ZIjuKYq3k0+jNy 7Bog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=O4Fq0wULSAdlbP4C6IAd32i2S3cTT+VPIqzS0KRfy3U=; b=ewDaKR7AvlE1iuufh0/xdFbSVpUM64L1nF8aoIkRwrvNeOLLldKZoeT+ze0WNnn+VE 3AxIRsquy1yDSyvLn5ulfK+aqIozQYI1PVudFxfwKGElHr5nAwmz4nfRbCFHL7/pCUaE oem+x3HDGkrHfCYmgfFy7Ypk5xvZGbMFzrw/3rKhO73Vrh2hjz73wpYkoyHlq202FHwY 9rlFFL5b0h7vUbyLIxTPBDsGkq7Bt3qSYP1ze7MIBE5UVVJaz+zjP6nlvdGYHAK5wTyi EAuacauuH+leUAzQw7JgDOBUUyLsf6mhit6wx0zWx3XlnHtmXcm6mPfXYhZUBsX0E+zf nHmA== X-Gm-Message-State: AHQUAuZLw3Oplx2AH85AKepnt+S5eWUX3fHVSpc/tboz23PaPpxNtZo4 skJOhY5K8QhcueLfaJk6sr5Hrb4x7xi8FdwRrrhWgEuo X-Google-Smtp-Source: AHgI3IbhuTb3GjeqZrNOpkskeT1YQ1FHJNoO//P6qKbllkYwGbVzUyIbabCH3yx/qEM+KapGiAOttBMX4U8/kg73w6s= X-Received: by 2002:a5d:4710:: with SMTP id y16mr17379886wrq.305.1551206499707; Tue, 26 Feb 2019 10:41:39 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Suresh Kumar Anaparti Date: Wed, 27 Feb 2019 00:11:28 +0530 Message-ID: Subject: Re: [DISCUSS] event.outcome information To: dev Content-Type: multipart/alternative; boundary="000000000000636f950582d06863" --000000000000636f950582d06863 Content-Type: text/plain; charset="UTF-8" Hi Nikos, Most of the events are scheduled and intercepted from the beginning of API cmd execution till its completion. The success or failure is indicated in the event description on that event completion. For example: +-----+---------------+-----------+-----------------------------------------------------------------------------------------+ | id | type | state | description | +-----+---------------+-----------+-----------------------------------------------------------------------------------------+ | 568 | VM.CREATE | Scheduled | starting Vm. Vm Id: 317cd9ef-28c5-4604-bd69-484a90d1b964Vm Name:testvm | | 569 | VM.CREATE | Started | starting Vm. Vm Id: 317cd9ef-28c5-4604-bd69-484a90d1b964 Vm Name: testvm | | 570 | VM.CREATE | Completed | Error while starting Vm. Vm Id: 317cd9ef-28c5-4604-bd69-484a90d1b964 Vm Name: testvm | +-----+---------------+-----------+-----------------------------------------------------------------------------------------+ and some events (without API cmds) are explicitly mentioned, ex: USER.LOGIN. The login event is not intercepted as above. It is explicitly marked as Completed upon login success. The failed logon can also be mentioned in the similar way. The outcomes of the events from API cmds can be retrieved from the job status. May be the events with new final states: Completed_Success(or Done) and Completed_Failure(or Failed) - without DB upgrade [or] a new boolean outcome flag (invalid for other states except Completed) can indicate the actual outcome. Any particular use cases for event.outcome information? - Suresh On Tue, Feb 26, 2019 at 4:36 AM Nikolaos Dalezios wrote: > Hi all! > While reading the code on the events, I realize that there is no > information for failed events. eg a failed logon. > Is this for real or I am missing something? > If an event.outcome information is actually missing do you think that there > is a point to include this on a future release? > > Thank you > > Nikos Dalezios > --000000000000636f950582d06863--