Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9095177DD for ; Wed, 18 Mar 2015 05:02:39 +0000 (UTC) Received: (qmail 27638 invoked by uid 500); 18 Mar 2015 05:02:39 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 27573 invoked by uid 500); 18 Mar 2015 05:02:39 -0000 Mailing-List: contact dev-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 dev@ambari.apache.org Received: (qmail 27394 invoked by uid 99); 18 Mar 2015 05:02:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2015 05:02:39 +0000 Date: Wed, 18 Mar 2015 05:02:38 +0000 (UTC) From: "Jayush Luniya (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-7072) Metadata information exposed through API 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/AMBARI-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366649#comment-14366649 ] Jayush Luniya commented on AMBARI-7072: --------------------------------------- [~keyki] [~matyix] Is this JIRA still and its sub-tasks still relevant? > Metadata information exposed through API > ---------------------------------------- > > Key: AMBARI-7072 > URL: https://issues.apache.org/jira/browse/AMBARI-7072 > Project: Ambari > Issue Type: New Feature > Components: ambari-server, contrib > Affects Versions: 1.7.0 > Reporter: Janos Matyas > Assignee: Janos Matyas > Fix For: 2.1.0 > > > We'd like to retrieve metadata information (most of them are already persisted) through the API. We have open sourced a project called Periscope https://github.com/sequenceiq/periscope which brings SLA policy based autoscaling for Hadoop clusters installed with Ambari, and when up and downscaling clusters we need to know certain metadata information listed below - these features we have implemented in Periscope but would like to add in Ambari API, REST client and shell: > 1. Ability to know the host-hostgroup relationship - from both directions > 2. Ability to know the services/components-host relationship - from both directions > 3. Ability to know the blueprint-cluster(s) relationship > 4. Once Slider is supported, keep and retrieve the Slider apps related metadata -- This message was sent by Atlassian JIRA (v6.3.4#6332)