[AMBARI-10385] On nodes that already have packages pre-installed, Ambari should skip install altogether

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 2.3.0
• Component/s: ambari-agent, ambari-server
• Assignee: Unassigned
• Reporter: Sumit Mohanty
• Created: 07/Apr/15 19:56
• Updated: 25/Apr/19 09:44

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.

Sub-Tasks

• Support skipping install operations on hosts that are already sys-prepped: Resolved
• Oozie tar extraction and folder set up should be skipped for sys-prepped hosts: Resolved