On Wed, Oct 14, 2009 at 10:00:40AM +1100, Mark Goodwin wrote:
> Martin Hicks wrote:
>> We still have a bit of a build problem with PCP and the bits that
>> require infiniband in order to build correctly. This currently means
>> the ib PMDA and the cluster PMDA. Upstream debian is still being built
>> without a build-dep on infiniband. It looks like I have a special
>> repository added in order to get these dependencies:
>>
>> deb http://pkg-ofed.alioth.debian.org/apt/ofed ./
>>
>> However, both Redhat and SuSE now ship ofed with their products. I
>
> but are they shipping the version with Max's change included?
> (was that v1.4?). Without that, the IB PMDA wont work, or did we
> figure out a workaround for that? In any case, it's complicated
> because some of the already released Red Hat and SuSE products will
> not have the right version of the library, or wont have it at all.
I think 1.4 is correct. You're right that this complicates matters...
Can we do some magic like
%if %rh_version > X || %suse_version > 11
BuildRequiress: libibmad-devel libibumad-devel libibcommon-devel
%endif
>
>> would like to see a Build-dep added to the specfile to get these PMDAs
>> to build, but I don't like adding another dependency to the core pcp
>> RPM.
>>
>> How should this be handled? Should we just stick the ib PMDA into a
>> separate sub-package, like pcp-infiniband?
>
> yeah that'll work. I can pull together the RPM spec changes to make
> this happen fairly easily (and I assume Nathan can ditto for deb).
>
>>
>> The dependencies for the cluster PMDA are only really build-time. If
>> you run the cluster PMDA you'll currently end up with a log message
>> about failing to open the local context to the ib pmda (or something
>> else like that...I'll have to check this out). If I'm wrong, then this
>> is what *should* happen. :)
>
> can we some how manage the dependency between the cluster PMDA and the
> IB PMDA, or should the cluster PMDA go into it's own sub-package too?
I'm not sure that there really are dependencies. There is certainly no
hard requirement that the cluster PMDA monitor infiniband. SGI
certainly has this use-case, but others may just want the
ultra-lightweight push-style monitoring from cluster PMDA for core
metrics. This works fine with the cluster PMDA.
I think I just need to verify that the cluster PMDA issues a useful
error message if the IB pmda is not found or not loaded correctly.
In terms of ensuring that there is a new enough version of the IB
libraries, I would hope that there's some kind of versioning info that
could be checked at runtime...
mh
|