AWS Thinkbox Discussion Forums

Feature Request: Filters for adding pools/groups/etc

I’m frequently moving slaves in and out of pools, adding new slaves, etc. On many of our machines, we have secondary slaves running that are meant to be in different pools than the primary slaves. Right now that is making me ctrl+click on every other slave in the list to select only the primary or the secondary slaves. This is starting to take a chunk out of the day when it comes to modifying pools/groups, or even things like submitting a Command Script job to Deadline and making a machine list.

I was hoping that it was possible to put the same filtering system on these features that exists on the “Slaves” panel or “Jobs” panel. That sort of power would really make the pool/group modifications much more powerful. For larger render farms I think this would help out a lot. That would allow me to filter out any slave that contains the word “secondary” or filter out any machines that have less than 32 gigs or anything like that. Right now I’m having to first filter the slaves list to the machines I want to modify, then visually check the filtered slaves list and compare that to the machines I have selected to modify a pool for. What do you think?

I agree that this would definitely be helpful. We’ve put this on the wishlist. We won’t have time to do this for 6.1, but hopefully we can get it on the roadmap of a future version soon.

Cheers,

  • Ryan

What might be even better, is if the modify pool/group window was simply just a panel, that used your active selection from the slaves panel. That way all the infromation you require would be available.

Right now, since that panel is modal, i usually remote into another machine, start the monitor there as well (to have an interactive slave panel), and then do the pool/group management from my main workstation.

I totally agree Laszlo. I would definitely enjoy having pools/groups as their own panel. I also use two or more monitor instances to get this stuff done more quickly.

Thanks for the feedback guys. This has all been logged, so we’ll consider all possibilities when we look at improving how this works.

Privacy | Site terms | Cookie preferences