[
https://issues.apache.org/jira/browse/AMBARI-20755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969436#comment-15969436
]
Laszlo Puskas commented on AMBARI-20755:
----------------------------------------
pushed:
* branch-2.5:
committer lpuskas <[email protected]>
Fri, 14 Apr 2017 18:50:54 +0200 (18:50 +0200)
commit a9cda4f1f82aa0f42aa3fb7ddee5947ef2dab603
* trunk:
committer lpuskas <[email protected]>
Fri, 14 Apr 2017 16:01:10 +0200 (16:01 +0200)
commit 103e49a899b57ff286889b8840e758c53bdaf1e8
> 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.b-2.5.v2.patch, AMBARI-20755.trunk.v3.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)
