Management huge BOINC farm

Message boards : BOINC client : Management huge BOINC farm
Message board moderation

To post messages, you must log in.

AuthorMessage
Lucas

Send message
Joined: 1 May 06
Posts: 1
Poland
Message 4152 - Posted: 1 May 2006, 12:41:14 UTC

Hello

My name is Lucas, I'm new on this forum and quite new in BOINC (about 1999-2000 I joined to SETI@home project).
We will hope to run BOINC client at about 100 computers working 24h/d and I have small question (idea) about management BOINC farm.

I know that I can manage BOINC client remotely (by RPC) but I thing that it is a bit uncomfortable and in some circumstances that may by unacceptable for security reasons.

So I was thinking about some kind “Command Centre”.

Example:
We have got 4 computers in 2 departments.

Every computer is identified by URI:
comp1: http://my.org/department1/comp1
comp2: http://my.org/department1/comp2
comp3: http://my.org/department2/comp1
comp4: http://my.org/department2/comp2

The URI represent role of computers.

We have got our Command Centre on URL:
http://my.org/cc.xyz
And we can query our CC to give us current task to given role.

Example:
Request:
http://my.org/cc.xyz?role=http://my.org/department1/comp1
Response:
<task>
<id>rosetta@home</id>
<auth>info about rosetta's user</auth>
</task>

We can configure our CC in kind like this:

<cc>
<role id=”http://my.org/department1/”>
<id>rosetta@home</id>
<auth>info about rosetta's user</auth>
</role>

<role id=”http://my.org/department2/”>
<id>seti@home</id>
<auth>info about seti's user</auth>
</role>

<role id=”http://my.org/department2/comp1”>
<id>Einstein@home</id>
<auth>info about einstein's user</auth>
</role>
</cc>

Most matching role is selected, so:
comp1: rosetta@home
comp2: rosetta@home
comp3: Einsein@home
comp4: seti@home

On client site we must add module that will be checking that configuration has changed. If “Yes” we attach new project.

I think that it may simplify management process in huge BOINC farm.

I think that it is possible to do this by some additional BOINCmonitor that will be run simultaneously with BOINC client. It is ok if I have got homogeneous clients (only on Linux) but in heterogeneous farm it will be problem. So I think that it may by include as part of core client.

Of course this is only brief view (without security issues, etc.)

What do You think ?
Maybe You have got own solution for management huge BOINC farm ?

Greeting
Lucas
ID: 4152 · Report as offensive

Message boards : BOINC client : Management huge BOINC farm

Copyright © 2024 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.