Merge pull request #556 from tony-kerz/master

[docs:api] add clarity around values available for constraints

Author: gkleiman

docs/docs/api.md

@@ -23,6 +23,7 @@ All examples in this section assume that you've found a running leader at `chron
 - [Obtaining Remote Executables](#obtaining-remote-executables)
 - [Job Configuration](#job-configuration)
 - [Sample Job](#sample-job)
+- [Constraints](#constraints)
 
 
 ## Leaders
@@ -57,7 +58,7 @@ Get the job definition by searching for the following attributes by using the se
 * `name`: Name of a job.
 * `command`: Command to execute.
 * `any`: Search term contained in `name` or `command`.
-* 
+*
 * Endpoint: __/scheduler/jobs/search__
 * Method: __GET__
 * Example: `curl -L -X GET chronos-node:8080/scheduler/jobs/search?name=request_event_counter_hourly`
@@ -386,6 +387,9 @@ When specifying the `command` field in your job hash, use `url-runner.bash` (mak
 
 ## Constraints
 
+These constraints will currently only work against attributes that are specifically set on the Mesos slaves [as described in the Mesos documentation](http://mesos.apache.org/documentation/latest/configuration).
+(i.e. the `hostname` attribute is not currently automatically available for constraints [as it is in Marathon](https://mesosphere.github.io/marathon/docs/constraints))
+
 ### EQUALS constraint
 
 Schedule a job on nodes that share a common attribute.