User:Cis4914.s09/Documentation

 Document your work here.

Cis4914.s09 18:32, 4 February 2009 (UTC)


 * Document in details all steps that you did.
 * Reread the documentation to see whether you had made any implicit assumptions; if yes, document explicitly these implicit assumptions.

Egm6322.s09 15:45, 19 February 2009 (UTC)

= Things to do =
 * test

= Documentation =

Why we chose Ubuntu 8.04 (Hardy Heron)
Ubuntu has an uncommonly steady release cycle. A new release is made available every six months with LTS versions coming out once every four cycles. Regular releases are maintained for 1.5 years. LTS releases are maintained for 3+ years. Because of the stability provided by LTS releases we decided to go with Ubuntu 8.04 (Hardy Heron) since it is the latest LTS version.

Keyboard shortcuts
Switch to command line interface (CLI) Ctrl-Alt-F1 Switch to GUI Ctrl-Alt-F7

Set up It's All Text to edit wiki articles
Documenting intensive command line work and configuration files can be very cumbersome with normal wiki text boxes. The tool 'It's All Text!' will invoke an external editor of your choice instead of having to use the text boxes provided by the wiki. If you have firefox 2 or 3 and use Windows, Linux, or Mac then you are ready to begin installation.

You will need to install gvim in order for this to work under Linux distributions. For Ubuntu: sudo apt-get install vim-gnome You can download and install the 'It's All Text!' plugin here. After you install it Firefox will prompt you to restart. Go ahead and restart Firefox. Now you need to go to a wiki page and click the 'edit' button or hit 'alt-shift-e'. You should see a little 'edit' bubble at the bottom right of the text box area. Right click it and select 'Preferences'. We now need to enter the path to the editor of our choice. The path '/usr/bin/vim' will not work as we need the graphical version. Enter '/usr/bin/gvim' into the empty box and hit the 'close' button to save the changes.

Now when you are on a wiki edit page clicking the 'edit' bubble will bring up a gvim window to edit in. After making changes you can type :w to send the changes back to the wiki. (the wiki text box will flash yellow) Hit 'alt-tab' to change windows back to the wiki and hit 'alt-shift-p' to preview the changes.

More tips and tricks with 'It's All Text!' can be found here.

= Preparing base system in hydra3 =

Register an MSDNAA account
The Microsoft Developers Network Academic Alliance (MSDNAA) product is a licensing program  donated to the College of Engineering by Microsoft which allows all College of Engineering units,  students, faculty, and staff to use various Microsoft software products and online resources  for academic and non-profit research purposes.  Students may obtain an official copy of Microsoft Windows XP through MSDNAA. Send an e-mail to software@eng.ufl.edu asking whether you have an account at on MSDNAA or not and if there is an account then what is the username and password<BR> Normally UF engineering students have a MSDNAA account created automatically but <BR> if one does not have an account then he/she can Register here.<BR> Fill in the form with appropriate data and if you are not registered within <BR> two business days then email software@eng.ufl.edu with a request for creating a MSDNAA account. <BR>

<div style="width: 80%; margin-left: auto; margin-right: auto; padding: 4px; border: 2px solid #FF0000; background-color: #FFDDDD; text-align: left;"> You want to document whom you contacted to know that "Normally UF engineering students have a MSDNAA account created automatically". Give contact info (name, phone, e-mail address, etc.) Egm6322.s09 14:21, 26 February 2009 (UTC)

Download Windows XP
After your account has been created, you may log into the MSDNAA system here.<BR> In case you have forgotten your password: (a) Click here and enter your gatorlink email-id as your username. The password will be e-mailed to your gatorlink email <BR> (b) If step (a) fails, then send an email to software@eng.ufl.edu reporting the problem with your UF-ID <BR> After you have logged in, click on the "Software" tab on the upper left side <BR> Either browse through the list of softwares shown or enter the name <BR> of the specific software you want to download in the blank next to "Search" and click "Go" tab<BR> Click on the tab "Add to cart".<BR> Click on the "I Agree" tab <BR> Next click on the "Download" button<BR> If asked "Are you sure you want to run this software?" click on "Run" <BR> Type the desired path where you want to download and click on "Resume" <BR> After Downloading, the process of Unpacking will automatically start, you need not do anything now <BR> After unpacking is complete click on "Launch Install" <BR> The folder will open where the ISO file has been downloaded<BR> Enter an empty CD in the CD ROM and burn the ISO file on this CD. This CD is called the Live CD<BR>

Installing Windows XP
Boot up the computer with the above Windows XP Installation disk. <BR> Click any button to boot from the CD<BR> Setup will start loading files<BR> Press ENTER to setup Windows XP<BR> Click on F8 to agree to the agreement<BR> Use UP and DOWN arrows to select an item from the list, select C and Press ENTER. <BR> To continue setup press C<BR> Use the UP and DOWN arrows and Select "Format partition using NTFS file system (quick)" and Press ENTER<BR> Press F to format the drive <BR> Setup will start formatting <BR> Setup will then copy all the files <BR> Setup then initializes Windows XP configuration<BR> Then the Computer reboots<BR> When the computer reboots, either remove the live CD or when asked to press any button to start setup <BR> do not press any button <BR> Installing windows phase will start which will take around 35 minutes <BR> In the Regional and Language option click on "Customize" and select English (US)and click Next <BR> Enter the name as clesm-g and organization as CLESM and click Next<BR> Enter the product key which has been provided with the software. <BR> If you have forgotten the product key then log into your MSDNAA account here <BR> You can see the list of softwares you have downloaded, under the software which you have downloaded on your live CD click on "Download" which will lead you to another page<BR> Note down the serial number, it is your product key and click Next<BR> Enter the computer name and administrator password and click Next<BR> In the Date and time settings, set the time zone to GMT – 5:00 Eastern Time (US and Canada) and enter the date and time and click Next <BR> For Network Settings, select Typical Settings and click Next <BR> In the next step, choose the option No to the question "Do you want this computer to be a member of a domain?" and click Next<BR> Windows XP gets installed and system restarts <BR>

To set up the network do the following:<BR> After you have logged in click on Start>Settings>Control Panel>Network connections<BR> Right click on the Local Area Connection and click on Properties<BR> Under the Networking tab, select the item which ends with "TCP/IP" in brackets and click on Properties<BR> Select the option where you will have to enter the IP address, Subnet mask and Default gateway.<BR> Enter the following:<BR> <BR> Static IP address: 10.227.237.37<BR> Subnet mask: 255.255.255.0<BR> Default gateway: 10.227.237.1<BR> <BR> Then select the option you will have to enter the DNS server addresses: <BR> Preferred DNS: 128.227.116.4 <BR> Alternative DNS: 128.277.128.24 <BR> Click on OK <BR>

Partitioning the drive
Boot up the computer with the Ubuntu CD already in the drive slot.<BR> You will encounter a menu with 5 different options. Select the 'Install Ubuntu' option.<BR> In case it leads to warning or does not load for some reason, reboot the system by clicking Ctrl+Alt+Delete and when you<BR> reach the menu click F4 and choose Safe Graphics mode and then select the 'Install Ubuntu' option<BR> You will soon see a screen prompting you for the language selection. Make sure 'English' is selected and hit the Forward button.<BR> Next comes the Time Zone. Select 'New York' and hit the Forward button again.<BR> Now comes the keyboard layout. Select 'USA' and hit a few keys in the text area to ensure this setting is correct and hit Forward again.<BR> <BR> We are now ready to partition the drive.<BR> Our goal is the following:<BR> 1 x 8GB ntfs (for Microsoft Windows XP, already done)<BR> 7 x 4GB ext3 (1 for Ubuntu Hardy, the rest for future installs)<BR> 1 x 1GB swap (linux swap space)<BR> <BR> At the first menu select 'Manual' and then hit forward when it asks how you would like to partition the disk.<BR> The partition table should look like the following:<BR> /dev/sda<BR> /dev/sda1 ntfs<BR> free space<BR> <BR> Click on the 'free space' and hit the 'New partition' button.<BR> For 'Type for the new partition' select 'Primary'.<BR> For 'New partition size in MB' write in 4000.<BR> For 'Location for the new partition' select 'Beginning'.<BR> For 'Use as' select Ext3.<BR> You can leave 'Mount point' empty for now.<BR> Note that when you are back at the main partition screen the partition size will not be exactly 4000 MB. This is expected.<BR> Repeat the above steps until you have 7 partitions of 4 GB. Be sure that for these you select 'Logical' for 'Type for the new partition'.<BR> Otherwise, we will be limited to only 4 partitions total.<BR> There is now about 3.6 GB left. Use 2.6 GB of this for another logical partition.<BR> Now comes time to create our swap space. There should be 1GB left. Click the 'free space' and select 'New partition'.<BR> Everything will be the same except for the 'Use as' area. Select 'swap area' and click Ok.<BR> Now we need to select our '/' or root mount point.<BR> Click on /dev/sda2 and click 'edit'.<BR> For 'Mount point' select '/'. This is the partition we will be installing Hardy to.<BR> You will receive some warnings about mount points for the logical partitions. You can ignore these.<BR> <BR> The partition table should now look like the following:<BR> /dev/sda<BR> /dev/sda1 <=primary (our windows partition)<BR> /dev/sda2 <=primary (where we will install ubuntu)<BR> /dev/sda5 <=logical (note the jump in number)<BR> /dev/sda6<BR> /dev/sda7<BR> /dev/sda8<BR> /dev/sda9<BR> /dev/sda10<BR> /dev/sda11<BR> /dev/sda12<BR> <BR> We are now done partitioning. Click Forward to continue.<BR>

Installing Hardy
You will now be at a screen requesting your personal information. Fill in the appropriate fields and hit 'Forward'.<BR> You will now be asked about importing accounts. Do not. Hit 'Forward' to continue.<BR> The screen you are on now will give you an overview of your installation. Hit 'Install' when you feel comfortable.<BR> Depending on hardware this process can take 15 minutes to an hour.<BR> You will eventually be prompted to restart the computer. Do this and take the disk out when prompted.<BR> When the computer boots back up you'll be taken to a screen with a few boot options. For Ubuntu, select the topmost option and hit the enter key.<BR> If you make it to a log in screen, success!<BR>

Network information for hydra3
IP: 10.227.237.37 <BR> Subnet mask: 255.255.255.0 <BR> Gateway: 10.227.237.1 <--note that this is now 10.xxx instead of 128.xxx<BR> DNS: 128.227.116.4<BR> <BR> For Galileo:<BR> the correct settings in the file /etc/network/interfaces are:<BR>

auto eth0 <BR> iface eth0 inet static <BR> address 128.227.237.55 (galileo)<BR> gateway 128.227.237.1 <BR> network 128.227.237.0 <BR> broadcast 128.227.237.127 <BR>

The DNS nameservers in the file /etc/resolv.conf are: <BR>

search mae.ufl.edu <BR> nameserver 128.227.128.24 <BR> nameserver 128.227.116.4 <BR> nameserver 128.227.42.51 <BR>

Resolve internet connection problem in Hydra3
System>Administration>Network<BR> Click on the unlock tab and enter password.<BR> Change Gateway address for eth0 to: 10.227.237.1<BR> Click OK.<BR>

Success. An internet connection has been established.<BR> There appears to have been an issue with the host (hydra3) not being under the same subnet as the gateway. Whoops.<BR>

System updates
Many updates have been made since the creation of the Hardy .iso install CD.<BR> To update the repository information and download/install these updates do the following.<BR> sudo apt-get update<BR> sudo apt-get upgrade<BR> The following will output to the terminal screen.<BR> Enter 'y' and hit 'enter' to download and install the updates.<BR> Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: bind9-host dnsutils libbind9-30 libisccc30 libisccfg30 linux-generic linux-headers-generic linux-image-generic linux-restricted-modules-generic ssl-cert The following packages will be upgraded: acpi-support acpid alacarte anacron app-install-data-commercial apt apt-utils avahi-autoipd avahi-daemon base-files bsdutils compiz-fusion-plugins-main console-setup cpp-4.2 cupsys cupsys-bsd cupsys-client cupsys-common dbus dbus-x11 deskbar-applet eject eog evince evolution evolution-common evolution-data-server evolution-data-server-common evolution-exchange evolution-plugins firefox firefox-3.0 firefox-3.0-gnome-support firefox-gnome-support foo2zjs gcalctool gcc-4.2 gcc-4.2-base gdb gdm gedit gedit-common gksu gnome-about gnome-cards-data gnome-desktop-data gnome-games gnome-games-data gnome-panel gnome-panel-data gnome-power-manager gnome-system-monitor grub gstreamer0.10-tools gtk2-engines gtk2-engines-murrine gtk2-engines-pixbuf gtk2-engines-ubuntulooks gtkhtml3.14 guidance-backends gvfs gvfs-backends gvfs-fuse hal hal-info hpijs hplip hplip-data initramfs-tools initscripts iproute jockey-common jockey-gtk language-pack-en language-pack-en-base language-pack-gnome-en language-pack-gnome-en-base libavahi-client3 libavahi-common-data libavahi-common3 libavahi-compat-libdnssd1 libavahi-core5 libavahi-glib1 libavahi-ui0 libc6 libc6-i686 libcamel1.2-11 libcupsimage2 libcupsys2 libdbus-1-3 libebook1.2-9 libecal1.2-7 libedata-book1.2-2 libedata-cal1.2-6 libedataserver1.2-9 libedataserverui1.2-8 libegroupwise1.2-13 libexchange-storage1.2-3 libexif12 libffi4 libfreetype6 libgadu3 libgcc1 libgdata-google1.2-1 libgdata1.2-1 libgksu2-0 libglib2.0-0 libglibmm-2.4-1c2a libgnome-desktop-2 libgnutls13 libgomp1 libgphoto2-2 libgphoto2-port0 libgstreamer0.10-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtkhtml3.14-19 libgtksourceview2.0-0 libgtksourceview2.0-common libgvfscommon0 libgweather-common libgweather1 libhal-storage1 libhal1 libisc32 liblcms1 libldap-2.4-2 liblwres30 libnautilus-extension1 libnm-glib0 libnm-util0 libnspr4-0d libnss3-1d libntfs-3g23 libpanel-applet2-0 libpango1.0-0 libpango1.0-common libpcre3 libperl5.8 libpoppler-glib2 libpoppler2 libpurple0 libsmbclient libsmbios1 libsnmp-base libsnmp15 libsoup2.4-1 libssl0.9.8 libstdc++6 libtiff4 libvorbis0a libvorbisenc2 libvorbisfile3 libwnck-common libwnck22 libxml2 libxml2-utils libxslt1.1 linux-headers-2.6.24-19 linux-headers-2.6.24-19-generic linux-image-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic linux-restricted-modules-common login logrotate module-init-tools mount myspell-en-gb myspell-en-us myspell-en-za nautilus nautilus-data nautilus-sendto nautilus-share network-manager ntfs-3g ntpdate openoffice.org-base-core openoffice.org-calc openoffice.org-common openoffice.org-core openoffice.org-draw openoffice.org-gnome openoffice.org-gtk openoffice.org-help-en-gb openoffice.org-help-en-us openoffice.org-impress openoffice.org-l10n-common openoffice.org-l10n-en-gb openoffice.org-l10n-en-za openoffice.org-style-human openoffice.org-thesaurus-en-us openoffice.org-writer openssl passwd pciutils perl perl-base perl-modules pidgin pidgin-data poppler-utils procps python-apt python-gobject python-gtkhtml2 python-libxml2 python-uno python2.5 python2.5-minimal rdesktop readahead samba-common smbclient sudo sysv-rc sysvutils thunderbird-locale-en-gb totem totem-common totem-gstreamer totem-mozilla totem-plugins ttf-opensymbol tzdata ubuntu-docs ufw update-manager update-manager-core update-notifier update-notifier-common util-linux util-linux-locales vim-common vim-tiny vinagre xkb-data xserver-xorg-video-amd xserver-xorg-video-ati xserver-xorg-video-geode xserver-xorg-video-intel xsltproc xterm xulrunner-1.9 xulrunner-1.9-gnome-support yelp 247 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. Need to get 270MB of archives. After this operation, 1139kB of additional disk space will be used. Do you want to continue [Y/n]?

Moving /home to it's own partition
The following process was outlined in this guide as well as this guide.<BR> <BR> To take a look at our partition table run the following: sworkman@hydra3:~$ sudo fdisk -l Disk /dev/sda: 30.0 GB, 30020272128 bytes<BR> 255 heads, 63 sectors/track, 3649 cylinders<BR> Units = cylinders of 16065 * 512 = 8225280 bytes<BR> Disk identifier: 0xa033a033<BR> Device Boot     Start         End      Blocks   Id  System<BR> /dev/sda1  *           1         736     5911888+   7  HPFS/NTFS<BR> /dev/sda2            737        1222     3903795   83  Linux<BR> /dev/sda3           1223        3649    19494877+   5  Extended<BR> /dev/sda5           1223        1708     3903763+  83  Linux<BR> /dev/sda6           1709        2194     3903763+  83  Linux<BR> /dev/sda7           2195        2680     3903763+  83  Linux<BR> /dev/sda8           2681        3166     3903763+  83  Linux<BR> /dev/sda9           3167        3519     2835441   83  Linux<BR> /dev/sda10          3520        3649     1044193+  82  Linux swap / Solaris<BR>

sda5 through sda9 are all formated to ext3 and ready for use. We'll use sda5.<BR>

First we need to create a mount point.<BR> We'll create it under /mnt. sudo mkdir /mnt/newhome Next, mount the partition: sudo mount -t ext3 /dev/sda5 /mnt/newhome Next, copy files over from old /home:<BR> A regular cp will not do the job completely, so we'll use a command from the Debian archiving guide. The following command would not work using sudo. You must be logged in as root. cd /home find. -depth -print0 | cpio --null --sparse -pvd /mnt/newhome Unmount the new partition: sudo umount /mnt/newhome Backup the old /home: sudo mv /home /old_home Recreate the /home directory: sudo mkdir /home Mount the new /home: sudo mount /dev/sda5 /home Now we have to tell Ubuntu to mount the new home directory on boot. Add the following line to /etc/fstab: /dev/sda5 /home ext3 nodev,nosuid 0 2 Now it's time to reboot and see if everything goes smoothly.<BR> There appears to be permission problems with the $HOME/.dmrc file and .ICEauthority file. The following procedure will fix this.<BR> Boot the computer into Recovery Mode:<BR> Restart the computer and select the second entry (it will have 'Recovery Mode' next to it) After the boot up process is complete you'll be presented with a menu. Select the 'Drop to root shell prompt' entry. Enter the following commands (note that there is a set of commands for each affected user): chown -R sworkman:sworkman /home/sworkman chmod 644 /home/sworkman/.dmrc chmod 644 /home/sworkman/.ICEauthority chown -R vql:users /home/vql chmod 644 /home/vql/.dmrc chmod 644 /home/vql/.ICEauthority chown -R clesm-g:users /home/clesm-g chmod 644 /home/clesm-g/.dmrc chmod 644 /home/clesm-g/.ICEauthority exit You will now be back at the same menu as before. Check the 'Continue Normal Boot Process' and see if you able to log in without problems. After you have checked to make sure everything is in working order you can remove the old mount point we made under /mnt and the old home directory under /old_home sudo rm -r /mnt/newhome sudo rm -r /old_home Good to go now. Users are in their own partition and permission problems have been resolved.

Setting up root account
Ubuntu no longer sets a root password upon installation (security reasons). The following process outlines the steps needed to enable the root user: stephen@nix:~$ su Password: su: Authentication failure stephen@nix:~$ sudo passwd root [sudo] password for stephen: Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully stephen@nix:~$ su Password: root@nix:/home/stephen# whoami root root@nix:/home/stephen# exit exit stephen@nix:~$

Configuring SSH
The client is installed by default but to be able to log into the machine the server package is needed. Install using the following: sudo apt-get install openssh-server No further configuration is necessary. If you would like to change the default behavior of the openssh server application you can edit the following file: sudo vim /etc/ssh/sshd_config

= Preparing base system in euclid =

OS Installations
The goal here was to have Euclid running in a similar fashion to Hydra3.<BR> Euclid already had a fresh install of Windows XP so this partition was left alone.<BR> Using the steps outlined above for the Hydra3 installation, Euclid received a fresh install of Ubuntu Hardy Heron.<BR> There was one problem with the installation for Euclid. Booting into the install disk resulted in the following error:<BR> user not known to the underlying authentication module This was easily worked around by doing the following:<BR> Boot into the install disk like normal, selecting English as your primary language.<BR> Hit 'F4' to bring up different boot options.<BR> Select 'Safe Graphics Mode.'<BR> Now you can select 'Install Ubuntu' and it will proceed as it should.<BR>

Network information for euclid
IP: 10.227.237.42<BR> Subnet Mask: 255.255.255.0<BR> Gateway: 10.227.237.1<BR> DNS: 128.227.116.4, 128.227.116.1, 128.227.128.24, 128.227.42.51<BR> Search: mae.ufl.edu<BR>

Euclid customizations
The goal at this point is to have Hydra3 and Euclid running in the same manner. All changes to Hydra3 mentioned above (moving the /home partition, configuring an ssh server, etc) were all done with Euclid. For clarity and space I am not going to repeat these steps again here. Just note that everything done for Hydra3 was also done for Euclid.

= Grid computing =

SciLab

ProActive

ProActive applications

Find out how to access this applications web page from the home page of ProActive.

ProActive
ProActive is an open source software package for parallel, distributed, and multi-core programming. It will be the base of our grid framework for use with Scilab. The official site for ProActive can be found here.

Downloading ProActive
From the home page (linked above), click on the 'Downloads' tab and select 'ProActive Programming'.<BR> You will be directed to a page requesting some personal information and an email. Fill these fields out and click 'Go to the download page' button.<BR> You will now have to agree to the GNU General Public License for ProActive. Click the 'I agree' button at the bottom of the page to continue.<BR> You will finally be at the download page. There are a lot of different packages hosted on this page. The one we want is at the top under the heading "ProActive Programming: Java Parallel Frameworks -- Enterprise-ready Java Grid". There's no reason not to grab the most recent version so go ahead and click on 'ProActive Programming 4.0.2 (zip)'. A download dialog box will open. Save to the directory of your choice.

Installing ProActive
We need to first install the Sun Java Development Kit (JDK) 5.0. Other packages will be marked for installation such as the JRE which we also need.: sudo apt-get install sun-java5-jdk We now need to set the environment variable for the JDK (note BASH syntax!) Add the following to the .bashrc file in your home directory as well: export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun-1.5.0.16 ProActive will be installed beneath the /etc directory. Lets start by unzipping the the downloaded file. Assuming you saved the .zip to your home directory run the following command: unzip ProActive-4.0.2.zip A new directory will be present on the desktop with the same name (minus the .zip extension of course). We'll now move this under /etc using the following: sudo mv ProActive-4.0.2 /etc/proactive We now need to set the classpath for using ProActive to write applications.<BR> First cd to the install directory: cd /etc/proactive Next, enter the following (note that this is BASH syntax!): PA_PATH=$(pwd) export CLASSPATH=.:${PA_PATH}/lib/dist/ProActive_examples.jar:\ ${PA_PATH}/lib/dist/ProActive/ProActive.jar:${PA_PATH}/lib/dist/ibis:\ ${PA_PATH}/lib/dist/asm-2.2.1.jar:\ ${PA_PATH}/lib/dist/log4j.jar:${PA_PATH}/lib/dist/xercesImpl.jar:\ ${PA_PATH}/lib/dist/fractal.jar:${PA_PATH}/lib/dist/bouncycastle.jar:\ ${PA_PATH}/lib/dist/javassist.jar We now need to edit the java.policy file to set permissions: sudo vim /etc/java-1.5.0-sun/security/java.policy Now add the following lines: grant codeBase "file:/etc/proactive/*" { permission java.security.AllPermission; }; ProActive supports logging through log4j. It's a nice feature, so we might as well use it. Install log4j by running the following: sudo apt-get install liblog4j1.2-java The option -Dlog4j.configuration=file:pathToFile will specify which logging policy file to use within ProActive. An example of such a file is below. If you choose not to use one, ProActive will use the file proactive-log4j by default. # This file represents the log4j config file for non regression tests. # It is given as property (in the proactive.xml) when starting nonregression tests # The default logging level is INFO # The root logger logs in the test.log file log4j.rootLogger=INFO,CONSOLE # If INFO is enabled Jetty is too verbose at startup log4j.logger.org.mortbay = WARN ########### The following are existing categories in ProActive #log4j.logger.proactive = INFO #log4j.logger.proactive.classloader = DEBUG #log4j.logger.proactive.events = DEBUG #log4j.logger.proactive.runtime = DEBUG #log4j.logger.proactive.body = DEBUG #log4j.logger.proactive.mop = DEBUG #log4j.logger.proactive.groups = DEBUG #log4j.logger.proactive.sync_call = DEBUG #log4j.logger.proactive.deployment = DEBUG #log4j.logger.proactive.deployment.log = DEBUG #log4j.logger.proactive.deployment.process = DEBUG #log4j.logger.proactive.deployment.filetransfer = DEBUG,CONSOLE #log4j.logger.proactive.filetransfer = DEBUG #log4j.logger.proactive.nfe = FATAL #log4j.logger.proactive.gc = DEBUG #log4j.logger.proactive.ft = DEBUG #log4j.logger.proactive.ft.cic = DEBUG #log4j.logger.proactive.ft.pml = DEBUG #log4j.logger.proactive.communication.transport.http = DEBUG #log4j.logger.proactive.communication.rmi = DEBUG #log4j.logger.proactive.communication.ssh = DEBUG #log4j.logger.proactive.communication.transport.http = DEBUG #log4j.logger.proactive.migration = DEBUG #log4j.logger.proactive.communication.requests = DEBUG #log4j.logger.proactive.examples = DEBUG #log4j.logger.proactive.components = DEBUG #log4j.logger.proactive.components.requests = DEBUG #log4j.logger.proactive.components.activity = DEBUG #log4j.logger.proactive.components.bytecodegeneration = DEBUG #log4j.logger.proactive.components.adl = DEBUG #log4j.logger.proactive.components.gui = DEBUG #log4j.logger.proactive.p2p = DEBUG #log4j.logger.proactive.p2p.startservice = DEBUG #log4j.logger.proactive.p2p.vn = DEBUG #log4j.logger.proactive.p2p.vn.service = DEBUG #log4j.logger.proactive.p2p.nodes = DEBUG #log4j.logger.proactive.p2p.acquaintances = DEBUG #log4j.logger.proactive.p2p.first_contact = DEBUG #log4j.logger.proactive.p2p.skeletons = DEBUG #log4j.logger.proactive.p2p.skeletons.worker = DEBUG #log4j.logger.proactive.p2p.skeletons.manager = DEBUG #log4j.logger.proactive.p2p.daemon = DEBUG #log4j.logger.proactive.security = DEBUG #log4j.logger.proactive.security.node = DEBUG #log4j.logger.proactive.security.session = DEBUG #log4j.logger.proactive.security.body = DEBUG #log4j.logger.proactive.security.manager = DEBUG #log4j.logger.proactive.security.request = DEBUG #log4j.logger.proactive.security.runtime = DEBUG #log4j.logger.proactive.security.policy = DEBUG #log4j.logger.proactive.security.policyserver = DEBUG #log4j.logger.proactive.security.crypto = DEBUG #log4j.logger.proactive.security.psm = DEBUG #log4j.logger.proactive.skeletons = DEBUG #log4j.logger.proactive.skeletons.taskpool = DEBUG #log4j.logger.proactive.skeletons.structure = DEBUG #log4j.logger.proactive.skeletons.environment = DEBUG #log4j.logger.proactive.skeletons.application = DEBUG #log4j.logger.proactive.skeletons.diagnosis	 = DEBUG #log4j.logger.proactive.skeletons.system = DEBUG #log4j.logger.proactive.masterworker = DEBUG #log4j.logger.proactive.masterworker.workermanager = DEBUG #log4j.logger.proactive.masterworker.pinger = DEBUG #log4j.logger.proactive.masterworker.repository = DEBUG #log4j.logger.proactive.masterworker.workers = DEBUG #log4j.logger.proactive.configuration = DEBUG #log4j.logger.proactive.remoteobject = DEBUG #log4j.logger.proactive.jmx = DEBUG #log4j.logger.proactive.jmx.mbean = DEBUG #log4j.logger.proactive.jmx.notification = DEBUG ################ Appenders #################### # # Appender output can be configured by using a pattern layout # See: http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html # #   - %c the category of the logging event #  - %d the date #  - %m he application supplied message #  - %n the platform dependent line separator character or characters #  - %p the priority of the logging event #  - %t the name of the thread that generated the logging event #  - %X{hostname}         the hostname #  - %X{id@hostname}      the VMID and the hostname #  - %X{shortid@hostname} the short VMID and the hostname (a collision can occur between two shortids, you should use id@hostname) #  - %X{runtime}          the ProActive runtime url (does not work very well since a different MDC is associated to each thread) # CONSOLE appender is used by default log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=%X{shortid@hostname} - [%p %20.20c{2}] %m%n # Appender FILE writes to the file "tests.log". # This file is recreated a file for each run log4j.appender.FILE=org.apache.log4j.FileAppender log4j.appender.FILE.File=tests.log log4j.appender.FILE.Append=false log4j.appender.FILE.layout=org.apache.log4j.PatternLayout log4j.appender.FILE.layout.ConversionPattern=%5p [%t]: %m%n

Testing ProActive
To make sure everything is working properly we should run a few examples. The examples are located under /etc/proactive/examples. A few interesting examples to run are: The Reader/Writer Problem: /etc/proactive/examples/readers/reader.sh The Dining Philosophers Problem: /etc/proactive/examples/philosophers/philosophers.sh The N-Body Simulation (for use later, as a deployment example for multiple machines): /etc/proactive/examples/nbody/nbody.sh

= Scilab = Scilab is an open source platform for numerical computation and is the reason for which the ProActive grid interface was installed. The Scilab homepage can be found here. It is important to note that the current version of ProActive currently only supports up to version 4.1.2 of Scilab. The current stable version of Scilab is 5.1.

Downloading Scilab
For Scilab to function properly we will need to install version 4.1.2 from SOURCE. The download page is here or alternatively you can just download the file directly.

Installing Scilab
The first thing we need to do is unzip the .tar.gz file we downloaded. You may run the following: tar -xvzf scilab-4.1.2-src.tar.gz We'll now have the folder scilab-4.1.2 on the desktop. Let's move (and rename it to something easier) to /etc like we did with the ProActive installation. sudo mv scilab-4.1.2 /etc/scilab Now we can start the real installation. There are a few requirements we need to meet before we can start. Scilab requires a C compiler, a Fortran compiler, tcl, and a few other dependencies. Let's go ahead and install all these by running the following: sudo apt-get install gcc gfortran tcl tk-dev libxaw7-dev Go to the newly created Scilab directory: cd /etc/scilab We need to configure the system by issuing the following command: ./configure --with-gcc --with-gfortran If configure finishes without any errors you may continue. If it does you likely have some dependency issues. DO NOT CONTINUE until configure finishes successfully.<BR>

Now it's compile time. This may take about 15-20 minutes to complete. While still in the /etc/scilab directory run the following: make all We now need to install it into our path. Run the following in the /etc/scilab directory (if unsuccessful run 'make distclean' before attempting again): sudo make install Comment out the following line in the scilab.star file. sudo vim /etc/scilab/scilab.star Here's the line to comment out. It's on line 196: //show_startupinfo; We now need to complete the installation of ProActive. Go to the ProActive directory: cd /etc/proactive/compile Now it's time to compile. Run the following: ./build compile Attempting to run a test of Scilab from within ProActive resulted in the following error: sworkman@hydra3:/etc/proactive/examples/scilab$ ./scilab_test.sh .: 10: Can't open ./../../.././scripts/unix/env.sh Well, it turns out this file and scilab_env.sh are in the wrong place (or at minimum referenced incorrectly). Run the following commands to put them in the right place. mv /etc/proactive/examples/scilab/scilab_env.sh /etc/proactive/scripts/unix/scilab/scilab_env.sh mv /etc/proactive/examples/env.sh /etc/proactive/scripts/unix/env.sh We need to make a quick change to /etc/proactive/examples/scilab/scilab.sh as well. vim /etc/proactive/examples/scilab/scilab.sh Make corrections to look like the following: PROACTIVE=/etc/proactive Now we should be able to launch the Scilab Grid ToolBox: cd /etc/proactive/examples/scilab ./scilab.sh Success.
 * 1) PROACTIVE=$workingDir/../../../.