/clusters/{clusterName}/services/{serviceName}/roles

Mount Point: /api/v7/clusters/{clusterName}/services/{serviceName}/roles

POST

Create new roles in a given service.

Service Type	Available Role Types
HDFS (CDH3)	NAMENODE, DATANODE, SECONDARYNAMENODE, BALANCER, GATEWAY
HDFS (CDH4)	NAMENODE, DATANODE, SECONDARYNAMENODE, BALANCER, HTTPFS, FAILOVERCONTROLLER, GATEWAY, JOURNALNODE
MAPREDUCE	JOBTRACKER, TASKTRACKER, GATEWAY
HBASE	MASTER, REGIONSERVER, GATEWAY
YARN	RESOURCEMANAGER, NODEMANAGER, JOBHISTORY, GATEWAY
OOZIE	OOZIE_SERVER
ZOOKEEPER	SERVER
HUE (CDH3)	HUE_SERVER, BEESWAX_SERVER, KT_RENEWER, JOBSUBD
HUE (CDH4)	HUE_SERVER, BEESWAX_SERVER, KT_RENEWER
FLUME	AGENT
IMPALA	IMPALAD, STATESTORE
HIVE	HIVESERVER2, HIVEMETASTORE, WEBHCAT, GATEWAY
SOLR	SOLR_SERVER
SQOOP	SQOOP_SERVER

When specifying roles to be created, the names provided for each role must not conflict with the names that CM auto-generates for roles. Specifically, names of the form "--" cannot be used unless the is the same one CM would use. If CM detects such a conflict, the error message will indicate what is safe to use. Alternately, a differently formatted name should be used. Since API v6: The role name can be left blank to allow CM to generate the name.