peg install asking to "peg fetch" doesn't do anything. After some digging I realize that this is happening because PEG_ROOT is not set. A good fix would be to check if PEG_ROOT is not set and warn about that since at the moment it looks like peg fetch is working properly but peg install doesn't see the result. See below:
ursu-laptop ~ $ peg install hadoop second_peg_inst_velicanu
cluster does not exist locally
run peg fetch <cluster-name> first
ursu-laptop ~ $ peg fetch second_peg_inst_velicanu
pem key velicanu-IAM-keypair found locally
velicanu-IAM-keypair.pem has been added to your ssh-agent
second_peg_inst_velicanu cluster instance type histogram
6 m4.large
MASTER NODE:
Hostname: ip-10-0-0-5
Public DNS: ec2-34-227-6-167.compute-1.amazonaws.com
WORKER NODE:
Hostname: ip-10-0-0-6
Public DNS: ec2-18-233-246-162.compute-1.amazonaws.com
WORKER NODE:
Hostname: ip-10-0-0-8
Public DNS: ec2-18-235-118-123.compute-1.amazonaws.com
WORKER NODE:
Hostname: ip-10-0-0-4
Public DNS: ec2-35-174-247-65.compute-1.amazonaws.com
WORKER NODE:
Hostname: ip-10-0-0-14
Public DNS: ec2-50-16-66-196.compute-1.amazonaws.com
WORKER NODE:
Hostname: ip-10-0-0-13
Public DNS: ec2-18-214-202-110.compute-1.amazonaws.com
ursu-laptop ~ $ peg install hadoop second_peg_inst_velicanu
cluster does not exist locally
run peg fetch <cluster-name> first
peg install asking to "peg fetch" doesn't do anything. After some digging I realize that this is happening because PEG_ROOT is not set. A good fix would be to check if PEG_ROOT is not set and warn about that since at the moment it looks like peg fetch is working properly but peg install doesn't see the result. See below: