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 36A7D200C92 for ; Mon, 12 Jun 2017 22:05:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 35435160BD9; Mon, 12 Jun 2017 20:05:04 +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 78D47160BCF for ; Mon, 12 Jun 2017 22:05:03 +0200 (CEST) Received: (qmail 68358 invoked by uid 500); 12 Jun 2017 20:05:02 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 68349 invoked by uid 99); 12 Jun 2017 20:05: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; Mon, 12 Jun 2017 20:05: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 56AE7CD41C for ; Mon, 12 Jun 2017 20:05:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id mP054sDORMig for ; Mon, 12 Jun 2017 20:05:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 19B095F36F for ; Mon, 12 Jun 2017 20:05: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 5EF71E01D8 for ; Mon, 12 Jun 2017 20:05: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 0881321938 for ; Mon, 12 Jun 2017 20:05:00 +0000 (UTC) Date: Mon, 12 Jun 2017 20:05:00 +0000 (UTC) From: "Alejandro Fernandez (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20853) Service Advisor - Allow Service to define its Advisor Type as Python or Java MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 12 Jun 2017 20:05:04 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20853: ----------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit f1ca09c03a2fe316129aa5623c675b62d3177112 > Service Advisor - Allow Service to define its Advisor Type as Python or Java > ---------------------------------------------------------------------------- > > Key: AMBARI-20853 > URL: https://issues.apache.org/jira/browse/AMBARI-20853 > Project: Ambari > Issue Type: Story > Components: service-advisor > Affects Versions: 3.0.0 > Reporter: Alejandro Fernandez > Assignee: Alejandro Fernandez > Fix For: trunk > > Attachments: AMBARI-20853.trunk.patch > > > See Epic AMBARI-20852 > First step is to allow a Service's metainfo.xml file to define what type of Service Advisor it uses, Python or Java. > For now, continue to call Python for all services since all services are not specifying which type to use (so defaults to Python) > If set to Java, will eventually call a class to invoke the existing Service Advisor in Python as a way to ensure compatibility. > If set to Python, continue to call the current script. > In both cases, we will continue to generate the services.json file. > Today, we call Stack Advisor on all services even if only one service is modified, so it's ok to hardcode a service name until the UI is able to provide that granularity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)