Ability to apply "policies" for miner cofiguration
I am suggesting a policy-based approach to miner configuration. Instead of applying things like power settings, pool settings, tags and alert settings individually, you could build policies containing these settings and then apply the policies to miners. Policies could be applied to individual miners, or to any miners added to a pickaxe or client.
Comments
1 comment
For pools in particular, it is now possible to have “valid mining pools” configuring in settings that conflicts with triggers to correct pools.
This configuration must be linked to prevent loops. Meaning, the valid mining pools screen and a correction trigger should be configured at the same place, with a way to evaluate the policy first before applying corrections at least during initial policy setup.
The way valid pools have to be mapped to specific miner types in a mixed scrypt/btc fleet is also cumbersome. Basically, you should configure a policy and it enforces it right there from the valid pools configuration. This should not require a trigger, it should be a policy.
Please sign in to leave a comment.