[
https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500646#comment-14500646
]
ASF GitHub Bot commented on STORM-766:
--------------------------------------
GitHub user redsanket opened a pull request:
https://github.com/apache/storm/pull/529
JIRA STORM-766 (Include version info in the service page)
I have included the code to display the version info in the web-page. Let
me know if you need any other requirement.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/redsanket/storm master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/529.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #529
----
commit 458042ea89bd648770dcfed19d8f840fa2aea8bb
Author: sanket <[email protected]>
Date: 2015-04-17T17:33:13Z
made changes for adding the supervisor-info version
commit 337f187eff5894d07e207861639cf55304936f79
Author: sanket <[email protected]>
Date: 2015-04-17T20:34:05Z
made changes for adding the supervisor-info version
----
> Supervisor summary should include the version.
> ----------------------------------------------
>
> Key: STORM-766
> URL: https://issues.apache.org/jira/browse/STORM-766
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Parth Brahmbhatt
> Assignee: Sanket Chintapalli
> Priority: Minor
> Fix For: 0.10.0
>
>
> With the support for rolling upgrade, different nodes in the cluster can run
> different versions of storm. We should include the version in
> SupervisorSummary just like NimbusSummary so admins can identify nodes that
> needs upgrading/downgrading from UI.
> As part of this change I will also add a supervisor/log link in the ui.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
