perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.]" <>]

Hi Mark,

 

I’ve took this little project off the shelf and tried to build pscheduler in a vagrant VM.  I started the make but  it bombed while building jq.

 

Thanks,

George

 

#

# BUILDING jq

#

 

make[1]: Entering directory `/home/uhl/pscheduler/jq'

rm -rf ./rpmbuild ./BUILD-ROOT build.log *.rpm *.src.rpm

find . -name '*~' | xargs rm -rf

find . -depth -name Makefile \

    -exec /bin/sh -c \

    '[ "{}" != "./Makefile" ] && make -C `dirname {}` clean' \;

rm -rf rpmbuild

mkdir -p ./rpmbuild/BUILD ./rpmbuild/RPMS ./rpmbuild/SOURCES ./rpmbuild/SPECS ./rpmbuild/SRPMS 

cp jq.spec ./rpmbuild/SPECS

cp jq-1.6.tar.gz ./rpmbuild/SOURCES

cp jq-1.6-00-jv_is_integer_large.patch ./rpmbuild/SOURCES

mkdir -p BUILD-ROOT

set -o pipefail \

                && HOME=/home/uhl/pscheduler/jq \

                   rpmbuild-with-deps -ba \

              --buildroot /home/uhl/pscheduler/jq/BUILD-ROOT \

              jq.spec 2>&1 \

       | tee build.log

Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.oRniyo

Patch #0 (jq-1.6-00-jv_is_integer_large.patch):

patching file src/jv.c

patching file src/jv.h

Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qat4yk

 

 

RPM build errors:

Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.t70oal

+ umask 022

+ cd /home/uhl/pscheduler/jq/rpmbuild/BUILD

+ cd /home/uhl/pscheduler/jq/rpmbuild/BUILD

+ rm -rf jq-1.6

+ /usr/bin/gzip -dc /home/uhl/pscheduler/jq/rpmbuild/SOURCES/jq-1.6.tar.gz

+ /usr/bin/tar -xf -

+ STATUS=0

+ '[' 0 -ne 0 ']'

+ cd jq-1.6

+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .

+ cat

+ echo 'Patch #0 (jq-1.6-00-jv_is_integer_large.patch):'

Patch #0 (jq-1.6-00-jv_is_integer_large.patch):

+ /usr/bin/cat /home/uhl/pscheduler/jq/rpmbuild/SOURCES/jq-1.6-00-jv_is_integer_large.patch

+ /usr/bin/patch -p1 --fuzz=0

patching file src/jv.c

patching file src/jv.h

+ exit 0

Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.hRc5Er

+ umask 022

+ cd /home/uhl/pscheduler/jq/rpmbuild/BUILD

+ cd jq-1.6

+ autoreconf -fi

Use of uninitialized value $msg in concatenation (.) or string at /usr/bin/autom4te line 1026.

Use of uninitialized value $stacktrace in pattern match (m//) at /usr/bin/autom4te line 1026.

unknown channel HECK_MATH_FUNC(nexttoward)

])

m4trace:configure.ac:194: -1- AC_C at /usr/share/autoconf/Autom4te/Channels.pm line 638.

       Autom4te::Channels::msg('HECK_MATH_FUNC(nexttoward)\x{a}])\x{a}m4trace:configure.ac:194: -1- AC_C', undef, 'warning: ', 'partial', 0) called at /usr/bin/autom4te line 1026

aclocal: error: echo failed with exit status: 1

autoreconf: aclocal failed with exit status: 1

error: Bad exit status from /var/tmp/rpm-tmp.hRc5Er (%build)

 

 

RPM build errors:

    Bad exit status from /var/tmp/rpm-tmp.hRc5Er (%build)

make[1]: *** [build] Error 1

make[1]: Leaving directory `/home/uhl/pscheduler/jq'

make: *** [packages] Error 2

[root@psdev1 pscheduler]# 

 

 

From: <> on behalf of Mark Feit <>
Reply-To: Mark Feit <>
Date: Monday, February 1, 2021 at 10:31 AM
To: "George.D.Uhl" <>, "" <>, "" <>
Subject: Re: [perfsonar-user] [EXTERNAL] Re: Adding homegrown tools to perfsonar

 

Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.] writes:

 

I went ahead and tried to add the TCPping client into the suite of pscheduler tools for RTT.  Using subversion, I downloaded the latest trunk branch of the pscheduler package off github and followed the instructions provided here: https://github.com/perfsonar/pscheduler/tree/master/scripts/PDK. I completed steps #1 and #2 but I’m stuck on #3.  I don’t see anything called “cbic” anywhere in the package.    If I don’t need to do that step, how do I get my tool recognized by pscheduler?

 

There’s a missing step:  The plugin needs to be developed on a system that’s set up for pScheduler development.  (Ed:  That should probably be mentioned in the docs.)  You’re one of a very few people outside the project who’s taken on plugin development, so we’ll use this process to fill in the gaps.

 

The quickest route to that is with Vagrant.  I have a Vagrantfile that builds up a set of CentOS 7 systems that’s properly configured for development:  https://github.com/perfsonar/pscheduler/blob/master/scripts/vagrant/dev-cluster/Vagrantfile.  Do the following:

 

• Fork pScheduler into to your own GitHub account.
• Follow the instructions at the top of the Vagrantfile.  You’ll probably want to set the number of machines to 1 unless you need two.
• Log into the VM as yourself per the instructions.
• Become root (sudo -i).
• cd /local/<yourlogin>
• Clone the forked repository (git clone https://github.com/george/...)
• cd pscheduler
• Check out the current production branch (git checkout 4.3.2)
• make
• Wait awhile.  When the make finishes, you’ll have a system with a fully-functioning pScheduler (but none of the toolkit’s other ameneties).
• Go through the development process as outlined in the PDK.  The missing ‘cbic’ is a target in a Makefile template I developed that stands for “clean, build, install, clean” and will compile the plugin into an RPM and install it.

 

If you need some Zoom time to get underway, I have some time over the next few days that’s not spoken for.

 

--Mark