[
https://issues.apache.org/jira/browse/AMBARI-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834298#comment-15834298
]
Hudson commented on AMBARI-18739:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6516 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6516/])
AMBARI-18739. Perf: Create Rolling and Express Upgrade Packs. Fix
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8362dcefd6550323f94fabdf40dfcbedd2db4fc2])
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/configuration/hadoop-env.xml
> Perf: Create Rolling and Express Upgrade Packs
> ----------------------------------------------
>
> Key: AMBARI-18739
> URL: https://issues.apache.org/jira/browse/AMBARI-18739
> Project: Ambari
> Issue Type: Story
> Components: ambari-agent
> Affects Versions: 2.5.0
> Reporter: Alejandro Fernandez
> Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
>
> In order to run Rolling/Express Upgrade, will need to create the
> Rolling/NonRolling Upgrade Packs and potentially config packs if we decide to
> do it across major versions.
> This means each service will need to support start commands with the
> upgrade_type option, have symlinks already in distro-select, etc.
> At first, this can be a handful of services.
> The goal is to simulate Rolling/Express Upgrade on the PERF stack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
