Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 01-06-2017 06:41 PM
I am planning to create 4 node cluster on Azure using Cloudbreak Automated Deployment. I wanted to create 1 Name Node, 2 Data Nodes and 1 Edge Node.
I wanted to know how to create Edge Node in Cluster using Cloudbreak(Ambari Blueprints)?
Created 01-06-2017 07:42 PM
Edge node is nothing more just a properly configured hostgroup with e.g. client libraries and/or with perimeter security components like Knox. What is in the hostgroup is transparent for Cloudbreak, I have copied an example here:
...
{
"name": "host_group_edge",
"configurations": [],
"components": [
{
"name": "ZOOKEEPER_CLIENT"
},
{
"name": "PIG"
},
{
"name": "OOZIE_CLIENT"
},
{
"name": "HBASE_CLIENT"
},
{
"name": "HCAT"
},
{
"name": "KNOX_GATEWAY"
},
{
"name": "METRICS_MONITOR"
},
{
"name": "FALCON_CLIENT"
},
{
"name": "TEZ_CLIENT"
},
{
"name": "SLIDER"
},
{
"name": "SQOOP"
},
{
"name": "HDFS_CLIENT"
},
{
"name": "HIVE_CLIENT"
},
{
"name": "YARN_CLIENT"
},
{
"name": "METRICS_COLLECTOR"
},
{
"name": "MAPREDUCE2_CLIENT"
}
],
"cardinality": "1"
}
...If you would like you create your own blueprint, then probably the easiest way is to use a default blueprint delivered together with Cloudbreak (e.g. hdp-small-default blueprint) and delete those hostgroups and components what you don't need.
Created 01-06-2017 07:42 PM
Edge node is nothing more just a properly configured hostgroup with e.g. client libraries and/or with perimeter security components like Knox. What is in the hostgroup is transparent for Cloudbreak, I have copied an example here:
...
{
"name": "host_group_edge",
"configurations": [],
"components": [
{
"name": "ZOOKEEPER_CLIENT"
},
{
"name": "PIG"
},
{
"name": "OOZIE_CLIENT"
},
{
"name": "HBASE_CLIENT"
},
{
"name": "HCAT"
},
{
"name": "KNOX_GATEWAY"
},
{
"name": "METRICS_MONITOR"
},
{
"name": "FALCON_CLIENT"
},
{
"name": "TEZ_CLIENT"
},
{
"name": "SLIDER"
},
{
"name": "SQOOP"
},
{
"name": "HDFS_CLIENT"
},
{
"name": "HIVE_CLIENT"
},
{
"name": "YARN_CLIENT"
},
{
"name": "METRICS_COLLECTOR"
},
{
"name": "MAPREDUCE2_CLIENT"
}
],
"cardinality": "1"
}
...If you would like you create your own blueprint, then probably the easiest way is to use a default blueprint delivered together with Cloudbreak (e.g. hdp-small-default blueprint) and delete those hostgroups and components what you don't need.
Created 01-07-2017 01:21 PM
Hi Attila,
Thanks for the answer.
Just another question -- Suppose i have set up a cluster with HDP stack as 2.3. But now i want to upgrade the HDP stack of that particular cluster to 2.5? Can we do it using cloudbreak? And how do we add services like Apache Atlas, Ranger, Falcon if required to already running cluster using Cloudbreak automated deployment?
Thanks
Rahul