anchor.diff:  
   == Testing the setup
   
  -Any Hawkular client that supports connecting using SSL can be used. ManageIQ and HawkFX will be show below.
  +Any Hawkular client that supports connecting using SSL can be used. Curl, ManageIQ and HawkFX will be show below.
   
   NOTE: If using self-signed certificates, the client machine needs to trust Hawkular Services certificate or the client
   should support to specify which certificate to trust.
   See link:http://www.hawkular.org/blog/2016/09/14/consuming-hawkular-api-over-ssl.html[here]
   for more info.
  +
  +=== Curl
  +
  +Simplest way to test, we only need to tell curl how to resolve `hawkular-services` and pass the public certificate.
  +
  +```
  +curl -H "Hawkular-Tenant: hawkular" --resolve "hawkular-services:8443:127.0.0.1" --cacert hawkular-services-prd -X GET https://hawkular-services:8443/hawkular/metrics/metrics
  +```
  +
  +It will output metrics stored on Hawkular Services.
   
   === ManageIQ
   
  
positive.code: it will be linked to the cassandra instance (hawkular-cassandra)
  
  ```
  docker run --name hawkular-services --link=hawkular-cassandra -e CASSANDRA_NODES=hawkular-cassandra -e HAWKULAR_HOSTNAME=hawkular-services -e HAWKULAR_USE_SSL=true -p 8443:8443 -v `pwd`/hawkular-services-private.key:/client-secrets/hawkular-services-private.key -v `pwd`/hawkular-services-public.pem:/client-secrets/hawkular-services-public.pem hawkular/hawkular-services
  ```
  
  NOTE: To avoid guessing the host, we explicitly set it to hawkular-services
  
negative.code: Hawkular Services requires a cassandra instance, you can start one by doing:
  
  ```
  docker run --name hawkular-cassandra -e CASSANDRA_START_RPC=true -d cassandra:3.0.12
  ```
  
  == Starting Hawkular Services on SSL
  