Hi Joe, Great to hear you're interested. TBH I have heard the name Heroku but know absolutely nothing about it. Certainly the challenges you mention sound familiar, so you're probably right about sharing things between these projects. Some more detailed replies below,
On Sun, Feb 14, 2016 at 8:03 PM, Joe Kutner <[email protected]> wrote: > I’m very interested in this. I’ve been working on a similar project to run > BOINC on Heroku, a PaaS that uses an execution model that inspired Docker. > Heroku uses LXC containers and shares similar principles of isolation and > ephemerality. > > I think we could share a lot between these projects (I’m working through > some minutia before officially releasing). And I agree it's en essential > effort if BOINC is to remain relevant. > > Here are the challenges I’ve faced: > > - BOINC assumes the filesystem is mutable (i.e. you often need to SSH into > a server to change stuff) > - BOINC assumes the filesystem is persistent (i.e. presumes a change made > on the filesystem will be there later) > These I've largely solved by storing the project directory on a Docker volume. > - BOINC assumes background processes run on the same server as the other > processes. > This is true of I think the scheduler / transitioner (?) but not some of the other daemons. Nevertheless I run all of the daemons inside the same container, but in theory it might be nice to separate out some of them to separate containers, then one could use "docker-compose scale" to quickly create more deamons on other machines if your severs need to grow. > - BOINC uses static config files with hostnames, which may need to change > between Docker/LXC containers > In Docker at least its easy, you can pick your hostname by hand. > I’ve been able to work-around most of this. But I think a lot of this and > be easily improved with better knowledge of PHP. I have more expertise with > Docker, and that’s the bit I’d be happy to help with. > > Do you have any issues in particular that you’re trying to work through? > I have a list of the top TODO items here <https://github.com/marius311/boinc-server-docker/blob/master/docs/TODO.md>, for someone with Docker expertise 1, 5, & 6 might be good ones. Let me know if you're interested. Marius > > > On Feb 14, 2016, at 12:13 PM, Marius Millea <[email protected]> wrote: > > > > Hi guys, > > > > Her <http://cosmicmar.com/2016/02/14/boinc-server-docker-1/>e's > > <http://cosmicmar.com/2016/02/14/boinc-server-docker-1/> a short ~10 > minute > > screen cast of how to run a BOINC server with Docker and how to run > Docker > > applications on it. My target audience for this is basically you guys, > > BOINC developers and BOINC project maintainers, i.e. these mailing lists. > > It'd be great if you could take a look. > > > > This is my vision for the future of BOINC because it makes it extremely > > easy to develop and maintain your project, letting you focus your time on > > the important part, the science. This is also a call for help because > this > > isn't quite a finished product yet, and I don't know that it can be > without > > me getting some help from one or two other BOINC experts. > > > > So, would anyone want to help? > > > > I am also curious to get opinions on how something like this might fit > into > > BOINC in the future, either as a part of BOINC, or its own separate > > project. For example, I think it would be great if boinc-server-docker > > became the recommended way for new users to run a server (pending of > > course, more work and documentation) > > > > > > If anyone has any questions about any of this, please don't hesitate to > ask > > here! > > > > Marius > > _______________________________________________ > > boinc_projects mailing list > > [email protected] > > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects > > To unsubscribe, visit the above URL and > > (near bottom of page) enter your email address. > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
