You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "John Speidel (JIRA)" <ji...@apache.org> on 2014/08/07 04:37:12 UTC

[jira] [Resolved] (AMBARI-6762) Include configuration in exported blueprint

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

John Speidel resolved AMBARI-6762.
----------------------------------

    Resolution: Fixed

pushed to trunk

> Include configuration in exported blueprint
> -------------------------------------------
>
>                 Key: AMBARI-6762
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6762
>             Project: Ambari
>          Issue Type: New Feature
>            Reporter: John Speidel
>            Assignee: John Speidel
>              Labels: api, blueprints, configuration
>             Fix For: 1.7.0
>
>
> Include both host group and cluster scoped configuration in an exported blueprint.
> To export a blueprint, use the api:
> AMBARI_HOST:8080/api/v1/clusters/:clustername?format=blueprint
> The exported blueprint will contain the entire configuration for the associated cluster.  The only properties which are not included are those that are marked as "input required" in the stack.  All passwords are marked as required so they will not be exported.  Also, any hostnames in the configuration properties are replaced with a hostgroup token: %HOSTGROUP::group1%.  When a cluster is provisioned from the blueprint, the hostgroup tokens are resolved to host names for the target cluster. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)