Hey, A current flaw with Aurora is that it will automatically inject a rack limit constraint of 1 into a task's scheduling constraints even if the job was submitted without any constraints [1]. This means that Aurora needs all Mesos slaves to have a 'rack' attribute, so it can satisfy this scheduling constraint.
I don't think there is a very good reason to have this default here as not everyone can encode a 'rack' value into their Mesos slaves. I propose we remove this default rack limit and allow Aurora to schedule jobs to Mesos slaves that do not have a 'rack' attribute set. Does anyone object to this? [1]: https://github.com/apache/incubator-aurora/blob/900a2b299347c71f7c7601a3a3d0a3f0f0afbcb7/src/main/java/org/apache/aurora/scheduler/configuration/ConfigurationManager.java#L142-L153 -- Zameer Manji
