THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| No Format |
|---|
$ cat puppet-hbase.properties
whirr.cluster-name=hbase
# We would like to have 1 node running all the services listed
# and 3 nodes running a different set of services
whirr.instance-templates=1 puppet:bigtop::kerberos::kdc+ \
puppet:bigtop::kerberos::client+ \
puppet:bigtop::zookeeper::server+ \
puppet:bigtop::hdfs::namenode+ \
puppet:bigtop::hdfs::datanode+ \
puppet:bigtop::hbase::master+ \
puppet:bigtop::hbase::regionserver \
\
3 puppet:bigtop::kerberos::client+ \
puppet:bigtop::zookeeper::server+ \
puppet:bigtop::hdfs::datanode+ \
puppet:bigtop::hbase::regionserver \
# Where to fetch the module code from
puppet.bigtop.module=git://github.com/rvs/bigtop-puppet.git
# this parameter is applicable to the entire cluster
bigtop.auth=kerberos
# this one only concerns hbase master service
bigtop.hbase.master.heap_size=1024
# this one is HDFS specific (namenode and datanode services both will get it)
bigtop.hdfs.dirs=["/mnt"]
$ whirr launch-cluster --config puppet-hbase.properties
|
rpelavin questions:
Roman, is the whirr description something that works with current Puppet manifests or is a description of what you would like to work?
Also, if hiera is used, are you looking to get as close to one-to-one parameter mapping between parameters here (e.g., bigtop.auth, bigtop.hdfs.dirs, bigtop.hbase.master.heap_size) and 'hiera parameters'?
An external wizard/orchestrator use case
...