It was at this point that hbase-master would stick in agent-state: pending, public-address: null
So I ran juju destroy-environment, changed these lines in .juju/environments.yaml:
demo:
data-dir: /home/project64198/demo
After an mkdir demo, juju bootstrap and all the deploys and add-relations, my cloud was up.
Sure. First, I ssh'd to project64198@deneb, a (metal) server of mine. There prepared for local deployment:
sudo apt-get install python- software- properties
sudo add-apt-repository ppa:juju/pkgs
sudo apt-get update && sudo apt-get install juju
sudo apt-get install lxc apt-cacher-ng libzookeeper-java zookeeper
Now I ran juju bootstrap and got a .juju/environme nts.yaml, which I modiified:
environments: 4c2f636f067f89c c14862c e28308fd9f2a7ba f3 198/democluster
democluster:
type: local
control-bucket: juju-c81e728d9d
admin-secret: eccbc87e4b5ce2f
default-series: precise
juju-origin: ppa
data-dir: /home/project64
Also, I ran ssh-keygen -t rsa and mkdir democluster, and prepared for hbase by writing this config.yaml:
hadoop-master: port: 9090
hbase: True
hadoop-workers:
hbase: True
thrift:
monitoring_
After another juju bootstrap I deployed my cloud:
juju deploy zookeeper master: namenode hadoop- workers: datanode master: namenode hbase-master: namenode master: namenode hbase-regions: namenode regionserver
juju deploy --config config.yaml hadoop hadoop-master
juju deploy --config config.yaml hadoop hadoop-workers
juju deploy hbase hbase-master
juju deploy hbase hbase-regions
juju add-relation hadoop-
juju add-relation hbase-master zookeeper
juju add-relation hbase-regions zookeeper
juju add-relation hadoop-
juju add-relation hadoop-
juju add-relation hbase-master:master hbase-regions:
It was at this point that hbase-master would stick in agent-state: pending, public-address: null environment, changed these lines in .juju/environme nts.yaml:
So I ran juju destroy-
demo: 198/demo
data-dir: /home/project64
After an mkdir demo, juju bootstrap and all the deploys and add-relations, my cloud was up.