Mik-TF
commented
8 months ago Proposition from the farmer (Jeroen):
"Thing is, if already some other pre node is running on the ip, node gets rejected. I think it would be hard to have a check built in using the ip, but this would be ideal. What's not waterproof, but a step in the right direction and easier to implement, is to check whether there is a contract for pre deployment already on some node of the corresponding farm. This would already decrease the number of nodes a lot, only possible conflict left is then a pre node running outside of threefolds zero os. But probably hard to account for anyway
Proposed steps:
- 1 find all nodes running pre
- 2 find all corresponding farms of those nodes
- 3 build a check in pre node selection to not include any node from farms in this list
It would be really helpful if the ip as displayed by presearch was displayed in the 'show details' section of the tf dashboard That would allow for mass deployment because you can then make 100 vms with pre, and if only 40 are accepted you can then easily find which 40 are good and delete the other 60"
Which package/s are you suggesting this feature for?
Dashboard
Is your feature request related to a problem? Please describe
A farmer and user of the tfgrid wants to deploy 200 presearch nodes on the grid. For now he is doing all this manually.
Describe the solution you'd like
Could we add a feature on either dashboard (the presearch node weblet) or tfrobot/tfcmd, so a user can deploy massively presearch nodes?