From AIMSWiki

Table of contents

1 Welcome to the home of Star Team 2 Monday_16_July 2007 Report 1 Installation Procedure 1.1 Tuesday_17_July 2007 Report 2 BOINC Server Installation Procedure

Welcome to the home of Star Team

Huda Mohamed Ahmed EI Hag [[1] (http://www.aims.ac.za/wiki/index.php/huda)]

Wonder Chikohomero [[2] (http://www.aims.ac.za/wiki/index.php/wonder)]

Raji [[3] (http://www.aims.ac.za/wiki/index.php/raji)]

Monday_16_July 2007 Report

Problem 1

The exercise completed successifully, though with a few comments below.

The link was very slow for downloading the client package, thanks to Nick for his flash disk that reduced the download time to a few seconds.

Installation Procedure

• Download the BOINC client from BOINC compute science (http://boinc.berkeley.edu/download.php)
• Locate the directory were the installation file is locate by running
• Run the executable downloaded by using the following command.

 $cd /parent_directory/example_of_folder_containing_the_package, then
 $./bo press tab for auto complete, then press return key

• run the application by entering

 $BONIC/run_manager

• During execution of the BOINC manager, there were errors that we still have no explanation. Here is a printscreen of the errors.

Skin Manager: Failed to parse static line color. Using default.

Skin Manager: Application name was not defined. Using default.

Skin Manager: Failed to load application logo. Using default.

Problem 2

The site with more credit is vtu@home (http://boinc.netsoft-online.com/e107_plugins/boinc/get_cpcs.php)

Problem 3

Problem 4

Problem 5

Tuesday_17_July 2007 Report

BOINC Server Installation Procedure

Problem 1 In this exercise we set up the BOINC server successfully. The main problems we encountered was we forgot our server password.

Problem 2 we set up the password but then we had deleted the file and worked without a password

Problem 3

• Platforms : different platforms from intel to sun-sparc
• Applications : application name and workunits, versions
• Application versions: different versions of the application and creation times
• Users: the strange thing is it has a field labelled seti_total_cpu and our app is called upercase
• Teams: strange field seti_id
• Hosts
• Workunits
• Results

Regular Operations:

• Screen user profiles
• Manage special users: THESE ARE THE PROJECT ADMIN TEAM

Special Operations: operations which need to be propagated to a large number of users

• Manage applications
• Manage application versions
• Send mass email to a selected set of users
• Email user with misconfigured host
• FLOP count statistics
• Cancel workunits

Problem 4 WE JUST LOOKED AT THE DIFFERENT TABLES IN THE DATABASE