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 8169E9591 for ; Tue, 14 May 2013 06:03:34 +0000 (UTC) Received: (qmail 17618 invoked by uid 500); 14 May 2013 06:03:18 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 17575 invoked by uid 500); 14 May 2013 06:03:18 -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 17562 invoked by uid 99); 14 May 2013 06:03:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 06:03:18 +0000 Date: Tue, 14 May 2013 06:03:18 +0000 (UTC) From: "Sumit Mohanty (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-1783) Specification for a cluster blueprint consumable by Ambari 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-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-1783: ---------------------------------- Attachment: HostManifest.txt > Specification for a cluster blueprint consumable by Ambari > ---------------------------------------------------------- > > Key: AMBARI-1783 > URL: https://issues.apache.org/jira/browse/AMBARI-1783 > Project: Ambari > Issue Type: New Feature > Affects Versions: 1.3.1 > Reporter: Sumit Mohanty > Assignee: Sumit Mohanty > Fix For: 1.3.1 > > Attachments: Ambari-BluePrint-0.2.docx, Ambari-BluePrint-0.3.docx, HostComponentMapping.txt, HostManifest.txt, PackageConfiguration.txt, PackageDefinition.txt > > > Deployment of a hadoop cluster can be modeled as the mapping of a stack definition to a set of host while satisfying placement constraints. A stack definition refers to the description of various services that comprise a hadoop stack (e.g. HDP-1.2.1), components associated with the services, and configuration properties. A set of available hosts is specified through a host-manifest that lists the available hosts and relevant properties/characteristics of each host. A cluster blueprint is specification of a hadoop stack mapped to a set of hosts. Mapping to a host can be a direct mapping - e.g. deploy this component X on host Y or a host can be specified as a set of requirements which is used to select the most appropriate host(s) from a host-manifest. -- 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