ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <>
Subject [jira] [Created] (AMBARI-605) Add UI flow/groundwork for handling Ambari / Hadoop stack version upgrades
Date Fri, 06 Jul 2012 03:33:33 GMT
Yusaku Sako created AMBARI-605:

             Summary: Add UI flow/groundwork for handling Ambari / Hadoop stack version upgrades
                 Key: AMBARI-605
             Project: Ambari
          Issue Type: New Feature
    Affects Versions: 0.9.0
            Reporter: Yusaku Sako
            Assignee: Yusaku Sako
             Fix For: 1.0

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/ called
$GLOBALS["BYPASS_ROUTER"].  Setting this to TRUE, the router (hmc/html/_router.php - used
to be called hmc/html/ - 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:!default.jspa
For more information on JIRA, see:


View raw message