Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E763BE3E5 for ; Tue, 12 Feb 2013 16:57:20 +0000 (UTC) Received: (qmail 96564 invoked by uid 500); 12 Feb 2013 16:57:14 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 96539 invoked by uid 500); 12 Feb 2013 16:57:14 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 96472 invoked by uid 99); 12 Feb 2013 16:57:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 16:57:14 +0000 Date: Tue, 12 Feb 2013 16:57:14 +0000 (UTC) From: "John Speidel (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-1380) Publish a management API which is consistent with the version 1 monitoring 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-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated AMBARI-1380: --------------------------------- Attachment: Ambari-Cluster_Controller-SPI_v2.docx ambari-monitoring-api-v102.docx plugging_into_ambari_rest_api_framework.docx Ambari REST API Guidelines.docx > Publish a management API which is consistent with the version 1 monitoring API > ------------------------------------------------------------------------------ > > Key: AMBARI-1380 > URL: https://issues.apache.org/jira/browse/AMBARI-1380 > Project: Ambari > Issue Type: Bug > Reporter: John Speidel > Assignee: John Speidel > Fix For: 1.3.0 > > Attachments: Ambari-Cluster_Controller-SPI_v2.docx, ambari-monitoring-api-v102.docx, Ambari REST API Guidelines.docx, plugging_into_ambari_rest_api_framework.docx > > > Review existing management services for usability and consistency with the monitoring API. All management API resources must utilize the API framework and follow the same pattern as the monitoring API where there is a plural collection resource followed by a singular instance resource. Also, package names should be consistent and have a common parent package where it makes sense to avoid having service classes strewn all over the place. Following these guidelines will help to ensure a consistent behavior across the entire API. If a service is truly private it should be clear by the package name. All services need to be represented as a single consistent API, not a random collection of independent API's/services. Current services will also be evaluated to ensure that they are necessary and can't be replaced/combined with other services. > This is an umbrella Jira for all management API cleanup. The actual work of updating the API for a specific resource will be tracked in separate Jira's. > For more information, see the attached documents. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira