No, igwn-dev-node
.
igwn-submit-node
is for things needed to support analysts designing and submitting HTCondor workflows.
Updated to include texlive-revtex4-1
.
@duncanmmacleod Is igwn-submit-node
the correct place to specify this dependency?
There's probably more, but I guess is the goal here to just be able to build LALSuite or run the testsuite as well? From my usage it'd be good to be able to run the test suite as well so I can just use this for setting up the test containers.
refs: computing/helpdesk#3814
@duncanmmacleod, sorry for late response, I am not actively monitoring this group/project.
the emfollow-* instances have a set of puppet rules to provide this set of functions however there is more than just dnf install <list of packages>
packages
ensure_packages(
[
'puppet-agent',
'httpd',
'mod_ssl',
'shibboleth',
'cvmfs',
"redis",
"python3-ligo-segments",
"ligo-proxy-utils",
'systemd-networkd',
'texlive-bibtex',
'python39-devel',
],
{ ensure => 'present' }
)
ensure_packages(['dejavu-sans-fonts','dejavu-sans-mono-fonts', 'dejavu-fonts-common'],
{ ensure => 'present' })
then you have a variety of systemd unit files (wait for network shares to be up), cron jobs (ensure the persistence of redis data in a somewhat tidy way), apache configuration files (gwcelery and flower reverse proxy) ...
Lately I've been adding systemd unit dropins to allow for larger ring buffer on /dev/shm/kafka (with differing rules different instances to allow for larger MDC or larger live data.
I want to point out that all that is only SUPPORTING gwcelery. AFAIK, gwcelery itself is "packaged" and deployed by the project themselves as a poetry driven virtual environment build in gitlab CI and residing in the matching emfollow-* shared account home dir
(edits: fix typos)
Adam Mercer (c2d9fbb4) at 10 Feb 00:09
igwn-packaging-test: fix date
Adam Mercer (cb01c7bb) at 09 Feb 23:49
igwn-packaging-test: add igwn-lalsuite-devel
Adam Mercer (32d92a99) at 09 Feb 23:39
igwn-packaging-test: remove igwn-lalsuite-devel
I like the idea of igwn-data-tools
that starts with framel
, which is not current a dependency of any other metapackage.
It might be nice to test each metapackage in isolation, in its own test
stage CI job.
To avoid having to hardcode the list of metapackages into the CI config, this likely requires a dynamic child pipeline.
Shouldn't be too hard and might be a nice simple case to extend to other projects.
This MR implements #62.
Adam Mercer (5fa77eb4) at 31 Jan 18:00
Merge branch 'dynamic-test-pipeline' into 'main'
... and 2 more commits
This MR implements #62.
@adam-mercer, this is now (finally) ready to be reviewed, after a few false-positive pipeline results (failing to properly propagate the non-zero exit code up the stack).
I have prepared !133 to start fixing the failing igwn-lalsuite-dev
tests.
This MR fixes #64.
I would merge this first to formally expose the bug, and then we can use the improved CI to test the fix.
The igwn-lalsuite-dev{el}
metapackage is missing many of the Python packages necessary to ./configure
LALSuite properly.
This is now exposed by !131:
+ ./configure
...
=== configuring in lal (/builds/duncanmmacleod/metapackages/lalsuite/lal)
configure: running /bin/bash ./configure --disable-option-checking '--prefix=/builds/duncanmmacleod/metapackages/lalsuite/_inst' --cache-file=/dev/null --srcdir=.
...
checking /usr/bin/python3 version... 3.7
checking for sysconfig... yes
checking for NumPy... configure: error: could not import NumPy
configure: error: ./configure failed for lal
Install igwn-lalsuite-dev{el}
on an otherwise empty system and then run
WORKING_DIR=$(mktemp -d)
git clone https://git.ligo.org/lscsoft/lalsuite.git ${WORKING_DIR}
cd "${WORKING_DIR}"
./00boot
./configure
After installing only igwn-lalsuite-dev{el}
at least the ./configure
should work, ideally make && make install
as well (but probably not make check
, not sure).
Sorry, I missed this until now.
I would pedantically argue (but not hold too firm) that we define a new metapackage for this (igwn-data-tools
, or similar), or just ask the CIT puppet configuration to handle this.