[
https://issues.apache.org/jira/browse/AMBARI-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983836#comment-14983836
]
Eric Yang commented on AMBARI-13364:
------------------------------------
All Linux repository has similar approach in package management, either a
global major version or a code name follow by architecture name. This will
allow a list of repositories to share the common ancestry. i.e. CentOS
repository 6 repositories have base, extra, source, updates. Ubuntu has
UtopicUnicorn and architecture name. In Ubuntu or Debian world, there is
multiverse which allow addition of repositories for commercial software. This
is similar to have multiple yum repositories. The fundamental idea are the
same, the repositories are governed by a release number or code name. It would
be ideal, if the stack definition version can apply globally across multiple
repositories to avoid picking up binaries from incompatible repositories. I
had a really painful day today for supporting a client because a value added
repository version number was ramping faster than common stack. Ambari 2.1.0
was not able to cope with the logic of multiple version numbers of add-on
stacks with minor increments. Ambari attempts to generate repository files
from repo_version table, and this made a mess in generating both minor
increment add-on repositories, and cause installation to fail in cascaded
failures.
It would be great to follow Linux software repository design to have distinct
repository only when major changes happen. Otherwise, it would be best to use
same repository for incremental updates or add-ons. Just making sure that I
put this out here for consideration before proper implementation can be
written. Thanks
> Parameterize stack information used by common services
> -------------------------------------------------------
>
> Key: AMBARI-13364
> URL: https://issues.apache.org/jira/browse/AMBARI-13364
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Reporter: Tuong Truong
> Assignee: Juanjo Marron
> Attachments: AMBARI-13364 Parameterize stack information used by
> common services.pdf, AMBARI-13364.patch
>
>
> This feature will add a basic framework to remove hardcoded stack information
> out of the common services and use parameter to get access to stack
> information. Currently, the common services hardcoded much information
> specific to Hortonworks' HDP stack including name (HDP), specific versions
> (2.0, 2.1, 2.2), and install location. This feature will propose a way of
> configuration these information and parameterize them into the services for
> reference as require.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
