Skip to content

Commit ac6b6b3

Browse files
graeme-a-stewartdrbenmorgan
authored andcommitted
Packaging minutes from 2018-03-07
1 parent 51103c7 commit ac6b6b3

File tree

1 file changed

+101
-0
lines changed

1 file changed

+101
-0
lines changed
Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
---
2+
title: "HSF Packaging Group Meeting #20, March 7, 2018"
3+
layout: default
4+
---
5+
6+
# {{page.title}}
7+
8+
Agenda
9+
======
10+
[https://indico.cern.ch/event/708110/](https://indico.cern.ch/event/708110/)
11+
12+
Participants: Ben Morgan, Graeme Stewart, Lucio Anderlini, Patrick
13+
Gartung, Oana Boeriu, Giulio Eulisse, Pere Mato, Shazad Malik Muzaffar,
14+
Emil Obreshkov, Guilherme Amadio, Geri Ganis, Emil Obreshkov
15+
16+
Introduction - Graeme
17+
=====================
18+
- Group invited to Naples WLCG/HSF Software Development session
19+
- All welcome, though time (AM Central Europe) not optimal for all
20+
people!
21+
- As always, suggestions for additional talks in future welcome.
22+
23+
Use Cases - Graeme
24+
==================
25+
- [Document](https://docs.google.com/document/d/1h-r3XPIXXxmr5tThIh6gu6VcXXRhBXtUuOv14ju3oTI/edit?usp=sharing)
26+
at "v0.99"
27+
- Refined to remove (but
28+
[archive](https://docs.google.com/document/d/1dsgq_ba9WYd69yX6EKOwwaZCT26LJ3UbS7WTrlzXEZc/edit?usp=sharing))
29+
useful discussion on ease of use by end clients.
30+
- Editing to focus on Use Cases rather than Requirements, though
31+
some blurring.
32+
- Any remaining questions to go from 0.99-\>1.00?
33+
- Look through of document:
34+
- Build section mostly unchanged, some additions on
35+
interoperability between different via build config files
36+
(pkg-config/CMake)
37+
- Want to be clear on separation between responsibility of
38+
build system (developer) vs package manager (librarian)
39+
- Comments that this is more on Software Development side.
40+
- Install time relocatability not always required by all
41+
experiments, but keep it in to cover everyone.
42+
43+
Test Stack - Ben
44+
================
45+
- List of packages now in a reasonable state.
46+
- Ben will send round a mail requesting input on "how to" on
47+
installing stack through considered package managers. Only
48+
consider install/build from scratch, no CVMFS just yet, just build
49+
from scratch on a bare metal Linux/macOS box.
50+
51+
Spack Status/Open Issues Discussion - All
52+
=========================================
53+
- Starting point using Javier's presentation, initially three
54+
questions:
55+
- Need a higher/more generic layer of software to configure Spack?
56+
- Patrick: almost certainly if we don't want spack itself to
57+
become a kitchen sink.
58+
- From developer point of view, likely not going to run spack
59+
directly.
60+
- Main config: `packages.yaml` file to use/reuse packages from
61+
system or LCG. Right now this is awkward. Solution could
62+
be, e.g., SpackDev may generate this automatically.
63+
- How do you manage the Spack configuration when building full
64+
stack?
65+
- Patrick: Looking at [Lmod](https://lmod.readthedocs.io/en/latest/)
66+
to configure used packages, but
67+
issues with tracking a large number of dependencies and
68+
more than one core compiler. Also, "stack" spack on top of
69+
system by linking/softlinking system packages into area
70+
known by spack. Jim A looking at better way of doing this
71+
to track dependencies better than simple links; idea is to
72+
allow spack to read multiple spack-db files (i.e., local
73+
and pre-installed).
74+
- Patrick: Lmod seems to be the way to go for setting up an
75+
environment portability across systems (local vs
76+
supercomputing) compared with say Scram/UPS. Question:
77+
what does lmod add vs EnvModules? Patrick: Use Lua rather
78+
than TCL, plus extra features such as "axes" for
79+
compiler/system etc. (though only three axes at the
80+
moment).
81+
- How to distribute software using Spack?
82+
- Patrick: Benedikt Riedel, from IceCube, was
83+
trying install/use of spack on CVMFS.
84+
- Question: Is spack not relocatable on CVMFS? Patrick: yes,
85+
apart from a few cases where absolute paths are compiled
86+
in (e.g., TCL). O.k. if can guarantee CVMFS mount point.
87+
- Patrick: looking at checking/editing binaries (via strings)
88+
to see/fix up packages. Giulio: In AliBuild, store all
89+
path info hash, and have only use of dynamic loader path.
90+
CMSSW: Install part, relocate part, so can handle install
91+
not equal to relocate path.
92+
- General discussion:
93+
- Giulio: Good to have generated files to help pick up
94+
packages from system. Patrick: Jim A has something in
95+
SpackDev to do this.
96+
- Patrick: Will probably find more issues as we go along at
97+
FNAL.
98+
99+
AOB
100+
===
101+
Next Meeting: 21 March 2018. Look again at Nix from Chris Burr.

0 commit comments

Comments
 (0)