[Bigjob-users] [saga-users] Documentation for BigJob on SAGA Website

Ole Weidner oweidner at cct.lsu.edu
Sun Nov 13 16:13:54 CST 2011


I would *highly* recommend to make the saga/python.bigjob deployment in CSA based on 'virtualenv' (http://www.virtualenv.org/en/latest/index.html). This should spare you a lot of headaches! 

My 'pystrap.py' script might serve you well in this context -- it supports non-standard Python installations.You can find it here: https://gist.github.com/1321016

Cheers,
Ole


On Nov 13, 2011, at 6:27 AM, Andre Merzky wrote:

> No, not yet:
> 
> -bash-3.2$ python setup.py install $HOME/tmp_install/
> Traceback (most recent call last):
>  File "setup.py", line 5, in ?
>    from setuptools import setup, find_packages
> ImportError: No module named setuptools
> 
> -bash-3.2$ /N/soft/SAGA/external/python/2.7.1/gcc-4.1.2/bin/python
> setup.py install $HOME/tmp_install/
> Traceback (most recent call last):
>  File "setup.py", line 5, in <module>
>    from setuptools import setup, find_packages
> ImportError: No module named setuptools
> 
> Also, I am still having issues with the fact that this is putting
> another python binary into $SAGA_LOCATION...
> 
> 
> Cheers, Andre.
> 
> 
> On Sun, Nov 13, 2011 at 3:36 AM, Andre Luckow <aluckow at cct.lsu.edu> wrote:
>> HI Andre,
>> did you use the setup.py as documented at
>> http://faust.cct.lsu.edu/trac/bigjob/wiki/install?
>> 
>> python setup.py install --prefix=<target-dir>
>> 
>> Currently, it looks like that the BJ dependencies (e.g. threadpool and
>> redis) are not correctly installed in the CSA Python installation.
>> 
>> Thanks!
>> 
>> Best,
>> Andre
>> 
>> 
>> 
>> On Sat, Nov 12, 2011 at 11:29 AM, Andre Merzky <andre at merzky.net> wrote:
>>> Thanks for the catch, I'll update that!
>>> 
>>> Best, Andre.,
>>> 
>>> 
>>> 
>>> On Sat, Nov 12, 2011 at 4:56 PM, Melissa Romanus
>>> <melissa.romanus at rutgers.edu> wrote:
>>>> Hi all-
>>>> 
>>>> Apologies for the cross-post, but this is an issue regarding BigJob on
>>>> the SAGA deployments page.
>>>> 
>>>> Note that the for the FutureGrid deployments webpages (eg:
>>>> https://svn.cct.lsu.edu/repos/saga-projects/deployment/tg-csa/doc/README.saga-1.6.gcc-4.1.2.hotel),
>>>> BigJob is listed as living in
>>>> "BigJob is installed in
>>>> /gpfs/software/x86_64/el5/hotel/SAGA/saga/1.6/gcc-4.1.2//lib/python2.7.1/site-packages//bigjob
>>>> ."
>>>> 
>>>> This will path is wrong... and will not actually allow the user to
>>>> import bigjob from the CSA installation. Additionally, it has caused
>>>> me a significant amount of grief lately.
>>>> 
>>>> BigJob is installed at:
>>>> /gpfs/software/x86_64/el5/hotel/SAGA/saga/1.6/gcc-4.1.2//lib/python2.7.1/site-packages/saga/bigjob
>>>>  on hotel.
>>>> 
>>>> On sierra, /N/soft/SAGA/saga/1.6/gcc-4.1.2//lib/python2.7.1/site-packages/saga/bigjob
>>>> 
>>>> Note that the crucial missing piece of the puzzle is that it must say
>>>> "...site-packages/saga/bigjob" instead of "...site-packages//bigjob".
>>>> 
>>>> Please note that this issue persists for CSA deployment documentation
>>>> on sierra, alamo, hotel, and india.
>>>> 
>>>> Once you correct the PYTHONPATH to use the bigjob path that I
>>>> provided, users can import bigjob without any issues. Andre/Ole, can
>>>> you update the website?
>>>> 
>>>> Thanks,
>>>> -Melissa
>>>> _______________________________________________
>>>> saga-users mailing list
>>>> saga-users at cct.lsu.edu
>>>> https://mail.cct.lsu.edu/mailman/listinfo/saga-users
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Nothing is ever easy...
>>> _______________________________________________
>>> Bigjob-users mailing list
>>> Bigjob-users at mail.cct.lsu.edu
>>> https://mail.cct.lsu.edu/mailman/listinfo/bigjob-users
>>> 
>> 
> 
> 
> 
> -- 
> Nothing is ever easy...
> _______________________________________________
> Bigjob-users mailing list
> Bigjob-users at mail.cct.lsu.edu
> https://mail.cct.lsu.edu/mailman/listinfo/bigjob-users



More information about the Bigjob-users mailing list