[
https://issues.apache.org/jira/browse/AMBARI-24397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24397:
------------------------------------
Labels: pull-request-available (was: )
> Allow PATCH VDFs to Specify Services Which Are Not Installed in the Cluster
> ---------------------------------------------------------------------------
>
> Key: AMBARI-24397
> URL: https://issues.apache.org/jira/browse/AMBARI-24397
> Project: Ambari
> Issue Type: Task
> Affects Versions: 2.6.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> AMBARI-21832 limited the flexibility of a PATCH VDF by requiring that the
> list of {{available-services}} match what is installed in the cluster. For
> example, if a cluster contained ZooKeeper and Storm, a patch VDF which
> specified Storm and Accumulo could not be registered.
> Ambari should allow registration of a VDF without restricting it to the
> services which are currently installed in the cluster. In the above mentioned
> case, one concern would be what would happen if Accumulo was added after the
> patch was applied. In this case, Ambari should add Accumulo from the parent
> {{STANDARD}} repo.
> When a patch is reverted, Ambari must now check to ensure that a service
> included in that patch wasn't added after the patch was applied. Consider
> this scenario:
> - Install a ZK only cluster
> - Register and patch using a VDF with ZK, STORM
> - Add Storm
> - Revert the patch
> - Re-apply the patch
> When the patch is re-applied, the hosts will not have the new storm packages
> installed since the patch repository was distributed before Storm was a part
> of the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
