THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Perform your Ambari Server install and setup.
yum install ambari-server
ambari-server setup
- Start After setup completes, start your Ambari Server.
ambari-server start
- Install Ambari Agents on the hosts you plan to include in your cluster.
yum install ambari-agent
- Set the Ambari Server on the Ambari Agents.
vi /etc/ambari-agent/conf/ambari-agent.ini
- Set hostname= to the Fully Qualified Domain Name for the Ambari Server. Save and exit.
hostname=c6401.ambari.apache.org
- Start the Agents to initiate registration to Server.
ambari-agent start
- Confirm the Agent hosts are registered with the Server.
http://your.ambari.server:8080/api/vi/hosts
- Proceed with defining your blueprint and creating a cluster instance from that blueprint.
...
Code Block |
---|
POST /api/v1/clusters/MyThreeNodeCluster
202 - Accepted
{
"href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/MyCluster/requests/1",
"Requests" : {
"id" : 1,
"status" : "InProgress"
}
} |
Setting Configurations
By default, Blueprints will use all the default configuration setting values. You can optionally specify to override configuration properties as part of your blueprint. In the example below, we are setting the NameNode directory in hdfs-site.xml to /hadoop/nn.
Code Block |
---|
{
"configurations" : [
{
"hdfs-site" : {
"dfs.namenode.name.dir" : "/hadoop/nn"
}
}
],
"host_groups" : [
{
"name" : "host_group_1",
"components" : [
{
"name" : "NAMENODE"
},
{
"name" : "SECONDARY_NAMENODE"
},
{
"name" : "DATANODE"
},
{
"name" : "HDFS_CLIENT"
},
{
"name" : "RESOURCEMANAGER"
},
{
"name" : "NODEMANAGER"
},
{
"name" : "YARN_CLIENT"
},
{
"name" : "HISTORYSERVER"
},
{
"name" : "MAPREDUCE2_CLIENT"
},
{
"name" : "ZOOKEEPER_SERVER"
},
{
"name" : "ZOOKEEPER_CLIENT"
}
],
"cardinality" : "1"
}
],
"Blueprints" : {
"blueprint_name" : "single-node-hdfs-yarn",
"stack_name" : "HDP",
"stack_version" : "2.0"
}
} |