Display Manager 13.2 Administrator’s Guide - PBS … · WinProp v.14.5 ©2000-2017 Special Notice: Pre-release versions of Altair software are provided ‘as is’, without warranty

PBS Works is a brand of

Display Manager 13.2

Administrator’s Guide

Display Manager 13.2 Administrator’s Guide

Intellectual Property Rights Notice: Copyrights, Trademarks, and Third Party Licenses

Updated: May 16, 2017.

Altair® PBS Works™ 13.2Enabling On-Demand Computing™Copyright© 1994-2017 Altair Engineering Inc. All Rights Reserved.

Altair PBS Works™: Compute Manager™ ©2012-2017; Display Manager™ ©2013-2017; PBS Pro™ ©1994-2017; PBSProfessional® ©1994-2017; PBS Application Services™ ©2008-2017; PBS Analytics™ ©2008-2016;PBS Desktop™ ©2008-2012; and e-Compute™ ©2000-2010.

HyperWorks® Products: HyperMesh® ©1990-2017; HyperCrash® ©2001-2017; OptiStruct® ©1996-2017; RADIOSS® ©1986-2017; HyperView® ©1999-2017; HyperView Player® ©2001-2017; HyperMath® ©2007-2017; HyperStudy® ©1999-2017; HyperGraph® ©1995-2017; MotionView® ©1993-2017; MotionSolve® ©2002-2017; HyperForm® ©1998-2017; HyperXtrude® ©1999- 2017; Process Manager™ ©2003-2016; Templex™ ©1990-2017; TextView™ ©1996-2017; MediaView™ ©1999-2017; TableView™ ©2013-2017; BatchMesher™ ©2003-2017; HyperWeld® ©2009-2017; HyperMold® ©2009-2017; Manufacturing Solutions™ ©2005-2017; solidThinking Inspire® 2017 ©2009-2017; solidThinking Evolve®2017 ©1993-2017; Durability Director™ ©2009-2017; Suspension Director™ ©2009-2017; AcuSolve® ©1997-2017; AcuConsole® ©2006-2017; SimLab® ©2004-2017; Virtual Wind Tunnel™ ©2012-2017; FEKO® (©1999-2014 Altair Development S.A. (Pty) Ltd.; ©2014-2017 Altair Engineering, Inc.); ConnectMe™ ©2014-2017; Click2Extrude™ Polymer 2017 ©1996-2017; Click2Extrude™ Metal 2017 ©1996-2017; Click2Form™ 2017 ©1998-2017.

Additional Altair Products: Multiscale Designer™ ©2011-2017; Flux v.12.2 ©1983-2017; InCa3D v.3.1©1996-2016; CDE v.2 ©2012-2016; Got-It v.3 ©2002-2016; WinProp v.14.5 ©2000-2017

Special Notice: Pre-release versions of Altair software are provided ‘as is’, without warranty of any kind. Usage is strictly limited to non-production purposes.

ii


Altair Packaged Solution Offerings (PSOs): Automated Reporting Director™ ©2008-2017; GeoMechanics Director ©2011-2017; Impact Simulation Director™ ©2010-2017; Model Mesher Director™ ©2010-2017; Model Verification Director™ ©2013-2017; NVH Director™ ©2010-2017; Squeak and Rattle Director™ ©2012-2017; Virtual Gauge Director™ ©2012-2017; Weight Analytics™ ©2013-2017; Weld Certification Director™ ©2014-2017; Multi-Disciplinary Optimization™ ©2012-2017.

Altair Simulation Cloud Suite: Simulation Manager™ ©2003-2016; Compute Manager™ ©2003-2017; Display Manager™ ©2003–2017; and Process Manager™ ©2003-2016.

Software products of solidThinking, Inc., a wholly owned subsidiary of Altair Engineering:solidThinking Inspire® 2017 ©2009-2017; solidThinking Evolve®2017 ©1993-2017; solidThinking Compose® 2017 ©2007-2017, solidThinking Activate® 2017 ©1989-2017, solidThinking Embed® 2017 ©1989-2017, solidThinking Embed® SE 2017 ©1989-2017; Click2Extrude™ Metal 2017 ©1996-2017; Click2Extrude™ Polymer 2017 ©1996-2017; Click2Cast® 4.0 ©2011-2017; Click2Form™ 2017 ©1998-2017; Envision® 4.0 ©2013-2017.

Altair intellectual property rights are protected under U.S. and international laws and treaties. Additionally, Altair software is protected under patent #6,859,792 and other patents pending. All other marks are the property of their respective owners.

ALTAIR ENGINEERING INC. Proprietary and Confidential. Contains Trade Secret Information.

Not for use or disclosure outside of Altair and its licensed clients. Information contained in Altair software shall not be decompiled, disassembled, “unlocked”, reverse translated, reverse engineered, or publicly displayed or publicly performed in any manner. Usage of the software is only as explicitly permitted in the end user software license agreement. Copyright notice does not imply publication.

Third party software licenses

AcuConsole contains material licensed from Intelligent Light (www.ilight.com) andused by permission.

iii

http://www.altairhyperworks.com/ClientCenter3rdPartyLicense.aspx

http://www.altairhyperworks.com/ClientCenter3rdPartyLicense.aspx

http://www.ilight.com


Software Security Measures:

Altair Engineering Inc. and its subsidiaries and affiliates reserve the right to embed software security mechanisms in the Software for the purpose of detecting the installation and/or use of illegal copies of the Software. The Software may collect and transmit non-proprietary data about those illegal copies. Data collected will not include any customer data created by or used in connection with the Software and will not be provided to any third party, except as may be required by law or legal process or to enforce our rights with respect to the use of any illegal copies of the Software. By using the Software, each user consents to such detection and collection of data, as well as its transmission and use if an illegal copy of the Software is detected. No steps may be taken to avoid or detect the purpose of any such security mechanisms.

Technical Support

This document is proprietary information of Altair Engineering, Inc.

Location Telephone e-mail

China +86 (0)21 6117 1666 [email protected] +33 (0)1 4133 0992 [email protected] +49 (0)7031 6208 22 [email protected] +91 80 66 29 4500 [email protected] +39 800 905595 [email protected] +81 3 5396 2881 [email protected] +82 70 4050 9200 [email protected] America +1 248 614 2425 [email protected] +46 (0) 46 460 2828 [email protected] +44 (0)1926 468 600 [email protected]

iv

Contents

About this Guide xi

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiDocument Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiAcronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Introduction to Display Manager 1

Overview of the Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Prerequisites 3

Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Execution Host Requirements for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Execution Host Requirements for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Sample Configurations for Execution Hosts for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Sample Configurations for Execution Hosts for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Web Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Java Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Prerequisites for installing Display Manager Agent for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisites for installing Display Manager Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operating System Groups and User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Software Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Display Manager Deployment Options 11

Network Implementation of Display Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Network Connections of Java Applet Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Network Connections of HTML5 Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Distributed Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Single Host Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing Display Manager 17

Configuration of PBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Manual Installation Configuration of PBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

v

Manual Uninstallation Configuration of PBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Display Manager Installation on Linux 21

Starting the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Splash Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Altair Applications and Service Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26PBS and PAS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28License Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Single Sign-On Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Domain Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Access Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Authentication Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Authorization Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38GPU Configuration for the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41GPU Configuration for the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42PBS Works Portal Administrator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Display Manager Installation on Windows 45

Starting the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Splash Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Altair Applications and Service Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51License Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Single Sign-On Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Domain Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

vi Contents

Access Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Authentication Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Authorization Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62PBS Works Portal Administrator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65PBS Works Service User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Display Manager Console Installation 69

Starting the Installer in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69License Agreement Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Altair Applications Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Display Manager Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72PBS and PAS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73License Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Single Sign-On Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Domain Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Access Management Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Authentication Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Authorization Module for AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Database Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78GPU Configuration for the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78GPU Configuration for the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79PBS Works Portal Administrator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Pre-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Installation Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Installing DM Execution Components for Linux 83

Display Manager Add-on Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Configure PBS and PAS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Pre-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Installing the Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Choose Install Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Contents vii

AMS Configuration for Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Install Display Manager Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91GPU Configuration for Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Pre-installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Unconfigure PBS and PAS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Install the Display Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Installing DM Execution Components for Windows 97

Display Manager Add-on Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Starting the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configure PBS and PAS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Pre-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Installing the Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Choose Install Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102AMS Configuration for Display Manager Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Install Display Manager Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Choose Install Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Pre-installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Unconfigure PBS and PAS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Uninstalling Display Manager 109

Configurations 113

PBS Applications and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Verifying Display Manager Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Access Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115PBS Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116GPU Configuration as PBS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117PAS Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117GPU Resource Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Display Manager Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Display Manager Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Changing the DM Router Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Display Manager Settings Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

viii Contents

Client Configuration for Application Launch Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Setup the ALF Desktop Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Modify the ALF Client Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Starting, Stopping and Restarting 125

PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Determine the PBS Works Portal Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Starting the PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Stopping the PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Restarting the PBS Works Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126DM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Determine the DM Router Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Starting DM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Stopping DM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Post Installation Administration 129

Network Ports for Java Applet Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Network Ports for HTML5 Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Managing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Location of Application definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Main components of Display Manager Application Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 130Application specific for Linux and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Adding a New Application for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Adding a New Application for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Display Manager Specific Information for Application Definitions . . . . . . . . . . . . . . . . . . . . . . . . 135

Managing Graphical Node Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Modify the Cluster GPU Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Modify the Node GPU Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Configuring the Browser for Application Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140HTML5 Viewer for VNC and RDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Enable HTML5 View Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140HTML5 Supported and Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Configuration of Display Proxy for Windows Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Keyboard Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Contents ix

Troubleshooting 143

Quick Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Resource Availability Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Resource Acquisition Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Only the display session is shown but not the application that was started . . . . . . . . . . 146Graphic Card Compatibility Issues with Display Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Glossary 149

x Contents

About this Guide

This document describes how to install, configure and administer PBS Works.

This chapter contains the following topics:• Audience• Related Documentation• Document Conventions• Acronyms

AudienceThis document is intended for administrators who perform the following tasks:

• Install and administer PBS Works products• Monitor the operation of PBS Works products• Troubleshoot PBS Works products

Related DocumentationThe other PBS Works related documents are as follows:

• PBS Works Installation Guide• PBS Works Administrator’s Guide• PBS Works Release Notes• Compute Manager Administrator’s Guide• Display Manager Administrator’s Guide• Results Visualization Service Administrator’s Guide

Documentation can be found at the following URL:

http://www.pbsworks.com/SupportGT.aspx?d=PBS-Professional,-Documentation

xi

http://www.pbsworks.com/SupportGT.aspx?d=PBS-Professional,-Documentation


Document ConventionsThe following typographical conventions are used in this document:

PBS Works Home Directory

CONFIG_HOME is where the PBS Works configuration and log files are stored. The location of this directory is platform dependent. For more information see Software Organization on page 9.

For example:

config.properties is stored in CONFIG_HOME\services\cm\config

PBS Works Execution Directory

SERVER_HOME is where the PBS Works binaries are stored. The location of this directory is platform dependent. For more information see Software Organization on page 9.

For example:

PBSWorksService.bat is stored in SERVER_HOME\scripts\

File Pathname

Names of a file or a directory are displayed as follows:

/home/user1/submission_dir/PBSJobApp/174.hwesuse113.oe

Keyboard Inputs

Keyboard inputs, for example commands that are entered are displayed as follows:

./etc/init.d/pbsworks-pbsa start

Code Example and File Contents

Examples of programming code or the contents of a file are displayed as follows:

Parameters, Environment Variables, XML tags

Environment variables, XML tags, parameters, and references to a snippet of a file are displayed as follows:

Set the value of the MaxBackupIndex parameter to the maximum number of log files to keep.

if userInputs['ACCOUNT']:

job.attr_accounting_label =userInputs['ACCOUNT']

xii


UI Controls

User Interface controls such as command buttons, tab names, menu options, application fields, or items in a list are displayed as follows:

Click the Settings button.

Document References

References to an external document are displayed as follows:

For more information see the PBS Works 13.2 Administrator’s Guide.

Messages

Log file messages or messages returned from a command are displayed as follows:Please make sure PBSA engine and Monetdb Server are not running.

Notes

Information or notes that supplement or emphasize important points are displayed as follows:

Tips

Tips that makes your work easier are displayed as follows:

Cautions

Cautions draw special attention to any action that could cause damage to the product or cause the loss of data. For example:

The default TOC type for a result file is set in the plugin_def.xml file

If you get an error during registration of the HyperView Player, right click on the shortcut and choose the Run as Administrator option from the context menu.

Do not turn the monitor off by unplugging it from the computer or wall socket. Severe damage to the monitor may result. Turn the monitor off before unplugging it.

xiii


AcronymsThe following acronyms are used in this guide.

Table 1. Acronyms

Term DefinitionAD Active DirectoryALF Application Launch FrameworkAMD Advanced Micro DevicesAMS Access Management ServiceCentOS Community Enterprise Operating SystemCM Compute ManagerDM Display ManagerESR Extended Support ReleaseGPU Graphics Processing UnitGUI Graphical User InterfaceHPC High Performance ComputingHWU HyperWorks UnitJRE Java Runtime EnvironmentLDAP Lightweight Directory Access ProtocolMOM Machine Oriented MiniserverNPAPI Netscape Plugin Application Programming InterfacePAS PBS Application ServicePBS Portable Batch SystemPBSA PBS AnalyticsRDP Remote Desktop ProtocolRDS Remote Display ServerRGS Remote Graphics SoftwareRHEL Red Hat Enterprise LinuxRVS Results Visualization ServiceSLES SuSE Linux Enterprise ServerSSH Secure Socket ShellUI User InterfaceVNC Virtual Network ComputingXML eXtensible Markup Language

xiv

1. Introduction to Display Manager

Display Manager is a platform for collaboration and remote visualization of applications and data. It enables high performance remote display of applications over the networks using a web browser. It fosters team work and communications by allowing to share the sessions among users.

Overview of the GuideThis guide describes how to install and configure Display Manager. The following topics are cov-ered in this guide:

• Prerequisites• Display Manager Deployment Options

1


• Installing Display Manager• Display Manager Installation on Linux• Display Manager Installation on Windows• Display Manager Console Installation• Installing DM Execution Components for Linux• Installing DM Execution Components for Windows• Uninstalling Display Manager• Configurations• Starting, Stopping and Restarting• Post Installation Administration• Troubleshooting

What’s NewHere’s a quick look at the latest features available in Display Manager 13.2:

• HTML5 Viewer now supports VNC and RDP for remote desktop.• Ability to use Single Sign-On (SSO) for the applications. With SSO enabled, users will be

logged in using their domain credentials, i.e., the username and password they use to login to their client system.

• Notifications are listed in the Notification panel. The notification comprises a message detailing the event, type of notification (error, warning, information), priority (with color indication), the application that is generating the notifications (CM, DM, AMS), date and time of event.

2 Introduction to Display Manager

2. Prerequisites

Minimum System Requirements

Execution Host Requirements for LinuxOperating System Any Linux distribution in the Red Hat Enterprise or SUSE Enterprise fam-

ilies which contains GLIBC 2.3.2 or laterGraphics • Only NVIDIA and [AMD] ATI cards are supported.

• For Linux, install the 3D adapter drivers provided by the manufacturer.• Full 3D acceleration or Pixel Buffer support should be enabled by the

Linux drivers.GPU cores and GPU memory

Specific to the applications used.

CPU cores and Physical memory


Others • For running Display Manager sessions, X Server and application on local display must be configured and working. X Server must be config-ured to export True Color (24 bit or 32 bit) visuals.

• Use Virtual Private Networking or secured channels for communication between clients and Display Manager server if encryption is required.

• The execution host must be able to access and run the applications avail-able through Display Manager.

3


Execution Host Requirements for Windows

Sample Configurations for Execution Hosts for LinuxHere are some sample execution host configurations on which Display Manager has been tested for Linux.

Operating System Windows Server 2008 R2, 2012 and 2012 R2Graphics Only NVIDIA and [AMD] ATI cards are supported.CPU cores and Physical memory


Others • Use Virtual Private Networking or secured channels for communication between clients and Display Manager server if encryption is required.

• The execution host must be able to access and run the applications avail-able through Display Manager.

If Remote Desktop Protocol (RDP) is in use, then ensure that the latest updates and patches are installed. Refer Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008 R2 for more infor-mation.

Graphics Card Model Processor OS RAM

System 1 NVIDIA Quadro FX 5500

2 x AMD® Opetron® CPU 2220 (4 cores total)

RHEL WS R4 (Nahant Update 6)

4 GB

System 2 NVIDIA Quadro 600

2 x Intel® Xeon® CPU E31280 @ 3.50GHz (8 cores total)

RHEL Client R 5.1 (Tikanga)

32GB


2 x Intel® Xeon® CPU X5675 @3.07GHz(12 cores total)

Cent OS 5.5 48GB


2 x Intel® Xeon® CPU X5675 @3.07GHz (12 cores total)

Cent OS 5.5 48GB

4 Prerequisites

https://support.microsoft.com/en-us/kb/2592687

https://support.microsoft.com/en-us/kb/2592687


Sample Configurations for Execution Hosts for WindowsHere are some sample execution host configurations on which Display Manager has been tested for Windows.

System 5 NVIDIA (2) Quadro 4000

2 x Intel® Xeon® CPU E5620 @ 2.40GHz(8 cores total)

Cent OS 5.5 32GB


2 x Intel® Xeon® CPU E5620 @ 2.40GHz (8 cores total)

RHEL Server R 6.3 (Santiago)

24GB


Intel® Xeon® CPU E5620 @ 2.40GHz (4 cores)

RHEL 5 4GB

System 8 [AMD] ATI Device 6809

Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz (4 core)

Cent OS 6.4 32GB

System 9 NVIDIA Quadro K4000, NVIDIA Quadro 2000


SLES 11 SP3 32GB

System 10 NVIDIA Quadro K5000


SLES 11 SP3 32GB



Intel(R) Pentuim(R) CPU 3.00GHz (2 core)

Windows 2008 R2 4GB


Intel(R) i7 CPU 2.20GHz (4 core)

Windows 2012 R2 8GB


Intel(R) i7 CPU 2.20GHz (4 core)

Windows 2012 R2 8GB


Prerequisites 5


Web Server Requirements

Web Client Requirements

Java RequirementJava Extensions are required on the browsers. Java Runtime Environment (JRE) should be avail-able on the Web Client.

Download the latest JRE version from https://java.com/en/download/.

For information about installing Java, refer to http://www.java.com/en/download/help/down-load_options.xml.

To enable Java, refer to http://www.java.com/en/download/help/enable_browser.xml.

To enable NPAPI in Chrome, refer to https://java.com/en/download/faq/chrome.xml#npapi-chrome.

Operating System • Windows Server 2008 R2, 2012 and 2012 R12• Red Hat Enterprise Linux version 6 and 7• SUSE Linux Enterprise Server version 11 and 12• CentOS version 6 and 7

CPU Intel(R) Xeon(R) CPU X5675 @ 3.07GHz or fasterPhysical Memory 8GB or higher

CPU Pentium 4/Xeon, 2.0 GHz or fasterRAM 2 GB or higherSupported Browsers On Windows:

• Mozilla Firefox ESR (Extended Support Release) 52.1.1 (32 bit)• Google Chrome 58• Microsoft Internet Explorer 11On Linux:• Mozilla Firefox ESR 52.1.1 (32 bit)Note: Java Extensions are required on the browsers.

6 Prerequisites

https://www.mozilla.org/en-US/firefox/organizations/

https://java.com/en/download/

http://www.java.com/en/download/help/download_options.xml

http://www.java.com/en/download/help/enable_browser.xml

https://www.mozilla.org/en-US/firefox/organizations/

https://java.com/en/download/faq/chrome.xml#npapichrome


For troubleshooting the Java installation, refer to http://www.java.com/en/download/help/trouble-shoot_java.xml.

Prerequisites for installing Display Manager Agent for LinuxThe following prerequisites have to be met to allow the Display Manager Agent (DM Agent) to configure ngpus on PBS MOMs (Machine Oriented Miniservers).

Configuring GPU Resources

A custom resource called ngpus has to be configured for Display Manager sessions. This can be adjusted any time.

The ngpus setting limits the number of concurrent display sessions that can utilize the GPU on the host. When more concurrent sessions are using the same GPU, the display session performance will be affected.

Apart from configuring GPUs, performance can be improved by increasing host memory, network performance and CPU cores.

Configuration of PBS Server

PBS Server should have been configured using either the PBS Works 13.2 installer or the PBS Works 13.2 Display Manager add-on installer to make sure that ngpus are configured as a custom resource.

The PBS Works 13.2 installer will perform the following:• Install the DM components• Define a new custom resource called ngpus• Set the custom resource at each execution host

The PBS Works 13.2 Display Manager add-on installer will perform the following:• Configure PBS and PAS Server• Installing the Display Manager Router• Install Display Manager Agent• Unconfigure PBS and PAS Servers• Install the Display Proxy

Prerequisites 7

http://www.java.com/en/download/help/troubleshoot_java.xml


PBS Privileges

For the Display Manager Add-on installer to set the custom resource at each execution host, the root user of all execution hosts must be granted operator access. Prior to starting the DM Add-on installer, issue the following command to grant this access:

qmgr: s s operators+=root@*

If this access is not granted, then you will manually have to set the custom resource by issuing a qmgr set command for each execution host after installation of DM. For example:e.g. set node <node> resources_available.ngpus = 4

After applying such a setting, every user named root from any host on any network will be able to operate on jobs from other users. To prevent misuse, restrict the above setting to the sub domain containing the execution hosts or list them one by one.

After installing Display Manager components, you can remove the root user of the PBS MOMs from the operators list on the PBS server using the command: qmgr: s s operators-=root@*

Prerequisite Resource Libraries for DM Agent

If the following libraries must be installed before attempting to install DM. If they are not, they can be installed using the appropriate system tools (e.g. RPM, YUM, YAST etc.).

libc.so.6()(64bit)

libc.so.6(GLIBC_2.2.5)(64bit)

libc.so.6(GLIBC_2.3)(64bit)

libcrypt.so.1()(64bit)

libdl.so.2()(64bit)

libdl.so.2(GLIBC_2.2.5)(64bit)

libGL.so.1()(64bit)

libGLU.so.1()(64bit)

libICE.so.6()(64bit)

libm.so.6()(64bit)

libm.so.6(GLIBC_2.2.5)(64bit)

libpam.so.0()(64bit)

libpthread.so.0()(64bit)

libpthread.so.0(GLIBC_2.2.5)(64bit)

libpthread.so.0(GLIBC_2.3.2)(64bit)

libSM.so.6()(64bit)

libX11.so.6()(64bit)

libXaw.so.7()(64bit)

libXcursor.so.1()(64bit)

libXext.so.6()(64bit)

libXmu.so.6()(64bit)

libXt.so.6()(64bit)

libXv.so.1()(64bit)

libz.so.1()(64bit)

8 Prerequisites


Prerequisites for installing Display Manager Agent for WindowsConfiguration of PBS Server

PBS Server should have been configured using either the PBS Works 13.2 installer or the PBS Works 13.2 Display Manager add-on installer.

The PBS Works 13.2 installer will Install the DM components.

The PBS Works 13.2 Display Manager add-on installer will perform the following:• Configure PBS and PAS Server• Installing the Display Manager Router• Install Display Manager Agent• Unconfigure PBS and PAS Servers

Operating System Groups and User RequirementsDisplay Manager requires the following user accounts to be defined on the hosts it is installed on.

1. An existing user who will become the PBS Works portal administrator. The portal admin-istrator can define policies and manage resources.

2. An existing user who will be the database administrator.

During installation, the credentials of these users will be required.

Software OrganizationAfter a successful installation of PBS Works, two main directory structures are created. The loca-tion of these directories is platform dependent.

PBS Works home directory (CONFIG_HOME)

This is where the PBS Works configuration and log files are stored.

The default location for CONFIG_HOME is:

on Windows: C:\altair\pbsworks\13.2\home

on Linux: /var/spool/pbsworks/13.2/home

Prerequisites 9


PBS Works execution directory (SERVER_HOME)

This is where the PBS Works binaries are stored.

The default location for SERVER_HOME is:

on Windows: C:\altair\pbsworks\13.2\exec

on Linux: /opt/altair/pbsworks/13.2/exec

10 Prerequisites

3. Display Manager Deployment Options

Network Implementation of Display ManagerThere are two options for viewing a remote session:

• Legacy Java Applet Viewer• HTML5 Viewer

The network connections for viewing remote session is provided in the following sections:• Network Connections of Java Applet Viewer• Network Connections of HTML5 Viewer

11


Network Connections of Java Applet ViewerThe network connections for Display Manager components of Java Applet Viewer is shown below:

When a user double-clicks an application icon in Display Manager (DM), the remote application is started and the following sequence of events are initiated.

1. The DM Application sends the request to the DM Web Service.2. The DM Web Service interfaces with PAS to submit an interactive job.3. The interactive job script updates DM Web Service with the Remote Display Server (RDS)

information.4. DM Web Service responds to DM Web Application with the RDS information. The DM

Web Application transfers the information to Client Viewer.5. Client Viewer connects to the Display Server directly. If the Display Server is not reachable,

then it tries to connect to Display Server through configured Display Router.

12 Display Manager Deployment Options


Virtual Private Networking or secured channels for communication between clients and Display Manager Server can be used if encryption is required. Only the users currently logged in into DM that have a valid session ID are allowed to connect to the DM router.

The ports for the Display Manager portal (application server, port 8086 by default) and the Display Manager Router (port 9500 by default) should be open through the firewall or gateway for clients to connect. The port information for these two components is displayed in the installation sum-mary. Installation Summary shows this information for Display Manager application server and Installation Complete shows the screen for the Display Router installation summary.

Network Connections of HTML5 ViewerThe network connections for Display Manager components of HTML5 Viewer is shown below:

When a user double-clicks an application icon in Display Manager (DM), the remote application is started and the following sequence of events are initiated.

1. The DM Application sends the request to the DM Web Service.



2. The DM Web Service interfaces with PAS to submit an interactive job.3. The interactive job script updates DM Web Service with the Remote Display Server (RDS)

information.4. DM Web Service responds to DM Web Application with the RDS information. The DM

Web Application transfers the information to Client Viewer.

Virtual Private Networking or secured channels for communication between clients and Display Manager Server can be used if encryption is required.

The port for the Display Manager portal (application server, port 8086 by default) should be open through the firewall or gateway for clients to connect. Installation Summary shows the port infor-mation for Display Manager application server.

Distributed Deployment

In this deployment, all the applications - Compute Manager, Display Manager, the Database, Access Management Service, Display Manager Router, PBS and PAS servers can be in one system (System A).



DM Components and MOM (Machine Oriented Miniserver) should be in systems B1, B2, B3, B4, and so on.

The distributed deployment options are:• CM and DM on same machine as PAS/PBS• CM and DM on separate machine from PAS/PBS• CM and DM on machine 1, PAS on machine 2, PBS on machine 3

The DM components are the Remote Display Server and the DM Router. These components use TurboVNC and VirtualGL technology.

To install and configure the DM components use the Display Manager Add-on Installer.

Single Host Deployment In this deployment option, all the following components are installed in a single system.

Enterprise Foundation• Access Management Services• Database

Applications• Compute Manager• Display Manager



Other Components• Display Manager Router• PBS and PAS Servers• PBS MOM• Display Manager Agent


4. Installing Display Manager

This guide covers the information relevant to Display Manager. More information regarding the other products available in the PBS Works Suite installer is available in the PBS Works Administra-tor’s Guide.

Display Manager is available as part of the PBS Works 13.2 Installer. In this installer, Compute Manager, Results Visualization Service, Display Manager, Display Manager Router, Display Man-ager Agent and PBS Customizations are available. Use this installer for a Single Host Deployment option.

For a single host deployment use the PBS Works 13.2 installer to install DM. When you install DM, Compute Manager is automatically installed.

For a distributed deployment use the PBS Works 13.2 installer to install DM and then use the DM Add-On installer to configure PBS and PAS servers, install Display Manager Router and Display Manager Agent.

Separate installers are available in the Altair download area for Windows and Linux operating sys-tems. The installer walks you through the installation process, requesting installation and configu-ration information along the way. Once the installation is complete, Display Manager is ready for use.

The Display Manager Add-on Installer is available to install the execution components of Dis-play Manager Router, Display Manager Agent and PBS Customizations. Use this installer to com-plete the installation for a distributed deployment option.

This guide provides a step by step description of: 1. Installing Display Manager using the PBS Works Installer.

a. Display Manager Installation on Linuxb. Display Manager Installation on Windowsc. Display Manager Console Installation (applies to both)

2. Display Manager Add-on installer to install execution components of Configure PBS and PAS Server, Installing the Display Manager Router, Install Display Manager Agent, and Unconfigure PBS and PAS Servers.

3. Uninstalling Display Manager

17


Configuration of PBSThe PBS Works installer provides an option to automatically or manually configure the PBS Server with a new custom resource called ngpus and a new queue called iworkq and restart at the time of Installation and Uninstallation.

Manual Installation Configuration of PBS If you opted for manual configuration of PBS during installation, follow the steps below:

1. Stop the PBS server:/etc/init.d/pbs stop

2. Edit the file /var/spool/PBS/sched_priv/sched_config and add ngpus to the resources line.For example: resources: "ncpus, mem, arch, host, vnode, netwins, aoe, ngpus"

3. Edit the file /var/spool/PBS/server_priv/resourcedef and add the custom resource ngpus as below:ngpus type=long flag=nh

4. Start the PBS Server/etc/init.d/pbs start

5. Add a queue to the complex: create queue iworkq

set queue iworkq queue_type = Execution

set queue iworkq Priority = 150

set queue iworkq max_queued_res.ngpus = [o:PBS_ALL=<MAX_NO_GPUS_IN_CLUSTER>]

set queue iworkq resources_max.ngpus = 1

set queue iworkq resources_min.ngpus = 1

set queue iworkq enabled = True

set queue iworkq started = True

6. If the machine where you are installing PBS Works is also a graphical execution host, then set the ngpus count:qmgr -c "set node <NODE_NAME> resources_available.ngpus=<NO_GPUS_ON_NODE>"

Manual Uninstallation Configuration of PBSDuring uninstallation, if you opt for an automatic uninstallation, the PBS ngpus resources and the iworkq queue will be removed and the PBS server will be restarted.

To skip this, manually restart the PBS server and perform the following steps:1. Remove the DM entries:

18 Installing Display Manager


If ngpus is not used by any other application other than Display Manager, remove ngpus from the "resources:" line of PBS_HOME/sched_priv/sched_config and the line containing the ngpus resource from PBS_HOME/server_priv/resourcedef.

2. Delete iworkq:qmgr -c "delete queue iworkq"

3. On each GPU node, unset resources_available.ngpus using the command:qmgr -c "unset node <NODE_NAME> resources_available.ngpus"

4. Restart PAS and PBS Servers.

Installing Display Manager 19


20 Installing Display Manager

5. Display Manager Installation on Linux

Display Manager is installed using the PBS Works Installer. The installation package can be obtained using your usual Altair support channels.

Starting the Installer

Start the installer by executing the following command: ./PBS_Works_13.2_Linux_x86_64.bin

[root@localhost PBS Works 13.2 Installer]# ./PBS_Works_13.2_Linux_x86_64.bin

Preparing to install...

Extracting the JRE from the installer archive...

Unpacking the JRE...

Extracting the installation resources from the installer archive...

Configuring the installer for this system's environment...

Launching installer...

The graphical launcher will work only if running the installer from within an X graphic environment or if proper redirection (e.g. "set DISPLAY=myhost:0.0") is set for the running shell.

21


Splash ScreenAfter extracting the files, the installation will proceed by displaying the splash screen.

22 Display Manager Installation on Linux


IntroductionThe Introduction screen provides information on navigating the installer using the Next and Pre-vious buttons and specifies the Prerequisites for Installation.



License AgreementTo continue with the installation, please scroll down to read the license agreement and accept it.



Installation TypeTo install Compute Manager and Display Manager using windows authentication on Windows, SSH on Linux, using local authorization with a new database, choose Express Install.

Custom Install enables you to specify all options available in the installer. In this guide, all the options specific to installing Display Manager are described in detail using the custom Install option.



Altair Applications and Service SelectionSelect the Display Manager option to install:

1. Display Manager Application2. Display Manager Router3. Compute Manager (Prerequisite for Display Manager)

If the installer detects PBS and PAS servers in the target system, it will configure them for Display Manager. If PBS MOM is detected, it will install the DM Agent components.

If PBS and PAS servers are installed on the target system, the installer will inform that they will be restarted during installation.



If you would like to continue the installation, click Yes. Otherwise to cancel the installation click No.

PBS and PAS configurationIf the PBS Works installer detects PBS and PAS servers. It provides an option to automatically con-figure the servers and restart them or you can manually configure the servers and restart them.

If you opted for manual configuration, perform the steps in Manual Installation Configuration of PBS after the installation.



Installation FolderChoose the installation folder on the target system. During PBS Works installation, the following directory structures are created:

• Binaries Install Location - This is where the PBS Works binaries are stored. The default location is: /opt/altair/pbsworks/13.2/execBinaries install location is referred as PBSWorks_HOME.

• Config Install Location - This is where the PBS Works configuration and log files are stored. The default location is: /var/spool/pbsworks/13.2/homeConfig install location is referred as PBSWorks_EXEC.

The location of these directories is platform dependent.



License Server ConfigurationProvide the license server location information. More than one location can be provided by sepa-rating them with a colon (:).



Access Management Service ConfigurationAccess Management Service (AMS) can be installed on the target system to implement Authoriza-tion and Authentication rules for applications.



An existing instance of AMS can be used by providing the Hostname or IP Address and the port at which the AMS instance is running.



Single Sign-On ConfigurationIn this screen, you can enable Single Sign-On (SSO) for the application. With SSO enabled, users will be logged in using their domain credentials, i.e., the username and password they use to login to their client system.

By default, the SSO is disabled. If you want to enable SSO, then choose Yes.

Service Principal Names (SPN) has to be set for SSO to work.

Refer to PBS Works Administrator’s Guide to manually enable SSO and to register SPN.



The following screen is displayed, if you enable SSO:

Domain Server ConfigurationIn this screen, provide the domain server to verify SPN.



Access Management ServiceAMS (Access Management Service) is used to implement authentication and authorization rules for the users of Display Manager application. The following options are available for AMS.

Authentication Module for AMS

The portal (PBS Works) and services can be configured to use the following authentication mech-anisms:

SSH (Secure Shell): All the users will be authenticated against a SSH server provided by the administrator during installation.

The Authentication Module for AMS is not displayed if Single Sign-On (SSO) is not enabled.



Access Management Service: All the users will be authenticated against a datastore and managed using the AMS console.



Authorization Module for AMSThe authorization module is used by AMS to query group memberships and user details. AMS supports two authorization modules: Active Directory and AMS.

Active Directory

If you choose to use Active Directory, provide the details of the LDAP compatible server.



Access Management Service

If you choose Access Management Service, no further inputs are required by the installer. Use the AMS console for authorizing users through the local datastore.



Database ConfigurationIn this screen, a New Database can be created or the application can reuse a database installed ear-lier using the same PBS Works installer. In the example below, the database will be created in the local host. The installer can create a non-admin user on the server where the database is installed, (with username pbsworksuser) who will become the owner (Super User) of the database.



You can also provide the credentials of an existing OS user who will become the database Super User.



If the application is pointed to an existing database from a previous installation using the PBS Works installer, provide the credentials of the database super user.



GPU Configuration for the ServerIf PBS is detected on the target system, the installer will ask you for the number of GPUs available in the cluster to configure the PBS Server.



GPU Configuration for the NodeIf the installer detects PBS MOM on the target system, it will prompt you to enter the number of GPUs available and use the information to configure PBS MOM.



PBS Works Portal Administrator ConfigurationProvide the username for the PBS Works Portal Administrator. The administrator username should be available in the server.



Installation SummaryThis screen summarizes all your choices before beginning the installation.

During installation, the billboards are displayed based on the installation options you selected.

On completion, the installer will provide the details of the Installation Directory, Host, Port and the link to login to the portal.

Bookmark the link and make it available to the users of the portal.


6. Display Manager Installation on Windows


Starting the InstallerLocate the installer executable in Windows Explorer, right click and choose the Run as adminis-trator option from the context menu as shown below.

Splash ScreenThe installer will extract the required files.

45


After extracting the files, the installation will proceed by displaying the splash screen.

46 Display Manager Installation on Windows


IntroductionThe Introduction screen provides information on navigating the installer using the Next and Pre-vious buttons and specifies the Prerequisites for Installation.



License AgreementTo continue with the installation, please scroll down to read the license agreement and accept it.



Installation TypeTo install Compute Manager and Display Manager using windows authentication on Windows, SSH on Linux, using local authorization with a new database, choose Express Install.

Custom Install enables you to specify all options available in the installer. In this guide, all the options specific to installing Display Manager are described in detail using the custom Install option.



Altair Applications and Service SelectionSelect the Display Manager option to install:

1. Display Manager Application2. Display Manager Router3. Compute Manager (Prerequisite for Display Manager)

If the installer detects PBS and PAS servers in the target system, it will configure them for Display Manager. If PBS MOM is detected, it will install the DM Agent components.

If PBS and PAS servers are installed on the target system, the installer will inform that they will be restarted during installation.




• Binaries Install Location - This is where the PBS Works binaries are stored. The default location is: C:\altair\pbsworks\13.2\execBinaries install location is referred as PBSWorks_HOME.

• Config Install Location - This is where the PBS Works configuration and log files are stored. The default location is: C:\altair\pbsworks\13.2\homeConfig install location is referred as PBSWorks_EXEC.




License Server ConfigurationProvide the license server location information. More than one location can be provided by sepa-rating them with a semicolon (;).



Access Management Service ConfigurationAccess Management Service (AMS) can be installed on the target system to implement Authoriza-tion and Authentication rules for applications.



An existing instance of AMS can be used by providing the Hostname or IP Address and the port at which the AMS instance is running.





Service Principal Names (SPN) has to be set for SSO to work.

Refer to PBS Works Administrator’s Guide to manually enable SSO and to register SPN.



If you enable SSO and if SPN is not registered, then the following screen is displayed:.

Domain Server ConfigurationIn this screen, provide the domain server and its corresponding details to verify SPN.

Access Management ServiceAMS (Access Management Service) is used to implement authentication and authorization rules for the users of Display Manager application.



Authentication Module for AMS The portal (PBS Works) and services can be configured to use the following authentication mech-anisms:

SSH (Secure Shell): All the users will be authenticated against a SSH server provided by the administrator during installation.



Windows: Windows credentials can be used to authenticate users.



Access Management Service: All the users will be authenticated against a datastore managed by AMS.



Authorization Module for AMSThe authorization module is used by AMS to query group memberships and user details. AMS supports two authorization modules: Active Directory and AMS.

Active Directory

If you choose to use Active Directory, provide the details of the LDAP compatible server.




If you choose Access Management Service, no further inputs are required by the installer. Users will be authorized through a Local Datastore.



Database ConfigurationIn this screen, a New Database can be created or an Existing Database installed earlier with the PBS Works installer can be reused. In the example below, the database will be created in the local-host. The installer can create a non-admin user, (with username pbsworksuser) who will become the owner (Super User) of the database.



You can also provide the credentials of an existing OS user who will become the database Super User.



If the application is pointed to an existing database from a previous installation using the PBS Works installer, provide the credentials of the database super user.






PBS Works Service User ConfigurationTo run PBS Works service, provide the credentials of a user in the target system.



Installation SummaryThis screen summarizes all your choices before beginning the installation.

During installation, the billboards are displayed based on the installation options you selected.


Bookmark the link and make it available to the users of the portal.




7. Display Manager Console Installation


The installation steps in the console mode are identical to the steps in the GUI mode. In this chap-ter, screenshots of the console mode installation on Linux is displayed. Windows specific informa-tion is included wherever required.

Starting the Installer in Console ModeTo start the installer in console mode navigate to the location of the installer and type the name of the installer followed by -i console.

In the Linux terminal, enter the following command:./PBS_Works_13.2_Linux_x86_64.bin -i console

In Windows command prompt, enter the following command:PBS_Works_13.2_Windows_x86_64.exe -i console

Type next and previous to navigate the screens. To exit the installer, type quit. Type the number of your choice and press Enter to select the choice. To make multiple choices, enter the numbers of your choices separated by commas.

The Introduction screen is displayed. Press the Enter key to continue.[root@localhost PBS WORKS 13.2 Installer]# ./PBS_Works_13.2_Linux_x86_64.bin -i console



Unpacking the JRE...




===================================================================================

PBS Works Suite (created with InstallAnywhere)

-----------------------------------------------------------------------------------

69


Preparing CONSOLE Mode Installation...

===================================================================================

Introduction

------------

PBS Works Suite 13.2 installer will guide you through the installation.

It is strongly recommended that you quit all programs before continuing with

this installation.

Use the ''Enter" key to go to the next step and type "Back" to navigate to the

previous installation step. You may cancel this installation at any time by

using Ctrl-C.

Pre-requisites for Installation:

1. Minimum hard disk space of 4 GB

2. Minimum RAM of 4 GB

3. A non-admin User name and password to act as owner of PBSWorks Database

4. An User name and password of the user who would be acting as Portal

Administrator. This user should be existing on the authentication server.

5. An existing user in case you choose Enterprise data store to query user

details for authorization.

PRESS <ENTER> TO CONTINUE:

License Agreement ScreensThe License Agreement is displayed in a series of screens, please press Enter to scroll down and read it. To continue with the installation, press Y to accept it. PRESS <ENTER> TO CONTINUE:

counterparts, all of which together shall constitute one and the same instrument. Execu-tion. Copies of this Agreement executed via origin signatures, facsimile or email shall be deemed binding on the parties.

DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N) : Y

70 Display Manager Console Installation


Installation TypeChoose the Custom Installation option by typing 2 and pressing Enter.===============================================================================

Installation Type

-----------------

Please choose the type of installation that you would like to go ahead with. A

small description for the installation types is as below:

Express Install - Installs Compute Manager and Display Manager applications,

Results Visualization Service is not installed, uses windows authentication on

windows and ssh on Linux, uses local authorization, installs a new DB and

creates a default DB user.

Custom Install - Provides option to the users to configure the installation.

->1- Express Install

2- Custom Install

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:: 2

Altair Applications SelectionChoose the Applications option by typing 1 and pressing Enter.===============================================================================

Altair Applications and Service

-------------------------------

Please specify your installation options.

->1- Applications

2- Service: Results Visualization Service




Display Manager SelectionTo install Display Manager, type 2 and press Enter.===============================================================================

Applications

------------

Please select the applications you would like to install.

->1- Compute Manager

2- Display Manager(Compute Manager will be installed as a pre-requisite)

ENTER A COMMA-SEPARATED LIST OF NUMBERS REPRESENTING THE DESIRED CHOICES, OR

PRESS <ENTER> TO ACCEPT THE DEFAULT: 2

If the installer detects PBS and PAS servers in the target system, it will configure the servers for DM. If PBS MOM is also detected, it will install the DM Components. If the PBS and PAS servers are not detected, the Add On installer has to be run on PBS server, PAS server and the PBS MOMs for completing the DM installation.

PBS and PAS configurationIf the PBS Works installer detects PBS and PAS servers. It provides an option to automatically con-figure the servers and restart them or you can manually configure the servers and restart them.===================================================================PBS Professional Configuration------------------------------

To use Display Manager, PBS Professional must be configured. Configuration requires creating a new interactive work queue and adding a custom resource “ngpus” to the resourcedef and sched_config files, and then restarting PBS Pro.

This can be automatically done for you or you can choose to manually update the config-uration.

->1- Auto Configuration

2- Manual Configuration

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT::

If you opted for manual configuration, perform the steps in Configuration of PBS after the instal-lation.




• Binaries Install Location - This is where the PBS Works binaries are stored. The default location is:On Linux - /opt/altair/pbsworks/13.2/execOn Windows - C:\altair\pbsworks\13.2\execBinaries install location is referred as PBSWorks_HOME.

• Config Install Location - This is where the PBS Works configuration and log files are stored. The default location is:On Linux - /var/spool/pbsworks/13.2/homeOn Windows - C:\altair\pbsworks\13.2\homeConfig install location is referred as PBSWorks_EXEC.


===================================================================Choose install folder---------------------

Please choose the location of the install folders

Binaries install location (Default: /opt/altair/pbsworks/13.2):

Config install location (Default: /var/spool/pbsworks/13.2):

License Server ConfigurationType the license server location information. More than one location can be provided by separat-ing them with a colon (:) on Linux and a semicolon (;) on Windows.===============================================================================

License Server Configuration

----------------------------

"Applications" requires access to the Altair License Server to function. Please

provide the license server location.

You can provide multiple license server locations seperated by a colon.



License Servers (e.g: [email protected]:6200@lmxserver): (Default: ): [email protected]:6200@licsvr

Access Management Service ConfigurationAccess Management Service (AMS) can be installed on the target system to implement Authoriza-tion and Authentication rules for applications. Type 1 and press Enter to install a new instance of AMS in the target system.===============================================================================

Access Management Service Configuration

---------------------------------------

Please choose to install Access Management Service or use an existing instance

of the service.

->1- Install Access Management Service

2- Use an Existing Instance


Type 2 and press Enter to use an existing instance of AMS by providing the Hostname or IP Address and the port at which the AMS instance is running.



===================================================================Enable Single Sign-On (SSO)---------------------------

Do you want to enable Single Sign-On (SSO)? With SSO enabled, users will be logged in using their domain credentials.

i.e. the username and password they use to login to their client system

Service Principal Names (SPN) has to be set for SSO to work. Refer to PBS Works Administrator’s Guide for registering SPN.



1- Yes

->2- No

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT::

The following screen is displayed, if you enable SSO:

===================================================================Alert------

You Have choosen Yes to enable SSO

Please set SPN in system if not already set.

Please click “OK” to proceed or click “Cancel” to go to previous panel.

->1- OK

2- Cancel

ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT::

Domain Server ConfigurationIn this screen, provide the domain server and its corresponding details to verify SPN.

===================================================================Single Sign-On (SSO) Configuration----------------------------------

Please provide domain server details:

Domain Server: (Default: ):

Domain User: (Default: ):

===================================================================Enter Password--------------

Please Enter the Password:



Access Management Service ConfigurationAMS (Access Management Service) is used to implement authentication and authorization rules for the users of Display Manager application. The following options are available for AMS.

Authentication Module for AMS

The portal (PBS Works) and services can be configured to use the following authentication mech-anisms:

SSH (Secure Shell): All the users will be authenticated against a SSH server provided by the administrator during installation. Type 1 and press Enter to use SSH authentication.===============================================================================

Access Management Service: Authentication Module

------------------------------------------------

Access Management Service provides Authentication and Authorization services

for all Altair Products. It also helps create policies that define access

permissions to all the product features and services.

The next set of screens will guide you through the installation of Access

Management Service.

Please specify the module to be used for authentication.

->1- SSH

2- Access Management Service


On choosing SSH, provide the Hostname or IP address of the SSH server, or press Enter to use the localhost.===============================================================================

Access Manager : SSH Server Hostname/IP Address

-----------------------------------------------

Access Manager is a service to create policies that define access permissions

The Authentication Module for AMS is not displayed if Single Sign-On (SSO) is not enabled.



to product features and servers. It also provide Authentication and

Authorization services for all Altair products.

The next set of screens will guide you through the installation of Access

Manager. On Linux, SSH based authentication is supported. Please provide SSH

Server.

Hostname or IP Address (Default: localhost): sshsvr

Access Management Service: All the users will be authenticated against a datastore managed by AMS. Type 2 and press Enter to use AMS.

Authorization Module for AMSThe authorization module is used by AMS to query group memberships and user details. AMS supports two authorization modules: Active Directory and AMS===============================================================================

Access Manager: Authorization Module

------------------------------------

You can manage your users and groups using either of the following:

1. Windows Active Directory Server or any LDAP compatible server.

2. Altair's Access Management Service

1- Active Directory (LDAP)

->2- Access Manager Service


Type 2 and press Enter to use AMS based authorization.

Type 1 and press Enter to use Active Directory, provide the details of the LDAP compatible server in the next screens.



Database Configuration ScreenIn this screen, a New Database can be created or the application can be pointed to the address of an Existing Database. Type 1 and press Enter to create a new database in the localhost. The installer can create a non-admin user, (with username pbsworksuser) who will become the owner (Super User) of the database.===============================================================================

Database Configuration

----------------------

The selected options need access to the PBS Works Database.

Please choose to install a new database or use an existing database.

->1- New Database

2- Existing Database


If you want to use an existing database, type 2, press Enter and provide the hostname/ip address, the port of the database and the credentials of the database super user.

GPU Configuration for the ServerIf PBS is detected on the target system, the installer will ask you for the number of GPUs available in the cluster to configure the PBS Server===============================================================================

Display Manager: GPU Configuration for Server

---------------------------------------------

Provide the maximum number of GPUs available for the server

Available GPUs on the Cluster: (Default: 1): 2



GPU Configuration for the NodeIf PBS MOM is detected on the target system, the installer will ask you for the number of GPUs available in the node.===============================================================================

Display Manager: GPU Configuration for Node

---------------------------------------------

Available GPUs on the Node: (Default: 1): 2


===============================================================================Portal Administrator Credentials--------------------------------

Please provide the username to be used as the PBS Works Suite Portal

Administrator .This user must exist on the authentication server.

SSH based authentication is being used

User (Default: root): cmadmin



Pre-Installation Summary

After entering all the required information, a summary of all the chosen options is displayed. You can navigate to earlier screens and change your choices by typing previous or back. No changes are made to the server till the choices are confirmed in this screen.===============================================================================


------------------------

Please Review the Following Before Continuing:

Install Folder:

/opt/altair/pbsworks/13.2

Product Name:

PBS Works Suite 13.2

Installation Host:

localhost.localdomain

Applications/Service selected for installation:

Applications

Application Server Port:

8086

Database Host:

localhost

Database Port:

6767

DM Router Port:

9500

For the Windows installation, the credentials of a user has to be provided for the PBS Works Service. This information is not required for Linux.



Database Super User:

pbsworksuser

Portal Admin User:

pbsworksuser

Disk Space Information (for Installation Target):

Required: 818.78 MegaBytes

Available: 10,166.8 MegaBytes

PRESS <ENTER> TO CONTINUE:

Press the Enter key to start the installation process with your selected options.

Installation ProgressDuring installation, the following information is displayed.===============================================================================

Installing ...

------------------------

[===============|===============|===============|===============|===============]

[...............|...............|...............|...............|...............]

===============================================================================

PBS Works Suite Installation Complete

--------------------------------------

Congratulations! PBS Works Suite has been successfully installed to:

Install Directory : /opt.altair/pbsworks/13.2

Host : localhost.localdomain

Port : 8086

To login, proceed to

http://localhost.localdomain.8086/pbsworks

Press "Done to quite the installer.

PRESS <ENTER> TO EXIT THE INSTALLER:



=================================================================================

Restart Required!

------------------

System needs to be restarted for changes to take effect.

Would you like to restart now?

->1. Yes

2. No

ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: 1


In Linux, restarting the system is advised if DM Agent is installed. It is only required to restart X server to enable the DM Agent component access to the GPU.

Bookmark the link and make it available to the users of the portal


8. Installing DM Execution Components for Linux

This section provides the step by step procedure to install the Display Manager execution compo-nents (i.e Display Manager Agent and Display Manager Router) and configure PAS and PBS.

The DM Add-on installer should be used to complete the DM installation, if the PBS Works Suite installer does not detect PBS, PAS servers and PBS MOM on the target system. This is required for a distributed deployment option.

Display Manager Add-on InstallerThe DM Add-on installer is available through your usual Altair support channels.

To start the installer, type the name of the installer executable in the Linux console as shown below.[root@localhost PBS Works 13.2 Installer]# ./PBS_Works_13.2_DMA_Linux_x86_64.bin



Unpacking JRE...




The graphical launcher will work only if running the installer from within an X graphic environment or if proper redirection (e.g. "set DISPLAY=myhost:0.0") is set for the running shell.

83


The installer provides a notification that the PBS and PAS Servers might require to be restarted. It is advisable to run the installer when critical jobs are not running.

Choose No to exit and run the installer at a more suitable time. On choosing Yes, the Introduc-tion and License screens are displayed. On agreeing to the License, the available installation options are displayed.

Install OptionsThe Display Manager Add-On installer provides the following four install options.

• Configure PBS and PAS Server• Installing the Display Manager Router• Install Display Manager Agent• Unconfigure PBS and PAS Servers• Install the Display Proxy

The rest of this chapter explains the details for each of these options available in the installer.

84 Installing DM Execution Components for Linux


Configure PBS and PAS ServerThis option performs the following configurations:

• Creates and configures interactive work queue (iworkq)• Installs interactive application definition




Review the summary of choices made before proceeding with the installation.

On clicking the Install button, the installation progress is displayed along with the splash screens and the installation complete message is shown.



Installing the Display Manager RouterThis option installs the DM router.



Choose Install Folder

Choose the installation folder on the target system. During PBS Works installation, the following directory structures are created:






AMS Configuration for Display Manager Router

Provide the Hostname or IP Address of the Access Management Service Server for authenticating connections to the DM Router.




Install Display Manager AgentThis option installs the DM Agent and configures GPUs for the node.



Installation Folder







GPU Configuration for Node

Enter the number of GPUs available on the node.



Pre-installation Summary

Review the summary of your choices before proceeding to install.


It is recommended to restart the system on completing the installation.



Unconfigure PBS and PAS ServersThis option performs the following unconfigurations:

• Deletes the interactive queue• Unconfigures GPUs as a custom resource• Uninstalls interactive application definition

On choosing the Unconfigure PBS and PAS Server option, the following message is displayed.

While unconfiguration is in progress, splash screen is displayed and the process is completed.



Install the Display ProxyThis option installs the display proxy used for HTML5 viewer.



Installation Folder







9. Installing DM Execution Components for Windows

This section provides the step by step procedure to install the Display Manager execution compo-nents (i.e Display Manager Agent and Display Manager Router) and configure PAS and PBS.

The DM Add-on installer should be used to complete the Display Manager installation, if the PBS Works Suite installer does not detect PBS, PAS servers and PBS MOM on the target system. This is required for a distributed deployment option.

Display Manager Add-on InstallerThe DM Add-on installer is available through your usual Altair support channels.

Starting the InstallerLocate the installer executable in Windows Explorer, right click and choose the Run as adminis-trator option from the context menu as shown below.

97


The installer provides a notification that the PBS and PAS Servers might require to be restarted. It is advisable to run the installer when critical jobs are not running.

Choose No to exit and run the installer at a more suitable time. On choosing Yes, the Introduc-tion and License screens are displayed. On agreeing to the License, the available installation options are displayed.

Install OptionsThe Display Manager Add-On installer provides the following four install options.

• Configure PBS and PAS Server• Installing the Display Manager Router• Install Display Manager Agent• Unconfigure PBS and PAS Servers

The rest of this chapter explains the details for each of these options available in the installer.

98 Installing DM Execution Components for Windows


Configure PBS and PAS ServerThis option performs the following configurations:

• Creates and configures interactive work queue (iworkq)• Installs interactive application definition




Review the summary of choices made before proceeding with the installation.




Installing the Display Manager RouterThis option installs the Display Manager router.










AMS Configuration for Display Manager Router

Provide the Hostname or IP Address of the Access Management Service Server for authenticating connections to the DM Router.




Install Display Manager AgentThis option installs the Display Manager Agent.










Pre-installation Summary

Review the summary of your choices before proceeding to install.

The Display Manager billboards and file copy progress is displayed during installation. On com-pleting installation, a message is displayed. It is recommended to restart the system on completing the installation.



Unconfigure PBS and PAS ServersThis option performs the following unconfigurations:

• Deletes the interactive queue• Uninstalls interactive application definition

On choosing the Unconfigure PBS and PAS Server option, the following message is displayed.

While unconfiguration is in progress, splash screen is displayed and the process is completed.




10. Uninstalling Display Manager

In Linux, navigate to the _PBS Works Suite_installation directory in the location where the DM application is installed. Run the following command:

./Change\ PBS\ Works\ Suite\ Installation

[root@localhost _PBS Works Suite_installation]# ./Change\ PBS\ Works\ Suite\ Installation

In Windows, navigate to the _PBS Works Suite_ installation folder in the location where DM is installed. Right click on the Change PBS Works Suite Installation executable and select the Run as administrator option from the context menu as shown below.

The steps from this point onwards to uninstall Display Manager is identical on Windows and Linux platform. In this section, the example screenshots are based on the Linux version.

109


The Installer launches in Maintenance Mode. Select Uninstall Product and click on the Next but-ton.

In the next screen, click on the Uninstall button.

110 Uninstalling Display Manager


Confirm your choice in the alert box.

Confirm your choice for removing the CONFIG_HOME folder.

When you are uninstalling the DM in Linux, you can choose to update the servers automatically and restart them or you can manually update the servers and restart them.If you opted for manual configuration, perform the steps in Manual Uninstallation Configuration of PBS.

The following alert box is displayed when you are uninstalling the DM in Windows.

Uninstalling Display Manager 111


The uninstall process will begin and the progress will be shown

A confirmation message will be displayed. Click on Done to exit the installer.

112 Uninstalling Display Manager

11. Configurations

On successful installation, the PBS Works portal will be ready for use. Here is a list of configura-tions the installer takes care of:

• PBS Applications and Services• Verifying Display Manager Configurations• Database• Access Management Service• PBS Server Configurations• GPU Configuration as PBS resource• PAS Server Configurations• GPU Resource Configuration• Display Manager Agent Configuration• Display Manager Router Configuration• Display Manager Settings Configuration• Client Configuration for Application Launch Framework

PBS Applications and ServicesFollowing are the configurations made by the installer based on the inputs provided during instal-lation.

File What gets updatedLinux: /etc/pbsworks.confWindows: %SystemRoot%\System32\Driv-ers\etc\pbsworks.conf

Installation Home

SERVER_HOME/thirdparty/apache/tomcat/conf/server.xml

Control Ports

CONFIG_HOME/services/framework/data/factoryset-tings.xml

LMX License Location

CONFIG_HOME/AMS/AA/AA_Client.properties Access Management Service HostAccess Management Service Port

113


Verifying Display Manager ConfigurationsYou can use the information to configure DM without reinstalling it. In the PAS server, you can configure the PBS server location and port in the dmrest.properties file. You can configure the DM Router host and port in the dmviewer.properties file located in the PAS server.

DatabasePostgres will be silently installed by PBSWorks Suite installer without any input from user.

The following databases will be created based on the choice of applications.

If you choose to create a new user during installation, the installer will create a user with username as pbsworksuser.

CONFIG_HOME/framework/config/platform.xml Default LocaleLinux: /etc/init.d/pbsworks

Windows: SERVER_HOME\scripts\PBSWorksSer-vice.bat

Application Service Startup Scripts

Linux: /etc/init.d/pbsworks

Windows: SERVER_HOME\scripts\pbsworksdb.bat

Database Service Scripts

Postgres version 9.4.4Install Location SERVER_HOME/thirdparty/postgres

Postgres Home SERVER_HOME/thirdparty/postgres

Port The default port is 6767. If this port is not available, the installer tries to find a free port in next 100 ports. If it is unable to find a free port, the installer will request you to provide a suitable port number. Port details will be shown in the summary page before installation

Product Database Super User/PasswordCompute Manager pbsworksdb Provided by the user during installation.Display Manager pbsworksdb Provided by the user during installation.

File What gets updated

114 Configurations


Configurations:

Following files will be updated by the installer:

**The port by default will be 6767. The installer will search for next 100 ports if 6767 is not avail-able. If there is not free port even after searching for 100 ports, you will be asked to provide a port that's available.


Configurations Files

The installer modifies the following files based on the inputs given during the installation.

Here is a brief description of what these files are meant for:• CONFIG_HOME/AMS/AA_ServiceHome/config

- AA_jaas.config: This file contains the authentication module and its related settings- log4j.properties: This file contains the settings for Access Management Service log

settings

File What gets updatedSERVER_HOME\services\dm\config\spring-con-fig.xml

Database HostDatabase Port**Database User NameEncrypted Database Password

AMS Version RC 8.8Install Location SERVER_HOME/binaries/framework/webapps

AAService Home CONFIG_HOME/AMS/AAServiceHome

File What gets updatedCONFIG_HOME/AMS/AA_ServiceHome/config/AA_-jaas.config

Authentication Details based on the mode selected

CONFIG_HOME/AMS/AA_ServiceHome/config/AA_Ser-vice.properties

Authorization Mode

CONFIG_HOME/AMS/AA_ServiceHome/config/Data-store/Datastore.properties

Datastore settings

Configurations 115


- AA_Service.properties: This file contains the settings for time out and the mode of authorization.

- Datastore/Datastore.properties: This contains the settings of LDAP or Domain con-troller when you choose Enterprise mode authorization

• CONFIG_HOME/AMS/AA_ServiceHome/applications

- cm/cmActions.xml: The actions that Compute Manager administrators can perform through Access Management Service is defined in this file.

• CONFIG_HOME/AMS/AA_ServiceHome/resources

- AA_Groups.xml: This file holds the information about groups. CM administrators are defined in this file under the group "CMAdmin"

- AA_Users.xml: This file holds the details of the users when a local datastore is chosen as Authorization mode.

PBS Server ConfigurationsBelow are the configurations made to PBS by the installer (applicable for Linux cluster).

Verifying the Interactive Queue Configuration

The installer creates a queue called iworkq and configures it with ngpus provided during installa-tion. You can verify the configuration with the following command:zeethon:/var/spool/pas/config-private # qmgr -c "p q iworkq"

#

# Create queues and set their attributes.

#

#

# Create and define queue iworkq

#

create queue iworkq

set queue iworkq queue_type = Execution

set queue iworkq Priority = 150

set queue iworkq max_queued_res.ngpus = [o:PBS_ALL=32*]

set queue iworkq resources_max.ngpus = 1

set queue iworkq resources_min.ngpus = 1

set queue iworkq enabled = True

set queue iworkq started = True

*32 is the GPU count provided during the installation. This is the count of GPUs avail-able on the cluster

116 Configurations


GPU Configuration as PBS resourceresourcedef

An entry will be made to resourcedef under PBS_HOME/server_priv/.

You can verify the resourcedef configuration as below:zeethon:/var/spool/PBS/server_priv # grep -A3 "DM STATIC" resourcedef

# *********** BEGINNING OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND ******

ngpus type=long flag=nh

# *********** END OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND ************

sched_config

An entry will be made in PBS_HOME/sched_priv/sched_config as below:

zeethon:/var/spool/PBS/sched_priv # grep ngpu sched_config

resources: "ncpus, mem, arch, host, vnode, netwins, aoe, ngpus"

PAS Server ConfigurationsInteractive Application Definition:

An application definition will be installed in PAS_HOME/repository/applications folder and ijob.conf will be updated to point to the Display Manager server.

GPU Resource ConfigurationGPU will be configured as a resource in PAS Server by making the following entries to aif_re-sources_definitions.txt and resource_type.xml files in PAS_HOME/config-private/ directory.zeethon:/var/spool/pas/config-private # grep -A2 "DM STATIC" aif_resources_defini-tions.txt

# *********** BEGINNING OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND ******

ngpus type=long flag=nh

# *********** END OF DM STATIC RESOURCES SECTION.DO NOT EDIT BY HAND **

zeethon:/var/spool/pas/config-private # grep -A2 -B1 ngpus resource-type.xml

<JOB_RESOURCE>

<WMS_NAME>ngpus</WMS_NAME>

<WMS_TYPE>chunk</WMS_TYPE>

</JOB_RESOURCE>

Configurations 117


Display Manager Agent ConfigurationThe installer configures GPUs.

GPU Node Configuration

You can verify the GPU configuration as below:zeethon:~ # pbsnodes -a

Mom = zeethon.pbsworks.com

Port = 15002

ntype = PBS

state = free

pcpus = 1

resources_available.arch = linux

resources_available.host = zeethon

resources_available.mem = 3903096kb

resources_available.ncpus = 1

resources_available.ngpus = 2*

resources_available.vnode = zeethon

resources_assigned.accelerator_memory = 0kb

resources_assigned.mem = 0kb

resources_assigned.naccelerators = 0

resources_assigned.ncpus = 0

resources_assigned.netwins = 0

resources_assigned.ngpus = 0

resources_assigned.vmem = 0kb

resv_enable = True

sharing = default_shared

*This is the value provided during the installation process.

Display Manager Router ConfigurationThe only file that will be updated is the /etc/dmrouter.conf with the installation path.

Changing the DM Router PortsTo change the DM Router ports, follow the steps below:

1. Edit the router port entry in the routingservice.properties file located in the CONFIG_HOME/dmrouter/config/ directory.

118 Configurations


2. Edit the AMS or CM URL entry in the AA_Client.properties file located in the CONFIG_HOME/dmrouter/home/AA/config/ directory.

3. Edit the router port entry in the dmrest.properties file located in the CONFIG_HOME/services/dm/config/ directory.

Configurations 119


Display Manager Settings ConfigurationThe settings for Display Manager can be modified in adminSettings.xml located at CONFIG_HOME\services\dm\data\.

The following settings can be modified in the adminSettings.xml:

Settings Name Definitionmaxstarttimeout The maximum wait time for the display session to start. The possible

values are 30 seconds, 1 minute and 5 minute. By default it is set to 1 minute. A Session Timer dialog box is displayed showing the wait time for the session to start. If the session is not started within the specified wait time, then the session is aborted. You can also abort the session while the timer is running.

eststartuptimeout This is a soft timeout which triggers the startup dialog box to appear informing that the session is taking long time to start. By default, the value is set to 10 seconds.

viewerwindow Enable this option to launch the display session in a new independent applet window, instead of the browser window.

copybackfiles Specify a location for the staged out job. After running the session, the files used in the session are copied to this location.

If a DM session fails to start, this option can be used to download the files and examine the reasons for failure.

sessionaction Your sessions are retained even after you log out. This enables you to resume the work you were doing when you log in again. However, this value sets a time limit to specify how long the sessions should be retained after you log out.

By default, the sessions will be terminated after 5 years.view This is used to persist the ID of session in view; basically to connect

back the user to the last viewed session.

The factorySettings.xml available in the location CONFIG_HOME\services\dm\data\ has the default factory settings.

120 Configurations


To change Display Manager settings in the application, follow the steps:1. Click the settings icon, and choose the Settings option from the drop down menu as

shown below:

A Settings dialog box will be displayed.

The Settings dialog box can be used to set session save options, update license server infor-mation, set Display Manager preferences and Application Launch Framework client loca-tion.

Once a category has been selected and updates have been made, click Apply to apply the changes. To cancel any changes made, and close the Settings dialog box, click Cancel. To apply any changes made, and close the Settings dialog box, click OK. To restore any defaults, click Restore Defaults.

Configurations 121


2. Click Display Manager and update the preferences.

Client Configuration for Application Launch FrameworkDisplay Manager has the capability to launch session like RDP and RGS using the Application Launch Framework. The ALF client has to be configured, so that it can open the remote sessions.

Setup the ALF Desktop Component1. The ALF desktop component is available at http://<host>:<port>/pbsworks/ui/alf/

alf.zip (eg., http://dm-02:8086/pbsworks/ui/alf/alf.zip)2. Download the ALF zip and extract to the default install location on windows. The default

install location is SERVER_HOME\applications\alf\binaries\uiThe folder structure and the files in the alf folder after extracting the ALF zip file in the default location would be:- config- java.zip- libs- logs- launchmgr.bat- README.txt

122 Configurations


3. Extract the java.zip in the SERVER_HOME\applications\alf\binaries\ui path.

Modify the ALF Client LocationIf you extract the ALF client in a different location, then you have to modify the ALF client loca-tion in the application as follows:

1. Click the Settings icon, and choose the Settings option from the drop down menu as shown below:

A Settings dialog box will be displayed.

The ALF desktop component install location (SERVER_HOME\applica-tions\alf\binaries\ui) will match the ALF Client Location preference in Application Launch Framework. If you modify the default location, then the ALF desktop component install location must be modified.

Configurations 123


2. Click Application Launch Framework and update the ALF Client Location.

124 Configurations

12. Starting, Stopping and Restarting

PBS Works Portal

Determine the PBS Works Portal Status---------------------------------------------------------------------------------------

zeethon:/etc/init.d # /etc/init.d/pbsworks status

PBS Works 13.2 (pid 18908) is running

You can access the portal using link http://zeethon.pbsworks.com:8086/pbsworks

---------------------------------------------------------------------------------------

Starting the PBS Works PortalOn Windows:

1. Click Start, choose Run and type services.msc to open the Services Management Con-sole.

2. Select the PBSWorks Service in the list of services. Click the Start link to start the service.

125


On Linux:zeethon:/etc/init.d # /etc/init.d/pbsworks start

Stopping the PBS Works PortalOn Windows:

From the services console select the PBSWorks Service and click the Stop link.

On Linux:zeethon:/etc/init.d # /etc/init.d/pbsworks stop

Restarting the PBS Works PortalOn Windows:

From the services console select the PBSWorks Service and click the Restart link.

126 Starting, Stopping and Restarting


On Linux:

From the terminal window with root privilege, type the following command to restart the service:

zeethon: /etc/init.d # /etc/init.d/pbsworks restart

DM Router

Determine the DM Router Statuszeethon:/etc/init.d # /etc/init.d/dmrouter status

dmrouter is running with pid: 18860

Starting DM Routerzeethon:/etc/init.d # /etc/init.d/dmrouter start

Starting dmrouter

dmrouter started, pid: 29252

Stopping DM Routerzeethon:/etc/init.d # /etc/init.d/dmrouter stop

Stopping dmrouter

dmrouter stopped, was pid: 18860

Starting, Stopping and Restarting 127


128 Starting, Stopping and Restarting

13. Post Installation Administration

This chapter describes the post installation administration procedures.

The following topics are covered in this chapter:• Network Ports for Java Applet Viewer• Network Ports for HTML5 Viewer• Managing Applications• Managing Graphical Node Limits• Configuring the Browser for Application Shortcuts• HTML5 Viewer for VNC and RDP

- Enable HTML5 View Mode- HTML5 Supported and Unsupported Features- Configuration of Display Proxy for Windows Platform

• Keyboard Configuration

Network Ports for Java Applet ViewerThe Display Manager Application server and the Display Manager Router server should be able to communicate to the web browser through the firewall or gateway. Ensure the ports for the Display Manager application server (port 8086 by default) and the Display Manager Router (port 9500 by default) are able to communicate through the firewall or gateway. The port information for these two components is displayed in the installation summaries. Installation Summary shows this information for Display Manager application server and Installation Complete shows the screen for the Display Router installation summary.

Network Ports for HTML5 ViewerThe Display Manager Application server should be able to communicate to the web browser through the firewall or gateway. Ensure the port for the Display Manager application server (port 8086 by default) is able to communicate through the firewall or gateway. Installation Summary shows the port information for Display Manager application server.

129


Managing ApplicationsThe applications available in Display Manager are deployed as PAS Application definitions. Appli-cation definitions are a predefined set of instructions to describe application parameters, store responses and prepare responses for job execution.

In this section we describe the application definition details specific to Display Manager. More comprehensive information regarding Application Definitions is available in the PBS Application Services Administrator's Guide and the Diving Into Application Definitions Guide.

Location of Application definitionsWhen PAS server starts up, it scans the application definitions stored in a central repository to list the applications as resources available for PBS Professional.

Windows: C:\Program Files\altair\pas\13.2\PAS\home\repository\applications

Linux: /var/spool/pas/repository/applications

Main components of Display Manager Application DefinitionsA Display Manager Application Definition consists of the following components:

• An Application input file (e.g.app-inp-GlxSpheres.xml). The valid arguments for the application is specified in this file.

• The Application converter file (app-conv-GlxSpheres.xml). The values received through the input file are converted and communicated to the PAS and PBS through this file. The Job submission environment is configured in this file.

• The Application action file (e.g. app-actions-GlxSpheres.xml) The custom actions defined in this file enable Display Manager to communicate to PAS to perform actions on the interactive job while it is running.

• The Site Configuration file (site-config.xml). The information stored in this file can be referenced by any application definition. Applications, Application versions, Job projects and policies are some common settings that can be defined in the site configuration file.

Application specific for Linux and WindowsWriting a DM specific application definition is a bit more complex than writing simple applica-tions definitions. We recommend a simple procedure of copying and modifying the GLXSpheres application definition which is available as part of the Display Manager installation. A description

130 Post Installation Administration


of the important points to keep in mind while creating DM specific applications is covered in the next section.

Adding a New Application for LinuxThe steps to add a new application to Display Manager:

1. In the application definitions directory, copy the GlxSpheres application definition directory and rename it to the name of the application. In this example, let's assume we are adding HyperView to Display Manager. Run the following command. cp -rp GlxSpheres HyperView

2. Rename the GlxSpheres application definition files to the name of the application.mv app-actions-GlxSpheres.xml app-actions-HyperView.xml

mv app-conv-GlxSpheres.xml app-conv-HyperView.xml

mv app-inp-GlxSpheres.xml app-inp-HyperView.xml

3. Edit the app-inp-AppName file (e.g. app-inp-HyperView.xml).i. Change the <ApplicationId>GlxSpheres</ApplicationId> entry to the application

name.e.g. <ApplicationId>HyperView</ApplicationId>

ii. Change the <ApplicationName>GlxSpheres</ApplicationName> entry to the application name.e.g. <ApplicationName>HyperView</ApplicationName>

iii. Locate the VERSION category. In the xpath1 value, update the Application@id to the AppNamee.g.<ArgumentChoice>

<ArgumentStringEnumerated>

<Name>VERSION</NAME>

<Description> Version of the interactive application you selected to start</Description>

<DisplayName>Version</DisplayName>

<xi:include href="site-config.xml" pointer="xpath1 (//Application[@id='HyperView']/ApplicationVersions//Option)" />


</ArgumentChoice>

4. Open the app-actions-AppName file (e.g. app-actions-HyperView.xml) and change the <ApplicationId>GlxSpheres</ApplicationId> entry to the application name as described in step 3.i.



5. Open the app-conv-AppName file (e.g. app-conv-HyperView.xml) and make the changes described in step 3.i and step 3.ii. Set the required environment for the application.

You can set the ALTAIR_LICENSE_PATH, NCPUS, ngpus, MEMORY etc according to the requirements for the application.

(e.g. <jsdl-hpcp:Environment name="ALTAIR_LICENSE_PATH">6200@licsrv</jsdl-hpcp:Environment>

6. Restart the PAS services for these changes to take effect. Alternatively, you can remove the time stamp from the directory and wait for the services to pick up the updated files.

7. In the site-config.xml file located in the application definitions directory, add an entry for the application in the <Applications> section.

e.g.<Application id="HyperView">

<ApplicationVersions>

<ApplicationVersion>

<Option>13.2</Option>

<Executable>/altair/hw/13.2/altair/scripts/hv</Executable>

</ApplicationVersion>

</ApplicationVersions>

</Application>

Example to define multiple executable versions of the application definition:<Application id="HyperView">










</ApplicationVersions></Application>

You can also define multiple executable versions for the application defi-nition.



8. Once PAS picks up the new application definitions, the application will be available in Dis-play Manager.

Adding a New Application for WindowsThe steps to add a new application to Display Manager:

1. In the application definitions directory, copy the Notepad application definition directory and rename it to the name of the application. In this example, let's assume we are adding HyperView to Display Manager. Run the following command. copy Notepad HyperView

2. Rename the Notepad application definition files to the name of the application.rename app-actions-Notepad.xml to app-actions-HyperView.xml

rename app-conv-Notepad.xml to app-conv-HyperView.xml

rename app-inp-Notepad.xml to app-inp-HyperView.xml

3. Edit the app-inp-AppName file (e.g. app-inp-HyperView.xml).i. Change the <ApplicationId>Notepad</ApplicationId> entry to the application name.

e.g. <ApplicationId>HyperView</ApplicationId>ii. Change the <ApplicationName>Notepad</ApplicationName> entry to the application

name.e.g. <ApplicationName>HyperView</ApplicationName>

iii. Locate the VERSION category. In the xpath1 value, update the Application@id to the AppNamee.g.<ArgumentChoice>





<xi:include href="site-config.xml" pointer="xpath1 (//Application[@id='HyperView']/ApplicationVersions//Option)" />


</ArgumentChoice>

4. Open the app-actions-AppName file (e.g. app-actions-HyperView.xml) and change the <ApplicationId>Notepad</ApplicationId> entry to the application name as described in step 3.i.



5. Open the app-conv-AppName file (e.g. app-conv-HyperView.xml) and make the changes described in step 3.i and step 3.ii. Set the required environment for the application.

You can set the ALTAIR_LICENSE_PATH, NCPUS, MEMORY etc according to the requirements for the application.

(e.g. <jsdl-hpcp:Environment name="ALTAIR_LICENSE_PATH">6200@licsrv</jsdl-hpcp:Environment>

6. Restart the PAS services for these changes to take effect. Alternatively, you can remove the time stamp from the directory and wait for the services to pick up the updated files.

7. In the site-config.xml file located in the application definitions directory, add an entry for the application in the <Applications> section.

e.g.<Application id="HyperView">






</ApplicationVersions>

</Application>

Example to define multiple executable versions of the application definition:<Application id="HyperView">










</ApplicationVersions></Application>

You can also define multiple executable versions for the application defi-nition.



8. Once PAS picks up the new application definitions, the application will be available in Dis-play Manager.

Display Manager Specific Information for Application DefinitionsAny application that should be shown in Display Manager should contain the following <Interac-tive> tag in its app-inp-AppName application definition.

<ApplicationId>Application</ApplicationId>

<ApplicationName>Name of the Application</ApplicationName>

<Interactive>true</Interactive>

The <Interactive> tag should be set to true. PAS will scan an application definition for the <Interactive> tag and identify it as a DM application. Only these applications are filtered and dis-played in the DM UI.

Display Manager should contain the following <ArgumentChoice> declared in its app-inp-AppName application definition.

<ArgumentChoice>

<ArgumentString>

<Name>JOB_NAME</Name>

<Description>The name of the Job.</Description>

<DisplayName>Job Name</DisplayName>

<InputRequired>true</InputRequired>

</ArgumentString>

</ArgumentChoice>

Multiple versions of an application is derived from the PAS reserved keyword defined in the VER-SION section. This refers to the site-config.xml used by PAS.<ArgumentChoice>





If this section is not included, Display Manager will not be aware of the interactive application.



<xi:include href="site-config.xml" xpointer="xpath1(//Applica-tion[@id='HyperView']/ApplicationVersions//Options)" />


</ArgumentChoice>

Application Specific Configurations for GPUs, Display Geometry, Number of CPUs, and Memory can be defined in the app-input-AppName.xml.<ArgumentChoice>

<ArgumentBooleanWithDescription>

<Name>GPU</Name>

<Description>Is GPU required ?</Description>

<DisplayName>GPU(?)</DisplayName>

<InputRequired>false</InputRequired>

<FeatureEnabled>true</FeatureEnabled>

</ArgumentBooleanWithDescription>

</ArgumentChoice>

The following new application specific configuration for Display Manager can be defined in the app-input-AppName.xml file:

• Arguments - this can be used if multiple number of variables has to be specified for the submitted job. The variables should be separated by ‘\n’.

<ArgumentChoice>

<ArgumentString>

<Name>DM_APP_ARGS</Name>

<Description>'\n' separated args</Description>

<DisplayName>Arguments</DisplayName>


</ArgumentString>

</ArgumentChoice>

• Environment - this can be used to pass other environment related variables. The variables should be separated by ‘\n’.

<ArgumentChoice>

<ArgumentString>

<Name>DM_APP_ENVS</Name>

The FeatureEnabled option for GPU, controls the request for GPUs. For 2D applications set it to false and a request for GPUs will not be made for the application. For 3D applications, FeatureEnabled option has to be set to true.



<Description>'\n' separated envs</Description>

<DisplayName>Environments</DisplayName>


</ArgumentString>

</ArgumentChoice>

• WorkDirectory - use this argument to create a working directory for the jobs that are sub-mitted.

<ArgumentChoice>

<ArgumentString>

<Name>DM_APP_WDIR</Name>

<Description>Working dir</Description>

<DisplayName>Working Dir</DisplayName>


</ArgumentString>

</ArgumentChoice>

• Copy back files - use this argument to create a backup of the files that are submitted for the jobs in the stageout directory.

<ArgumentChoice>

<ArgumentBooleanWithDescription>

<Name>COPY_BACK_FILES</Name>

<Description>Should job file(s) be staged out</Description>

<DisplayName>Copy back files</DisplayName>

<InputRequired>true</InputRequired>

<FeatureEnabled>false</FeatureEnabled>

<RefreshOnUpdate>true</RefreshOnUpdate>

</ArgumentBooleanWithDescription>

</ArgumentChoice>

• Client View Mode - this can be used to change the view mode from Applet to HTML5. <ArgumentChoice>


<Name>DM_CLIENT_VIEW_MODE</Name>

The arguments mentioned above is disabled by default. Enable them by setting the InputRequired field to true.

The Copy_Back_Files arguments is disabled by default. Enable this field by setting the FeatureEnabled option to true. This options will be dis-played while submitting a job in Compute Manager. You can also change this option in the Display Manager Settings.



<Description>Viewer mode</Description>

<DisplayName>Viewer mode</DisplayName>


<Option>Applet</Option>

<Option>Desktop</Option>

<Option>HTML5</Option>

<Value>Applet</Value>

</ArgumentStringEnumerated>

</ArgumentChoice>

In the app-conv-AppName application definition file, the following section determines which jobs are displayed in Display Manager.<jsdl-hpcp:Environment name="DM_JOB">True</jsdl-hpcp:Environment>

If this is set to False, apart from the interactive Display Manager jobs, all the other jobs belonging to the user will be displayed. Ensure that this is set to True.

Application specific Environment values like ALTAIR_LICENSE_PATH, VERSION, NCPUS, ngpus, MEMORY etc. can be defined here.

To have the HTML5 View mode, change the Value to HTML5.

In the app-actions-AppName application definition file, apart from chang-ing the <ApplicationID>, no other changes are recommended.



Managing Graphical Node LimitsThe installer configures all the node and cluster limits for the GPUs. Follow the below procedure in situations where these limits might change (e.g. a node going down or being removed, adding new graphical nodes post install, etc.)

Modify the Cluster GPU LimitAn attribute that controls this limit is defined for the PBS queue (iworkq) that exclusively handles interactive job requests for a PBS server.

For example,

set queue iworkq max_queued_res.ngpus = [o:PBS_ALL=5]

The numerical value "5" is the available GPU limit for the cluster. This is the cumulative number of all the GPUs available in the cluster managed by the PBS server. Change this value to accommo-date any changes in the limit due to addition or removal of Graphical nodes or Graphic devices in nodes.

Modify the Node GPU LimitAn attribute that controls this limit is defined for every Graphical node configured in the cluster.

For example,

set node v03 resources_available.ngpus = 2

The numerical value "2" is the available GPU limit for the node v03, this is the cumulative number of all the graphical devices available in a particular node. This value will need to be changed to accommodate any changes to the limit due to addition or removal of Graphical devices to the node.

Refer to the Troubleshooting section for fixing any known issues during setup.



Configuring the Browser for Application ShortcutsSeveral applications like HyperMesh and HyperView use the mouse scroll wheel for critical opera-tions like rotating a model or zooming in and out. For a consistent and smooth application experi-ence, these shortcuts must not be intercepted by the web browser.

In Mozilla Firefox, open the configurations section by typing about:config in the address bar. Set the value of the parameter mousewheel.with_controlkey.action to 0.

In Internet Explorer in Windows,

1. Go to Start > Run and type gpedit.msc

2. Navigate to User Configuration > Windows Components > Internet Explorer

3. On the right hand side page double click to open Turn off page-zooming functionality. Click on enabled.

4. Restart Internet Explorer.

HTML5 Viewer for VNC and RDPHTML5 Viewer now supports VNC and RDP for remote desktop.

Enable HTML5 View ModeTo enable HTML5 View Mode for an application, it's application definition file has to be edited.

1. Open the application input file.

Location of the application definition files:Windows: C:\Program Files\altair\pas\13.2\PAS\home\repository\applicationsLinux: /var/spool/pas/repository/applications

2. Locate the DM_CLIENT_VIEW_MODE category.

Reset these option after using Display Manager to return to your normal browsing experience.

By default, GLXSpheres application definition is available as part of the Display Manager installation.



For example: <ArgumentChoice>


<Name>DM_CLIENT_VIEW_MODE</Name>

<Description>Viewer mode</Description>

<DisplayName>Viewer mode</DisplayName>


<Option>Applet</Option>

<Option>Desktop</Option>

<Option>HTML5</Option>

<Value>Applet</Value>

</ArgumentStringEnumerated>

</ArgumentChoice>

3. Change the Value field to HTML5.

e.g. <Value>HTML5</Value>4. Save the file.5. Remove the time_stamp.txt file located in the repository folder or Restart the PAS Server.

Location of the time_stamp.txt file:Windows: C:\Program Files\altair\pas\13.2\PAS\home\repositoryLinux: /var/spool/pas/repository/

HTML5 Supported and Unsupported FeaturesHTML5 Supported feature:

• HTML5 view mode will open the application in a new window

HTML5 Unsupported feature:• Session Settings option:

- Image Quality settings- Performance Metrics

• Dynamic resizing of the windows

By default the DM_CLIENT_VIEW_MODE is set to Applet.



Configuration of Display Proxy for Windows PlatformIf the portal is running on Windows, then the display proxy for windows portal has to point to a server instance on Linux.

To update the display proxy: 1. Open the guacamole.properties located at:

Windows: SERVER_HOME\services\dm\configLinux: SERVER_HOME/services/dm/

2. Change the hostname and port of display proxy to point to the Linux server instance.The default hostname and port details are:guacd-hostname: localhost

guacd-port: 4822

Keyboard ConfigurationKeyboard entries for the certain characters like @ # [ ] { } do not work in OS X using JRE 7. These keys will work when using JRE 6. Currently, if you are using OS X, please use JRE 6 to work on Display Manager.


14. Troubleshooting

Quick Troubleshooting ChecklistOn completing the installation the services relevant to Display Manager should be up and run-ning. This quick troubleshooting section assumes services like vncrouter, dmagent, application services, PAS and PBS with PBS-P are running and configured

Checklist for the Web Client:

1. Verify that Java is enabled and working in the web browser. To solve Java related issues, refer to the Java troubleshooting document at: http://www.java.com/en/download/help/trouble-shoot_java.xml

Checklist for the Execution node (or Graphics node):

2. Make sure that all the DM components are able to communicate with each other. Hostname resolution should be consistent with DM needs and information entered during installation.

3. As a prerequisite, the execution node should be set up to run VNC server successfully for the user. Run the following command:

/opt/TurboVNC/bin/vncserver -noauth

Browse to: http://$host:$vncwebport (e.g. http://v01:5801),

Replace v01 with the VNC server host name and 5801 (5800 + display #) with the http port of the VNC server.

If you don't see the virtual desktop, please forward the ~/.vnc folder to the support team for further investigation.

4. As another prerequisite, X server must be configured and running.

Verify if X server is running for display:0 (usually with process name Xorg or X). In case it is not running, reconfigure X server with /usr/bin/nvidia-xconfig --use-display-device=NONE --enable-all-gpus --keyboard=us

This will overwrite existing configurations and configure the X server with all available GPUs.

5. Access to X server must be granted for the user. (The DM Installer will do this)

143




Run the following command in a terminal window in the remote desktop session created in Step 1

/opt/VirtualGL/bin/glxinfo -display :0 -c

the command should output a list of visuals and complete with no errors.

6. Does the Graphics driver support VirtualGL?

To verify, use the command:

glxinfo -display :0

Look for visuals with a class of "tc", a buffer size of 24 or 32, a caveat of "None", and drwtyp "P" in the right-most column. direct rendering: Yes

OpenGL version string: "should state vendor driver version here"

e.g., 3.3.0 NVIDIA 260.19.36 and not a software renderer like mesa. Latest vendor drivers are recommended

7. Is VirtualGL configured and functional. (Pre-requisite)

Run the following command in a terminal window in the remote desktop session created in Step 1

/opt/VirtualGL/bin/vglrun -d :0.0 -sp /opt/VirtualGL/bin/glxspheres64".

If GLXSpheres starts, then VirtualGL is properly configured. If not, a detailed investigation is required by the support team.

8. Check for errors for the DM appdef in the PAS logs.

9. Verify that the pbs_mom logs do not report any error related to the DM jobs associated with the DM sessions. i.e. errors related to file transfers.

10. Verify that PBS Pro jobs submitted as DM ends up running on the expected host(s) without errors. For example, when debugging problems related to the execution host dmhost1, verify that a job like:

qsub -l select=1:ncpus=1:mem=8gb:ngpus=1:host=dmhost1 -Wsandbox=PRIVATE -I

is correctly running and does not generate any errors in any PBS Pro logs, most importantly in the related pbs_mom logs. Tune the resource requests to match the actual ones DM uses when generating this jobs. PBS Pro job history will help identify the correct values: qstat -fx <jid of failed dm job>.

144 Troubleshooting


Resource Availability Error Graphical resources are not available at this time

This error message is shown when there are no available graphical resources to schedule the sub-mitted job.

Level: Production & Admin.

Occurrence: Frequent.

What to look for:

Verify whether all the configured graphical resources in the cluster are occupied. Each interactive job will occupy a GPU, switch to Compute Manger monitoring page or run qstat command on PBS the head node to know the list of running interactive jobs at a given time.

1. If the number of running interactive jobs is equal to the total number of available GPU's configured in the cluster, then the user has to wait until one of them gets finished for the error message to disappear.

2. Another cause might be due to PAS/PBS errors which are not in the scope of this docu-ment, however refer to relevant guides to provide a fix for the identified problem.

Resource Acquisition ErrorExecution host information not available on time

This error message is shown when the DM web service did not get an update from the PBS job script of an interactive job about the execution node information within a time period after being successfully scheduled.

Level: Admin.


What to look for:1. The job script of the interactive job (/var/spool/pas/applications/interactiveApp/run-

time/iJobStart.py) uses certain environments that are prefixed with PAS, but with the older versions of PAS installation same variables are prefixed with AIF. The references need to be changed to match the current PAS installation.

2. Another cause might be due to PAS/PBS errors which are not in the scope of this docu-ment, however refer to relevant guides to provide a fix for the identified problem.

Troubleshooting 145


Only the display session is shown but not the application that was startedAfter starting an application, you might notice that the display session was shown but not the application. Generally it happens when the user doesn't have access to the 3D X server.

Level: Admin.


What to look for:1. Check whether the user has access to the 3D X server.

a. Open a terminal and run "xdpyinfo -display :0" or "/opt/VirtualGL/bin/glxinfo -display :0 -c"

"unable to open display :0" means the user doesn't have permission to access the 3D X Server, verify whether VGL server is configured correctly (http://www.virtualgl.org/vgldoc/2_2_1/#hd005001) or the user doesn't belong to the vglusers group.

2. Check whether the X is configured correctly.Verify whether X Server is configured to export True Color (24 bit or 32 bit) visuals. (eg., use "/usr/bin/nvidia-xconfig --use-display-device=NONE --enable-all-gpus --key-board=us" to configure X server for nVidia devices)

3. Check whether the application is configured correctly.Refer to the Managing Applications section of this guide.

Graphic Card Compatibility Issues with Display ManagerUse the drivers provided by the manufacturer of the graphic card. If the manufacturer of your 3D adapter provides proprietary drivers for Linux, then it is recommended that you install these. Many of the drivers that ship with Linux do not provide full 3D acceleration or Pbuffer (pixel buf-fer) support.

Level: Admin.


What to look for:

Inspect the output of /opt/VirtualGL/bin/glxinfo -display :0 -c for the below.

146 Troubleshooting

http://www.virtualgl.org/vgldoc/2_2_1/#hd005001

http://www.virtualgl.org/vgldoc/2_2_1/#hd005001


1. Look at the OpenGL renderer string and make sure it doesn't contain any variant of mesa or software

2. Direct Rendering is Yes3. Look for visuals with a class of tc, a buffer size of 24 or 32, a caveat of None, and have a P in

the right-most column.

Here is an example output for the command:

[root@dmsystem-linux ~]# /opt/VirtualGL/bin/glxinfo -display :0

name of display: :0

display: :0 screen: 0

direct rendering: Yes

server glx vendor string: NVIDIA Corporation

server glx version string: 1.4

server glx extensions:

GLX_ARB_context_flush_control, GLX_ARB_create_context,

GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness,

GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age,

GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,

GLX_EXT_framebuffer_sRGB, GLX_EXT_stereo_tree, GLX_EXT_swap_control,

GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap,

GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer,

GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer,

GLX_NV_multisample_coverage, GLX_NV_swap_group, GLX_NV_video_capture,

GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control,

GLX_SGI_video_sync

client glx vendor string: NVIDIA Corporation

client glx version string: 1.4

client glx extensions:



GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample,

Troubleshooting 147


GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,

GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float,

GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree,

GLX_EXT_swap_control, GLX_EXT_swap_control_tear,

GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,

GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap,

GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_present_video,

GLX_NV_swap_group, GLX_NV_video_capture, GLX_NV_video_out,

GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control,

GLX_SGI_video_sync

GLX version: 1.4

GLX extensions:



GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample,

GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,

GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB,

GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear,

GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,

GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap,

GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_swap_group,

GLX_NV_video_capture, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,

GLX_SGI_swap_control, GLX_SGI_video_sync

148 Troubleshooting

Glossary

Account. An account is an arbitrary character string, which may have meaning to one or more hosts in the batch system. Frequently, an account is used as a grouping for charging for the use of resources.

Accounting Log. The PBS Professional accounting log is a text file containing information about a cluster's HPC job activity.

Administrator. A person who administers a product (CM, DM, RVS, PAS, PBSA, or PBS), per-forming functions such as downloading, installing, upgrading, configuring, or managing the product. Administrator is distinguished from "site administrator", although often these are the same person.

Access Management Service, AMS. A centralized configuration system for authentication and authorization.

Application Definition. A predefined set of instructions to describe your application parameters to users, store their responses, and prepare those responses for job execution via PBS Professional. An application definition provides a flexible set of instructions that can be manipulated to allow for precise control over all aspects of application-specific parameters and job execution.

Chart. A charts is a visual representation of data. Charts are used to ease understanding of large quantities of data and the relationships between parts of the data.

Cluster. A relatively homogeneous set of systems that are used as if they are a single machine.

Commands, PBSA Commands, PAS Commands. A set of command-line commands. PBSA Commands are commands that assist with the configuration of PBSA. PAS Commands provide job submission, monitoring, as well as file operations capabilities from the command-line.

Complex. A PBS complex consists of the machines running one primary server+Scheduler (plus, optionally, a secondary backup server+Scheduler) and all the machines on which the MoMs (attached to this server+Scheduler) are running. A complex can be a heterogeneous mix of system architectures, and can include one or more clusters.

Consumable resource. A consumable resource is a resource that is reduced or taken up by being used. Examples of consumable resources are memory or CPUs.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

149


CPU. Has two meanings, one from a hardware viewpoint, and one from a software viewpoint: • A core. The part of a processor that carries out computational tasks. Some systems present

virtual cores, for example in hyperthreading.• Resource required to execute a program thread. PBS schedules jobs according, in part, to

the number of threads, giving each thread a core on which to execute. The resource used by PBS to track CPUs is called "ncpus". The number of CPUs available for use defaults to the number of cores reported by the OS. When a job requests one CPU, it is requesting one core on which to run.

Custom group. Custom groups are specific to PBS Analytics, and are an alternative for tracking usage of HPC resources at a project level for sites running versions of PBS Professional prior to 11.2.

Custom resource. A resource that is not defined in PBS as shipped. Custom resources are created by the PBS administrator or by PBS for some systems.

Daily Parsing. A PBSA activity where information from the PBS Professional accounting logs is parsed, and then loaded into a database. Once the PBS Professional accounting logs have been parsed for the first time (see Initial Parsing), daily parsing is scheduled by default to occur at 1:00 am, and will parse any newly generated accounting logs.

Dashboard. A dashboard is a visual display of the most important information needed to achieve one or more objectives; consolidated and arranged on a single screen so the information can be monitored at a glance.

Dimension. A field or variable that is displayed on a PBSA chart. Dimensions are the independent variable (often denoted by the x-axis) whose variation does not depend on another variable. Examples are users, software, servers, and nodes. PBSA requires that Dimensions be displayed on the x-axis or z-axis (in the case of a three dimensional chart).

Demonstration Database. A database that is loaded with demonstration data. An installation option is available that installs PBSA with a demonstration database, so that all out-of-the box charts, dashboards, and slideshows can be viewed, and all key features of PBSA can be accessed and evaluated.

Execution host. A computer which runs PBS jobs. An execution host is a system with a single operating system (OS) image, a unified virtual memory space, one or more CPUs and one or more IP addresses. Systems like Linux clusters, which contain separate computational units each with their own OS, are collections of hosts. Systems such as the SGI ICE are also collections of hosts. The SGI Altix 4700 is a single execution host.

150 Glossary of Terms


An execution host can be comprised of one or more vnodes. For example, the SGI Altix 4700, while being a single execution host, can contain multiple vnodes, where each vnode is a blade. On the SGI ICE, each blade is treated as a vnode. See Vnode.

File Service Provider, FSP. A PAS mechanism for executing remote file operations on the PBS Professional execution hosts. It removes the dependency upon PBS Professional for remote file operations and file transfers.

Finished Jobs. Jobs whose execution is done, for any reason:• Jobs which finished execution successfully and exited • Jobs terminated by PBS while running • Jobs whose execution failed because of system or network failure • Jobs which were deleted before they could start execution

Fully Qualified Domain Name, FQDN. The complete domain name for a specific computer, or host, on the Internet. The FQDN consists of two parts: the hostname and the domain name.

Furnishing Server. The server from which the job is pulled when peer scheduling is implemented.

Group. A collection of system users. A user must be a member of at least one group, and can be a member of more than one group.

Head Node. Machine where the PBS Server is installed.

High Performance Computing, HPC. High Performance Computing (HPC) most generally refers to the practice of aggregating computing power in a way that delivers much higher perfor-mance than one could get out of a typical desktop computer or workstation in order to solve large problems in science, engineering, or business.

Holiday. A non-working day usually associated with a special day of celebration.

Host. A machine running an operating system. A host can be made up of one or more vnodes.

Initial Parsing. A PBSA activity where information from the PBS Professional accounting logs is parsed, and then loaded into a database. Initial parsing is when the accounting logs are parsed for the first time after installation and configuration of PBSA is complete. Initial parsing may take anywhere from several hours to several days depending upon the amount of data stored in the PBS Professional accounting log(s), number of processors, and amount of available RAM.

Job or Batch job. A unit of work managed by PBS. A job is a related set of tasks, created and sub-mitted by the user. The user specifies the resources required by the job, and the processes that make up the job. When the user submits a job to PBS, the user is handing off these tasks to PBS to

Glossary of Terms 151


manage. PBS then schedules the job to be run, and manages the running of the job, treating the tasks as parts of a whole. A job is usually composed of a set of directives and a shell script.

Job ID, Job identifier. When a job is successfully submitted to PBS, PBS returns a unique identi-fier for the job. Format: sequence_number[.server][@new server]

Job State. A job exists in one of the possible states throughout its existence within the PBS system. For example, a job can be queued, running, or exiting.

License Server. A centralized computer software system which provides access tokens, or keys, to client computers in order to enable licensed software to run on them.

Measure. A field or variable that is displayed on a PBSA chart. Measures are the dependent vari-able (often denoted by the y-axis) whose value changes dependent on the other variables. Exam-ples are total numbers of jobs, average memory used, and total CPU walltime. Measures are displayed on the y-axis. The PBSA Web Application refers to Measures as Values.

MoM. The daemon which runs on an execution host, managing the jobs on that host. MoM is the informal name for the process called pbs_mom. One MoM runs on each execution host.

MoM runs each job when it receives a copy of the job from the server. MoM creates a new session that is as identical to the user's login session as possible. For example under UNIX, if the user's login shell is csh, then MoM creates a session in which .login is run as well as .cshrc. MoM returns the job's output to the user when directed to do so by the server.

MoM is a reverse-engineered acronym that stands for "Machine Oriented Mini-server".

Mother Superior. Mother Superior is the MoM on the head or first host of a multihost job. Mother Superior controls the job, communicates with the server, and controls and consolidates resource usage information. When a job is to run on more than one execution host, the job is sent to the MoM on the primary execution host, which then starts the job.

Node. No longer used. See Execution Host.

Nodeclass. A custom resource that groups or classifies PBS Professional nodes. PBSA automati-cally assign a nodeclass based on cores and memory when node information is added to PBSA via the pbsa-config-nodes command.

Node Details. A map of your site's PBS Professional cluster, that is each PBS Professional server and its associated execution hosts. This information is stored in a configuration file, and is used by PBSA to provide HPC resource usage statistics.

Non-consumable resource. A non-consumable resource is a resource that is not reduced or taken up by being used. Examples of non-consumable resources are Boolean resources and walltime.



Non-Prime Time Hours. Non-working hours.

Owner, Job owner. The user who submitted a specific job to PBS.

Parsing. A PBSA activity where information from the PBS Professional accounting logs is parsed, and then loaded into a database.

PAS_EXEC.The path containing PAS executables. The path under which PAS executables are installed on the local system. The location of this directory is platform dependent.

PAS_HOME. The path containing PAS configuration and log files. The path under which PAS configuration and log files are installed on the local system. The location of this directory is plat-form dependent.

PBS Analytics, PBSA. A job accounting and reporting solution that provides PBS Works adminis-trators with advanced analytics to support data-driven planning and decision making. Data from multiple PBS Professional servers can be consolidated, providing a global view of your HPC usage for chargeback, capacity planning, troubleshooting and project management.

PBS Application Services, PAS. A middleware component that communicates with the PBS Pro-fessional complex and the operating system, and provides services for the front end client applica-tions such as graphical user interfaces.

PBS Professional. A workload management system consisting of a server, a Scheduler, and any number of execution hosts each managed by a MoM. PBS accepts batch jobs from users, and schedules them on execution hosts according to the policy chosen by the site. PBS manages the jobs and their output according to site-specified policy.

PBS Works. PBS Works is a suite of products for comprehensive, secure workload management for high-performance computing (HPC) environments.

PBS_EXEC. The path containing PBS executables. The path under which PBS executables are installed on the local system.

PBS_HOME. The path containing PBS files. The path under which PBS files are installed on the local system.

PBSA Data Collector, Data Collector. A software component of PBSA, installed on execution hosts, responsible for making the PBS Professional accounting logs accessible to the PBSA engine.

PBSA Engine, PBSA Web Application. A software component of PBSA that consists of web ser-vices, a database, and an analytics engine responsible for the analysis and visualization of HPC resources.



PBSA Hook. A mechanism for adding a custom resource to PBSA.

PBSA Parser, Parser. A software component of PBSA that is responsible for parsing the PBS Pro-fessional accounting logs and loading this information into the PBSA database.

PBSWORKS_EXEC. The path containing PBS Works executables. The path under which PBS Works executables are installed on the local system. The location of this directory is platform dependent.

PBSWORKS_HOME. The path containing PBS Works configuration and log files. The path under which PBS Works configuration and log files are installed on the local system. The location of this directory is platform dependent.

Peer scheduling. A feature allowing different PBS complexes to automatically run each others' jobs. This way jobs can be dynamically load-balanced across the complexes. Each complex involved in peer scheduling is called a peer.

Prime Time Hours. Working hours.

Project. In PBS, a project is a way to group jobs independently of users and groups. A project is a tag that identifies a set of jobs. Each job's project attribute specifies the job's project.

Queue. A queue is a named container for jobs at a server. There are two types of queues in PBS: routing queues and execution queues. A routing queue is a queue used to move jobs to other queues including those that exist on other PBS servers. A job must reside in an execution queue to be eligible to run and remains in an execution queue during the time it is running. In spite of the name, jobs in a queue need not be processed in queue order (first-come first-served or FIFO).

Resource. A resource can be something used by a job, such as CPUs, memory, high-speed switches, scratch space, licenses, or time, or it can be an arbitrary item defined for another pur-pose. PBS has built-in resources, and allows custom-defined resources.

Scheduler. The PBS scheduler is the daemon which implements the site's job scheduling policy controlling when and where each job is run. The scheduler is the process called pbs_sched.

Scheduling. The process of selecting which jobs to run when and where, according to a predeter-mined policy. Sites balance competing needs and goals on the system(s) to maximize efficient use of resources (both computer time and people time).

Server. The central PBS daemon, which does the following:• Handles PBS commands • Receives and creates batch jobs• Sends jobs for execution



The server is the process called pbs_server. Each PBS complex has one primary server, and if the complex is configured for failover, a secondary server. The server contains a licensing client which communicates with the licensing server for licensing PBS jobs.

Server Configuration File. A file containing all configurable parameters available with PAS.

Service User. Windows platforms only. The user under which the CM or PAS Windows service is registered.

Site Configuration File. A central repository for site specific information that can be used across all application definitions.

User. Has two meanings:• A person who submits jobs to PBS, as differentiated from Operators, Managers and

administrators.• A system user, identified by a unique character string (the user name) and by a unique

number (the user ID). Any person using the system has a username and user ID.

User ID, UID. A unique numeric identifier assigned to each user.

Values. The PBSA Web Application refers to Measures as Values. Values are the dependent vari-able (often denoted by the y-axis) whose value changes dependent on the other variables. Exam-ples are total numbers of jobs, average memory used, and total CPU walltime. Values are displayed on the y-axis.

Vnode. A virtual node, or vnode, is an abstract object representing a set of resources which form a usable part of an execution host. This could be an entire host, or a nodeboard or a blade. A single host can be made up of multiple vnodes. Each vnode can be managed and scheduled inde-pendently. Each vnode in a complex must have a unique name. Vnodes can share resources, such as node-locked licenses.

Documents

Display Manager 13.2 Administrator’s Guide - PBS … · WinProp v.14.5 ©2000-2017 Special Notice: Pre-release versions of Altair software are provided ‘as is’, without warranty