Repository: bigtop Updated Branches: refs/heads/master b9255e18b -> 6780b1caf
BIGTOP-2065. Update deployment README.md to reflect on better deployment experience Signed-off-by: Evans Ye <[email protected]> Project: http://git-wip-us.apache.org/repos/asf/bigtop/repo Commit: http://git-wip-us.apache.org/repos/asf/bigtop/commit/6780b1ca Tree: http://git-wip-us.apache.org/repos/asf/bigtop/tree/6780b1ca Diff: http://git-wip-us.apache.org/repos/asf/bigtop/diff/6780b1ca Branch: refs/heads/master Commit: 6780b1caf511cabf9f810bb41828b02179a6f535 Parents: b9255e1 Author: Konstantin Boudnik <[email protected]> Authored: Mon Sep 21 19:55:08 2015 -0700 Committer: Evans Ye <[email protected]> Committed: Tue Sep 22 15:51:55 2015 +0000 ---------------------------------------------------------------------- bigtop-deploy/puppet/README.md | 36 +++++++++++++++++++++++++----------- 1 file changed, 25 insertions(+), 11 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/bigtop/blob/6780b1ca/bigtop-deploy/puppet/README.md ---------------------------------------------------------------------- diff --git a/bigtop-deploy/puppet/README.md b/bigtop-deploy/puppet/README.md index 1e9c68a..260d19c 100644 --- a/bigtop-deploy/puppet/README.md +++ b/bigtop-deploy/puppet/README.md @@ -117,19 +117,33 @@ Bigtop toolchan can take care of that for you, so just be aware of it. And run the following on those nodes: ``` -# cp bigtop-deploy/puppet/hiera.yaml /etc/puppet -# mkdir -p /etc/puppet/hieradata -# rsync -a --delete bigtop-deploy/puppet/hieradata/bigtop/ /etc/puppet/hieradata/bigtop/ -# cat > /etc/puppet/hieradata/site.yaml <<EOF -# bigtop::hadoop_head_node: "hadoopmaster.example.com" -# hadoop::hadoop_storage_dirs: -# - "/data/1" -# - "/data/2" -# bigtop::bigtop_repo_uri: "http://mirror.example.com/path/to/mirror/"; -# EOF -# puppet apply -d --modulepath="bigtop-deploy/puppet/modules:/etc/puppet/modules" bigtop-deploy/puppet/manifests/site.pp +cp bigtop-deploy/puppet/hiera.yaml /etc/puppet +mkdir -p /etc/puppet/hieradata +rsync -a --delete bigtop-deploy/puppet/hieradata/site.yaml bigtop-deploy/puppet/hieradata/bigtop /etc/puppet/hieradata/ ``` +Edit /etc/puppet/hieradata/site.yaml to your liking, setting up the hostname for +hadoop head node, path to storage directories and their number, list of the components +you wish to install, and repo URL. At the end, the file will look something like this +``` +bigtop::hadoop_head_node: "hadoopmaster.example.com" +hadoop::hadoop_storage_dirs: + - "/data/1" + - "/data/2" +hadoop_cluster_node::cluster_components: + - ignite-hadoop + - hive + - spark + - yarn + - zookeeper +bigtop::jdk_package_name: "openjdk-7-jre-headless" +bigtop::bigtop_repo_uri: "http://bigtop.s3.amazonaws.com/releases/1.0.0/ubuntu/trusty/x86_64"; +``` + +And finally execute +``` +puppet apply -d --modulepath="bigtop-deploy/puppet/modules:/etc/puppet/modules" bigtop-deploy/puppet/manifests/site.pp +``` When ignite-hadoop accelerator is deployed the client configs are placed under `/etc/hadoop/ignite.client.conf`. All one needs to do to run Mapreduce jobs on ignite-hadoop grid is to set `HADOOP_CONF_DIR=/etc/hadoop/ignite.client.conf` in the client session.
