[ 
https://issues.apache.org/jira/browse/AMBARI-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511118#comment-15511118
 ] 

Alejandro Fernandez edited comment on AMBARI-18438 at 9/21/16 8:44 PM:
-----------------------------------------------------------------------

To test this, I prepared 3 CentOS 6.4 VMs with the following.

* Ambari Server on c6401 host (set ambari.properties file with 
packages.pre.installed=true)
* Ambari Agent on all 3 hosts with manual registration (c6401, c6402, c6403)
* Setup repo files,
** /etc/yum.repos.d/HDP.repo
** /etc/yum.repos.d/HDP-UTILS.repo
* Installed bits by running [^install_packages.sh] on each host
* Used blueprint [^blueprint_fast_install_more_services.json] and 
[^topology.json]




was (Author: afernandez):
To test this, I prepared 3 CentOS 6.4 VMs with the following.

* Ambari Server on c6401 host (set ambari.properties file with 
packages.pre.installed=true)
* Ambari Agent on all 3 hosts with manual registration (c6401, c6402, c6403)
* Setup repo files,
** /etc/yum.repos.d/HDP.repo
** /etc/yum.repos.d/HDP-UTILS.repo
* Installed bits by running install_packages.sh
* Used blueprint [^blueprint_fast_install_more_services.json] and 
[^topology.json]



> Add granular flags for sysprepped clusters to copy tarballs, Oozie share lib, 
> fast jar, and create users
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18438
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18438
>             Project: Ambari
>          Issue Type: Story
>          Components: stacks
>    Affects Versions: 2.5.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: blueprint_fast_install_more_services.json, 
> install_packages.sh, topology.json
>
>
> 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_create_users_and_groups=true|false (default is true)
> For existing users that have automated everything on a sysprepped cluster, 
> they should set these flags as true, true, true, false, respectively.
> These flags are only valid if ambari.properties knows the cluster is 
> sysprepped, i.e.,
> packages.pre.installed=true



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to