[AMBARI-18438] Add granular flags for sysprepped clusters to copy tarballs, Oozie share lib, fast jar, and create users

• Type: Story
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.5.0
• Component/s: stacks
• Assignee: Alejandro Fernandez
• Reporter: Alejandro Fernandez
• Created: 21/Sep/16 20:35
• Updated: 23/Sep/16 02:06
• Resolved: 22/Sep/16 23:51

Description

In order to support sysprepped clusters using Docker containers, we need more granular flags about what steps must be done, e.g.,

• Copy tarballs to HDFS
• Copy Oozie share lib to HDFS
• Copy fast jar (fast-hdfs-resource.jar) to /var/lib/ambari-agent/lib/
• Create users and groups

These properties will be stored in cluster-env instead of ambari.properties so they can be changed without requiring a restart of Ambari Server.

sysprep_skip_copy_tarballs_hdfs=true|false (default is false)
sysprep_skip_copy_oozie_share_lib_to_hdfs=true|false (default is false)
sysprep_skip_copy_fast_jar_hdfs=true|false (default is false)
sysprep_skip_create_users_and_groups=true|false (default is false)

For existing users that have automated everything on a sysprepped cluster, they should set these flags as true.

These flags are only valid if ambari.properties knows the cluster is sysprepped, i.e.,
packages.pre.installed=true

Issue Links

• links to: Review Board patch