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

2016-09-22 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk, commit ed28ff483f8afb994932a62ea177f06b31fae36f
branch-2.5, commit a3d7a30b7ac739e7902209413a65d795436bfa33

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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_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



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


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

2016-09-22 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Attachment: (was: AMBARI-18438.branch-2.5.patch)

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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_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



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


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

2016-09-22 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Status: Patch Available  (was: Open)

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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_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



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


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

2016-09-22 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Attachment: AMBARI-18438.trunk.patch
AMBARI-18438.branch-2.5.patch

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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_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



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


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

2016-09-22 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
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

  was:
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


> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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_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



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


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

2016-09-22 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Attachment: (was: AMBARI-18438.trunk.patch)

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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_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



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


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

2016-09-22 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Status: Open  (was: Patch Available)

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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_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



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


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

2016-09-21 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Status: Patch Available  (was: Open)

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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)


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

2016-09-21 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Attachment: AMBARI-18438.trunk.patch
AMBARI-18438.branch-2.5.patch

> 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: AMBARI-18438.branch-2.5.patch, AMBARI-18438.trunk.patch, 
> 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)


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

2016-09-21 Thread Alejandro Fernandez (JIRA)

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

Alejandro Fernandez updated AMBARI-18438:
-
Attachment: topology.json
install_packages.sh
blueprint_fast_install_more_services.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)