ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20871) Unify repository file creation
Date Thu, 27 Apr 2017 15:08:04 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-20871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nate Cole updated AMBARI-20871:
-------------------------------
    Status: Patch Available  (was: In Progress)

> Unify repository file creation
> ------------------------------
>
>                 Key: AMBARI-20871
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20871
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20871.patch
>
>
> Repo files are written two different ways in Ambari.  The first way makes each repository
its own file:
> {noformat}
> # cat /etc/yum.repos.d/HDP.repo
> [HDP-2.5]
> name=...
> baseurl=...
> path=/
> enabled=1
> # cat /etc/yum.repos.d/HDP-UTILS.repo
> [HDP-UTILS-1.1.0.21]
> name=...
> baseurl=...
> path=/
> enabled=1
> {noformat}
> With installing packages for upgrade purposes, only ONE file is created:
> {noformat}
> # cat /etc/yum.repos.d/HDP-2.5.3.0-38.repo
> [HDP-2.5.3.0-38]
> ...
> [HDP-UTILS-2.5.3.0-38]
> ...
> {noformat}
> This behavior should be unified as in the 2nd behavior.  This is going to be important
to be able to support multiple deployed versions, per host, as is required for PU/CU.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message