[
https://issues.apache.org/jira/browse/AMBARI-10472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494768#comment-14494768
]
Eric Yang commented on AMBARI-10472:
------------------------------------
Hi Nate,
Ambari repositories are distinct versions, such as HDP/2.0, and HDP/2.1. This
has certain user experience issues associated with updating ambari.repo to
point to the correct repository to install Ambari and stack of software.
Wouldn't it be better if we manage RPMs more like Redhat, where there is a
Major release repository, and all minor releases are just symlinks to the major
version repositories? Any compatible changes are actually put in "updates"
directory for incremental updates. This will reduce the tight coupling of
stack definition and compatible stacks for upgrade purposes. In CentOS, they
can simply replace the URL to migrate from Redhat owned repository to their own
CentOS stack of software. This removes the need for Ambari to manage yum
repository metadata. Ambari only tracks dependencies to be satisified cross
node dependencies, which yum repository doesn't track. Stack compatibility can
be tracked using RPM signing key package metadata. This will ensure that
future version can track what version that they are backward compatible with
without having software dependency logic in Ambari.
> RU: add compatible stacks for upgrade purposes
> ----------------------------------------------
>
> Key: AMBARI-10472
> URL: https://issues.apache.org/jira/browse/AMBARI-10472
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 2.1.0
>
> Attachments: AMBARI-10472.patch
>
>
> Changes required to support adding cross-stack versions and installation for
> a cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
