PBS Control Administrator’s Guide · FluxMotor® 2018 ©2017-2018; WinProp v.2018 ©2000-2018.2018. Additional Altair Products: Multiscale Designer™ ©2011-2017 ESAComp™ v.4.7

PBS Works is a brand of

PBS Control

Administrator’s Guide

PBS Control 2018.1 Administrator’s Guide

ii

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

Updated: April 30, 2018.

Altair® PBS Works™ 2018.1Accelerating Innovation in the Cloud™ Copyright© 1994-2018 Altair Engineering, Inc. All Rights Reserved.

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

Runtime 2017 © 1995 – 2018

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

Additional Altair Products: Multiscale Designer™ ©2011-2017ESAComp™ v.4.7 ©1992-2018

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.


iii

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

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

solidThinking Inspire® 2018 ©2009-2018; solidThinking Evolve®2017 ©1993-2018; solidThinking Compose® 2018 ©2007-2018, solidThinking Activate® 2018 ©1989-2018, solidThinking Embed® 2018 ©1989-2018, solidThinking Embed® SE 2018 ©1989-2018; Click2Extrude® Metal 2018 ©1996-2018; Click2Extrude® Polymer 2018 ©1996-2018; Click2Cast® 4.1 ©2011-2018; Click2Form® 2018 ©1998-2018.

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) and used by permission.

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.


iv

Technical Support

This document is proprietary information of Altair Engineering, Inc.

Location Telephone e-mail

North America +1 248 614 2425 [email protected] +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] +46 (0) 46 460 2828 [email protected] +44 (0)1926 468 600 [email protected]

Contents

1 Overview......................................................................................................................... 4

1.1 Document Conventions.................................................................................................51.2 About PBS Control.......................................................................................................61.3 Supported Platforms, Browsers and Product Configurations...............................................71.4 Ports Used by PBS Control........................................................................................... 91.5 Location of Log Files..................................................................................................111.6 PBS Works Licensing..................................................................................................131.7 Before Installing PBS Control...................................................................................... 151.8 PBS Control Deployment Options.................................................................................16

1.8.1 Deployment Option 1...................................................................................... 181.8.2 Deployment Option 2...................................................................................... 20

2 Installing PBS Control............................................................................................... 23

2.1 Deployment Option 1................................................................................................. 242.1.1 Installing PBS Professional............................................................................... 242.1.2 Installing the PAS Server and PAS Commands.................................................... 242.1.3 Installing HyperWorks......................................................................................242.1.4 Installing PBS Analytics................................................................................... 252.1.5 Installing MongoDB......................................................................................... 252.1.6 Installing and Starting PBSCloud.......................................................................282.1.7 Installing PBS Control......................................................................................33

2.2 Deployment Option 2................................................................................................. 352.2.1 Installing PBS Professional............................................................................... 352.2.2 Installing the PAS Server and PAS Commands.................................................... 352.2.3 Installing HyperWorks......................................................................................352.2.4 Installing Simulator Components on the PAS Server and PBS MoM.........................362.2.5 Installing PBS Analytics................................................................................... 382.2.6 Installing MongoDB......................................................................................... 382.2.7 Installing PAS Commands................................................................................ 412.2.8 Installing and Starting PBSCloud.......................................................................412.2.9 Installing PBS Control......................................................................................46

3 Uninstalling PBS Control........................................................................................... 49

3.1 Uninstalling PBS Control............................................................................................. 503.2 Uninstalling PBS Analytics...........................................................................................513.3 Uninstalling PBSCloud.................................................................................................52

1

4 Starting and Stopping Services...............................................................................53

4.1 PBS Control Services..................................................................................................544.2 PBS Control Service Commands.................................................................................. 55

4.2.1 Starting PBS Control....................................................................................... 554.2.2 Stopping PBS Control...................................................................................... 554.2.3 Restarting PBS Control.................................................................................... 554.2.4 Determining the Status of a PBS Control Service................................................ 55

4.3 PBSCloud Service Commands......................................................................................574.3.1 Starting PBSCloud After a Machine Reboot......................................................... 574.3.2 Stopping PBSCloud..........................................................................................57

5 Advanced Configuration............................................................................................ 58

5.1 Granting Login Access to PBS Control.......................................................................... 595.2 Configuring Single Sign-On......................................................................................... 60

5.2.1 Enabling Single Sign-On.................................................................................. 605.2.2 Disabling Single Sign-On..................................................................................62

5.3 Enabling Multi-Factor Authentication.............................................................................635.4 Configuring Concurrent Threads for Retrieving Job Details.............................................. 655.5 Configure the Job and Node Details Refresh Interval......................................................665.6 Changing the SSH Server...........................................................................................675.7 Configuring the Session Timeout................................................................................. 685.8 Changing the PBS Control License Server..................................................................... 695.9 Changing the HyperStudy License Server..................................................................... 705.10 Changing the Hostname of the Analytics Service......................................................... 715.11 Changing the Hostname of the PBSCloud Service.........................................................725.12 Changing the Gateway HTTPS Port.............................................................................735.13 Resetting the Analytics Accounting Log Data............................................................... 74

5.13.1 Deleting All Simulation and Model Data............................................................745.14 Logging...................................................................................................................75

5.14.1 Changing Authentication Logging Level............................................................ 755.14.2 Changing the Configure Service Logging Level.................................................. 765.14.3 Changing the Gateway Logging Level...............................................................765.14.4 Changing the Licensing Logging Level..............................................................765.14.5 Changing the Websocket Bridge Logging Level.................................................. 775.14.6 Changing the Simulator Service Logging Level.................................................. 77

5.15 Advanced Configuration for PBSCloud.........................................................................785.15.1 Creating a Service to Start and Stop PBSCloud................................................. 785.15.2 Finding the Current PBSCloud Version..............................................................785.15.3 Accessing PBSCloud Logs............................................................................... 795.15.4 Accessing PBSCloud Analytics......................................................................... 79

6 Cloud Bursting............................................................................................................. 80

2

6.1 Cloud Bursting...........................................................................................................816.2 Prerequisites for Cloud Bursting.................................................................................. 826.3 Configuring Amazon Web Service Cloud Bursting........................................................... 836.4 Configuring Microsoft Azure Cloud Bursting...................................................................916.5 Configuring Google Cloud Platform Cloud Bursting....................................................... 102

Index.................................................................................................................................110

3

Overview 11 Overview

This chapter covers the following:

• 1.1 Document Conventions (p. 5)

• 1.2 About PBS Control (p. 6)

• 1.3 Supported Platforms, Browsers and Product Configurations (p. 7)

• 1.4 Ports Used by PBS Control (p. 9)

• 1.5 Location of Log Files (p. 11)

• 1.6 PBS Works Licensing (p. 13)

• 1.7 Before Installing PBS Control (p. 15)

• 1.8 PBS Control Deployment Options (p. 16)

PBS Control Administrator's Guide1 Overview p.5

1.1 Document ConventionsCommon typographical conventions for PBS Control technical publications.

PC_HOMEThe PBS Control home directory which contains configuration and logging files. Default is:/var/spool/pbsworks/2018.1/pbscontrol/home

This default location can be overridden during the installation of PBS Control.

PC_EXECThe PBS Control execution directory which contains binaries and scripts. Default is:/opt/altair/pbsworks/2018.1/pbscontrol/exec

This default location can be overridden during the installation of PBS Control.

PC_INSTALLERThe PBS Control installer directory which contains installer configuration and log files. Default is:/opt/altair/pbsworks/2018.1/pbscontrol/installer

The location of this directory is based on the location of PC_EXEC.

Proprietary Information of Altair Engineering


1.2 About PBS ControlHPC Administrators control center for managing, optimizing and forecasting HPC Resources.

Altair’s PBS Control is an easy-to-use web application for monitoring and managing jobs and nodesof an High-Performance Computing (HPC) cluster with advanced analytics to support data-drivenplanning and decision making. Also, administrators can perform what-if analysis for determining themost productive way to scale an HPC system's resources by running simulations and manage cloudappliances.

Features include:

• Single pane of glass: configure, deploy, monitor, burst, manage, troubleshoot, simulate, analyze,tune

• Real-time monitoring: simplify troubleshooting and maintenance

• Reporting: PBS Analytics powered by Carriots Analytics™

• Workload simulator: simulate and optimize infrastructure sizing

• Multi-cloud bursting: burst to any cloud for peak loads

• One-click appliance deployment: effortless for public, hybrid, and on-premise / private clouds

• Modern UX: drag-and-drop simplicity



1.3 Supported Platforms, Browsers and ProductConfigurationsA list of supported OS platforms and browsers for the 2018.1 release.

Supported Platforms for PBS Control, PBS Analytics and PBSCloudCentOS 7.2, 7.3, and 7.4

RHEL 7.2, 7.3, and 7.4

SLES 12 SP2

OpenSUSE 42.2

Supported BrowsersThe latest version of the following browsers are supported:

• Chrome

• Firefox

• Safari

Supported Product ConfigurationsThe currently supported product configurations are:

Table 1: Supported Product Configurations

PBSProfessional

PAS MongoDB HyperWorks PBS Analytics PBSCloud PBSControl

13.1 & 14.2 13.0 & 13.2 3.4 & 3.6 2017.x 2018.1 2018.1 2018.1

Hardware RequirementsPBS Control requires a minimum hardware configuration:

Table 2: Hardware Requirements for PBS Control

Hardware Minimum Requirement Recommended

CPU 4 cores 4 cores

Memory (physical) 8 GB 16 GB

Disk space 2 GB 4 GB



Additional CPUs, memory, and disk space may be required depending upon the PBS Control componentsinstalled and the size of your site's HPC cluster. Large environments may need more memory for PBSAnalytics, and PBSCloud has a minimum disk space requirement of 30GB, with a recommendation of 50GB.



1.4 Ports Used by PBS ControlA list of ports used by PBS Control services and components.

These ports must be free for PBS Control to be installed successfully.

Table 3: Ports Used by PBS Control

Port Service Using the Port

3000 UI Monitoring for PBSCloud

4505 and 4506 Saltstack for PBSCloud

5601 ELK Stack for PBSCloud

9000 Analytics Service

9080 Analytics Tomcat-8

9100 Authentication and licensing services

9105 Websocket Bridge

9143 Analytics On-Demand Analysis HTTPS API

9200 Analytics MonetDB

9343 Analytics Data Collector HTTPS

9443 Analytics (Carriots Analytics™) HTTPS

9500 Gateway HTTPS

9501 GUI Server

9600 Monitor Server

9603 Monitor PostgreSQL Server

9672 ActiveMQ (Carriots Analytics™)

9700 Analytics MongoDB

9800 Simulator Executor HTTP API

9810 Simulator Storage Service HTTP API

9820 Messagerouter HTTP API

9830 Simulator Storage Service MongoDB port



Port Service Using the Port

9835 MessageRouter DB

9840 MessageRouter RabbitMQ TCP Listener

9850 Configure HTTP API

9860 Configure MongoDB port

9870 Configuration Service MongoDB

9880 Configuration Service HTTP API

9980 PBSCloud Server

15672 RabbitMQ HTTP Admin API

25672 RabbitMQ internal use



1.5 Location of Log FilesUse log files to troubleshoot problems with PBS Control.

Installer Log FilesObtain detailed logging information for the installation process by navigating to PC_INSTALLER.

A log file is written to this directory whenever PBS Control is installed, therefore each installation logfile is timestamped. During the installation process, information is written to this file as each serviceis installed. Service installation is done asynchronously so messages pertaining to all services areinterspersed throughout this log file. Installation messages are also written to a log file that is specificto each service. These log files are located at:

PC_HOME/logs/<SERVICE>/<SERVICE>_node_config.log

Where <SERVICE> is the name of the service.

Monitor Log FilesLog files for the Monitor service can be found at: PC_HOME/logs/monitor/tomcat.

Simulator Log FilesLog files for the Simulator service can be found at: PC_HOME/logs/pbs-control-simulator.

Configure Log FilesLog files for the Configure service can be found at: PC_HOME/logs/pbsworks-configure.

Message Router Log FilesLog files for the Message Router service can be found at: PC_HOME/logs/pbsworks-messagerouter.

Web Interface Log FilesLog files for the Web Interface service can be found at: PC_HOME/logs/pcgui/tomcat.

Gateway Log FilesLog files for the Gateway service can be found at: PC_HOME/logs/api_gateway.

Licensing Log FilesLog files for the Licensing service can be found at: PC_HOME/logs/license.

Authentication Log FilesLog files for the Authentication service can be found at: PC_HOME/logs/pbswauth/tomcat.

Websocket Log FilesLog files for the Websocket service can be found at: PC_HOME/logs/ws_bridge



AMS Log FilesLog files for the AMS service can be found at: PC_HOME/logs/ams

Configuration Log FilesLog files for the Configuration service can be found at: PC_HOME/logs/pbsworks-admin

Shared Resources Log FilesLog files for shared resources (Java libraries, Apache Web Server, Tomcat) can be found at: PC_HOME/logs/shared



1.6 PBS Works LicensingLicensing model for PBS Control.

Three types of licenses are consumed by PBS Control:

• PBS Works User license - consumed when a user logs into PBS Control

• PBS Works Node license - consumed when an HPC cluster is added via the Monitor tab.

• PBS Works Bursted Node license - consumed when a node is bursted into the cloud.

Licensing for Logging into PBS ControlEach user that logs into PBS Control consumes a PBS Works User license. If a user logs into PBS Controland then opens a second browser window to access PBS Control, a single PBS Works User license isconsumed.

To login to PBS Control at least one PBS Works User license and one PBS Works Node license must beinstalled and available via the Altair LMX license server.

Monitor LicensingWhen a cluster is added to PBS Control, a PBS Works Node license is consumed for each HPC clusternode. A node in PBS Control is considered a PBS Professional vnode regardless of the number of coresor devices associated with the vnode.

Once the number of PBS Works Node licenses is exceeded, job and node summary and detailinformation is not available for any newly added HPC clusters. A next to the name of the cluster onthe Job Summary or Node Summary page indicates that Node licenses have been exceeded.

Figure 1: PBS Works Node Licenses Exceeded

Configure LicensingNo licenses are consumed when accessing the capabilities of the Configure service.

Analyze LicensingIf a cluster is licensed for the Monitoring service, then it is licensed for the Analyze service.

Simulate LicensingNo licenses are consumed when accessing the capabilities of the Simulator service.



PBSCloud LicensingNo licenses are consumed when accessing the capabilities of PBSCloud, except for cloud bursting. PBSWorks Bursted Node Hours are consumed when nodes are bursted in the cloud. For example, if 10nodes are bursted for 10 hours, then 10 Bursted Node Hours are consumed.



1.7 Before Installing PBS ControlThings to know before you install.

Deployment OptionsReview the deployment options before installing PBS Control. Based on your selected deploymentoption, note the hostname/IP addresses of the machine where the different components are to beinstalled. You will need this information during the installation.

Access to PBS Control Post-InstallationThe only user with login access post-installation is the Service User entered during the installation ofPBS Control. You may configure login access for other users post-installation.

See AlsoPBS Control Deployment OptionsGranting Login Access to PBS Control



1.8 PBS Control Deployment OptionsTwo deployment options are available for installing PBS Control. Choose the option that best suits yoursite's needs.

PBS Control ServicesPBS Control consists of a collection of services, accessed and invoked via a common interface. Each ofthese services can conceivably reside on a separate host; for the purposes of the 2018.1 release it isrecommended to install everything on a single host. Services and their associated responsibility are:

Web InterfaceProvides client access to the simulation, analytics, configuration, cloud bursting, and monitoringcapabilities of PBS Control. It also provides traffic routing through the gateway/proxy server andmessaging routing utilizing RabbitMQ.

AnalyticsProvides analytics reporting and simulation results.

SimulatorAllows administrators to run simulations and is responsible for storage of simulation data.

MonitorAllows administrators to monitor and manage HPC nodes and jobs.

ConfigureAllows administrators to configure default WLM server and security settings, and manage queues,resources, resource defaults and limits.

PBSCloud

Allows an HPC appliance to be ran on both public and private clouds, and provides cloud burstingcapabilities so that jobs can be run in the cloud based on demand.

MongoDB is used by the Analytics, Configure and Simulator services for data storage. Due to legalreasons, its installation could not be incorporated into the 2018.1 installer, therefore it must bemanually installed wherever the Analytics, Configure, and Simulator services are installed.

Postgres is used by the Monitor service for data storage. It is automatically installed when the Monitorservice is installed.

Currently, a separate installer is responsible for installing the Analytics component and a separateinstallation process is necessary for PBSCloud that utilizes Docker containers. All other PBS Controlservices are installed using a single installer.

Some of the PBS Control services take advantage of other Altair products to realize their functionality;specifically, the Simulator service uses PBS Professional, PAS, and HyperWorks Desktop. Therefore,these products must also be installed.

PBS Control Installation TypesThe PBS Control installer offers two installation types for installing its services:



Express

Installs the Web Interface, Simulator, Configure, and Monitor services in a single installationprocess. Choose this installation type when deploying all PBS Control services, as well as theother products that are necessary for running simulations, onto a single machine (DeploymentOption 1). Minimal information is requested when utilizing this installation type:

• Service user

• License server

• Installation location for the home and execution directories

AdvancedAllows services to be distributed across multiple machines . Choose this installation type whendeploying the PBS Professional Server and the PBS MoM, PAS, and HyperStudy on a separatemachine from the PBS Control services (Deployment Option 2).

Both installation types assume that all external dependencies have been satisfied prior to installing PBSControl and that the default ports are free and available for use.

Prerequisites for Installing PBS ControlBefore running the PBS Control installer on the machine hosting PBS Control, PBS Analytics, andPBSCloud, the following prerequisites must be met:

• Installation must be done on a machine running on a supported platform.

• SeLinux must be disabled.

• The socat package must be installed if it is not already present on the system.

• MongoDB must be installed in the standard MongoDB default location.

During the installation of PBS Control, you are asked to provide a username that will be the PBS ControlService User. All PBS Control services including the database instances will run as this user. By default,this user will be the only user to have login access to PBS Control once installation is complete (youmay configure login access for other users post-installation). Prerequisites for the Service User:

• The Service User is required to have a home directory in /home.

• Wherever the Simulator service is being installed, the Service User must be able to submit jobs viaPAS from the node on which the Simulator service is running, therefore pas-passwd must be runfor the Service User prior to installing PBS Control.

• The Service User must be able to SSH without a password from and into any machine running theSimulator services (e.g. from machine A to machine A).



1.8.1 Deployment Option 1This deployment option installs all PBS Control services, as well as the other products that arenecessary for running simulations, onto a single machine.

Figure 2: PBS Control Deployment Option 1

Sequence for Installing PBS Control Components and ServicesThe services and components necessary for PBS Control are installed in this order:

1. PBS Professional

2. PAS

3. HyperWorks

4. PBS Analytics

5. MongoDB

6. PBSCloud

7. PBS Control

Note: Simulator application definitions must be installed on the PAS Server and a Simulatorsolver must be installed on the PBS MoM. These components are installed automaticallywhen the Simulator service is installed for this deployment option.



InstallersThe table below describes the installers necessary for installing PBS Control and associated componentsin installation order.

Table 4: Installers and Associated Component/Service

Installer Component/Service

PBSPro_13.1.x-<OS>_x86_64.tar.gz


PBS Professional Server and MoM

PBSAppSvcs_13.0.0-<OS>_x86_64.bin

PBSAppSvcs_13.2_<OS>_x86_64_20170510_1147.bin

PAS Server and Commands

hwDesktop2017.x_linux64.bin HyperWorks

PBSA_2018.1_Linux_x86_64.bin PBS Analytics

Manual installation - no installer available MongoDB

Manual installation - no installer available PBSCloud

PBS Control Web Application

Simulator service

Monitor service

Configure service

Simulator application definitions (on PASServer)

PBSControl_2018_1.bin

Simulator solver (on PBS MoM)



1.8.2 Deployment Option 2A second deployment option is available that installs the HPC cluster components on a separatemachine from the PBS Control services.

Figure 3: PBS Control Deployment Option 2

Services and Components Installed on Machine AMachine A hosts all PBS Control services, as well as the PAS Client (PAS Commands), and MongoDB(required for the Analytics, Simulator and Configure services).

Components Installed on Machine BMachine B hosts the PBS Professional Server and the PBS MoM, PAS, and HyperStudy.

Simulator application definitions must be installed on the PAS Server and a Simulator solver must beinstalled on the PBS MoM. These components are installed by running the PBS Control installer onMachine B. Therefore the PBS Control installer is ran twice, once to install the Simulator applicationdefinitions on the PAS Server and the Simulator solver on the PBS MoM, and a second time to install thePBS Control services on Machine A.

Note: The PBS MoM may be hosted on a machine separate from the PBS Server. If that isthe case, then HyperStudy and the Simulator solver are installed on the machine hosting thePBS MoM. Installing the Simulator solver on the PBS MoM requires the PBS Control installerto be ran a third time on the PBS MoM.

Sequence for Installing PBS Control ComponentsThe services and components necessary for PBS Control are installed in this order:

1. PBS Professional

2. PAS



3. HyperWorks

4. Simulator application definitions on the PAS Server and the Simulator solver on the PBS MoM

5. PBS Analytics

6. MongoDB

7. PAS Commands

8. PBSCloud

9. PBS Control

InstallersThe table below describes the installers necessary for installing PBS Control and associated componentsin installation order.

Table 5: Installers and Associated Component/Service

Installer Component/Service InstallMachine



PBS Professional Server andMoM

Machine B



PAS Server and PASCommands

Machine B

hwDesktop2017.x_linux64.bin HyperWorks Machine B

Simulator applicationdefinitions

Machine BPBSControl_2018_1.bin

Simulator solver Machine B

PBSA_2018.1_Linux_x86_64.bin PBS Analytics Machine A

Manual installation - no installer available MongoDB Machine A



PAS Commands Machine A

Manual installation - no installer available PBSCloud Machine A

PBS Control Web Application Machine A

Simulator service Machine A

PBSControl_2018_1.bin

Monitor service Machine A



Installer Component/Service InstallMachine

Configure service Machine A


Installing PBS Control 22 Installing PBS Control


• 2.1 Deployment Option 1 (p. 24)

• 2.2 Deployment Option 2 (p. 35)

PBS Control Administrator's Guide2 Installing PBS Control p.24

2.1 Deployment Option 1This deployment option installs all PBS Control services, as well as the other products that arenecessary for running simulations, onto a single machine.

2.1.1 Installing PBS ProfessionalInstall the HPC cluster workload manager.

It is recommended to use PBS Professional v13.1 or v14.2 as these are the versions that have currentlybeen tested. If you have an existing HPC cluster already installed, you may skip these steps.

Install PBS in its default location.

1. Login to the machine where all PBS Control components, as well as PBS Professional, PAS, andHyperWorks are to be installed as a user with sudo privileges.

2. Install the PBS Professional Server, execution and commands (option 1).

2.1.2 Installing the PAS Server and PAS CommandsInstall PAS on the machine hosting the PBS Professional Server.

PBS Control requires PAS (PAS Server and PAS Commands) to be installed on the PBS ProfessionalServer (headnode). Testing has been performed using PAS 13.0 and 13.2.

If PAS has already been installed on the PBS Professional Server, then you may skip these steps.

1. Login to the machine where the PBS Professional Server is installed as a user with sudo privileges.

2. Install the PAS Server and PAS Commands by following the instructions in the PAS Administrator’sGuide.

3. Start PAS: /etc/init.d/pas start

PAS does not automatically set the PBS Professional job_history_enable attribute to true. Therefore,to enable job history use the PBS Professional command:qmgr -c 'set server job_history_enable=True'

2.1.3 Installing HyperWorksInstall HyperWorks on the PBS execution node which is necessary to run simulation parameter sweeps.

The environment variable ALTAIR_LICENSE_PATH must be set in /etc/environment to point to theAltair license server in the format port@hostname.

The PBS Control installer attempts to locate the HyperWorks installation. If the installer cannotdetermine where HyperWorks has been installed, the installer assumes that the HyperWorks installationdirectory is /opt/hwdesktop. Therefore, it is recommended to install HyperWorks in this location.



Important: Install the entire HyperWorks suite. Do not install HyperStudy only.

During the installation of PBS Control, you are asked to provide a username that will be the PBS ControlService User. The HyperWorks installation location must have executable permissions for the ServiceUser for Simulation job submission to work.

HyperStudy is necessary to run parameter sweep simulations, therefore HyperWorks must be installedon the PBS MoM.

Note: For parameter sweeps, licenses are necessary to run PBS Professional, PAS, andHyperStudy.

1. Login to the machine where the PBS Professional Execution component - the MoM - is installed asa user with sudo privileges.

2. Install the HyperWorks 2017.x by following the Linux installation instructions in the HyperWorks2017.x Installation Guide.

2.1.4 Installing PBS AnalyticsInstall the PBS Control services responsible for providing analytics.

If you have installed the Simulator components of PBS Control and are now re-installing PBS Analytics,all simulation and model data must be removed from PBS Control before re-installing PBS Analytics -see Deleting All Simulation and Model Data.

Analytics for simulation results are provided by PBS Analytics 2018.1 which uses Carriots Analytics™ fordata visualization.

Refer to the PBS Analytics Administrator's Guide for instructions on how to install the PBS Analyticsweb application, parser, and data collector. After installation do not start the PBS Analytics services.MongoDB must be installed before starting this service.

Install PBS Analytics on the machine where PBS Control will be installed.

2.1.5 Installing MongoDBInstall MongoDB for use by PBS Analytics and the Configure and Simulator services for data storage.

Installing MongoDB for RHEL and CentOSInstall MongoDB for RHEL and CentOS platforms.

The PBS Analytics services must be stopped before installing MongoDB 3.4 or MongoDB 3.6. Executethese commands to stop PBS Analytics:/etc/init.d/pbsworks-pbsa stop/etc/init.d/pbsworks-dc stop



MongoDB is used by the Analytics, Configure and Simulator services for data storage. Due to legalreasons, its installation could not be incorporated into the 2018.1 installer, therefore it must bemanually installed, wherever the Analytics, Configure, and Simulator services are installed. OnceMongoDB is installed, no other configuration is necessary.

1. Login to the machine where PBS Analytics is installed as root.

2. Create an environment variable using the command:export PBSA_INSTALL_DIR=<INSTALL_DIR>

where <INSTALL_DIR> is the location where PBS Analytics is installed.

3. Create a file /etc/yum.repos.d/mongodb-org-<ver>.repo.

Where <ver> is the version of MongoDB being installed.

4. Edit the file and choose one of the following options:

• Add the following lines for MongoDB 3.4:[mongodb-org-<version>3.4]name=MongoDB Repositorybaseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/3.4/x86_64/gpgcheck=1enabled=1gpgkey=https://www.mongodb.org/static/pgp/server-3.4.asc


5. Save the changes made to the file and exit the editor.

6. Install MongoDB using YUM:yum install -y mongodb-org

7. Change user to the username selected as the PBS Analytics Service User during the installation ofPBS Analytics.

This is the user under whom the PBS Analytics services run.su <PBSA_SERVICE_USER>

8. Execute the command:mkdir -p $PBSA_INSTALL_DIR/portal/thirdparty/mongodb/bin

9. Execute the command:cp /usr/bin/mong* $PBSA_INSTALL_DIR/portal/thirdparty/mongodb/bin

10. Execute the command:cp -r $PBSA_INSTALL_DIR/portal/scripts/mongodb/envisiondump \$PBSA_INSTALL_DIR/portal/thirdparty/mongodb

11. Execute the command:cp -r $PBSA_INSTALL_DIR/portal/scripts/mongodb/scripts \$PBSA_INSTALL_DIR/portal/thirdparty/mongodb

12. Verify that these newly created directories are owned by the PBS Analytics Service User.

13. Change user to root:su

14. Start the PBS Analytics service./etc/init.d/pbsworks-pbsa start



/etc/init.d/pbsworks-dc start

Installing MongoDB for SLES and SUSEInstall MongoDB for SLES and SUSE platforms.






3. Import the MongoDB public key by choosing one of the following options:

• To install MongoDB 3.4, enter the command:rpm --import https://www.mongodb.org/static/pgp/server-3.4.asc


4. Add the repository so that you can install MongoDB using zypper.

• For MongoDB 3.4, enter the command:zypper addrepo --gpgcheck \"https://repo.mongodb.org/zypper/suse/12/mongodb-org/3.4/x86_64/" mongodb


5. Install MongoDB:

• For MongoDB 3.4, enter the command:zypper install mongodb-org-3.4.10 \mongodb-org-server-3.4.10 \mongodb-org-shell-3.4.10 \mongodb-org-mongos-3.4.10 \ mongodb-org-tools-3.4.10

• For MongoDB 3.6, enter the command:zypper install mongodb-org-3.6.0 \mongodb-org-server-3.6.0 \mongodb-org-shell-3.6.0 \mongodb-org-mongos-3.6.0 \mongodb-org-tools-3.6.0




https://www.mongodb.org/static/pgp/server-3.6.asc









13. Start the PBS Analytics service./etc/init.d/pbsworks-pbsa start/etc/init.d/pbsworks-dc start

2.1.6 Installing and Starting PBSCloud

Installing DockerInstall Docker which is used to host PBSCloud.

• Before installing Docker, create a directory /var/lib/docker on a ext4 partition of more than30GB. 50GB is recommended.

• The machine where the installation is being performed requires internet access for installingPBSCloud.

1. Login to the machine where PBSCloud will be installed as a user with sudo permissions.

2. Setup the docker repository:sudo yum-config-manager --add-repo \https://download.docker.com/linux/centos/docker-ce.repo

3. Update docker:sudo yum update

4. Install the packets and its dependencies:sudo yum install docker-ce

5. Add the user into the docker group:

Enter this command exactly as is. Do not replace $USER with a username.sudo usermod -aG docker $USER

6. Open a new shell to load the new group permissions:

Enter this command exactly as is. Do not replace $USER with a username.sudo su - $USER



Note: You will need to start a new shell once you have added the user to the dockergroup. Otherwise, you will get an error when trying to use the docker command.

7. Start the daemon:sudo systemctl start dockersudo systemctl enable docker

If you encounter DNS errors, try to force Docker to use your site's DNS server:

a) Create the file /etc/docker/daemon.json.

b) Edit the file.

c) Add the following lines to the file:{ "dns": ["YOUR_NAMESERVER1", "YOUR_NAMESERVER2"]}

d) Save the file.

e) Restart the Docker daemon:sudo systemctl restart docker

Installing Pocker and Pulling PBSCloud ContainersPocker is a PBSCloud Docker wrapper, designed to setup, install and manage your PBSCloud containersinstallation.

Contact an Altair Application Engineer to obtain the PBSCloud configuration tar file config.tar.gzbefore proceeding.

1. Create an environment variable for the PBSCloud version:export PBSCLOUD_VERSION=2018.1

2. Connect to the PBSCloud Docker registry:docker login pbscloudio.azurecr.io -u a882d237-5d07-48a7-837e-9bd8652d79ec

Password is: kq9ZKzrToLGm78xGBDv5lKx5hg5YOB8JDz3usbp+2eo=

3. Untar config.tar.gz to the home directory of the user who is installing PBSCloud:tar xvfz config.tar.gz -C <HOME_DIR>

Replace <HOME_DIR> with the value of the current user’s home directory. For example, /users/tsmith.

4. Run the Pocker container used to setup and install PBSCloud:docker run -ti --rm -e PBSCLOUD_VERSION=$PBSCLOUD_VERSION \-v /run/docker.sock:/run/docker.sock \-v <HOME_DIR>/config:/config \-v <HOME_DIR>/kard:/pocker/kard pbscloudio.azurecr.io/pocker:$PBSCLOUD_VERSION bash


5. Install MongDB 3.0:docker pull mongo:3.0

6. Create your deployment environment definition:pocker kard create $PBSCLOUD_VERSION -e pbscloud \



--extra tag=$PBSCLOUD_VERSION ui_port=9980 \config_tpl_folder=/config/ ui_url_prefix='/pclm'

7. Pull the PBSCloud containers:pocker image pull -r pbscloudio.azurecr.io \-u a882d237-5d07-48a7-837e-9bd8652d79ec \-p kq9ZKzrToLGm78xGBDv5lKx5hg5YOB8JDz3usbp+2eo=

Where kq9ZKzrToLGm78xGBDv5lKx5hg5YOB8JDz3usbp+2eo= is the password that was used toconnect to the PBSCloud docker registry.

Configuring a Public IP Address for PBSCloudConfigure ports and a public IP address so that PBSCloud can communicate with deployed cloudappliances.

Note: Configuring a public IP address for PBSCloud is only necessary for cloud appliancedeployment. If you do not plan on creating and deploying an appliance using PBS Control,then you may skip this step.

Appliances deployed by PBSCloud need to be able to communicate to the PBSCloud service from thepublic cloud/internet on ports 4505 and 4506. The machine running the PBSCloud service must havethese ports available at an IP accessible from outside the local network or the network configurationneeds to be such that a publicly accessible IP address has these ports forwarded to the IP address ofthe machine running PBSCloud.

Once this configuration is set up, you must specify to PBSCloud which public IP address is going to beused to communicate with PBSCloud.

1. Edit the file <HOME_DIR>/kard/current/site_config/configurator.conf.

Replace <HOME_DIR> with the value of the home directory of the user who installed PBSCloud.

2. Place the following lines in the file:[configurator.drivers.salt]master_ip = <PUBLIC_IP>

Replace <PUBLIC_IP> with the public IP address that is going to be used for communication withPBSCloud.

3. Save the file.




6. Update the kard:pocker kard update

7. Update the Docker context:pocker kard make



Linking PBSCloud with the PBS Works License ServerConfigure PBSCloud so that it can access the PBS Works license server.

1. Navigate to the directory <HOME_DIR>/kard/current/site_config.


2. Edit the file pacioli.conf and add the following lines to the file:[drivers]method=pbsworks [[pacioli.drivers.pbsworks]]checkout_interval=10host=http://<PBSWORKS_LICENSE_SERVER_IP>:<PBSWORKS_LICENSE_SERVER_PORT>

The checkout_interval is in minutes and defines how often the bursted node hours are checkedagainst the purchased licenses.

3. Save the file.






Configuring a SMTP Server for Cloud Bursting Quota AlertsSet up a SMTP server so that when a cloud bursting resource alert limit is reached an email is sent tothe PBSCloud Administrator.

The PBSCloud Administrator is defined when PBSCloud is started and initialized.

1. Navigate to the directory HOME_DIR>/kard/current/site_config.


2. Edit the file executor.conf and add the following lines to the file:[smtp]host=<SMTP_SERVER_HOSTNAME/IP_ADDRESS>port=<SMTP_SERVER_PORT_NO>login=<SMTP_LOGIN_USERNAME>password=<SMTP_LOGIN_PASSWORD>

The SMTP Server port number defaults to 25.

3. Save the file.

4. Edit the file guardian.conf and add the following lines to the file:[smtp]host=<SMTP_SERVER_HOSTNAME/IP_ADDRESS>



port=<SMTP_SERVER_PORT_NO>login=<SMTP_LOGIN_USERNAME>password=<SMTP_LOGIN_PASSWORD>


5. Save the file.

6. Restart the executor and guardian Pocker containers:docker restart executor-api guardian






Starting and Initializing PBSCloudStart and initialize PBSCloud using Pocker.

1. Generate your environment:pocker kard make

2. Start PBSCloud:pocker start

3. Initialize PBSCloud by entering the command:pocker ext init full --domain_name <domain_name> \--username <admin_username> --password '<admin_password>' \--user_email '<admin_email>'

The values between the <> are used during the PBS Control installation process to link PBSCloudand PBS Control. You will need to replace these four values:

The domain_name does not have to be a true DNS domain, but it a group name for your project.It cannot include a period ( . ).

The admin_username and admin_password identify the credentials of the PBSCloud Administrator.The admin_username should not contain an asterisk ( * ). The admin_password must be at least6 characters in length and must contain at least one number.

Note: Email alerts are sent to the PBSCloud Administrator when a cloud burstingresource alert limit is reached.

Below is an example:

pocker ext init full --domain_name chrysler --username tsmith --password 'password@123' --user_email '[email protected]'



The output of this command contains keys to unlock the vault and main passwords. Copy theoutput of this command and store it in a location where you can find it easily.

2.1.7 Installing PBS ControlInstall all services necessary for PBS Control, including the Simulator application definitions and theSimulator solver.

Before running the PBS Control installer on the machine hosting PBS Control, PBS Analytics, andPBSCloud, the following prerequisites must be met:









Note: Installer log files are available in PC_INSTALLER/logs.

The PAS Server is restarted during the installation process. No configuration changes are made to PBSProfessional.

Several services use MongoDB for data storage, therefore there will be multiple database instancesrunning once PBS Control is installed.

The Monitor service uses Postgres for data storage. Once the Monitor service is installed and started, aPostgres database instance will be running.

1. Login to the machine where PBS Analytics and PBSCloud have been installed as a non-root userhaving sudo privileges.

2. Navigate to the directory where the installer was copied by changing your working directory.

3. Invoke the installer by running the installation binary:./PBSControl_2018_1.bin

4. Read the introduction and press ENTER.

5. Page through the license agreement by pressing ENTER until you are asked to accept its terms andconditions.

6. Accept the license agreement by entering Y and pressing ENTER.



7. Choose the Express installation type by entering 1 and pressing ENTER.

8. Enter a username that who will be the PBS Control Service User and press ENTER.

The user must exist on the machine where you are installing PBS Control. All PBS Control servicesincluding the database instances run as this user. This user is the only user to have login access toPBS Control once installation is complete.

Note: You may configure login access for other users post-installation.

9. Enter the license server in the format port@hostname and press ENTER.

10. Enter where you would like to install the PBS Control execution binaries (PC_EXEC) or press ENTERto use the default location.

11. Enter where you would like to install the PBS Control configuration files (PC_HOME) or press ENTERto use the default location.

12. Review the installation summary and then press ENTER to install the product.The installation may take some time to complete. If the installation is not successful, contact thePBS Control development team.

13. Navigate to the directory: <PC_HOME>/data/api_gateway.

14. Edit the file: Cloud_io_Credentials.json.

This file contains a key-value pair for "username" and "password" "username":"admin@altair", "password":"TM9RHX9nNLX0riiPM3/T6w=="

15. Change the value of username to those values entered while starting and initializing PBSCloud(Starting and Initializing PBSCloud step 3) in the format admin_username@domain_name.Ex. tsmith@chrysler

16. Encrypt the password (admin_password) entered while starting and initializing PBSCloud (Startingand Initializing PBSCloud step 3):./<EXEC>/exec/api_gateway/scripts/password_encryption.sh encrypt <admin_password>

Note: The output of this script is the encrypted password.

17. Copy the output from the previous step and paste it into the Cloud_io_Credentials.json file asthe value of password.

18. Save the file Cloud_io_Credentials.json.

19. Switch to the PBS Control Service User by issuing this command:su <SERVICE_USERNAME>

where SERVICE_USERNAME is the username of the PBS Control Service User.

20. Enter the following command:pbs-sim-agent --operation import_study --study-module parameter_sweep

This command returns JSON output which can be ignored.

The PBS Control web application is now accessible through the URL https://hostname:9500/pc.

You may now configure login access for users other than the Service User and perform other post-installation configuration. See the Advanced Configuration chapter.



2.2 Deployment Option 2This deployment option installs the HPC cluster components on a separate machine from the PBSControl services.

2.2.1 Installing PBS ProfessionalInstall the HPC cluster workload manager.

It is recommended to use PBS Professional v13.1 or v14.2 as these are the versions that have currentlybeen tested. If you have an existing HPC cluster already installed, you may skip these steps.

Install PBS in its default location.

1. Login to machine where PBS Professional, PAS, and HyperWorks are to be installed (Machine B) asa user with sudo privileges.

2. Install the PBS Professional Server, execution and commands (option 1).

2.2.2 Installing the PAS Server and PAS CommandsInstall PAS on the machine hosting the PBS Professional Server.

PBS Control requires PAS (PAS Server and PAS Commands) to be installed on the PBS ProfessionalServer (headnode). Testing has been performed using PAS 13.0 and 13.2.

If PAS has already been installed on the PBS Professional Server, then you may skip these steps.

1. Login to the machine where the PBS Professional Server is installed as a user with sudo privileges.

2. Install the PAS Server and PAS Commands by following the instructions in the PAS Administrator’sGuide.

3. Start PAS: /etc/init.d/pas start

PAS does not automatically set the PBS Professional job_history_enable attribute to true. Therefore,to enable job history use the PBS Professional command:qmgr -c 'set server job_history_enable=True'

2.2.3 Installing HyperWorksInstall HyperWorks on the PBS execution node which is necessary to run simulation parameter sweeps.

The environment variable ALTAIR_LICENSE_PATH must be set in /etc/environment to point to theAltair license server in the format port@hostname.

The PBS Control installer attempts to locate the HyperWorks installation. If the installer cannotdetermine where HyperWorks has been installed, the installer assumes that the HyperWorks installationdirectory is /opt/hwdesktop. Therefore, it is recommended to install HyperWorks in this location.



Important: Install the entire HyperWorks suite. Do not install HyperStudy only.

During the installation of PBS Control, you are asked to provide a username that will be the PBS ControlService User. The HyperWorks installation location must have executable permissions for the ServiceUser for Simulation job submission to work.

HyperStudy is necessary to run parameter sweep simulations, therefore HyperWorks must be installedon the PBS MoM.

Note: For parameter sweeps, licenses are necessary to run PBS Professional, PAS, andHyperStudy.

1. Login to the machine where the PBS Professional Execution component - the MoM - is installed asa user with sudo privileges.

2. Install the HyperWorks 2017.x by following the Linux installation instructions in the HyperWorks2017.x Installation Guide.

2.2.4 Installing Simulator Components on the PAS Serverand PBS MoMInstall the Simulator application definitions and solver on the machine hosting the PAS Server and PBSProfessional.


The PAS Server is restarted during the installation process. No configuration changes are made to PBSProfessional.

The installer will ask for the hostname (endpoint) for the following components:

• Executor Host (Simulator Server)

• Submission Host (PAS Server)

• Gateway Host (Web Interface)

1. Login to the machine where the PAS Server and PBS Professional are installed as a non-root userhaving sudo privileges.






7. Choose the Advanced installation type by entering 2 and pressing ENTER.

8. Choose to install the Simulator by entering: 3 and pressing ENTER.



9. Choose one of the following options:

• If the PBS MoM is installed on the same machine as the PAS Server and the PBS ProfessionalServer, enter 2,3 to configure both the PAS Server and the PBS MoM and press ENTER.

• If the PBS Mom is installed on a separate machine from the PAS Server and the PBSProfessional Server, enter 2 to configure the PAS Server only and press ENTER.

Note: When the PBS MoM is installed on a separate machine, you will need to runthe installer a third time on the machine hosting the PBS MoM. When you get tothis step, you will enter 3 to configure the MoM.

10. Enter the hostname of the machine where the PBS Control Simulator Server (Executor Host) willbe installed and press ENTER.

Note: You will not be asked for this information if you are configuring PAS only (i.e.,chose 2 in the previous step).

11. Enter the hostname of the machine where the PAS Server (Submission Host) is installed bypressing ENTER.

12. Enter the hostname of the machine where the PBS Control Web Interface (Gateway Host) will beinstalled and press ENTER.







Note: When the PBS MoM is installed on a separate machine from the PBS Server, you willneed to login to the PBS MoM and run the installer a third time to configure the PBS MoM.



2.2.5 Installing PBS AnalyticsInstall the PBS Control services responsible for providing analytics.

If you have installed the Simulator components of PBS Control and are now re-installing PBS Analytics,all simulation and model data must be removed from PBS Control before re-installing PBS Analytics -see Deleting All Simulation and Model Data.


Refer to the PBS Analytics Administrator's Guide for instructions on how to install the PBS Analyticsweb application, parser, and data collector. After installation do not start the PBS Analytics services.MongoDB must be installed before starting this service.

Install PBS Analytics on the machine where PBS Control will be installed.

2.2.6 Installing MongoDBInstall MongoDB for use by PBS Analytics and the Configure and Simulator services for data storage.

Installing MongoDB for RHEL and CentOSInstall MongoDB for RHEL and CentOS platforms.






3. Create a file /etc/yum.repos.d/mongodb-org-<ver>.repo.

Where <ver> is the version of MongoDB being installed.

4. Edit the file and choose one of the following options:


• Add the following lines for MongoDB 3.6:



[mongodb-org-<version>3.6]name=MongoDB Repositorybaseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/3.6/x86_64/gpgcheck=1enabled=1gpgkey=https://www.mongodb.org/static/pgp/server-3.6.asc

5. Save the changes made to the file and exit the editor.

6. Install MongoDB using YUM:yum install -y mongodb-org










Installing MongoDB for SLES and SUSEInstall MongoDB for SLES and SUSE platforms.








3. Import the MongoDB public key by choosing one of the following options:



4. Add the repository so that you can install MongoDB using zypper.



5. Install MongoDB:

• For MongoDB 3.4, enter the command:zypper install mongodb-org-3.4.10 \mongodb-org-server-3.4.10 \mongodb-org-shell-3.4.10 \mongodb-org-mongos-3.4.10 \ mongodb-org-tools-3.4.10

• For MongoDB 3.6, enter the command:zypper install mongodb-org-3.6.0 \mongodb-org-server-3.6.0 \mongodb-org-shell-3.6.0 \mongodb-org-mongos-3.6.0 \mongodb-org-tools-3.6.0














2.2.7 Installing PAS CommandsInstall PAS Commands for use by the Simulator service.

The PAS Server must be installed on the PBS Professional Server (headnode) before installing PASCommands.

Note: Install the same version of PAS Commands as the PAS Server.

1. Login to the machine where PBS Control will be installed as a user with sudo privileges.

2. Install PAS Commands by following the instructions in the PAS Administrator’s Guide.

2.2.8 Installing and Starting PBSCloud

Installing DockerInstall Docker which is used to host PBSCloud.

• Before installing Docker, create a directory /var/lib/docker on a ext4 partition of more than30GB. 50GB is recommended.

• The machine where the installation is being performed requires internet access for installingPBSCloud.

1. Login to the machine where PBSCloud will be installed as a user with sudo permissions.

2. Setup the docker repository:sudo yum-config-manager --add-repo \https://download.docker.com/linux/centos/docker-ce.repo

3. Update docker:sudo yum update

4. Install the packets and its dependencies:sudo yum install docker-ce

5. Add the user into the docker group:

Enter this command exactly as is. Do not replace $USER with a username.sudo usermod -aG docker $USER

6. Open a new shell to load the new group permissions:

Enter this command exactly as is. Do not replace $USER with a username.sudo su - $USER

Note: You will need to start a new shell once you have added the user to the dockergroup. Otherwise, you will get an error when trying to use the docker command.

7. Start the daemon:sudo systemctl start dockersudo systemctl enable docker

If you encounter DNS errors, try to force Docker to use your site's DNS server:



a) Create the file /etc/docker/daemon.json.

b) Edit the file.

c) Add the following lines to the file:{ "dns": ["YOUR_NAMESERVER1", "YOUR_NAMESERVER2"]}

d) Save the file.

e) Restart the Docker daemon:sudo systemctl restart docker

Installing Pocker and Pulling PBSCloud ContainersPocker is a PBSCloud Docker wrapper, designed to setup, install and manage your PBSCloud containersinstallation.

Contact an Altair Application Engineer to obtain the PBSCloud configuration tar file config.tar.gzbefore proceeding.


2. Connect to the PBSCloud Docker registry:docker login pbscloudio.azurecr.io -u a882d237-5d07-48a7-837e-9bd8652d79ec

Password is: kq9ZKzrToLGm78xGBDv5lKx5hg5YOB8JDz3usbp+2eo=

3. Untar config.tar.gz to the home directory of the user who is installing PBSCloud:tar xvfz config.tar.gz -C <HOME_DIR>




5. Install MongDB 3.0:docker pull mongo:3.0

6. Create your deployment environment definition:pocker kard create $PBSCLOUD_VERSION -e pbscloud \--extra tag=$PBSCLOUD_VERSION ui_port=9980 \config_tpl_folder=/config/ ui_url_prefix='/pclm'

7. Pull the PBSCloud containers:pocker image pull -r pbscloudio.azurecr.io \-u a882d237-5d07-48a7-837e-9bd8652d79ec \-p kq9ZKzrToLGm78xGBDv5lKx5hg5YOB8JDz3usbp+2eo=

Where kq9ZKzrToLGm78xGBDv5lKx5hg5YOB8JDz3usbp+2eo= is the password that was used toconnect to the PBSCloud docker registry.



Configuring a Public IP Address for PBSCloudConfigure ports and a public IP address so that PBSCloud can communicate with deployed cloudappliances.

Note: Configuring a public IP address for PBSCloud is only necessary for cloud appliancedeployment. If you do not plan on creating and deploying an appliance using PBS Control,then you may skip this step.

Appliances deployed by PBSCloud need to be able to communicate to the PBSCloud service from thepublic cloud/internet on ports 4505 and 4506. The machine running the PBSCloud service must havethese ports available at an IP accessible from outside the local network or the network configurationneeds to be such that a publicly accessible IP address has these ports forwarded to the IP address ofthe machine running PBSCloud.

Once this configuration is set up, you must specify to PBSCloud which public IP address is going to beused to communicate with PBSCloud.

1. Edit the file <HOME_DIR>/kard/current/site_config/configurator.conf.


2. Place the following lines in the file:[configurator.drivers.salt]master_ip = <PUBLIC_IP>

Replace <PUBLIC_IP> with the public IP address that is going to be used for communication withPBSCloud.

3. Save the file.






Linking PBSCloud with the PBS Works License ServerConfigure PBSCloud so that it can access the PBS Works license server.

1. Navigate to the directory <HOME_DIR>/kard/current/site_config.


2. Edit the file pacioli.conf and add the following lines to the file:[drivers]



method=pbsworks [[pacioli.drivers.pbsworks]]checkout_interval=10host=http://<PBSWORKS_LICENSE_SERVER_IP>:<PBSWORKS_LICENSE_SERVER_PORT>

The checkout_interval is in minutes and defines how often the bursted node hours are checkedagainst the purchased licenses.

3. Save the file.






Configuring a SMTP Server for Cloud Bursting Quota AlertsSet up a SMTP server so that when a cloud bursting resource alert limit is reached an email is sent tothe PBSCloud Administrator.

The PBSCloud Administrator is defined when PBSCloud is started and initialized.

1. Navigate to the directory HOME_DIR>/kard/current/site_config.


2. Edit the file executor.conf and add the following lines to the file:[smtp]host=<SMTP_SERVER_HOSTNAME/IP_ADDRESS>port=<SMTP_SERVER_PORT_NO>login=<SMTP_LOGIN_USERNAME>password=<SMTP_LOGIN_PASSWORD>


3. Save the file.

4. Edit the file guardian.conf and add the following lines to the file:[smtp]host=<SMTP_SERVER_HOSTNAME/IP_ADDRESS>port=<SMTP_SERVER_PORT_NO>login=<SMTP_LOGIN_USERNAME>password=<SMTP_LOGIN_PASSWORD>


5. Save the file.

6. Restart the executor and guardian Pocker containers:docker restart executor-api guardian

7. Create an environment variable for the PBSCloud version:



export PBSCLOUD_VERSION=2018.1





Starting and Initializing PBSCloudStart and initialize PBSCloud using Pocker.

1. Generate your environment:pocker kard make

2. Start PBSCloud:pocker start

3. Initialize PBSCloud by entering the command:pocker ext init full --domain_name <domain_name> \--username <admin_username> --password '<admin_password>' \--user_email '<admin_email>'

The values between the <> are used during the PBS Control installation process to link PBSCloudand PBS Control. You will need to replace these four values:

The domain_name does not have to be a true DNS domain, but it a group name for your project.It cannot include a period ( . ).

The admin_username and admin_password identify the credentials of the PBSCloud Administrator.The admin_username should not contain an asterisk ( * ). The admin_password must be at least6 characters in length and must contain at least one number.

Note: Email alerts are sent to the PBSCloud Administrator when a cloud burstingresource alert limit is reached.

Below is an example:

pocker ext init full --domain_name chrysler --username tsmith --password 'password@123' --user_email '[email protected]'

The output of this command contains keys to unlock the vault and main passwords. Copy theoutput of this command and store it in a location where you can find it easily.



2.2.9 Installing PBS ControlInstall the PBS Control Web Application, as well as the Monitor, Simulator and Configure services.

Before running the PBS Control installer on the machine hosting PBS Control, PBS Analytics, andPBSCloud, the following prerequisites must be met:










Several services use MongoDB for data storage, therefore there will be multiple database instancesrunning once PBS Control is installed.

The Monitor service uses Postgres for data storage. Once the Monitor service is installed and started, aPostgres database instance will be running.

The installer will ask for the hostname (endpoint) for the following components:

• PBS Analytics

• PBSCloud

• Submission Host (PAS Server)

1. Login to the machine where PBS Analytics and PBSCloud have been installed as a non-root userhaving sudo privileges.






7. Choose the Advanced installation type by entering 2 and pressing ENTER.

8. Choose to install all services by entering: 5 and pressing ENTER.



9. Choose one of the following options for the PBS Analytics Host:

• When PBS Analytics is installed on a separate machine, enter the hostname of the machinewhere PBS Analytics is installed and press ENTER.

• When PBS Analytics is installed on the same machine as PBS Control, press ENTER to acceptthe default of localhost.

10. Choose one of the following options for the PBSCloud Host:

• When PBSCloud is installed on a separate machine, enter the hostname of the machine wherePBSCloud is installed and press ENTER.

• When PBSCloud is installed on the same machine as PBS Control, press ENTER to accept thedefault of localhost.

Note: Recommendation is to install PBSCloud and PBS Control on the samemachine.

11. Choose Simulator Server by entering: 1 and pressing ENTER.

Choosing this option causes only the Simulator Server to be installed. The configuration of the PASServer (2- Submission Server Config) and the PBS MoM (3- Execution Node Config) should havealready been done in a separate installation process.

12. Enter the hostname (endpoint) of the machine where the PAS Server (Submission Host) isinstalled and press ENTER.




14. Enter the license server in the format port@hostname and press ENTER.




18. Navigate to the directory: <PC_HOME>/data/api_gateway.

19. Edit the file: Cloud_io_Credentials.json.

This file contains a key-value pair for "username" and "password" "username":"admin@altair", "password":"TM9RHX9nNLX0riiPM3/T6w=="

20. Change the value of username to those values entered while starting and initializing PBSCloud(Starting and Initializing PBSCloud step 3) in the format admin_username@domain_name.Ex. tsmith@chrysler



21. Encrypt the password (admin_password) entered while starting and initializing PBSCloud (Startingand Initializing PBSCloud step 3):./<EXEC>/exec/api_gateway/scripts/password_encryption.sh encrypt <admin_password>

Note: The output of this script is the encrypted password.

22. Copy the output from the previous step and paste it into the Cloud_io_Credentials.json file asthe value of password.

23. Save the file Cloud_io_Credentials.json.

24. Switch to the PBS Control Service User by issuing this command:su <SERVICE_USERNAME>

where SERVICE_USERNAME is the username of the PBS Control Service User.

25. Enter the following command:pbs-sim-agent --operation import_study --study-module parameter_sweep

This command returns JSON output which can be ignored.

The PBS Control web application is now accessible through the URL https://hostname:9500/pc.

You may now configure login access for users other than the Service User and perform other post-installation configuration. See the Advanced Configuration chapter.


Uninstalling PBS Control 33 Uninstalling PBS Control


• 3.1 Uninstalling PBS Control (p. 50)

• 3.2 Uninstalling PBS Analytics (p. 51)

• 3.3 Uninstalling PBSCloud (p. 52)

PBS Control Administrator's Guide3 Uninstalling PBS Control p.50

3.1 Uninstalling PBS ControlUninstall all PBS Control services and third-party packages.

Note: All services are automatically stopped during the uninstallation process.

1. Login to the machine where the PBS Control services are installed as root or a user with sudoprivileges.



4. Enter the instance you want to uninstall and press ENTER.

5. Enter 1 to uninstall the product and press ENTER.

6. Press ENTER to uninstall PBS Control.

It may take several minutes to uninstall PBS Control.

All services, files and third-party packages are removed. A single file /etc/pbswinstall_op_report isleft on the system. Installation information is appended to this file during the installation of PBS Control.This file is useful for diagnostics, therefore it is not removed during the uninstallation process.



3.2 Uninstalling PBS AnalyticsUninstall the PBS Control services responsible for providing analytics.


Refer to the PBS Analytics Administrator's Guide 2018.1 for instructions on how to uninstall the PBSAnalytics web application, parser, and data collector.



3.3 Uninstalling PBSCloudRemove an instance of PBSCloud

You must stop PBSCloud before uninstalling it.

1. Login to the machine where PBSCloud is installed as a user with sudo privileges.

2. Connect to pocker container:docker run -ti --rm -e PBSCLOUD_VERSION=$PBSCLOUD_VERSION \-v /run/docker.sock:/run/docker.sock \-v <HOME_DIR>/config:/config \-v <HOME_DIR>/kard:/pocker/kard pbscloudio.azurecr.io/pocker:$PBSCLOUD_VERSION bash


3. Clean PBSCloud services:pocker clean

4. Purge PBSCloud images:pocker image purge

5. Remove poker container:exitdocker image rm pbscloudio.azurecr.io/pocker:$PBSCLOUD_VERSIONrm -rf <HOME_DIR>/configrm -rf <HOME_DIR>/kard



Starting and Stopping Services 44 Starting and Stopping Services


• 4.1 PBS Control Services (p. 54)

• 4.2 PBS Control Service Commands (p. 55)

• 4.3 PBSCloud Service Commands (p. 57)

PBS Control Administrator's Guide4 Starting and Stopping Services p.54

4.1 PBS Control ServicesA description of the services installed for PBS Control.

Name of Service Description

pbsmonitor-postgres.service Monitor Postgres Server

pbsmonitor.service Monitor Server

pbssim-executor.service Simulator Executor HTTP API

pbssim-mongod.service Simulator Storage Service MongoDB port

pbssim-storage-http.service Simulator Storage Service HTTP API

pbswadmin-mongod.service Configuration Service MongoDB

pbswadmin-orchestrator.service Configure HTTP API

pbswadmin-worker.service Administrator Worker Orchestrator

pbswauth.service Authentication and Licensing Server

pbswconfig-mongod.service Configuration Service MongoDB

pbswconfig-orchestrator.service Configuration Service HTTP API

pbswconfig-worker.server Configuration Service

pbsworks-messagerouter-mongod.service

Messagerouter DB

pbsworks-messagerouter-http.service Messagerouter HTTP API

pbsworks-messagerouter-rabbitmq.service

RabbitMQ internal use

pbsworks-nginx.service Gateway HTTPS

pcgui.service GUI Server

ws-notification.service Websocket Bridge



4.2 PBS Control Service Commands

4.2.1 Starting PBS ControlStart all PBS Control services.


2. Enter the following command to start PBS Control:pbs-control-manager start

4.2.2 Stopping PBS ControlStop all PBS Control services.


2. Enter the following command to stop PBS Control:pbs-control-manager stop

4.2.3 Restarting PBS ControlRestart all PBS Control services.


2. Enter the following command to restart PBS Control:pbs-control-manager restart

4.2.4 Determining the Status of a PBS Control ServiceDetermine whether a PBS Control service is up or down.


2. Enter the following command to determine whether a PBS Control service is up or down:systemctl status <service>

Where <service> is the name of the PBS Control service that is being checked.

Messages similar to the below are displayed. When the service is running the status is "active" andwhen the service is down the status is "inactive".● pcgui.service - PBS Control GUI Server



Loaded: loaded (/etc/systemd/system/pcgui.service; disabled; vendor preset: disabled) Active: active (exited) since Sun 2017-11-12 23:04:29 EST; 2 weeks 5 days ago Process: 15546 ExecStart=/opt/altair/pbsworks/exec/shared/scripts/pbsworks-tomcat-manager --pbsworks-home /var/spool/pbsworks/home --start pcgui (code=exited, status=0/SUCCESS) Main PID: 15546 (code=exited, status=0/SUCCESS) Memory: 2.7G CGroup: /system.slice/pcgui.service └─15555 /opt/altair/pbsworks/exec/shared/thirdparty/java/bin/java -Djava.util.logging.config.file=/var/spool/pbsworks/home/config/pcgui/tomcat/conf/log...



4.3 PBSCloud Service Commands

4.3.1 Starting PBSCloud After a Machine RebootDocker and pocker instructions for starting PBSCloud



3. Connect to the pocker container:docker run -ti --rm -e PBSCLOUD_VERSION=$PBSCLOUD_VERSION \-v /run/docker.sock:/run/docker.sock \-v <HOME_DIR>/config:/config \-v <HOME_DIR>/kard:/pocker/kard pbscloudio.azurecr.io/pocker:$PBSCLOUD_VERSION bash


4. Start PBSCloud services:pocker start

5. Logout from the pocker container:exit

4.3.2 Stopping PBSCloudDocker and pocker instructions for stopping PBSCloud



3. Connect to Pocker container:docker run -ti --rm -e PBSCLOUD_VERSION=$PBSCLOUD_VERSION \-v /run/docker.sock:/run/docker.sock \-v <HOME_DIR>/config:/config \-v <HOME_DIR>/kard:/pocker/kard pbscloudio.azurecr.io/pocker:$PBSCLOUD_VERSION bash


4. Stop PBSCloud services:pocker stoppocker clean


Advanced Configuration 55 Advanced Configuration


• 5.1 Granting Login Access to PBS Control (p. 59)

• 5.2 Configuring Single Sign-On (p. 60)

• 5.3 Enabling Multi-Factor Authentication (p. 63)

• 5.4 Configuring Concurrent Threads for Retrieving Job Details (p. 65)

• 5.5 Configure the Job and Node Details Refresh Interval (p. 66)

• 5.6 Changing the SSH Server (p. 67)

• 5.7 Configuring the Session Timeout (p. 68)

• 5.8 Changing the PBS Control License Server (p. 69)

• 5.9 Changing the HyperStudy License Server (p. 70)

• 5.10 Changing the Hostname of the Analytics Service (p. 71)

• 5.11 Changing the Hostname of the PBSCloud Service (p. 72)

• 5.12 Changing the Gateway HTTPS Port (p. 73)

• 5.13 Resetting the Analytics Accounting Log Data (p. 74)

• 5.14 Logging (p. 75)

• 5.15 Advanced Configuration for PBSCloud (p. 78)

PBS Control Administrator's Guide5 Advanced Configuration p.59

5.1 Granting Login Access to PBS ControlPermit users other than the PBS Control Service User login access to PBS Control.

Note: Users must be valid NIS/SSH users.

1. Edit the file PC_HOME/data/ams/local-datastore/Access_controlled_users.json.

2. Grant login access to a user by adding comma separated usernames (within quotes) to the valueof username."username": ["pbsworks","user1","user2"],

Note: "pbsworks" is replaced with the Service User entered during the installation ofPBS Control.

3. Optionally, change the error message that is displayed when a user is not authorized to login toPBS Control by changing the value of error_message."error_message" : "New error message here"

4. Save the Access_controlled_users.json file.

The newly added user now has access to login to PBS Control.

Warning: Once a user is logged into PBS Control, they have access to PBS Controlas long as their login session is active. If their username is removed from theAccess_controlled_users.json file, they will continue to have access to PBS Control untilthey logoff and login again or until their login session expires.



5.2 Configuring Single Sign-On

5.2.1 Enabling Single Sign-OnEnable Single Sign-On (SSO) so that clients who are logged into a domain can access PBS Controlwithout providing credentials a second time.

The browser that is used to access PBS Control has to be configured for Kerberos and NT LAN Manager(NTLM). View How to configure supported browsers for Kerberos and NTLM for a list of supportedbrowsers and platforms, as well as steps for configuring the supported browser.

Additionally, every service that uses Kerberos authentication needs to have an SPN set for it so thatclients can identify the service on the network. For information on how to register a SPN see Registeringa SPN. If a SPN has already been registered, verify the SPN before enabling SSO - Verifying SPNRegistrations.

Note: By default SSO is disabled.

1. Edit the file PC_HOME/config/shared/auth-config/auth_details.json.

2. Enable SSO by changing the value of the sso key to true."sso": { "enable_sso": "true" },

3. Edit the file PC_HOME/config/shared/auth-config/krb5.conf.

4. Replace all instances of $SSO_DOMAIN$ with the domain name (in uppercase) against which theusers are authenticated.[libdefaults] default_realm=$SSO_DOMAIN$ default_tkt_enctypes = aes128-cts rc4-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc default_tgs_enctypes = aes128-cts rc4-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc permitted_enctypes = aes128-cts rc4-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc

[realms] $SSO_DOMAIN$ = { kdc = $SSO_DOMAIN$ default_domain = $SSO_DOMAIN$}

[domain_realm] .$SSO_DOMAIN$ = $SSO_DOMAIN$

On Windows, find the domain name by right-clicking My Computer and selecting Properties.

Figure 4: Windows Domain Name


https://ping.force.com/Support/%20PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM


On Linux, find the domain name using the command dnsdomainsname.

5. Edit the file PC_HOME/config/pcgui/tomcat/conf/web.xml.

6. Perform a search for the following text: ALTAIR PBSControl SSO Configurations.

7. Uncomment the XML just below this text by removing  that surround the XML.

8. Update SPN_USER_NAME and SPN_USER_PASSWORD with the credentials used when registeringthe SPN. <init-param> <param-name>spnego.preauth.username</param-name> <param-value>{SPN_USER_NAME}</param-value> </init-param>

<init-param> <param-name>spnego.preauth.password</param-name> <param-value>{SPN_USER_PASSWORD}</param-value> </init-param>

9. Restart the PBS Control Web Application service.systemctl restart pcgui

Registering a SPNRegister a Service Principal Name (SPN) so the you can implement Kerberos authentication.

SPNs are unique identifiers for services running on servers. Every service that uses Kerberosauthentication needs to have an SPN set for it so that clients can identify the service on the network.

1. Click this link: http://spnego.sourceforge.net/spnego_tomcat.html.

2. Scroll down until you find the section titled "Registering an SPN".

3. Follow the instructions to register a SPN.


http://spnego.sourceforge.net/spnego_tomcat.html


Verifying SPN RegistrationsCheck that a SPN is registered for a specific computer.

1. Click the Windows Start button.

2. Enter command in the search box.

3. Right-click Command Prompt.4. Click Run as administrator.5. Enter the command: setspn -T -F -Q http/<DNSNAME>.

<DNSNAME> is the DNS hostname used when registering the SPN.

5.2.2 Disabling Single Sign-OnDisable Single Sign-On so that users are forced to enter their credentials when logging into PBS Control.


2. Disable SSO by changing the value of the sso key to false."sso": { "enable_sso": "false" },

3. Edit the file PC_HOME/config/pcgui/tomcat/conf/web.xml.

4. Perform a search for the following text: ALTAIR PBSControl SSO Configurations.

5. Comment the XML just below this text by surrounding the XML with .

6. Restart the PBS Control Web Application:systemctl restart pcgui



5.3 Enabling Multi-Factor AuthenticationEnable DUO multi-factor authentication to strengthen access security by requiring two methods to verifyyour identity.

You must have already implemented DUO multi-factor authentication at your site.

Multi-factor authentication adds a second layer of security to your site. Verifying your identity using asecond factor (like your phone or other mobile device) prevents anyone but you from logging in, even ifthey know your password.


2. Enable multi-factor authentication by changing the value of the enable_multi_factor key to true. "multifactor": { "enable_multi_factor": "true",

3. Replace %INTEGRATION_KEY%, %SECRET_KEY%, and %APPLICATION_KEY% with theappropriate values obtained when you chose to protect a new application using the DUO AdminPanel."integration_key":"%INTEGRATION_KEY%","secret_key":"%SECRET_KEY%","application_key":"%APPLICATION_KEY%",

4. Replace %DUO_SCREEN_URL% with the URL that is hosting DUO authentication.

Note: PBS Control sends requests to this URL and communication must be done overHTTPS - i.e. https://someURL. Additionally, the request that PBS Control sends is asigned request, therefore you must be prepared to accept a signed request. For anexample, see the HTML in step 5.

"duo_screen_URL":"%DUO_SCREEN_URL%"

5. Make sure your post_action in the DUO web page points to the following URL:https://PC_HOSTNAME/auth/validate/mf

where PC_HOSTNAME is the hostname of the machine where PBS Control is installed.

Example of DUO HTML page:<!DOCTYPE html><html> <head> <meta charset="utf-8"> <title>Duo Security 2-factor auth Tut - Enable Two-Factor Auth</title> <link rel="stylesheet" href="css/main.css"> </head><body> <iframe id="duo_iframe" width="100%" height="500" frameborder="0"></iframe> <script src="js/Duo-Web-v2.js" type="text/javascript"></script>    <script> var urlParams = new URLSearchParams(window.location.search); var myVar = urlParams.get('sig_request'); console.log(urlParams.get('sig_request')); console.log(urlParams.toString()); Duo.init({ 'host': 'api-45d973a0.duosecurity.com', 'sig_request': myVar, 'post_action': 'https://PC_HOSTNAME/auth/validate/mf'



}); </script> Welcome to DUO login</body></html>



5.4 Configuring Concurrent Threads for RetrievingJob DetailsChange the number of concurrent threads that are created to retrieve PBS Professional job details whensystem memory issues arise.

Important: Do not change the number of concurrent threads unless your site isexperiencing system memory issues.

Monitor retrieves job details from PBS Professional using concurrent threads. By default, the number ofthreads created is based on the number of system cores multiplied by four (an 8 core system will create8 * 4 = 32 concurrent threads). This multiplication factor has been well tested and provides optimalresults. If your site is experiencing system memory issues, then the number of concurrent threads canbe reduced to free up memory.

CAUTION: The value of concurrent threads should always be set to a positive (great thanzero) number. Setting the number of concurrent threads to a low value will negatively affectjob refresh time. Assigning a higher value when there is a small number of PBS Professionaljobs will not improve performance.

1. Navigate to the PC_HOME/config/monitor/services directory.

2. Edit the file monitor.conf.

3. Update the value of QSTAT_THREADS.QSTAT_THREADS=0



5.5 Configure the Job and Node Details RefreshIntervalChange how often PBS Control requests job and node details from PBS Professional.

Important: Do not change the refresh interval unless your site is experiencingperformance issues.

Monitor runs a background process which retrieves job and node detail information from PBSProfessional. By default, this information is updated every 300 seconds (5 minutes). This interval can bemodified when performance issues are being observed.

CAUTION: Setting the refresh interval to a low value may overwhelm PBS Professional withcontinuous requests.

1. Navigate to the PC_HOME/config/monitor/services directory.

2. Edit the file monitor.conf.

3. Update the value of REFRESH_SCHEDULER_WAIT_TIME_IN_SECONDS.REFRESH_SCHEDULER_WAIT_TIME_IN_SECONDS=300



5.6 Changing the SSH ServerPoint to a new SSH server.

1. Edit the file <PC_HOME>/config/ams/jaas-config/AA_jaas.config.

2. Change the value of host to the hostname of the new SSH server.LoginModule { com.altair.jaas.module.SSHUnixLoginModule Required host="localhost" port="22" cache_ttl="60" debug=false; com.altair.jaas.module.UsersAccessControl Required;};



5.7 Configuring the Session TimeoutChange when a session closes as a result of inactivity over the client connection.

The default session timeout value is 5 hours.

1. Edit the file <PC_HOME>/config/ams/ AA_Service.properties.

2. Change the value of java.sessionTimeout to a new value in hours.



5.8 Changing the PBS Control License ServerPoint to a new license server for PBS Control.

1. Edit the file <PC_HOME>/config/license/environment.json.

2. Change the value of ALTAIR_LICENSE_PATH to the new license server in the formatport@hostname.

3. Restart the Authentication and Licensing service by executing the command:sudo systemctl restart pbswauth.service



5.9 Changing the HyperStudy License ServerPoint to a new license server for HyperStudy.

1. Edit the file <PC_HOME>/pbs-control-simulator/etc/pbssim/environment.

2. Change the value of ALTAIR_LICENSE_PATH to the new server containing the Hyperstudy license.



5.10 Changing the Hostname of the AnalyticsServiceChange the hostname of the Analytics service when it is moved to a new host.

1. Login to the machine where the PBS Control Web Interface is installed as a user with sudopermissions.

2. Edit the file <PC_HOME>/config/api_gateway/nginx/nginx.conf .

3. Change the Analytics service hostname by updating the existing value of server for upstreamAnalyticsHost in the format of hostname:port.upstream AnalyticsHost{ server dm-04:9000; }

4. Change the Analytics service hostname by updating the existing value of server for upstreamAnalyticsBAHost in the format of hostname:port.upstream AnalyticsBAHost{ server dm-04:9443; }

5. Restart the Gateway service by executing the command:sudo systemctl restart pbsworks-nginx

6. Login to the machine where the Simulator service is installed as a user with sudo permissions.


8. Change the value of PBS_SIM_ANALYTICS_HOST to the new hostname of the Analytics service.

9. Edit the file <PC_HOME>/pbs-control-simulator/etc/pbssim/pbssim.conf .

10. Change the value of analytics_host to the new hostname of the Analytics service.

11. Restart the Simulator service by executing the command:sudo systemctl restart pbssim-executor pbssim-storage-http



5.11 Changing the Hostname of the PBSCloudServiceChange the hostname of the PBSCloud service when it is moved to a new host.



3. Change the PBSCloud service hostname by updating the existing value of server for upstreamPBSCloud in the format of hostname:port. upstream PBSCloud{ server dm-01:9980; }




5.12 Changing the Gateway HTTPS PortChange the port that the Gateway HTTPS service listen on.



3. Change the Gateway HTTPS default port to a new port by updating the default value of 9500 oflisten of server. server { listen 9500 ssl default_server;

server_name _; ... ... }




5.13 Resetting the Analytics Accounting Log DataDiscard all parsed accounting log data and reset all Data Collectors.

Before resetting the Analytics accounting log data, all simulation and model data must be deleted - seeDeleting All Simulation and Model Data.

1. Login as root to the machine where the Analytics Web Application and Parser are installed.

2. Stop the PBS Analytics service by issuing the command:/etc/init.d/pbsworks-pbsa stop

3. Execute the following command:pbsa-data-reset

All parsed accounting log data is discarded and Data Collectors are reset. The PBS Analyticsdatabase password to is also reset to “pbsworks@123”.

4. Use the pbsa-data-password command to change it to a site specific password:pbsa-data-password OLD_PASSWORD NEW_PASSWORD

5.13.1 Deleting All Simulation and Model DataRemove simulation and model data before resetting the PBS Analytics dataset.

When the PBS Professional accounting log data is discarded, all simulation and model data must bedeleted as well.

1. Login to the machine where the Simulator Service has been installed as the PBS Control Serviceuser.

2. Execute the following command to remove all simulation and model data from PBS Control:pbs-sim-agent --operation delete_all --auth-token placeholder

Simulation and model data is removed when the following message is displayed:PBS Sim data reset complete.



5.14 LoggingGeneral logging information.

Logging behavior for the following functional areas can be modified:

• Authentication

• Gateway

• Licensing

• Websocket Bridge

• Simulator

Default Logging LevelThe default logging level is set to “info” providing informational messages that highlight the progress ofthe service at a coarse-grained level.

Logging LevelsLogging levels available are:

• OFF - has the highest possible rank and is intended to turn off logging.

• FATAL - very severe error events that will presumably lead the application to abort.

• ERROR - error events that might still allow the application to continue running.

• WARN - potentially harmful situations.

• INFO - informational messages highlighting the progress of the application at a coarse grained level.

• DEBUG - fine-grained informational events that are most useful to debug an application.

• TRACE - finer-grained informational events than the DEBUG.

• ALL - the lowest possible rank and is intended to turn on all logging.

5.14.1 Changing Authentication Logging LevelChange the logging level to troubleshoot authentication.

See Logging for a list of available logging levels.

1. Edit the file <PC_HOME>/config/ams/logging-config/log4j.properties.

2. Set the value of log4j.logger.com.altair to the appropriate logging level.




5.14.2 Changing the Configure Service Logging LevelChange the logging level to troubleshoot the Configure service.


1. Edit the file <PC_HOME>/pbsworks-configure/etc/environment.

2. Add the following line to the file:PBSWADMIN_LOG_LEVEL=

3. Set the value of PBSWADMIN_LOG_LEVEL to the appropriate logging level.


• INFO - informational messages highlighting the progress of the application at a coarse grainedlevel.

• WARNING - potentially harmful situations such as failures and exceptions.

4. Restart the Configure services by executing the command:sudo systemctl restart pbswadmin-orchestrator pbswadmin-worker

5.14.3 Changing the Gateway Logging LevelChange the logging level to troubleshoot the Gateway.


1. Edit the file <PC_HOME>/config/api_gateway/logging-config/log4j.properties.


3. Restart the Gateway service by executing the command:sudo systemctl restart pbsworks-nginx.service

5.14.4 Changing the Licensing Logging LevelChange the logging level to troubleshoot licensing.


1. Edit the file <PC_HOME>/config/license/log4j.properties.

2. Set the value of log4j.logger.com.altair.pbsworks.license to the appropriate logging level.

3. Set the value of log4j.logger.com.altair.pbsworks.license.api to the appropriate logginglevel.




5.14.5 Changing the Websocket Bridge Logging LevelChange the logging level to troubleshoot the Websocket Bridge.


1. Edit the file <PC_EXEC>/ws_bridge/binaries/log4js.json.


3. Restart the Websocket Bridge service by executing the command:sudo systemctl restart ws-notification.service

5.14.6 Changing the Simulator Service Logging LevelChange the logging level to troubleshoot the Simulator service.



2. Add the following line to the file:PBS_SIM_LOG_LEVEL=

3. Set the value of PBS_SIM_LOG_LEVEL to the appropriate logging level.


• INFO - informational messages highlighting the progress of the application at a coarse grainedlevel.

• WARNING - potentially harmful situations such as failures and exceptions.

4. Restart the Simulator services by executing the command:sudo systemctl restart pbssim-executor pbssim-storage-http



5.15 Advanced Configuration for PBSCloud

5.15.1 Creating a Service to Start and Stop PBSCloudCreate a systemd service to automatically start and stop PBSCloud

1. Navigate to the directory /etc/sysconfig.

2. Create and edit a file called pbscloud.

3. Place the following information in the file:PKER_IMG=pbscloudio.azurecr.io/pockerPKER_VER=2018.1PKER_VOL_OPTS="-v /run/docker.sock:/run/docker.sock -v <HOME_DIR>/config:/config -v <HOME_DIR>/kard:/pocker/kard"PKER_DKER_OPTS="--rm"


4. Navigate to the directory /etc/systemd/system.

5. Create and edit a file called pbscloud.service.

6. Place the following information in the file:[Unit]Description=PBSCLOUDAfter=docker.serviceRequires=docker.service [Service]EnvironmentFile=/etc/sysconfig/pbscloudTimeoutStartSec=infinityExecStart=/usr/bin/docker run $PKER_DKER_OPTS $PKER_VOL_OPTS ${PKER_IMG}:${PKER_VER} pocker startExecStop=/usr/bin/docker run $PKER_DKER_OPTS $PKER_VOL_OPTS ${PKER_IMG}:${PKER_VER} pocker stop [Install]WantedBy=multi-user.target

7. Save the file.

8. Enable the service:systemctl enable pbscloud.service

You can now use the following systemctl commands to start and stop PBSCloud:

systemctl start pbscloud.service and systemctl stop pbscloud.service

5.15.2 Finding the Current PBSCloud VersionFind the current Pocker and PBSCloud versions.


2. Enter the following command to find the current Pocker version:



docker run -ti --rm -e PBSCLOUD_VERSION=$PBSCLOUD_VERSION \-v /run/docker.sock:/run/docker.sock \-v <HOME_DIR>/config:/config -v <HOME_DIR>/kard:/pocker/kard pbscloudio.azurecr.io/pocker:$PBSCLOUD_VERSION \bash -c 'pocker -v'


3. Enter the following command to find the PBSCloud version.docker exec -ti ui sh -c 'echo $VERSION'

5.15.3 Accessing PBSCloud LogsMonitor PBSCloud by viewing its logs through a Kibana interface.

1. Open a supported web browser.

2. Enter the URL: http://hostname:5601

Where hostname represents the hostname of the machine where PBSCloud is installed.

5.15.4 Accessing PBSCloud AnalyticsView graphs of Docker container monitoring through a Grafana interface.


2. Navigate to the directory <HOME_DIR>/kard/current.


3. Display the contents of the meta.yaml file using the command:cat meta.yaml

4. Copy the value of grafana_password.

5. Open a supported web browser.

6. Enter the URL: http://hostname:3000

Where hostname represents the hostname of the machine where PBSCloud is installed.

7. Login in as "admin" and use the password obtained in step 4.


Cloud Bursting 66 Cloud Bursting


• 6.1 Cloud Bursting (p. 81)

• 6.2 Prerequisites for Cloud Bursting (p. 82)

• 6.3 Configuring Amazon Web Service Cloud Bursting (p. 83)

• 6.4 Configuring Microsoft Azure Cloud Bursting (p. 91)

• 6.5 Configuring Google Cloud Platform Cloud Bursting (p. 102)

PBS Control Administrator's Guide6 Cloud Bursting p.81

6.1 Cloud BurstingCloud bursting is a configuration that is set up between an HPC cluster and a public cloud to deal withpeaks in cluster demand. When resource capacity at the HPC reaches a certain point, the demand isdirected to a public cloud so there is no interruption of services.

Cloud bursting requires that you already have an account with one of the supported cloud providers:

• Microsoft Azure

• Amazon Web Services (AWS)

• Google Cloud Platform (GCP)

There is some setup required at the cloud provider level before a cloud bursting scenario can be createdusing PBS Control. There is also PBS Professional configuration that must be done. The followinginstructions cover what needs to be done at the cloud provider prior to creating a bursting scenarioand how to create the bursting scenario. Instructions for the PBS Professional configuration can befound in the chapter Cloud Bursting with PBS in the PBS Professional 14.2.6 Release Notes attachedto the Confluence page https://confluence.prog.altair.com/display/PPC/Released+End-user+PBS+Documentation.

Figure 5: Cloud Bursting


https://confluence.prog.altair.com/display/PPC/Released+End-user+PBS+Documentation



6.2 Prerequisites for Cloud BurstingA secure network connection and DNS must be in place before cloud bursting can be enabled.

Network Connection with the Cloud ProviderA secure connection between the cloud provider and your local HPC cluster is required. This can be doneby:

• using a dedicated line offered by the cloud provider.

• using a VPN solution like Openvpn.

In either case, the goal is to provide secure communication between the PBS Server and the cloudresources.

DNSNodes that are burst in the cloud need to be visible to the PBS cluster. This can be done using a localDNS or the cloud provider's DNS. You can configure PBS to register the node as it is bursted. This isdone through a cloud bursting periodic hook script. The DNS server must be setup on the same systemas the PBS Server. Alternatively, you can disable the DNS configuration done through the periodic cloudbursting hook and point /etc/resolv.conf to the DNS managed by the cloud provider.

PCLM CLIThe PCLM CLI must be installed on the PBS Server. Contact Altair support to obtain a copy of the tarball.



6.3 Configuring Amazon Web Service CloudBurstingCreate the necessary components in AWS that are required for cloud bursting and then create a PBSControl cloud bursting scenario.

6.3.1 Creating an Amazon Web Service User AccountCreate an Amazon Web Service (AWS) user account so that your can register it in PBS Control.

You must already have signed up for an AWS account.

1. Open your browser and navigate to https://aws.amazon.com.

2. From the top Navigation bar, click My Account > AWS Management Console.

3. Sign in to the AWS Management Console.

4. Using the search box located under AWS services, enter IAM.

5. Click the IAM search result.The IAM dashboard is opened.

6. In the navigation pane on the left-hand side of the web page, click Users.

7. Click Add user to add an administrative user.

This user will have administrative rights to any machines hosted in the cloud.

8. For User name, enter a user name.For example, aws_cloud_bursting.

9. For Access type, enable Programmatic access.

10. Click Next:Permissions.

11. Optional: Click Add user to group.

This button may already be selected.

12. Click Create group.

13. For Group name, enter a suitable name.For example, PBSControl.

14. For Policy type, enable AdministratorAccess.

15. Click Create group.You are returned to the Add user page and the new group is enabled indicating that the user willbe added to the new group.

16. Click Next: Review.

17. Verify the user and group details.

18. Click Create user.19. Click Download.csv.

20. Download and save this file in a secure location.

The information in this file is used later to add a cloud account to PBS Control.


https://aws.amazon.com


21. Click Close.The new user account is displayed.

6.3.2 Registering an Amazon Web Service AccountAdd an existing AWS user account to PBS Control.

You must already created an AWS user account and given it administrative permissions.

1. Login to PBS Control.

2. Click the Design tab.

3. Under Infrastructure, click Cloud.

4. Click Add Cloud Account.5. Click .

6. In the dialog box, select the following:

a) For Account name, enter the AWS username that you just created.

b) For Access Key ID, copy and paste the value of Access key ID from the downloaded CSV file.

c) For Secret Access Key, copy and paste the Secret access key value from the downloaded CSVfile.

7. Click Create account.

6.3.3 Creating a Virtual Private Cloud NetworkCreate a Virtual Private Network (VPC) in AWS so that you can perform cloud bursting.

Login to your AWS Management Console.

1. Using the search box located under AWS services, enter VPC.

2. Click the VPC search result.The VPC dashboard is opened.

3. In the menu located on the left-hand side of the web page, click Your VPCs.

4. Click Create VPC.

5. For Name tag, enter a name for the VPC.bursting_vpc

6. For IPv4 CIDR block, provide an address range in CIDR notation.

7. For Tenancy, choose Default.8. Click Yes, Create.

9. In the menu located on the left-hand side of the web page, click Subnets.

10. Click Create Subnet.11. For Name tag, enter a name for the subnet.

12. For VPC, choose the VPC that you just created (e.g. bursting_vpc).

13. For Availability Zone, choose a region.



14. For IPv4 CIDR block, provide an address range in CIDR notation.

15. Click Yes, Create.

6.3.4 Creating a Virtual MachineCreate a CentOS 7 virtual machine in AWS Elastic Compute Cloud (EC2).


1. Using the search box located under AWS services, enter EC2.

2. Click the EC2 search result.The EC2 dashboard is opened.

3. Under Create Instance, click Launch Instance.

4. In the menu located on the left-hand side of the web page, click AWS Marketplace.

5. Using the search box, enter CentOS 7.

6. Locate the CentOS 7 template and click Select.7. Click Continue.

8. Select an Instance Type based on the requirements for the VM.

9. Click Next: Configure Instance Details.

10. Configure the following Instance Details:

a) For Number of instances, specify 1.

b) For Network, choose the network that you previously created (e.g. aws_cloud_bursting).

c) For Subnet, select the subnet that you previously created.

11. Click Next: Add Storage.

12. Specify the storage options as per your site's requirements.

13. Click Next: Add Tags.

14. Optional: You can add tags in key-value pairs for the VM per your site's requirements.

15. Click Next: Configure Security Group.

16. For Assign a security group, enable Create a new security group.

17. For Type, select All traffic.

18. Click Review and Launch.

19. Review all the information of the VM and click Launch.

20. Create a new key pair by selecting Create a new key pair.21. Provide a name for the key pair.

22. Click Download Key Pair.23. Download and save this file in a secure location.

The information in this file is used later to create the OS image.

24. Click Launch Instances.



6.3.5 Installing and Configuring the PBS MoM on the VMInstall the PBS MoM on the virtual machine and configure the VM per your site's environment.

1. SSH into the virtual machine as pbsadmin (this user has sudo permissions).

2. Install the PBS MOM.

3. Once the PBS MOM is installed, edit the /etc/pbs.conf file.

4. Change the value of PBS_SERVER to the hostname of the PBS Server.

5. Save the file.

6. Edit the file PBS_HOME/mom_priv/config where PBS_HOME is the home directory of PBS.

7. Change the value of $clienthost to the hostname of the PBS Server.

8. Save the file.

9. Configure the VM for your site's environment such as pointing it the DNS server, mounting filesystems, connecting it to the authentication service, installing any applications, etc.

10. Connect the VM to your PBS server and submit a job to ensure it is working as expected.

6.3.6 Creating an OS ImageAn image file of the Virtual Machine with the PBS MOM and application configured as per your site'srequirements will be deployed on the nodes for cloud bursting.




3. In the menu located on the left-hand side of the web page, click Instances.

4. Select the required Instance from the list.

Note: Before you proceed, verify that the state of the instance that you just created isrunning.

5. At the top, click Actions > Instance State > Stop.

6. Click Yes, Stop.The instance is stopped.

Note: This may take some time. Do not proceed until the instance is stopped.

7. At the top, click Actions > Image > Create Image.

8. Click Image from the menu and select Create Image.

9. For Image name, enter a name for the image.

10. For Image description, provide a description for the image.

11. Click Create Image.



Creating the image may take some time.

12. Click Close.

6.3.7 Creating a Cloud Bursting Scenario and a TokenCreate a cloud bursting scenario which will be used by PBS Professional for cloud bursting.

Open a browser window and login to your AWS Management Console. Open a second browser windowand login to PBS Control.

A cloud bursting scenario defines the specifications for network, storage, location, VM image to enablecloud bursting.

To control the bursting, quotas are defined for nodes, CPUs, RAM and storage through limits. Alerts aresetup to track usage. A token is created and an API key is generated. This API key is used in the PBSProfessional Cloud Bursting hook.

1. Navigate to the PBS Control browser window.

2. Click Design.

3. Under Infrastructure, click Bursting.

4. Click Add Bursting Scenario.

5. For Name, enter a name for the cloud bursting scenario.

6. For Description, enter a description.

7. For Cloud Provider, click .

8. For Cloud Account, choose a registered AWS account from the list.

9. Select a region from the list that matches the zone selected for the Subnet.

10. Click Next.11. Navigate to the AWS browser window.

12. Click located in the upper left-hand side of the web page.



15. In the menu located on the left-hand side of the web page, click AMIs.

16. Select the Amazon Machine Image (AMI) created for cloud bursting to view its details.

17. In the Details tab, hover over the AMI ID in the image details.

A copy to clipboard icon is displayed.

18. Click .


20. For the AMI ID, paste the AMI ID copied from AWS.

21. Navigate to the AWS browser window.

22. In the menu located on the left-hand side of the web page, click Security Groups underNETWORK & SECURITY.



23. Select the Security Group associated with the VM that was created earlier to view its details.

24. In the Description tab, hover over the Group ID.

A copy to clipboard icon is displayed.

25. Click .


27. For the Security group ID, paste the Group ID copied from AWS.


29. Click located in the upper left-hand side of the web page.

30. Using the search box located under AWS services, enter VPC.

31. Click the VPC search result.The VPC dashboard is opened.

32. In the menu located on the left-hand side of the web page, click Subnets.

33. Locate the Subnet created for cloud bursting in the list.

34. Copy the Subnet ID from the list.


36. For the Subnet ID, paste the Subnet ID copied from AWS.

37. Enable the Add public IP to VMs if you need to connect to the cloud bursting nodes from theinternet.

It is recommended to leave this disabled.


39. Locate the IPv4 CIDR network configuration value for the Subnet created for cloud bursting.

40. Copy the IPv4 CIDR value of the Subnet.


42. For Internal network CIDR, copy the CIDR copied from AWS.

43. Provide the domain name of your organization for the cloud bursting network.altair.com, burst.altair.com

44. Enter a prefix for the names of the bursted nodes.

If "node" is entered for the Hostname prefix, the cloud bursting nodes will be available to PBSProfessional as node1, node2, node3, etc.

45. For the Initialization script, enter the script that will run after a cloud node is bursted.The below script initializes the bursted node for PBS Professional use and should be modified peryour site's needs.

#!/bin/sh

# Configure fstabecho "fstab setup"rm -rf /etc/fstabecho "UUID=692b1fcb-ae19-44db-91f8-e91f4454c6fg / xfs defaults 0 0" > /etc/fstabecho "UUID=f93072dc-8cf4-4ac9-a716-135b39fc11df /boot xfs defaults 0 0" >> /etc/fstabecho “pbs_svr:/stage/jobs /stage/jobs nfs4 defaults 0 0" >> /etc/fstabecho “pbs_svr:/home /home nfs4 defaults 0 0" >> /etc/fstab



# Configure resolv.confecho "resolv.conf setup"rm -rf /etc/resolv.confecho "search burst.example.com ubh102srx53eljzrmbg1rvhhhh.yx.internal.cloudapp.net" > /etc/resolv.confecho "nameserver 192.168.10.1" >> /etc/resolv.confecho "nameserver 168.63.129.16" >> /etc/resolv.conf

# Configure /etc/hostsecho "/etc/hosts setup"rm -rf /etc/hostsecho "127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4" > /etc/hostsecho "192.168.10.1 pbs_svr.default.domain pbs_svr" >> /etc/hostsecho "10.10.10.1 pbs_svr.default.domain pbs_svr" >> /etc/hosts

IP=ìp addr show eth0 | grep "inet\b" | awk '{print $2}' | cut -d/ -f1`HOST=ùname -nècho "$IP $HOST" >> /etc/hosts

# Tell NetworkManager to not overwrite the resolve.conf filesystemctl disable NetworkManagersystemctl stop NetworkManagersystemctl enable networksystemctl start networksystemctl enable rhel-domainnamesystemctl start rhel-domainname

# Configure NISecho "NIS setup"rm -rf /etc/yp.confecho "domain default.lan server 10.0.15.253" > /etc/yp.confsystemctl restart ypbind

# Make sure that home is mountedecho "mount setup"mount /home

# Configure pbs.confecho "pbs setup"rm -rf /etc/pbs.confecho "PBS_EXEC=/opt/pbs" > /etc/pbs.confecho “PBS_SERVER=pbs_svr" >> /etc/pbs.confecho "PBS_SERVER_HOST_NAME=admin.default.domain" >> /etc/pbs.confecho "PBS_START_SERVER=0" >> /etc/pbs.confecho "PBS_START_SCHED=0" >> /etc/pbs.confecho "PBS_START_COMM=0" >> /etc/pbs.confecho "PBS_START_MOM=1" >> /etc/pbs.confecho "PBS_HOME=/var/spool/pbs" >> /etc/pbs.confecho "PBS_CORE_LIMIT=unlimited" >> /etc/pbs.confecho "PBS_SCP=/bin/scp" >> /etc/pbs.confecho "PBS_LEAF_ROUTERS=util-node,pbs_svr" >> /etc/pbs.conf

# Restart pbs to ensure that it is using the latest configurationln -s /pbsworks/pbs/exec/14.2.3 /opt/pbssystemctl restart pbs

# Configure /var/spool/pbs/mom_priv/configecho "mom config setup"rm -rf /var/spool/pbs/mom_priv/configecho "\$clienthost pbs_svr" > /var/spool/pbs/mom_priv/configecho "\$clienthost pbs_svr.default.domain" >> /var/spool/pbs/mom_priv/configecho "\$restrict_user_maxsysid 999" >> /var/spool/pbs/mom_priv/config

systemctl restart pbs

46. Click Add to add a public key.

47. For Public SSH key, enter a public SSH key. To obtain the public SSH key:



a) Login as root into the PBS Server.

b) Enter these commands:

cd .sshcat id_rsa.pub

c) Copy the SSH key.

d) Paste the SSH into the Public SSH key field.

The public key is copied to each bursted node for secure connectivity.

48. Repeat steps 46 through 47 to add additional public SSH keys.

49. Click Next to define quotas for the cloud bursting scenario.

50. Click Add Quota.

51. Choose the Resource Type from the menu.


53. Add a Limit value for the resource.

When the Limit value is reached for the resource, the deployment will be blocked.

54. Click + to add an alert.

55. Add an alert value.

When the alert value is reached, an email is sent if an SMTP server is configured.

56. Repeat steps 50 through 55 to add quotas for other resources types.

57. Click Instantiate scenario.

58. Enter a name for the token.

59. Specify the Expiration date in MM/DD/YYYY format.

60. Click Add Token.An API key is generated.

61. Copy and save this key.

It is only displayed once. This key is pasted in the configuration file used to configure the PBSProfessional cloud bursting hook.

62. Click Close.Information about the cloud bursting scenario is displayed.

Once the cloud bursting scenario is created, there is additional configuration that needs to occur forPBS Professional. See the chapter Cloud Bursting with PBS in the PBS Professional 14.2.6 Release Notesattached to the Confluence page https://confluence.prog.altair.com/display/PPC/Released+End-user+PBS+Documentation.





6.4 Configuring Microsoft Azure Cloud BurstingCreate the necessary components in Microsoft Azure that are required for cloud bursting and thencreate a PBS Control cloud bursting scenario.

6.4.1 Creating a Microsoft Azure User AccountCreate an Microsoft Azurece (AWS) user account so that your can register it in PBS Control.

You must have already created a Microsoft Azure Account and an Azure subscription.

1. Login in to your Microsoft Azure account.

2. In the Azure dashboard panel, click Cost Management + Billing.

3. In BILLING ACCOUNT, click Subscriptions, under Other subscriptions.

4. Locate and click your subscription to view further details.

5. Hover over the Subscription ID and click the copy button when it appears.

6. Store the Subscription ID value to a file to be used later to create a cloud provider account in PBSControl.

7. In the Azure dashboard toolbar, click the Help icon (?) and select Show diagnostics.

8. A file called PortalDiagnostics.json will be downloaded.

9. Using any text editor, open this .json file and search for "tenantId".

10. Store the value of the tag to a file to be used later to create a cloud provider account in PBSControl.

11. In the Azure Dashboard panel, click Azure Active Directory.

12. In the Azure Active Directory panel, under MANAGE, click App registrations.

13. Click New application registration.

14. Enter the following to create an Active Directory application:

• For Name, enter the name of the application (e.g. pbscloud_bursting).

• For Application type, select Web app / API.

• For Sign-on URL, enter the URL https://<hostname>:9500/pc where <hostname> is thehostname of the machine where the PBS Control Web Interface is installed.

This step registers PBS Control to your Azure Active Directory.

15. Verify the information and click Create.The application will be listed under DISPLAY NAME.

16. Select the application from the list.

17. Copy the Application ID and store it in a file to be used later to create a cloud provider account inPBS Control.

18. In the App registrations panel, search for the new application you registered (i.e.pbscloud_bursting).

19. Click the application name.



20. In the Settings panel, click Keys.

21. In the Keys panel, enter the following:

• For DESCRIPTION, enter pbscontrol_access_key.

• For EXPIRES, select Never Expires.

• For VALUE , enter pbscontrol_access_key.

22. Verify the information and click Save.A key value is created.

23. Copy this key and store it in a file to be used later to create a cloud provider account in PBSControl

24. In the Azure Dashboard panel, click More services.

25. Locate and click Subscriptions.

26. In the Subscriptions panel, under the SUBSCRIPTION column, select your organization.A sub-panel appears.

27. Select Access control (IAM).

28. Click Add.

29. In the Add permissions panel, select the following to assign a role to your application:

• For Role, select Contributor.• For Assign access to, select Azure AD user, group, or application.

• For Select, search for the Active Directory application you just created (i.e.pbscloud_bursting).

30. Click Save.

6.4.2 Registering a Microsoft Azure User AccountAdd an existing Azure user account to PBS Control.

You must have already created a Microsoft Azure Account and an Azure subscription.




4. Click Add Account.5. In the dialog box, select the following:

• For Provider, select Microsoft Azure Cloud Services.

• For Account name, enter any name you wish you enter. Example: pbscloud_bursting.

• For Client ID, - enter the Application ID saved in the previous step.

• For Secret Key, - enter the key saved in the previous step.

• For AD tenant ID, enter the tenant ID in the previous step.

• For Subscription ID, enter the subscription id saved in the previous step.

6. Verify all the information and click Create account.



After the account is created, it appears in the Cloud providers list.

6.4.3 Creating a Resource GroupCreate a resource group that will later be used to create a cloud bursting scenario.

Login to your Microsoft Azure account and navigate to the Azure Dashboard. You must have alreadycreated an Azure subscription to create a resource group.

A resource group is container that holds related resources for an Azure solution. The resource group caninclude all the resources for the solution, or only those resources that you want to manage as a group.You decide how you want to allocate resources to resource groups based on what makes the most sensefor your organization. Resources that are going to be placed in the resource group are a virtual network,a virtual machine....

1. In the menu located on the left-hand side of the web page, click Resource groups.

2. Click + Add.

3. For Resource group name, enter a Resource group name.bursting_resource_group

4. For Subscription, select a previously created subscription.

5. For Resource group location, select a location based on the geographical location of users.

6. Click Create.

It may take a moment to create the resource group. All resources (networks, virtual machines,etc.) that are created are placed within this resource group. The name of the resource group isrequired for creating a bursting scenario in PBS Control.

6.4.4 Creating a Virtual NetworkCreate a Virtual Network so that you can perform cloud bursting.

You must have already created an Azure subscription and a resource group.

1. In the menu located on the left-hand side of the web page, click Virtual networks.

2. Click +Add.

3. For Name, enter a Name for the network.bursting_virtual_network

4. For Address space, add an address space for the network using CIDR notation.


6. For Resource group, enable Use existing.

7. Select the Resource group created for cloud bursting.

8. For Location, select the same location as was selected for the Resource Group.

9. For Subnet, enter a name for the Subnet.bursting_subnet

10. For Address range, enter an address range for the subnet in CIDR notation.



11. Click Create.

It may take a moment to create the virtual network. The name of the virtual network is requiredfor creating a bursting scenario in PBS Control.

6.4.5 Creating a Network Security GroupCreate a Network Security Group so that you can perform cloud bursting.

You must have already created an Azure subscription and a resource group.

1. In the menu located on the left-hand side of the web page, click Resource groups.

2. Select the Resource Group that you created for cloud bursting by clicking on its name.

3. Click +Add.

4. In the search box, enter network security group.

5. Select the Network security group search result.

6. Click Create.

7. For Name, enter a Name for the network security group.bursting_network_security_group


9. For Resource group, enable Use existing.

10. Select the Resource group created for cloud bursting.


12. Click Create.

It may take a moment for the network security group to deploy.

13. Once the network security group is deployed a message is displayed indicating success, click onGo to resource.

14. Click Inbound security rules.

15. Click Add.

16. For Source, choose Any.

17. For Source port ranges, enter *

18. For Destination, choose Any.

19. For Destination port ranges, enter 22.

20. For Protocol, click TCP.

21. Click OK.

It may take a moment for the security rule to be created.



6.4.6 Creating a Virtual MachineCreate a CentOS 7.3 virtual machine in Azure.

You must have already created an Azure subscription and a resource group. You may want to view thefollowing web page to learn about Azure Managed Disks before creating a VM. Additionally, a video isavailable from Microsoft that shows how to create a virtual machine: Create a Linux Virtual Machine.

1. In the menu located on the left-hand side of the web page, click Virtual Machines.

2. Click Add.

3. In the search bar, enter CentOS-based 7.3 and press ENTER.

4. Select CentOS-based 7.3 option from the search results list.

5. Click Create.

6. For Name, enter a name for the virtual machine.bursting-vm

7. For VM disk type, choose one of the following options:

• SSD (Solid State Drive)

• HDD (Hard Disk Drive)

Choose SSD for I/O-intensive applications, where low latency and high throughput are critical. Fortesting, consider HDD to keep costs down, as you scale up and down quickly.

8. For User name, enter pbsadmin.

9. For Authentication type, select SSH public key.

10. Provide a secure connection between your PBS Server and the virtual machine by copying the rootSSH public key (i.e., id_rsa.pub) from your PBS Server and pasting it in the SSH public key field.To obtain the public SSH key:





11. For Subscription, select a previously create subscription.

12. For Resource Group, enable Use Existing.

13. Select the Resource group created for cloud bursting


15. Click OK.

16. Select a VM size appropriate for your site's workload based on:

• the number of cores

• the amount of RAM

• disk drive size

• price


https://docs.microsoft.com/en-us/azure/virtual-machines/windows/managed-disks-overview

https://azure.microsoft.com/en-us/resources/videos/create-linux-virtual-machine/


Azure provides recommendations based on popular VM sizes, however you may view all availableVM's by clicking View all.

17. Click Select.18. For Storage, choose whether you want to use managed disks by selecting:

• Yes to use managed disks.

• No to not use managed disks.

Enable this feature to have Azure automatically manage the availability of disks to provide dataredundancy and fault tolerance, without creating and managing storage accounts on your own.This option is recommended by Azure as it is a lot more scalable.

19. Accept defaults for the rest of the optional features.

20. Select OK.A summary of your VM is displayed.

21. Click Create.

It may take a few minutes for the VM to be created. You will use this virtual machine to create anOS image.

Once the VM is created, a new web page is displayed where the VM can be managed.






5. Save the file.



8. Save the file.



6.4.8 Creating an OS ImageCreate an image of the virtual machine configured per your site's requirements.

You must have already created an Azure subscription and a resource group. You will also need todownload and install the Azure CLI.



Before you can create an OS image of the previously created VM, you must first SSH into the VM anddeprovision it. Next you will use the Azure CLI to deallocate the VM, generalize the VM and then createthe image. Generalizing the virtual machine removes any SSH keys and DNS settings from the it.

Follow Step 1 and Step 2 as documented at the URL How to create an image of a virtual machine orVHD to create an image of the VM.

Note: Before you can deallocate the virtual machine you may have to execute the followingcommands to set your subscription to be the active subscription.az account listaz account set --subscription yourSubscriptionID

An OS image is created of the virtual machine.

You can now delete the VM so that you are no longer charged for it.


Open a browser window and login to your Microsoft Azure account and navigate to the AzureDashboard. Open a second browser window and login to PBS Control.


Note: To create a bursting scenario you must enter a Resource Group, however theresources necessary for creating the bursting scenario (network, subnet, network securitygroup and the OS image) can all reside in a different Resource Group. However, theResource Groups must be in the same location for this to work.

1. Navigate to the PBS Control browser window

2. Click Design.



5. For Name, enter a name for the cloud bursting scenario.



8. For Cloud Account, choose a registered Azure account from the list.

9. Select a region from the list that matches the location selected for the Resource Group.

10. Click Next.11. Navigate to the Azure browser window.

12. In the menu located on the left-hand side of the web page, click Resource Groups.

13. Copy the name of the resource group created for cloud bursting.



https://docs.microsoft.com/en-us/azure/virtual-machines/linux/capture-image

https://docs.microsoft.com/en-us/azure/virtual-machines/linux/capture-image


15. For Resource group name, paste the resource group copied from Azure.

16. Navigate to the Azure browser window.

17. In the menu located on the left-hand side of the web page, click Virtual Networks.

18. Copy the name of the virtual network created for cloud bursting.


20. For Network name, paste the virtual network copied from Azure.

If the network is contained in a Resource group that is different from the one entered for thebursting scenario, it must be entered as Resource Group Name/Virtual Network Name.


22. Select the virtual network created for cloud bursting.

23. In the menu located to the left of the virtual network details, click Subnets.

24. Copy the name of the subnet created for cloud bursting virtual network.


26. For Subnet name, paste the Subnet copied from Azure.

If the subnet is contained in a Resource group that is different from the one entered for thebursting scenario, it must be entered as Resource Group Name/Subnet Name.



29. Select the Resource Group created for cloud bursting.

30. In the list, locate the Network Security group created for cloud bursting.

The Type is Network Security group.

31. Copy the name of the network security group.


33. For Network security group name, paste the network security group copied from Azure.

If the network security group is contained in a Resource group that is different from the oneentered for the bursting scenario, it must be entered as Resource Group Name/NetworkSecurity Group Name.

34. Choose one of the following options based on whether you chose to use the Azure managed diskfeature when creating the virtual machine:

• Enable Managed Storage if you enabled the managed disk feature.

• Disable Managed Storage if you disabled the managed disk feature.



37. Select the Resource Group created for cloud bursting.

38. In the list, locate the image that was created for cloud bursting.

The Type is Image.

39. Select the image.

40. Choose one of the following options:

• If you chose to use managed disks when you created the VM, copy the name of the image.



• If you did not choose to use managed disks when you created the VM, copy the Linux SourceBLOB URI.


42. For OS image URI, paste the information copied from Azure.

If the OS image is contained in a Resource group that is different from the one entered for thebursting scenario, it must be entered as Resource Group Name/OS Image Name or ResourceGroup Name/URI.




45. Enter a prefix for the names of the bursted nodes.If "node" is entered for the Hostname prefix, the cloud bursting nodes will be available to PBSProfessional as node1, node2, node3, etc.

46. For the Initialization script, enter the script that will run after a cloud node is bursted.The below script initializes the bursted node for PBS Professional use and should be modified peryour site's needs.

#!/bin/sh











# Restart pbs to ensure that it is using the latest configurationln -s /pbsworks/pbs/exec/14.2.3 /opt/pbssystemctl restart pbs































Once the cloud bursting scenario is created, there is additional configuration that needs to occur forPBS Professional. See the chapter Cloud Bursting with PBS in the PBS Professional 14.2.6 Release Notesattached to the Confluence page https://confluence.prog.altair.com/display/PPC/Released+End-user+PBS+Documentation.





6.5 Configuring Google Cloud Platform CloudBurstingCreate the necessary components in GCP that are required for cloud bursting and then create a PBSControl cloud bursting scenario.

6.5.1 Creating a GCP Service AccountCreate a Google Cloud Platform service account so that your can register it in PBS Control.

You must already have signed up for an GCP account.

A service account is a special Google account that belongs to an application or a virtual machine,instead of to an individual end user.

1. Login in to your GCP account.

2. Click located in the upper left-hand corner of the web page.

3. Click IAM & admin > Service accounts.

4. Click CREATE SERVICE ACCOUNT.

5. For the Service account name, enter a name for the service account.

6. For the Role, click Select a role > Compute Engine > Compute Admin.

7. Click on the Create serve account dialog box to save the role and continue.

8. Enable Furnish a new private key.

9. For Key type, enable JSON.

10. Click CREATE.The service account is created and a JSON file is downloaded.

11. Save the JSON file in a secure location.

The information in this file is used later to add a cloud account to PBS Control.

6.5.2 Registering a GCP Service AccountAdd an existing GCP service account to PBS Control.

You must have created a GCP service account and given it administrative permissions.




4. Click Add Cloud Account.5. Open the JSON file that was created in the previous step during the creation of the GCP service

account.

6. In the dialog box, select the following:



a) For Provider, select Google Cloud Platform.

b) For Account name, enter a name you wish to use.

c) For Project ID, copy and paste the project_id value from the JSON file.

d) For Client ID, copy and paste the client_id value from the JSON file.

e) For Client Mail, copy and paste the client_email value from the JSON file.

f) For Private Key ID, copy and paste the private_key_id value from the JSON file.

g) For Private Key, copy and paste the private_key value from the JSON file.

Note: Do not copy the '\n' characters at the end of the private_key value.

7. Click Create account.

6.5.3 Creating a Virtual Private Cloud NetworkCreate a Virtual Private Network (VPC) in GCP so that you can perform cloud bursting.

Login to your GCP account.


2. Click VPC network > VPC networks.

3. Click CREATE VPC NETWORK.

4. For Name, enter a name for the network.

5. In the Subnets section, click the Custom tab under Subnet creation mode.

6. For Name, enter a name for the subnet.

7. For Region, select a Region based on the geographical location of users.

Note: Subnet and Network have to be in the same region.

8. For IP address range, enter an IP address range using CIDR notationOnce an IP address range is entered, an Add subnet button appears.

9. For Private Google access, enable Off.10. Click Add subnet.

A form for entering another subnet is displayed.

11. Click just above the subnet Name field to close the subnet form.

12. For Dynamic routing mode, enable Regional.13. Click Create.

Creating the VPC network may take some time.



6.5.4 Creating a Virtual MachineCreate a CentOS 7.3 virtual Machine in GCP.

Login to your GCP account.


2. Click Compute Engine > VM instances.

3. Click CREATE INSTANCE.

4. For Name, enter a name for the virtual machine.

5. For Zone, select a zone that is in the same Region as the subnet of the VPC network created in theprevious step..

6. In the Machine type section, click the Customize link.

7. Specify the CPUs, GPUs and RAM.

8. In the Boot disk section click Change.

9. Choose CentOS 7.

10. For Boot disk type, choose one of the following options:

• Standard persistent disk

• SSD persistent disk

Choose SSD for I/O-intensive applications, where low latency and high throughput are critical. Fortesting, consider Standard persistent disk to keep costs down.

11. For Size, specify the size of the boot disk.

12. Click Select.13. Under the Identity and API access section, for Service Account, select No service account.14. For Firewall, choose Allow HTTP traffic.

15. Click Management, disks, networking, SSH Keys.

16. Under Firewall, click the Networking tab.

17. Click Add network interface.

18. Choose the VPC Network you created in a previous step.

19. Click Done.

20. Delete any default Network interfaces that might exist.

21. Under Firewall, click the SSH Keys tab.

22. Provide a secure connection between your PBS Server and the virtual machine by copying the rootSSH public key (i.e., id_rsa.pub) from your PBS Server and pasting it in the SSH public key field.

23. Click Create.Creating the virtual machine may take some time.








5. Save the file.



8. Save the file.



6.5.6 Creating an OS ImageAn image file of the Virtual Machine with the PBS MOM and application configured as per your site'srequirements will be deployed on the nodes for cloud bursting.

A virtual machine must have already been created.

1. Click next to the VM instance that was created in the previous step.

2. Click Stop from the Menu.

3. Click Stop.

It may take some time for the VM to be stopped. Do not proceed until the VM is stopped.

4. Click Compute Engine > Images.

5. Click CREATE IMAGEat the top.

6. Enter a name for the image.

7. For Source select Disk.

8. Select the VM you want to create an image from.

9. Click Create.


Open a browser window and login to your GCP account and navigate to the GCP console. Open a secondbrowser window and login to PBS Control.

A cloud bursting scenario defines the specifications for network, storage, location, VM image to enablecloud bursting.





2. Click Design.



5. For Name, enter a name the cloud bursting scenario



8. For Cloud Account, choose a registered GCP account from the list.

9. Select the same Region as the subnet of the VPC network.

10. Click Next.11. Navigate to the GCP browser window.


13. Click VPC network > VPC networks.

14. Click on the name of the VPC network that was created for cloud bursting.VPC network details are displayed.

15. Copy the name of the VPC network.


17. For Network name, paste the name of the VPC network copied from GCP.

18. Navigate to the GCP browser window.

19. Copy the name of the VPC network subnet.


21. For Subnetwork name, paste the name of the VPC network subnet copied from GCP.



23. Navigate to the GCP browser window.


25. Click Compute Engine > Images.

26. Select the image created for cloud bursting.

27. Click Equivalent REST28. Copy the value for the entry called selfLink.


30. For OS Image URI, paste the URI copied from GCP.


32. Enter a prefix for the names of the bursted nodes.

If "node" is entered for the Hostname prefix, the cloud bursting nodes will be available to PBSProfessional as node1, node2, node3, etc.

33. For the Initialization script, enter the script that will run after a cloud node is bursted.



The below script initializes the bursted node for PBS Professional use and should be modified peryour site's needs.

#!/bin/sh









# Restart pbs to ensure that it is using the latest configuration



ln -s /pbsworks/pbs/exec/14.2.3 /opt/pbssystemctl restart pbs





























Once the cloud bursting scenario is created, there is additional configuration that needs to occur forPBS Professional. See the chapter Cloud Bursting with PBS in the PBS Professional 14.2.6 Release Notes



attached to the Confluence page https://confluence.prog.altair.com/display/PPC/Released+End-user+PBS+Documentation.




IndexAALTAIR_LICENSE_PATH 24, 35authentication

multi-factorDUO 63enable 63

Service Principal NameKerberos 61register 61verify 62

Single Sign-Ondisable 62enable 60Kerberos 60NT LAN Manager 60NTLM 60Service Principal Name 60SPN 60

CCarriots Analytics™ 25, 38configure 33, 46conventions

PC_EXEC 5PC_HOME 5

Ddeployment 15, 16, 18, 20Docker 28, 41DUO 63

Eexecution host 24, 35

HHyperWorks 7, 18, 20

Iinstallation

advanced 36, 46analytics 25, 38configure 33, 46

110

dual machine 20express 33HyperStudy 24, 35HyperWorks 18, 20, 24, 35installers 18MongoDB 18, 20, 25, 38monitor 33, 46PAS Commands 24, 35PBSA 25, 38PBS Analytics 18, 20, 25, 38PBS Application Services 18, 20, 24, 35PBSCloud 18, 20, 28, 41PBS Commands 41PBS Control 18, 20, 33, 46PBS Professional 18, 20, 24, 35simulator 33, 46simulator application definitions 33, 36simulator solver 33, 36single machine 18web application 33, 46

KKerberos 60, 61

Llogin access

default 15granting 59

logsPBSCloud 79, 79

MMongoDB 18, 20, 25, 25, 33, 38, 38, 46monitor 33, 46

NNT LAN Manager 60NTLM 60

Pparameter sweep 24, 35PAS , See PBS Application ServicesPAS Commands 24, 35, 41PBS Analytics 7, 18, 20, 25, 25, 38, 38, 51

111

PBS Application Services 7, 18, 20, 24, 24, 35, 35PBSCloud 7, 18, 20, 28, 33, 41, 46, 52PBS Professional 7, 18, 20, 24, 24, 35, 35, 41PC_EXEC 5, 33, 36, 46PC_HOME 5, 33, 36, 46pocker

version 78ports 9

SService Principal Name 60, 61, 62services

analytics 16configure 16MongoDB 16monitor 16PBS Analytics 54PBSCloud 16PBS Control 54restart

PBS Control 55simulator 16start

PBSCloud 57, 78PBS Control 55

statusPBS Control 55

stopPBSCloud 57, 78PBS Control 55

web application 16Service User 15, 25, 33, 36, 38, 46, 59simulator 25, 33, 36, 38, 46simulator application definitions 33, 36simulator solver 33, 36SPN 60, 61, 62SSO 60, 61, 62supported

browsers 7operating systems 7products

HyperWorks 7PBS Analytics 7PBS Application Services 7PBSCloud 7PBS Professional 7

112

Uuninstall

PBS Analytics 51PBSCloud 52PBS Control 50

Wweb application 33, 46

113

Documents

PBS Control Administrator’s Guide · FluxMotor® 2018 ©2017-2018; WinProp v.2018 ©2000-2018.2018. Additional Altair Products: Multiscale Designer™ ©2011-2017 ESAComp™ v.4.7