Hi Adrian,
Adrian Sevcenco wrote:
> On 05/22/2014 01:19 PM, Jan Just Keijser wrote:
>
>> Hi Adrian,
>>
> Hi!
>
>
>> Adrian Sevcenco wrote:
>>
>>> Hi! I am looking for the emi-ui tarball in
>>> http://repository.egi.eu/mirrors/EMI/tarball/ and i see none ..
>>> Is there a problem with the tarballs?
>>> The target systems are fedora 20 and ubuntu.
>>>
>>>
>>>
>> The EMI tarballs are notoriously hard to find :)
>> I found the emi-ui-2.10.5 tarball here
>> http://repository.egi.eu/mirrors/EMI/tarball/test/sl6/emi2-emi-ui/
>>
>> and emi3 stuff seems to be present in
>> http://repository.egi.eu/mirrors/EMI/tarball/test/sl[56]/emi3-emi-{ui,wn}/
>>
> thanks! :) actually i ignored "test" dir .. it sounded fishy :)
>
>
>> At Nikhef we're using the emi-ui-2.10.5 tarball on a shared NFS volume
>> on both SL5 and SL6 - this required a little bit of hacking, as some SL5
>> libraries are not present on SL6 (libssl.so.6, libcrypt.so.6). For
>>
> yeah, i tried to install in fedora 20 the emi-ui directly from sl6 repos
> and i was hit by those .. i solved them but i could not get past errors
> like:
>
> Error: Package: SAGA.lsu-cpp.engine-1.6.0-1.sl6.x86_64 (EMI-3-third-party)
> Requires: libboost_thread-mt.so.5()(64bit)
> Error: Package: nordugrid-arc-python-3.0.3-1.el6.x86_64 (EMI-3-updates)
> Requires: libdb_cxx-4.7.so()(64bit)
> Error: Package: nordugrid-arc-python-3.0.3-1.el6.x86_64 (EMI-3-updates)
> Requires: python(abi) = 2.6
> Installed: python-2.7.5-11.fc20.x86_64 (@updates)
> python(abi) = 2.7
> python(abi) = 2.7
> Installed: python3-3.3.2-11.fc20.x86_64 (@updates)
> python(abi) = 3.3
> Available: python-2.7.5-9.fc20.i686 (fedora)
> python(abi) = 2.7
> python(abi) = 2.7
> Available: python3-3.3.2-8.fc20.i686 (fedora)
> python(abi) = 3.3
> Error: Package: unicore-hila-unicore6-2.4.1-1.sl6.noarch (EMI-3-updates)
> Requires: java-1.6.0-openjdk
>
> of course:
> root@sev-iss: ~ # rpm -qa boost
> boost-1.54.0-9.fc20.x86_64
>
> root@sev-iss: ~ # rpm -qa python
> python-2.7.5-11.fc20.x86_64
>
> root@sev-iss: ~ # rpm -qa python3
> python3-3.3.2-11.fc20.x86_64
>
> root@sev-iss: ~ # rpm -qa | grep openjdk
> java-1.7.0-openjdk-devel-1.7.0.60-2.4.7.0.fc20.x86_64
> java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc20.x86_64
> java-1.7.0-openjdk-headless-1.7.0.60-2.4.7.0.fc20.x86_64
>
> root@sev-iss: ~ # rpm -qa | grep libdb-cxx
> libdb-cxx-5.3.28-1.fc20.x86_64
> libdb-cxx-devel-5.3.28-1.fc20.x86_64
>
> so, it seems that there are some hard requires instead of a minimum
> version.. given that (it seems to me) fedora 20 have similar versions
> with rhel7 i would expect that the current versions not to work also in
> rhel 7.
>
> also, notable, is that a client version that should be universally
> available in order to use the respective technology, in the current
> implementation restrict the usage to only one OS (rhel&clones).
>
>
the dependencies you list are dependencies for the YUM repo's ; there
should be separated builds for Debian with different OS-specific
dependencies for those. However, as long as you are not using the SAGA,
unicore or nordugrid-arc then the UI tarball should work on FC20.
I do agree that the client code should be as distro-independent as
possible, but with the way things are built this is nearly impossible.
This is not specific to EMI but to most modern software: the stack of
dependencies grows so high so quickly that you're binding yourself to a
particular set of packages/RPMs in no time, and therefore are bound to a
particular platform.
>> Fedora20 I'd aim for the SL6 release.
>> There is currently no (real) YAIM support to configure the tarball, but
>> you can/must run yaim in order to properly configure the tarball. I've
>> hacked a site-info.def file for this, but of course that's quite
>> site-specific :)
>> Finally, it seems that no proper grid-env.{sh,csh} file is written out
>> by YAIM , and the support functions from glite 3.2 are also gone (e.g.
>> grid-env-funcs.sh contains 'gridpath_prepend' etc). I've hacked together
>> a grid-env.sh file that I'd be happy to share.
>>
> well, i would happy receive your hard work gathered experience and
> wisdom for both site-info.def and grid-env.sh and pass them along to my
> collaborators :)
>
>
>
I'll mail you the files off-list; once we've sorted out the
site-specific issues then we can make these files more publicly available.
HTH,
JJK / Jan Just Keijser
Nikhef
Amsterdam
|