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

Sumit Mohanty resolved AMBARI-12293.
------------------------------------
    Resolution: Won't Fix

> Allow auto execution of command/task at specific life cycle stages of a 
> cluster
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-12293
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12293
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server, stacks
>    Affects Versions: 2.1.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>            Priority: Critical
>             Fix For: 2.3.0
>
>
> During cluster creation (or add hosts), especially in the hosted clusters in 
> cloud environment, it is a requirement to execute tasks/commands at specific 
> life-cycle stages.
> Samples of such stages are:
> * pre-install - before any components are installed
> * post-install - after all components are installed
> * pre-start - before starting any components
> * post-start - after all starts are complete
> These tasks are generally expected to be executed for each host and at least 
> once. It is expected that these tasks be auto-executed. In addition if these 
> tasks fail it may result in fast fail - aborting any other tasks following 
> these.
> Samples of such tasks are -
> * perform host level setup (create local users, files, and folders)
> * perform custom health checks
> To support auto-execution, it is also necessary to allow saved configuration 
> for the tasks being auto-executed.
> While it may not be necessary, it will be good to allow execution of the 
> above tasks at any other time through explicit API calls.  
> Ambari today has support for custom command/action. Custom actions can be 
> defined as stand alone tasks that can be invoked anytime through APIs. Custom 
> commands are commands associated with specific services. The design of this 
> feature should take into account the existing capabilities.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to