The important note from that doc is: The format is $role(/.*)?. When a job is created, the scheduler requires that the $role component matches the role field in the job configuration, and will reject the job creation otherwise.
> On Mar 16, 2015, at 3:39 AM, Brian Brazil <brian.bra...@boxever.com> wrote: > > On 16 March 2015 at 06:13, Bhuvan Arumugam <bhu...@apache.org> wrote: > >> Hello, >> >> I've a requirement to reserve N number of slaves for specific aurora >> role. When a job is scheduled using this role, it should run in one of >> these N slaves. Jobs scheduled using other roles, should not run in >> one of these N slaves. Can you please let me know the best way to >> implement it? >> >> I can add a random attribute to mesos-slave, but it'll not restrict >> access to specific role. For example, i can add 'dedicated=$role' >> attribute to mesos-slave. With this, any job with this key/value in >> constraint will run on this host, irrespective of the role used to >> launch the job. >> > > https://aurora.incubator.apache.org/documentation/latest/deploying-aurora-scheduler/#dedicated-attribute > appears to be the way to do this. > > Brian > > >> >> -- >> Regards, >> Bhuvan Arumugam >> www.livecipher.com >>
