[MESOS-10171] Groundwork for constraints-based filtering using `Exists/NotExists` attribute constraint as an example.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Resolved
• Fix Version/s: 1.11.0
• Component/s: allocation, master
• Target Version/s: 1.11.0
• Epic Link: Constraints-based offer filtering
• Assignee: Andrei Sekretenko
• Reporter: Andrei Sekretenko
• Created: 31/Jul/20 19:03
• Updated: 25/Aug/20 12:33
• Resolved: 25/Aug/20 12:33

Description

This should allow schedulers to set Exists/NotExists constraint on an attribute/region/availability zone and have the constraint applied by the allocator.

The main goal it to get a foundation suitable for adding other attribute constraints.

Issue Links

• blocks: MESOS-10172 Add offer constraints on (pseudo)attribute value equality
• blocks: MESOS-10173 Add offer constraints on (pseudo)attribute (not) matching RE2 regex