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

Posted to issues@ambari.apache.org by "Laszlo Puskas (JIRA)" <ji...@apache.org> on 2017/04/13 10:41:41 UTC

[jira] [Updated] (AMBARI-20755) Configuration type validation in case of blueprint deployments

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

Laszlo Puskas updated AMBARI-20755:
-----------------------------------
    Attachment: AMBARI-20755.trunk.v1.patch

> Configuration type validation in case of blueprint deployments
> --------------------------------------------------------------
>
>                 Key: AMBARI-20755
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20755
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20755.trunk.v1.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Problem:
> Configuration types posted in the blueprint or in the cluster creation template need to be validated before the cluster provisioning is started and cluster resources are persisted in the database. 
> This validation should be done when the topology configuration comes together so that it's not modified and enhanced further.
> Currently the topology configuration is modified after the validation thus on blueprint deployments the cluster provisioning may fail despite of the right configuration. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)