You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Varun Kapoor (JIRA)" <ji...@apache.org> on 2012/05/11 00:06:48 UTC
[jira] [Created] (AMBARI-219) Break Deploy+Error Logs Into Their
Own Page
Varun Kapoor created AMBARI-219:
-----------------------------------
Summary: Break Deploy+Error Logs Into Their Own Page
Key: AMBARI-219
URL: https://issues.apache.org/jira/browse/AMBARI-219
Project: Ambari
Issue Type: Bug
Affects Versions: ambari-186
Reporter: Varun Kapoor
Assignee: Varun Kapoor
Fix For: ambari-186
Aside from being used on a bunch of pages (they can all be handled in-page by reusing the relevant JS modules), the option to see the Deploy+Error logs should also exist once the InstallationWizard has been exited, from the Cluster-centric page.
Once we have this page, we may as well make the Deploy+Error links from within the InstallationWizard also point to this new page instead of being an in-page panel (as it presently is), but that's a call we might make once we see how disruptive opening in a new tab/window is to the user experience.
--
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
[jira] [Assigned] (AMBARI-219) Break Deploy+Error Logs Into Their
Own Page
Posted by "Varun Kapoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Kapoor reassigned AMBARI-219:
-----------------------------------
Assignee: (was: Varun Kapoor)
> Break Deploy+Error Logs Into Their Own Page
> -------------------------------------------
>
> Key: AMBARI-219
> URL: https://issues.apache.org/jira/browse/AMBARI-219
> Project: Ambari
> Issue Type: Bug
> Affects Versions: ambari-186
> Reporter: Varun Kapoor
> Fix For: ambari-186
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Aside from being used on a bunch of pages (they can all be handled in-page by reusing the relevant JS modules), the option to see the Deploy+Error logs should also exist once the InstallationWizard has been exited, from the Cluster-centric page.
> Once we have this page, we may as well make the Deploy+Error links from within the InstallationWizard also point to this new page instead of being an in-page panel (as it presently is), but that's a call we might make once we see how disruptive opening in a new tab/window is to the user experience.
--
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
[jira] [Updated] (AMBARI-219) Break Deploy+Error Logs Into Their
Own Page
Posted by "Hitesh Shah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hitesh Shah updated AMBARI-219:
-------------------------------
Affects Version/s: (was: ambari-186)
0.9.0
Fix Version/s: (was: ambari-186)
> Break Deploy+Error Logs Into Their Own Page
> -------------------------------------------
>
> Key: AMBARI-219
> URL: https://issues.apache.org/jira/browse/AMBARI-219
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Varun Kapoor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Aside from being used on a bunch of pages (they can all be handled in-page by reusing the relevant JS modules), the option to see the Deploy+Error logs should also exist once the InstallationWizard has been exited, from the Cluster-centric page.
> Once we have this page, we may as well make the Deploy+Error links from within the InstallationWizard also point to this new page instead of being an in-page panel (as it presently is), but that's a call we might make once we see how disruptive opening in a new tab/window is to the user experience.
--
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