You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2012/10/17 10:16:03 UTC

[jira] [Updated] (AMBARI-875) Support cluster blueprint in Ambari

     [ https://issues.apache.org/jira/browse/AMBARI-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey updated AMBARI-875:
----------------------------------------

    Description: 
There have been previous discussions on cluster blueprint in Ambari. This jira revisits the concept of blueprint and aims to support blueprints keeping in view the latest architectural changes in AMBARI-666. The most fundamental use cases are 
a) To be able to encapsulate entire cluster definition in terms of a blueprint.
b) To expose APIs to take a cluster state to a specified blueprint.

  was:
There have been previous discussions on cluster blueprint in Ambari. This jira revisits the concept of blueprint and aims to support blueprints in keeping in view the latest architectural changes in AMBARI-666. The most fundamental use cases are 
a) To be able to encapsulate entire cluster definition in terms of a blueprint.
b) To expose APIs to take a cluster state to a specified blueprint.

    
> Support cluster blueprint in Ambari
> -----------------------------------
>
>                 Key: AMBARI-875
>                 URL: https://issues.apache.org/jira/browse/AMBARI-875
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>
> There have been previous discussions on cluster blueprint in Ambari. This jira revisits the concept of blueprint and aims to support blueprints keeping in view the latest architectural changes in AMBARI-666. The most fundamental use cases are 
> a) To be able to encapsulate entire cluster definition in terms of a blueprint.
> b) To expose APIs to take a cluster state to a specified blueprint.

--
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