You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yurii Shylov (JIRA)" <ji...@apache.org> on 2014/11/05 19:29:34 UTC

[jira] [Updated] (AMBARI-8162) Rolling Upgrade - Repository Version Management

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

Yurii Shylov updated AMBARI-8162:
---------------------------------
    Component/s: ambari-server

> Rolling Upgrade - Repository Version Management
> -----------------------------------------------
>
>                 Key: AMBARI-8162
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8162
>             Project: Ambari
>          Issue Type: Story
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Yurii Shylov
>            Assignee: Yurii Shylov
>             Fix For: 2.0.0
>
>
> Add the ability to manage the repository versions available to a cluster.
> In order to facilitate rolling upgrades, it will be necessary to maintain repository versions that get associated with a stack.
> Repo Versions include:
> Display name of the repo;
> Upgrade package name;
> The stack and the version the upgrade pack applies to;
> A list of repository definitions, aligned by operating system.  For example, redhat6 deployments include HDP and HDP-UTILS repository definitions.
> After a repo version has been determined, any number of them may be applied to an available cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)