Meeting of the Technical Steering Committee (TSC) Board

Transcription

1 Meeting of the Technical Steering Committee (TSC) Board Tuesday, January 8 th 11:00am ET

2 Meeting Logistics United States : +1 (510) (No PIN needed).

3 Antitrust Policy Notice Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation. 3

4 Agenda Some year end usage stats Review Cycle #5 Quick Change of Status Update Rsync server for OpenHPC repository System Registration Page Continue the RPM dependency discussion from last time... 4

5 Updated Usage/Access Statistics (thru 2017) Build Server Access: Unique Visitors # of Unique Visitors v1.0 Releases v1.0.1 v1.1 v1.1.1 v1.2 v1.2.1 v1.3 v1.3.2 v1.3.1 v1.3.3 Stats for build/repo server (tracking # of unique visitors per month and amount of data downloaded): 0 Jul-15 Oct-15 Jan-16 May-16 Aug-16 Nov-16 Mar-17 Jun-17 Sep-17 Dec-17 ~16 TB downloaded in 2017 Data Transfer Amount (GiB) Build Server Access: Data Downloaded v1.0 v1.1 v1.2 v1.3 v1.3.2 Releases v1.0.1 v1.1.1 v1.2.1 v1.3.1 v Jul-15 Oct-15 Jan-16 May-16 Aug-16 Nov-16 Mar-17 Jun-17 Sep-17 Dec Average # of vistors/month

6 Updated Usage/Access Stats (thru 2017) OpenHPC Package Repo Access 900 These stats monitor access specifically to package repository metadata (typically expected to be via yum/zypper) # Unique Visitors Repo access binned by minor version Nov-15 Dec-15 Jan-16 Feb-16 Mar-16 Apr-16 May-16 Jun-16 Jul-16 Aug-16 Sep-16 Oct-16 Nov-16 Dec-16 Jan-17 Feb-17 Mar-17 Apr-17 May-17 Jun-17 Jul-17 Aug-17 Sep-17 Oct-17 Nov-17 Dec-17

7 PEARC 17 tutorial (thru 2017) Recall we made the PEARC slides available in July 2017 after the tutorial Pointer from our GitHub site provides majority of referrers unique accesses in 2017

8 Review Cycle #5 openhpc / submissions Review #5 No due date 0% complete 6 Open 0 Closed Open UCX #27 opened 7 days ago by shamisp 9 of 21 slurm-spank-x11: x11 forwarding plugin for srun #28 opened 23 hours ago by adrianreber 10 of 22 MFEM #29 opened 15 hours ago by acfisher 10 of 21 GEOPM - Global Extensible Open Power Manager #25 opened on Nov 11 by cmcantalupo 10 of 22 DMTCP for openhpc #26 opened 27 days ago by shlomiya 10 of 22 LBNL NHC #24 opened on Oct 9 by novosirj 10 of 22 Edit milestone New issue From last time, our proposed reviewer deadline was January 5 th - Had a request for one extension - Also, looks like a number of folks could are still working on their reviews - Can we try to shoot for completion by next Monday, January 15th?

9 Status Update from Karl I am planning on returning to academia at UT Austin as a research faculty in mid-february Committed to serving my TSC term - might possibly need cancel a meeting or two during the transition Please feel free to voice any concerns you might have here - can also ping Jeff 9

10 Rysnc Server At SC 17 BoF, we had a question asking if we could enable rsync for mirroring of OpenHPC repositories We have control over the back end, so have enabled rsync access to: Followed up with the requesting user who tested it out satisfactorily Note: one concern we had was the ability to track downloads via this mechanism - other downloads thru yum/zypper log entries with web server - rsync has separate protocol - have updated the logging infrastructure on build server so we can track downloads made thru rsync Any objection to advertising this capability on ohpc wiki? - typical mirror (avoiding src RPMs) looks like: $ rsync -avzh --exclude src --exclude repocache --delay-updates rsync://build.openhpc.community/openhpc/1.3/

11 System Registration Page Recall, system registration page now published on wiki: Question that came up on TSC discussion list: - do we want to extend the current form to ask about architecture? (e.g. aarch64 or x86_64) 11

12 Renew RPM dependency discussion... 12

13 RPM dependencies Recall previous TSC discussion where we discussed the fact that we currently have some namespace collision with base OS packages with respect to.so libraries: # repoquery --whatprovides "libopenblas.so.0()(64bit)" openblas-0: el7.x86_64 openblas-gnu7-ohpc-0: ohpc.x86_64 # repoquery --whatprovides "libltdl.so.7()(64bit)" libtool-ltdl-0: el7_3.x86_64 libtool-ohpc-0: x86_64 This can lead to *base* system package installation breakage in that most ohpc provided.so s are not automatically included in ld search path Adrian discussed a potential remedy that involved disabling RPM s internal dependency generator and override with scripts to provide smaller Provides/Requires conditions leveraging our modules configuration 13

14 RPM dependencies Have spent some additional time diving more into this and wanted to share some of the things I ve learned and show another potential alternative - there are multiple dependency generators associated with RPM - will sometimes see them referred to as internal vs external dependency generator The external tools are apparently the old mechanism and are scripts that get called after the build completes: /usr/lib/rpm/find-requires /usr/lib/rpm/find-provides The internal tools are the new default. They are binaries, e.g. /usr/lib/rpm/rpmdeps /usr/lib/rpm/elfdeps 14

15 RPM dependencies The older find-requires/find-provides scripts are convenient to use as starting templates to modify for local needs However, one thing that confused me initially is that they can t reproduce all the dependencies found with newer tool - new tool embeds additional color information - Can see this explicitly with our gcc packaging: - old style generator (find-requires) calls out 38 dependencies for our gcc build - new style (rpmdeps) calls out 57 dependencies Example dependency with old style generator: - libquadmath.so.0()(64bit) And example with new generator: - libquadmath.so.0()(64bit) - libquadmath.so.0(quadmath_1.0)(64bit) 15

16 RPM dependencies The new dependency tool has a plugin infrastructure which allows you to call out to your own dependency generator on a per path (and per file type basis) An alternative approach we might consider (approach #2) is to use this functionality to append an additional color delimiter of our choosing (e.g. ohpc ) to all.so s contained in a non-standard path - i.e. our packages that install into /opt/ohpc This would avoid any namespace collision with distro packages Have a prototype in place on our OBS system. This approach adds 3 new files to our ohpc-buildroot package which is currently needed to build any of our packages - /usr/lib/rpm/fileattrs/ohpc.attr - /usr/lib/rpm/ohpc-find-provides - /usr/lib/rpm/ohpc-find-requires 16

17 RPM dependencies (Alternative approach #2) Let s look at ohpc.attr % ohpc_provides /usr/lib/rpm/ohpc-find-provides -r ohpc % ohpc_requires /usr/lib/rpm/ohpc-find-requires %{buildroot} % ohpc_path ^%{OHPC_HOME} % elf_exclude_path ^%{OHPC_HOME} % ohpc_magic % ohpc_flags ^ELF (32 64)-bit.*$ magic_and_path General approach here is to trigger these scripts for any build that has ELF binaries found in /opt/ohpc The scripts use the native rpm dependency tool (/usr/bin/rpm/elfdeps) to scan the dependencies as usual, and then augment the strings if necessary: - Provides logic: any.so found in /opt/ohpc has the (ohpc) color string appended - Requires logic: any.so found in the build (or coming in as BuildRequires) that lives in /opt/ohpc has matching (ohpc) color string appended. Otherwise, dependencies belonging to packages outside of OpenHPC maintain default string. 17

18 RPM dependencies: Alternative approach #2 Let s look at some of the resulting Provides: differences for gcc using this approach. Essentially, every.so detected in /opt/ohpc has delimiter appended # rpm -q --provides gnu7-compilers-ohpc egrep libgomp OHPC RPM Build with Approach #2 libgomp.so.1()(64bit) libgomp.so.1(goacc_2.0)(64bit) libgomp.so.1(goacc_2.0.1)(64bit) libgomp.so.1(gomp_1.0)(64bit) libgomp.so.1(gomp_2.0)(64bit) libgomp.so.1(gomp_3.0)(64bit) libgomp.so.1(gomp_4.0)(64bit) libgomp.so.1(gomp_4.0.1)(64bit) libgomp.so.1(gomp_4.5)(64bit) libgomp.so.1(gomp_plugin_1.0)(64bit) libgomp.so.1(gomp_plugin_1.1)(64bit) libgomp.so.1(oacc_2.0)(64bit) libgomp.so.1(omp_1.0)(64bit) libgomp.so.1(omp_2.0)(64bit) libgomp.so.1(omp_3.0)(64bit) libgomp.so.1(omp_3.1)(64bit) libgomp.so.1(omp_4.0)(64bit) libgomp.so.1(omp_4.5)(64bit) libgomp.so.1()(64bit)(ohpc) libgomp.so.1(goacc_2.0)(64bit)(ohpc) libgomp.so.1(goacc_2.0.1)(64bit)(ohpc) libgomp.so.1(gomp_1.0)(64bit)(ohpc) libgomp.so.1(gomp_2.0)(64bit)(ohpc) libgomp.so.1(gomp_3.0)(64bit)(ohpc) libgomp.so.1(gomp_4.0)(64bit)(ohpc) libgomp.so.1(gomp_4.0.1)(64bit)(ohpc) libgomp.so.1(gomp_4.5)(64bit)(ohpc) libgomp.so.1(gomp_plugin_1.0)(64bit)(ohpc) libgomp.so.1(gomp_plugin_1.1)(64bit)(ohpc) libgomp.so.1(oacc_2.0)(64bit)(ohpc) libgomp.so.1(omp_1.0)(64bit)(ohpc) libgomp.so.1(omp_2.0)(64bit)(ohpc) libgomp.so.1(omp_3.0)(64bit)(ohpc) libgomp.so.1(omp_3.1)(64bit)(ohpc) libgomp.so.1(omp_4.0)(64bit)(ohpc) libgomp.so.1(omp_4.5)(64bit)(ohpc) 18

19 RPM dependencies: Alternative approach #2 Let s look at some of the resulting Requires: differences for gcc using this approach. # rpm -q --requires gnu7-compilers-ohpc egrep libc.so libgc OHPC RPM Build with Aproach #2 libgcc_s.so.1()(64bit) libgcc_s.so.1(gcc_3.0)(64bit) libgcc_s.so.1(gcc_3.3)(64bit) libgcc_s.so.1(gcc_4.2.0)(64bit) libgcc_s.so.1(gcc_4.3.0)(64bit).so s contained within ohpc gcc build libgcc_s.so.1()(64bit)(ohpc) libgcc_s.so.1(gcc_3.0)(64bit)(ohpc) libgcc_s.so.1(gcc_3.3)(64bit)(ohpc) libgcc_s.so.1(gcc_4.2.0)(64bit)(ohpc) libgcc_s.so.1(gcc_4.3.0)(64bit)(ohpc) libc.so.6()(64bit) libc.so.6(glibc_2.10)(64bit) libc.so.6(glibc_2.11)(64bit) libc.so.6(glibc_2.14)(64bit) libc.so.6(glibc_2.16)(64bit) libc.so.6(glibc_2.17)(64bit) libc.so.6(glibc_2.2.5)(64bit) libc.so.6(glibc_2.3)(64bit) libc.so.6(glibc_2.3.2)(64bit) libc.so.6(glibc_2.3.3)(64bit) libc.so.6(glibc_2.6)(64bit) libc.so.6(glibc_2.7)(64bit).so s required from base OS supplied packages libc.so.6()(64bit) libc.so.6(glibc_2.10)(64bit) libc.so.6(glibc_2.11)(64bit) libc.so.6(glibc_2.14)(64bit) libc.so.6(glibc_2.16)(64bit) libc.so.6(glibc_2.17)(64bit) libc.so.6(glibc_2.2.5)(64bit) libc.so.6(glibc_2.3)(64bit) libc.so.6(glibc_2.3.2)(64bit) libc.so.6(glibc_2.3.3)(64bit) libc.so.6(glibc_2.6)(64bit) libc.so.6(glibc_2.7)(64bit) 19

20 RPM dependencies: Alternative approach #2 Full comparison for openblas RPM OHPC RPM: Requires Requires: Approach #2 gnu7-compilers-ohpc >= libc.so.6()(64bit) libc.so.6(glibc_2.2.5)(64bit) libc.so.6(glibc_2.3.2)(64bit) libc.so.6(glibc_2.3.4)(64bit) libc.so.6(glibc_2.6)(64bit) libc.so.6(glibc_2.7)(64bit) libgfortran.so.4()(64bit) libgfortran.so.4(gfortran_7)(64bit) libgomp.so.1()(64bit) libgomp.so.1(gomp_4.0)(64bit) libgomp.so.1(omp_1.0)(64bit) libm.so.6()(64bit) libm.so.6(glibc_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(glibc_2.2.5)(64bit) ohpc-filesystem gnu7-compilers-ohpc >= libc.so.6()(64bit) libc.so.6(glibc_2.2.5)(64bit) libc.so.6(glibc_2.3.2)(64bit) libc.so.6(glibc_2.3.4)(64bit) libc.so.6(glibc_2.6)(64bit) libc.so.6(glibc_2.7)(64bit) libgfortran.so.4()(64bit)(ohpc) libgfortran.so.4(gfortran_7)(64bit)(ohpc) libgomp.so.1()(64bit)(ohpc) libgomp.so.1(gomp_4.0)(64bit)(ohpc) libgomp.so.1(omp_1.0)(64bit)(ohpc) libm.so.6()(64bit) libm.so.6(glibc_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(glibc_2.2.5)(64bit) ohpc-filesystem OHPC RPM: Provides libopenblas.so.0()(64bit) openblas-gnu7-ohpc = openblas-gnu7-ohpc(x86-64) = Provides: Approach #2 libopenblas.so.0()(64bit)(ohpc) openblas-gnu7-ohpc = openblas-gnu7-ohpc(x86-64) =

21 RPM dependencies: Alternative approach #2 Net result is that we no longer conflict with OS provides.so s, and we maintain automatic dependencies for OS packages and OpenHPC pre-requisites. # repoquery --whatprovides "libopenblas.so.0()(64bit)" openblas-0: el7.x86_64 # repoquery --whatprovides "libopenblas.so.0()(64bit)(ohpc)" openblas-gnu7-ohpc-0: ohpc.x86_64 21

22 RPM dependencies Benefits - no change to current.spec files - maintains color capability of the current default RPM dependency analysis tool (e.g. ABI version of.so) - uses newer plugin infrastructure of RPM deps tool to isolate analysis to items in OHPC path - isolates ohpc packaging via explicit delimiter on.so s (similar in spirit to the RPM naming convention) - does not require us to call out all base OS dependencies Thoughts going forward - regardless of the approach, are people generally in favor of trying to implement a change to avoid collision with OS packages? - If so, thoughts on the first two approaches? 22