#Assumptions
- Loggregator is deployed and its traffic controller job has the allowAllAccess flag set to true. 
  Currently our forked version of loggregator (https://github.com/dajulia3/loggregator) supports this flag.  
- Diego-release is deployed
    
#Running The Whetstone Tests

For example, to Run Tests against Bosh Lite deployed Diego Release and Loggregator:
    ginkgo -r -untilItFails -- -etcdAddress="10.244.16.2:4001" -domain="10.244.0.34.xip.io" -loggregatorAddress="loggregator.10.244.0.34.xip.io"

#Assumptions
- Loggregator is deployed and its traffic controller job has the allowAllAccess flag set to true. 
  Currently our forked version of loggregator (https://github.com/dajulia3/loggregator) supports this flag.  
- Diego-release is deployed
    
#Running The Whetstone Tests

For example, to Run Tests against Bosh Lite deployed Diego Release and Loggregator:
    ginkgo -r -untilItFails -- -etcdAddress="10.244.16.2:4001" -domain="10.244.0.34.xip.io" -loggregatorAddress="loggregator.10.244.0.34.xip.io"


#Notes on Running against Bosh Lite:
  Cloudfoundry reccomends using xip.io with Bosh lite for DNS.
  This has been very flaky for us, resulting in no such host errors.
  The alternative that we have found is to use dnsmasq configured to resolve all xip.io addresses to the ip of the HA proxy.
  This also requires creating a /etc/resolvers/io file that points to 127.0.0.1. See further instructions [here http://passingcuriosity.com/2013/dnsmasq-dev-osx/]. 

Update readme with info on dnsmasq
Update readme with info on dnsmasq

Signed-off-by: David Julia <ed0cc118a79fb117c6af81e058eba4f0ecd53e11@pivotal.io>
