Menu

Tree [r57] /
 History

HTTPS access


File Date Author Commit
 0.3 2011-02-28 samircury [r48] the table works, now I'm mesing around with sel...
 1.0 2012-07-14 samircury [r57] Adds the condor state map. Have to review what ...
 etc 2010-04-19 samircury [r37] adding observation about condor env
 usr 2010-04-19 samircury [r39] adding checks for configurations
 LICENSE 2009-03-27 samircury [r5] licenses upgraded
 NOTICE 2009-05-02 samircury [r8] almost finished
 README 2010-04-19 samircury [r34] adding documentation
 TODO 2009-12-05 samircury [r26] added TODO
 c4w.pl 2011-02-07 samircury [r42] now we can read the xml of a submitter
 submitter.xml 2011-02-07 samircury [r42] now we can read the xml of a submitter

Read Me

Ok, this is supposed to teach you how to setup your condor4web:

First things first - make sure you can run by hand "condor_q -l -global", if not, put condor binaries on $PATH

1 - Inflate the tarball under /usr/local/condor4web

take a short look on auto_sender.sh (condor4web.pl "doesn't work" without that)

2 - (analyze) If your webserver is local, you can exchange the "scp" command to a simple "cp" of the index of the desired location

3 - After that you have to put auto_sender.sh on Cron.

with the user that can run condor4web (everyone), and can do the ssh, call :

$crontab -e

so, insert a line like that :

*/2 * * * * /usr/local/condor4web/auto_sender.sh

4 - Make sure here about the permissions, and if the ssh is working, the best way is running auto_sender.sh by hand

This will configure to run every 2 minutes, i think it's a good "resolution", but you can 
change at will.

Ok, this is it, if you experience any trouble subscribe and write to 
condor4web-users@lists.sourceforge.net 

here's the link :

https://lists.sourceforge.net/lists/listinfo/condor4web-users





############# DEPRECATED ##############################

First you have to consider:

 * My webserver is the same machine that will run condor4web

 * My webserver isn't on the same machine (this is assumed by default)

So what you need in the 2 cases, first to setup a location for your condor4web, where 
you will inflate the tarball, i recommend /usr/local/condor4web

Ok, inflate there your tarball, after this file the more important is auto_sender.sh

It is a bash script, that you'll have to configure some parameters, and configurations on 
the machines, that vary depending on case, so I'll split them here:

(I am assuming that you have some knowledge about apache, but if you have some difficult, 
you can write me)

  - If your apache is LOCAL : 
    create a directory called condor4web on your DocumentRoot, like 
    /var/www/html/condor4web
    after that you have to configure on auto_sender the following variables:
    * LOCAL_DIRECTORY - > in the ## LOCAL APACHE ## section
    * Don't forget!!! comment ALL VARIABLES in ## REMOTE APACHE ## section
    * Plus comment the "scp" command line in the end of the archive, it's indicated where

  - If your apache is REMOTE

Observation : it transfers the index.html via ssh(scp), so, be sure that the localuser 
that will run condor4web will have granted access on the user@webserver whithout 
password, and pay attention too in the permissions of the remote webserver's directory 
that condor4web will be hosted in (the remote user need to have write permissions on the 
condor4web remote location). If you understand this, then proceed.

   * REMOTE_WEBSERVER => the machine who is webserver (you must run sshd too)
   * REMOTE_USER => the user that shold be used to do for example ssh foo@webserver 
(whithout password) (you should configure priv/pub keys for that)
   * WEBDIR_FULLPATH => directory where the remote user will write the index.html 
(consequently if is on DocumentRoot/condor4web) users will have to access 
your.webserver.com/condor4web
   
   * If your sshd on the webserver isn't on the standard port (22), include "-p 
<portn>" on the beginning of the scp command at the end of the file
   * don't forget to check if everything's ok with SSH, otherwise, it won't work

########## /DEPRECATED #############################################################