ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <>
Subject [jira] [Updated] (AMBARI-9223) Add properties_attributes support to exported Blueprints
Date Tue, 20 Jan 2015 22:12:35 GMT


Robert Nettleton updated AMBARI-9223:
    Attachment: AMBARI-9223.patch

Uploaded initial version of patch

> Add properties_attributes support to exported Blueprints
> --------------------------------------------------------
>                 Key: AMBARI-9223
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 2.0.0
>         Attachments: AMBARI-9223.patch
> Attributes of configuration properties are not properly included when a Blueprint is
exported from a running cluster.
> To reproduce:
> 1. Start a cluster with the Ambari UI, mark some configuration properties as "final".
> 2. After the cluster has successfully started, use the Blueprint REST API to export a
Blueprint based on this running cluster.
> 3. The configuration elements in the exported Blueprint will not include the proper metadata
about a configuration property.  In this specific case, the Blueprint will not indicate which
configuration elements are "final".  
> This is only a bug in the Blueprint cluster renderer, as most of the support for "properties_attributes"
already exists in the BlueprintResourceProvider and ClusterResourceProvider.  
> The ClusterBlueprintRenderer class needs to be updated to pull out the properties_attributes
from the Cluster resource, and include these within the "configurations" map of the exported
> I'm working on a fix for this, and will be submitting a patch shortly.  

This message was sent by Atlassian JIRA

View raw message