Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <EFD3CF7F-183F-432A-B8C6-854F40771F25@hortonworks.com>
References: 
 <CADfbTpG=Vp_JtDvsRxYSC9TzCpjgH29-_Z6tH9vaVNbkr4rktw@mail.gmail.com>
	<F3D4B1CE-CF89-41D4-9C9E-449243513985@hortonworks.com>
	<EFD3CF7F-183F-432A-B8C6-854F40771F25@hortonworks.com>
Date: Wed, 11 Jul 2012 12:04:42 -0700
Message-ID: 
 <CALF7aMS=6McgFK92Ty_WVrVKrRibgYDhRPy4ZH0+1GjRyipFwQ@mail.gmail.com>
Subject: Re: [DISCUSSION] Cluster blue print concept
From: Mahadev Konar <mahadev@hortonworks.com>
To: ambari-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks Devaraj.

mahadev


On Tue, Jul 10, 2012 at 11:27 AM, Devaraj Das <ddas@hortonworks.com> wrote:
> The attachment didn't go thru. Just checkout the trunk rev 1176156 [svn c=
o  http://svn.apache.org/repos/asf/incubator/ambari@1176156] and then look =
at trunk/examples directory..
>
> On Jul 9, 2012, at 10:39 PM, Devaraj Das wrote:
>
>> For the uninitiated, here is what I remember about blueprint:
>> Blueprint was a concept for describing cluster configurations (including=
 repositories, stack definitions and individual component configurations). =
Blueprints would be versioned, and, one could inherit from a blueprint, etc=
. to define/override properties. For example, Ambari could ship with a defa=
ult blueprint which defines config values/properties that are appropriate t=
o the best of the Ambari developer's knowledge. In the production site, one=
 could inherit that blueprint and only override certain properties with sit=
e specific values.
>> Attached a sample blueprint json file that inherits from another bluepri=
nt, and selectively overrides a property in the namenode config..
>>
>> <blueprint.json>
>>
>> On Jul 9, 2012, at 11:38 AM, Eric Yang wrote:
>>
>>> Hi all,
>>>
>>> The original cluster blue print has been removed from Ambari website,
>>> and the cluster blue print concept has been removed from current
>>> Ambari code base.  It would be great to have a specification of master
>>> configuration for construct or clone other clusters.  This could be
>>> offered as open specification for community to implement or enhance
>>> the deployment execution engine.  What does the community think about
>>> this idea?
>>>
>>> regards,
>>> Eric
>>
>