how_to_cleanup_ambari.txt

# Stop existing cluster
 /usr/local/rvm/gems/ruby-1.9.3-p547@global/bin/bundle exec bin/weavr.rb hwx stop

# Delete the old blueprint, especially if uploading a new configuration
# This assumes you are on the Ambari server and you did not alter the blueprint name at all
curl -X DELETE -H 'X-Requested-By: your mom' -u admin:admin 'http://localhost:8080/api/v1/blueprints/dev_service_blueprint'

# On all nodes
# Blow away any possible remaining data
sudo rm -r /data/hadoop/*
sudo rm -r /hadoop/hbase/*
sudo rm -r /hadoop/oozie/*
sudo rm -r /hadoop/zookeeper/*

# On the Namenode (wherever it USED to be)
# you might need to run sudo yum install -y mlocate && updatedb && locate formatted
# Code-diving revealed multiple places where this is checked for existence
sudo rm -r /var/lib/hdfs/namenode/formatted