ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Nechiporenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13123) Usability: do not force redirect the user to the currently running wizard if another user logs in
Date Thu, 17 Sep 2015 10:29:48 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802728#comment-14802728
] 

Oleg Nechiporenko commented on AMBARI-13123:
--------------------------------------------

+1 for patch

> Usability: do not force redirect the user to the currently running wizard if another
user logs in
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13123
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13123
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-13123.patch
>
>
> When a user initiates "major" cluster reconfiguration operations, such as Enable NameNode
HA, Enable Kerberos, Add Hosts, Add Services, etc, the user forces any user who accesses Ambari
Web to be redirected to the wizard.
> This unnecessarily restricts what the users can do, and also it is dangerous because
multiple users may interact with the wizard (or keep the wizards open and multiple instances
can make API calls with side effects, causing failure).
> If users different from who initiated the major reconfiguration operation logs in while
the operation is still going on, the user should not be force redirected, but instead be able
to access the cluster in read-only mode with some indication that "NameNode HA is being enabled",
etc (much like what happens when Rolling Upgrade is happening).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message