You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2012/07/06 06:56:34 UTC
[jira] [Commented] (AMBARI-605) Add UI flow/groundwork for handling
Ambari / Hadoop stack version upgrades
[ https://issues.apache.org/jira/browse/AMBARI-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407704#comment-13407704 ]
Yusaku Sako commented on AMBARI-605:
------------------------------------
Committed to trunk.
> Add UI flow/groundwork for handling Ambari / Hadoop stack version upgrades
> --------------------------------------------------------------------------
>
> Key: AMBARI-605
> URL: https://issues.apache.org/jira/browse/AMBARI-605
> Project: Ambari
> Issue Type: New Feature
> Affects Versions: 0.9.0
> Reporter: Yusaku Sako
> Assignee: Yusaku Sako
> Fix For: 1.0
>
> Attachments: AMBARI-605.patch, AMBARI-605.sh
>
>
> Add the UI flow for handling Ambari and Hadoop stack version upgrades.
> The assumption is that the Ambari RPM has been upgraded and the necessary database schema upgrade has been applied already (this is to be implemented).
> Upon hitting any Ambari URL, the user is taken to the Upgrade wizard to complete upgrading the Hadoop stack bits (if this is necessary).
> To upgrade the stack, first we uninstall the stack while retaining data, have the user reconfigure services, and then install/start the new version of the stack.
> This is still preliminary and to be improved upon and merged with actual backend calls (yet to be implemented).
> Currently the front-end code is mocked with Sinon.JS so that XHR (AJAX) calls can be intercepted to return hard-coded values.
> Also, to ease development in general, a new parameter was added to php/conf/Config.inc called $GLOBALS["BYPASS_ROUTER"]. Setting this to TRUE, the router (hmc/html/_router.php - used to be called hmc/html/head.inc - the interceptor that is invoked upon hitting all front-end PHP pages) will not cause any forced redirects/forwards regardless of the application state. For production, this is to be set to FALSE to protect the users from performing actions that could lead the cluster to be in an inconsistent state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira