[
https://issues.apache.org/jira/browse/AMBARI-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-10385:
-----------------------------------
Description:
Especially in hosted deployment settings, its beneficial to create VM images
with all packages pre-installed. When Ambari is used to deploy hadoop on such
hosts, INSTALL operation should not be needed. The way INSTALL is implemented
by Ambari today there are potentially three ways to skip installation.
1. *Skip installation commands*
In this approach, Ambari Server should not issue install commands and silently
move all components to {{INSTALLED}} state. This solution is ideal as it will
eliminate command creation, execution etc. This approach will require:
** Modification to Ambari Server internal state machine to handle transparent
transition through INSTALL phase.
** Introduce explicit CONFIGURE commands to configure the clients
** Ensure that none of the stack definitions do anything more than installing
packages
As a work-around, agents can be made to short-circuit INSTALL calls. This is if
Ambari Server internal state machine needs to issue INSTALL command. The
pre-conditions of CONFIGURE command a a clean implementation of install()
functions still remain.
2. *Skip install_package() calls*
In this approach, Ambari Server does not change but a configuration allows
Agents to skip doing any work when install_package() is called.
> On nodes that already have packages pre-installed, Ambari should skip install
> altogether
> ----------------------------------------------------------------------------------------
>
> Key: AMBARI-10385
> URL: https://issues.apache.org/jira/browse/AMBARI-10385
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server
> Reporter: Sumit Mohanty
> Fix For: 2.2.0
>
>
> Especially in hosted deployment settings, its beneficial to create VM images
> with all packages pre-installed. When Ambari is used to deploy hadoop on such
> hosts, INSTALL operation should not be needed. The way INSTALL is implemented
> by Ambari today there are potentially three ways to skip installation.
> 1. *Skip installation commands*
> In this approach, Ambari Server should not issue install commands and
> silently move all components to {{INSTALLED}} state. This solution is ideal
> as it will eliminate command creation, execution etc. This approach will
> require:
> ** Modification to Ambari Server internal state machine to handle transparent
> transition through INSTALL phase.
> ** Introduce explicit CONFIGURE commands to configure the clients
> ** Ensure that none of the stack definitions do anything more than installing
> packages
> As a work-around, agents can be made to short-circuit INSTALL calls. This is
> if Ambari Server internal state machine needs to issue INSTALL command. The
> pre-conditions of CONFIGURE command a a clean implementation of install()
> functions still remain.
> 2. *Skip install_package() calls*
> In this approach, Ambari Server does not change but a configuration allows
> Agents to skip doing any work when install_package() is called.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
