Tuesday,January10th,201711:00amET

MeetingoftheTechnicalSteeringCommittee(TSC)Board

2017-02-02 OpenHPC Project 2

• https://www.uberconference.com/jeff_ef

• United States : +1 (510) 224-9559 (No PIN needed).

Meeting Logistics

2017-02-02 OpenHPC Project 3

OpenHPC Project 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 OpenHPC Project meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. 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.

Antitrust Notice

2017-02-02 OpenHPC Project 4

• Upcoming deadlines– ISC’17 (Frankfurt - June 18-22, 2017)

• BoFs: Feb 15• Tutorials: Feb 15

– PEARC (New Orleans, July 9-13, 2017)• Papers/Tutorials: March 6

• Build server updates• CI updates• 1.2.1 Release status• ISO discussion

Agenda/Updates

2017-02-02 OpenHPC Project 5

• While working on v1.2.1 release over the break, ran into an issue access packages for SLES– note that our OBS config is setup to access SLES OS

packages from a public OBS server at: https://build.opensuse.org

– normally this works fine: some occasional network hiccups and downtime of build.opensuse.org, but overall good

– for 1.2.1 builds, we encountered errors accessing the SP1 packages…

• error logs pointed to incompatibility with OBS @ build.opensuse.org• had to update our production OBS version to latest: v2.6.4 -> 2.6.10• connectivity restored now and SLES builds working again

Build server updates

2017-02-02 OpenHPC Project 6

Back to Dashboard

Status

Changes

Workspace

Build with Parameters

Delete Project

Configure

Move

Project RepoConfigThis build requires parameters:

Repo Release

UseExternalRepo

Build

KARL W. SCHULZ | LOG OUT search

trendBuild History

find

#1894

#1893

#1892

#1891

#1890

#1889

#1888

#1887

#1886

Jenkins RepoConfig

• While setting up the tests for v1.2.1, took the opportunity to tweak the Jenkins configuration based on lessons learned from 1.2 release:

– current workflow involves testing against a “Factory” build branch and then migrating to a formal “Release” branch

– for speed (and minimization of downloads from EC2), the CI system mirrors our public package repos

• use the mirrors initially• switch to official repo prior to release

• Previously, had to edit every job permutation to make repo changes…

• Moved this setting to a common job called by all permutations -> RepoConfig

– config logged on each job description now

CI/Jenkins Updates Back to Project

Status

Changes

Console Output

Edit Build Information

Delete Build

Parameters

Locked Resources

Environment Variables

Test Result

Previous Build

Next Build

Build #414(Jan 9, 2017 4:29:43 AM)Repo=Factory,Ext=false

edit description

Subproject Builds

RepoConfig #1775PXSE-Path #1710Boot-SMS #3463Install Cluster #3382

No changes.

Started by timer

Test Result (no failures)

KARL W. SCHULZ | LOG OUT search

Page generated: Jan 10, 2017 8:52:55 AM CST REST API Jenkins ver. 2.19.4

Started 1 day 4 hr agoTook 13 min on master

Jenkins (1.2.1) - (centos7.2,x86_64) - (warewulf+slurm) - short cycle #414 ENABLE AUTO REFRESH

ReleaseFactoryRC1RC2

2017-02-02 OpenHPC Project 7

v1.2.1 Release Status

• Builds completed

• Includes fixes for several items reported on the email lists since SC’16

New Item

People

Build History

Edit View

Project Relationship

Check File Fingerprint

Manage Jenkins

My Views

Lockable Resources

Credentials

No builds in the queue.

master

1 Idle

2 Idle

3 (1.2.1) - (centos7.2,x86_64) -

OpenHPC CI Infrastructure Thanks to the Texas Advanced Computing Center (TACC) for hosting support and to Intel, Cavium, and Dell for hardware donations.

add description

S Name ↓ Last Success Last Failure Last Duration

(1.2.1) - (centos7.2,x86_64) - (warewulf+pbspro) - long cycle 1 hr 13 min - #214 13 hr - #208 56 min

(1.2.1) - (centos7.2,x86_64) - (warewulf+pbspro) - short cycle 1 hr 10 min - #426 3 hr 10 min - #424 14 min

(1.2.1) - (centos7.2,x86_64) - (warewulf+slurm) - long cycle 2 hr 19 min - #215 4 hr 19 min - #214 1 hr 0 min

(1.2.1) - (centos7.2,x86_64) - (warewulf+slurm) - short cycle 48 min - #440 16 hr - #424 14 min

(1.2.1) - (centos7.2,x86_64) - (warewulf+slurm+PXSE) - long cycle 5 hr 49 min - #105 2 days 9 hr - #92 2 hr 29 min

(1.2.1) - (sles12sp1,x86_64) - (warewulf+pbspro) - long cycle 1 hr 16 min - #212 3 hr 16 min - #211 45 min

(1.2.1) - (sles12sp1,x86_64) - (warewulf+slurm) - long cycle 3 hr 36 min - #212 9 hr 36 min - #209 54 min

Icon: S M L Legend RSS for all RSS for failures RSS for just latest builds

KARL W. SCHULZ | LOG OUT search

Build Queue

Build Executor Status

1.1.1 1.2 All Interactive admin +1.2.1

Jenkins ENABLE AUTO REFRESH

2017-02-02 OpenHPC Project 8

v1.2.1 Release Status

This repository Pull requests Issues Gist

openhpc / ohpc

Code Issues 40 Pull requests 10 Projects 0 Wiki Pulse Graphs Settings

Tags Draft a new release

Draft OpenHPC v1.2.1 (11 January 2017) koomie drafted this 18 hours ago

Release Notes

General

1.2.1 is the first micro update release against 1.2updated SLURM packaging to include creation of slurm user (#337)introduce $compute_prefix variable for use in template recipes (#239)update nagios package installation for compute image (#248)removal of hard-coded paths in Makefiles installed with TAU (#355)document need for resolvable SMS hostname (#250)updated Requires stanza for mpiP packaging (#344)updated modulefile compatibility packaging for Intel Parallel Studio toolchain

support "2017 Update 1" version string (#342)support installation target that is a soft link (#347)

Component Version Changes

!!*!docs'ohpc!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!(v1.2!'>!v1.2.1)!!*!tau'gnu'impi'ohpc!!!!!!!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!*!tau'gnu'mpich'ohpc!!!!!!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!*!tau'gnu'mvapich2'ohpc!!!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!*!tau'gnu'openmpi'ohpc!!!!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!*!tau'intel'impi'ohpc!!!!!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!*!tau'intel'mpich'ohpc!!!!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!*!tau'intel'mvapich2'ohpc!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!*!tau'intel'openmpi'ohpc!!!!!!!!!!!!!!!!!!!(v2.25.2!'>!v2.26)!!

Latest release

v1.2.GA 4f4aa01

OpenHPC v1.2 (12 November 2016) koomie released this on Nov 13, 2016 · 8 commits to obs/OpenHPC_1.2_Factory since this release

Release Notes

General

introduction of aarch64 ARM builds (see Tech Preview for more info)first release with new package additions added using community submission process created

Edit

Edit

Releases

208 5168 Unwatch Star Fork

Remaining Items: • CI tests on ARM (confirm TAU)• Final ISO assembly

– would like to discuss potential options/issues next….

DRAFTReleasenotes

2017-02-02 OpenHPC Project 9

• For those with good external network access, the preferred download mode for OpenHPC packages is to access the package repositories directly at: http://build.openhpc.community/OpenHPC

• The provided ohpc-release RPM enables this functionality directly

• However, for those systems behind firewalls (or with poor connectivity, or just prefer to mirror locally), we have also been providing an ISO image

– we then suggest that the user create a .repo file locally before following the standard recipe(s)

ISO Image(s)

Index of /OpenHPC:/1.2/CentOS_7.2/iso Name Last modified Size Description

Parent Directory -

OpenHPC-1.2_CentOS_7.2_aarch64.iso 2016-11-17 21:06 631M

OpenHPC-1.2_CentOS_7.2_src.iso 2016-11-17 21:07 6.4G

OpenHPC-1.2_CentOS_7.2_x86_64.iso 2016-11-17 21:07 1.5G

2017-02-02 OpenHPC Project 10

• Example text shown here from 1.1 release

• For a minor release (e.g. 1.1), we were recommending that they still point to the public updates repository – thoughts?– obviously won’t work if they

don’t have network connectivity

• For this v1.2.1 release, the updates section will be populated….

ISO Image(s)In addition to online repositories the OpenHPC packages are also provided as ISO images-- one containing a repository of packages in the major release (1.1), and one containing source RPMS. When installing from the ISO repo, yum should be configured with the online OpenHPC updates repo enabled. To access the packages via this method download the ISO to your host:

# wget -O /tmp/OpenHPC_1.1_CentOS_7.2.iso http://build.openhpc.community/OpenHPC:/1.1/CentOS_7.2/iso/OpenHPC_1.1.1_CentOS_7.2.iso

You can now mount the ISO image via the loop device:

# mkdir -p /mnt/iso# mount -o loop /tmp/OpenHPC_1.1.1_CentOS_7.2.iso /mnt/iso

To configure the package manager create a file called /etc/yum.repos.d/OpenHPC:1.1.1.repo with the following contents:

[OpenHPC]name=OpenHPC-1 - Basebaseurl=file:///mnt/isogpgcheck=1gpgkey=file:///mnt/iso/repodata/repomd.xml.keyenabled=1

[OpenHPC-updates]name=OpenHPC-1 - Updatesbaseurl=http://build.openhpc.community/OpenHPC:/1.1/updates/CentOS_7.2gpgcheck=1gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-OpenHPC-1

Your package manager should now be able to install OpenHPC packages in the typical fashion:

# yum install docs-ohpc

2017-02-02 OpenHPC Project 11

Items for consideration:• are we on board with continuing to provide a downloadable ISO for mirroring locally?

– other alternative is to ask the user to handle the mirroring themselves (e.g. via reposync, rsync, etc…)

• if yes, should we consider providing a companion script with ISO image that mounts the .iso image and creates the OpenHPC.repo file accordingly?

– the XCAT ISO images provide a utility like this– we could also use this utility in a companion CI job to confirm ISO usability?

• should we suggest enabling any network repositories for OpenHPC, or should we assume usage to be completely offline?

– in offline case, user would download newer ISO image to get updated packages– our ISO images in a particular branch (e.g. 1.2, 1.2.1, 1.2.2) would have some duplication of

packages (when there is no component change), but would be self-contained• committ to building ISO images for every micro release?

ISO Image(s)