You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Babiichuk (JIRA)" <ji...@apache.org> on 2014/01/31 18:10:20 UTC

[jira] [Updated] (AMBARI-4489) Set some ui restriction for components/services/hosts in passive mode

     [ https://issues.apache.org/jira/browse/AMBARI-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrii Babiichuk updated AMBARI-4489:
-------------------------------------

    Attachment: AMBARI-4489.patch

> Set some ui restriction for components/services/hosts in passive mode
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-4489
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4489
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4489.patch
>
>
> make a restrictions according to these characteristics:
> A passivated target WILL NOT generate alerts.
> A passivated target WILL accept commands.  This means that you can start and stop a HostComponent or Service, or execute commands or actions; even with a passivated status.
> A passivated target WILL mark children with an implied passive.
> A passivated target that is a child CANNOT be brought out of passive status.  Only the parent may be.
> A passivated Service will not be included when “Start All Services” occurs.  But can be included if the command target IS the service.
> A passivated Host will not be included with a command if the target is a Service, but can be if the command target IS the Host.
> A passivated HostComponent will not be included with a command if the target is a Service or a Host, but can be if the command target IS the HostComponent.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)