[
https://issues.apache.org/jira/browse/AMBARI-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-2023:
--------------------------------
Description:
Ambari depends on third-party libraries, often with specific versions.
As one specific example, Ambari currently depends on Nagios 3.2.3.
The user can inadvertently do "yum upgrade" of all packages, causing Nagios to
be upgraded (due to availability of a newer version in one of the repos), and
breaking monitoring functionality of Ambari (as it relies on the specific
version 3.2.3).
That's just one example, but it would be better if such dependencies could be
sandboxed (just like how puppet, facter, etc, are sandboxed) and not interfere
with the user's package management practices.
One way is to rename the package to something like
ambari-[original-package-name]-version, and install such packages under some
Ambari-specific namespace.
was:
Ambari depends on third-party libraries, often with specific versions.
As one specific example, Ambari currently depends on Nagios 1.4.9.
The user can inadvertently do "yum upgrade" of all packages, causing Nagios to
be upgraded, and breaking monitoring functionality of Ambari (as it relies on
the specific version 1.4.9).
That's just one example, but it would be better if such dependencies could be
sandboxed (just like how puppet, facter, etc, are sandboxed) and not interfere
with the user's package management practices.
One way is to rename the package to something like
ambari-[original-package-name]-version, and install such packages under some
Ambari-specific namespace.
> Packages that Ambari depends on should be sandboxed to prevent
> conflicts/breakage
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-2023
> URL: https://issues.apache.org/jira/browse/AMBARI-2023
> Project: Ambari
> Issue Type: Improvement
> Components: agent, build, controller
> Affects Versions: 1.2.0
> Reporter: Yusaku Sako
>
> Ambari depends on third-party libraries, often with specific versions.
> As one specific example, Ambari currently depends on Nagios 3.2.3.
> The user can inadvertently do "yum upgrade" of all packages, causing Nagios
> to be upgraded (due to availability of a newer version in one of the repos),
> and breaking monitoring functionality of Ambari (as it relies on the specific
> version 3.2.3).
> That's just one example, but it would be better if such dependencies could be
> sandboxed (just like how puppet, facter, etc, are sandboxed) and not
> interfere with the user's package management practices.
> One way is to rename the package to something like
> ambari-[original-package-name]-version, and install such packages under some
> Ambari-specific namespace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
