AWS Thinkbox Discussion Forums

Thoughts on slave configuration profiles

One thing I’ve seen in other queue managers is the ability to create slave “profiles” and have them applied to slaves based on a set of criteria. These profiles can be automatically applied at slave startup based on comparisons with host attributes, either numerically (CPU count, RAM, etc) or using pattern-matching (IP address, hostname, slave name, OS name, architecture, slave user, etc.). In Deadline’s case, the profiles could then be able to (sparsely?) override things like the pool and group membership, concurrency, “extra info” values, etc.

What are the immediate reactions to potentially adding something similar to Deadline in the future (obviously as a low-priority item)?

In Deadline 7, we’re adding slave-based events, and one of those is an OnSlaveStarted event. This means you can write an event plugin that can configure the slave’s settings on startup, such as pool, group, concurrency, extra info, etc.

Cheers,
Ryan

Thanks for the info Ryan, that’s very cool.

Privacy | Site terms | Cookie preferences