Posts by XyDrKRulof

1) Message boards : Questions and problems : BOINC for private, local projects (Message 103181)
Posted 24 Feb 2021 by XyDrKRulof
Hello David,

thanks for your fast reply, it is very helpful. We will look into the answers you provided and will, in case of more questions, contact through the channels you gave us.

2) Message boards : Questions and problems : BOINC for private, local projects (Message 103136)
Posted 23 Feb 2021 by XyDrKRulof
Hello there,

I am currently evaluating the usability of BOINC for a project we have in a university context. What we would like to do is distributing tasks from different computers of the scientists/engineers to volunteering, free computers in our local network. This could be for example the student computers or also computers from other scientists/engineers.

Now I am evaluating whether it could be a good idea to use BOINC as an underlying system. It seems to have a lot of what we could need: Distributing tasks to volunteers, allowing to work with docker and thus enables us to be free of OS restrictions, allows to run nicely in the background, adding tasks on runtime, etc.

Just from reading the doc I have trouble to find out the following, though:

1. Is it possible to use BOINC without publishing the project on the internet?
2. Is it then possible to keep BOINC restricted to our local network?
3. Is it then possible to connect to our local BOINC project without setting up an account?
4. Is it possible that a volunteering node is not offering all but a subset of available resources? E.g. only 2 CPU cores and 32gb of memory?
5. From what I've gathered the output of a Docker Container executed on a volunteering node will be sent as a zip to the server? Can this be bypassed in some config to go to different destinations?

If you have additional documents for my questions (e.g. links to the doc I might've not seen yet) that would be very helpful. Thanks in advance.

Copyright © 2021 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.