pcp
[Top] [All Lists]

Re: [pcp] building PCP with IB build deps

To: Martin Hicks <mort@xxxxxxxx>
Subject: Re: [pcp] building PCP with IB build deps
From: Jeff Hanson <jhanson@xxxxxxx>
Date: Tue, 13 Oct 2009 21:16:17 -0400
Cc: Mark Goodwin <goodwinos@xxxxxxxxx>, pcp@xxxxxxxxxxx
In-reply-to: <20091014002417.GD4792@xxxxxxxxxxxxxxxxx>
Organization: SGI
References: <20091013191506.GG11060@xxxxxxxxxxxxxxxxxxxxxxxxx> <4AD50698.4030601@xxxxxxxxx> <20091014002417.GD4792@xxxxxxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.22 (X11/20090609)
Martin Hicks wrote:
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

rh would be 5.3.

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

_______________________________________________
pcp mailing list
pcp@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/pcp


--
-----------------------------------------------------------------------
Jeff Hanson - jhanson@xxxxxxx - Field Technical Analyst

You can choose a ready guide in some celestial voice.
If you choose not to decide, you still have made a choice.
You can choose from phantom fears and kindness that can kill;
I will choose a path that's clear
I will choose freewill. - Lee/Lifeson/Peart

<Prev in Thread] Current Thread [Next in Thread>