Regarding Option1: I was under the impression that you can use xxxx-env blocks without defining the whole block within blueprints, e.g. I was using a blueprint recently to add the existing MySQL configuration to "hive-env". But I didn't check hive-env after the blueprint installation via the Ambari API, so I am not sure if the hive-env was messed up or not (I'll run another test in a week or so), Hive did start though. Regarding Option 2: You can use a simple Python script, here are the necessary steps 1. Find current config version ("tag"-field), e.g. cluster-env curl -H "X-Requested-By:ambari" -u admin:your-pw -X GET "http://c6601.ambari.apache.org:8080/api/v1/clusters/bigdata?fields=Clusters/desired_configs/cluster-env" Response: {
"href" : "http://c6601.ambari.apache.org:8080/api/v1/clusters/bigdata?fields=Clusters/desired_configs/cluster-env",
"Clusters" : {
"cluster_name" : "bigdata",
"version" : "HDP-2.3",
"desired_configs" : {
"cluster-env" : {
"tag" : "version1434441386979",
"user" : "admin",
"version" : 7
}
}
}
} The tag-field is import => version1434441386979 2. Export current config (example result below) curl -H "X-Requested-By:ambari" -u admin:your-pw -X GET "http://c6601.ambari.apache.org:8080/api/v1/clusters/bigdata/configurations?type=cluster-env&tag=version1434441386979" Response (truncated): {
"href":"http://c6601.ambari.apache.org:8080/api/v1/clusters/bigdata/configurations?type=cluster-env&tag=version1434441386979",
"items":[
{
"href":"http://c6601.ambari.apache.org:8080/api/v1/clusters/bigdata/configurations?type=cluster-env&tag=version1434441386979",
"tag":"version1434441386979",
"type":"cluster-env",
"version":7,
"Config":{
"cluster_name":"bigdata"
},
"properties":{
...
"smokeuser_keytab":"/etc/security/keytabs/smokeuser.headless.keytab",
"smokeuser_principal_name":"ambari-qa@EXAMPLE.COM",
"sqoop_tar_destination_folder":"hdfs:///hdp/apps/{{ hdp_stack_version }}/sqoop/",
"sqoop_tar_source":"/usr/hdp/current/sqoop-client/sqoop.tar.gz",
"tez_tar_destination_folder":"hdfs:///hdp/apps/{{ hdp_stack_version }}/tez/",
"tez_tar_source":"/usr/hdp/current/tez-client/lib/tez.tar.gz",
"user_group":"hadoop"
}
}
]
} 3. Prepare the new configuration by copying all properties from above in the following template. Template: {
"Clusters" : {
"desired_configs" : {
"type" : "cluster-env",
"tag" : "version<INSERT_CURRENT_TIMESTAMP_IN_MILLISECONDS>",
"properties" : {
<INSERT_EXPORTED_CONFIGURATION_PROPERTIES_FROM_ABOVE>
}
}
}
} For example, lets say my user_group is not hadoop anymore, from now on its horton {
"Clusters" : {
"desired_configs" : {
"type" : "cluster-env",
"tag" : "version<INSERT_CURRENT_TIMESTAMP_IN_MILLISECONDS>",
"properties" : {
...
"smokeuser_keytab" : "/etc/security/keytabs/smokeuser.headless.keytab",
"smokeuser_principal_name" : "ambari-qa@EXAMPLE.COM",
"sqoop_tar_destination_folder" : "hdfs:///hdp/apps/{{ hdp_stack_version }}/sqoop/",
"sqoop_tar_source" : "/usr/hdp/current/sqoop-client/sqoop.tar.gz",
"tez_tar_destination_folder" : "hdfs:///hdp/apps/{{ hdp_stack_version }}/tez/",
"tez_tar_source" : "/usr/hdp/current/tez-client/lib/tez.tar.gz",
"user_group" : "horton"
}
}
}
} 5. Final step: Upload new configuration to cluster curl -H "X-Requested-By:ambari" -u admin:your-pw -X PUT "http://c6601.ambari.apache.org:8080/api/v1/clusters/bigdata" -d @<JSON_PAYLOAD_FROM_ABOVE> DONE 🙂 Hope it helps Jonas
... View more
