[
https://issues.apache.org/jira/browse/TRAFODION-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836906#comment-15836906
]
Steve Varnau commented on TRAFODION-2452:
-----------------------------------------
Also making changes for less hard-coding of trafodion release version numbers
in the ambari mpack packaging.
In working on this, I found that ambari does not yet support updating an add-on
service separate from a the whole stack.
That functionality will be coming in Ambari 3.0 according to current thinking.
https://lists.apache.org/thread.html/0ea5a62980be37e5f8eb2828c6876fd25daa45b4e532cdb7fc625c17@%3Cdev.ambari.apache.org%3E
To connect this mpack into the stack upgrade, it needs to be defined as a
stack-extension, and not just as an add-on service. Since there is currently
only one release (2.1 in development) that applies to multiple versions of HDP
stack, it does not seem to make sense to define it as a stack extension.
When/If we have different versions of trafodion that map to different HDP
stacks, then I think the extension definition will make sense.
> provide uninstall steps for ambari mpack
> ----------------------------------------
>
> Key: TRAFODION-2452
> URL: https://issues.apache.org/jira/browse/TRAFODION-2452
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: installer
> Affects Versions: 2.1-incubating
> Reporter: Steve Varnau
> Assignee: Steve Varnau
>
> Normally, there is no need to uninstall an ambari plugin (mpack), you can
> just remove the service(s) or ignore the services it provides.
> For developers and testers, however, there needs to be a simple way to remove
> the mpack in order to install a new version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)