Omega 2017.

1 Quick Start Guide - Omega Linux

Installation

Document Version Control

Classification Schlumberger Private - Customer Use
Release 2017.1
Date 07 Aug 2017
Source QsgOmegaLinuxShell
Copyright © 2017 Schlumberger. All rights reserved.
This document is copyright protected. No part of this document may be reproduced, stored in a retrieval system,
or transcribed in any form or by any means, electronic or mechanical, including photocopying and recording,
without the permission of Schlumberger. Further, the document contains information proprietary to Schlumberger
and should not be disclosed or distributed to third parties without the permission of Schlumberger. To the extent
that documents are provided in electronic format, Schlumberger grants permission for the document to be stored
electronically. All other restrictions set forth above regarding the document's use or distribution shall apply.

Schlumberger Trademarks & Service Marks

Schlumberger, the Schlumberger logotype, and other words or symbols used to identify the products and services
described herein are either trademarks, trade names, or service marks of Schlumberger and its licensors, or are the
property of their respective owners. These marks may not be copied, imitated or used, in whole or in part, without
the express prior written permission of Schlumberger. In addition, covers, page headers, custom graphics, icons,
and other design elements may be service marks, trademarks, and/or trade dress of Schlumberger, and may not be
copied, imitated, or used, in whole or in part, without the express prior written permission of Schlumberger.

Other company, product, and service names are the properties of their respective owners.

An asterisk (*) is used throughout this document to designate a mark of Schlumberger.

 Table of Contents
Note............................................................................................................................................................................1

1 Omega license installation....................................................................................................................................2

2 Oracle Installation.................................................................................................................................................3
2.1 System check...........................................................................................................................................3
2.2 Known issues with Oracle on RHEL 7.2................................................................................................4
2.3 Copy, untar installation files and install Oracle......................................................................................4
2.4 Post Oracle installation check.................................................................................................................5
2.5 Create OPM instance..............................................................................................................................6
2.6 Create InVA instance..............................................................................................................................6
2.7 Create OCM instance (optional).............................................................................................................6
2.8 Create WHSM instance (optional)..........................................................................................................7

3 Prepare to install Omega......................................................................................................................................8

3.1 System check...........................................................................................................................................8
3.2 Set up alias ulog for omadmin to log Omega system changes (optional)...............................................8
3.3 Sample ulog format.................................................................................................................................9

4 Install Omega 2017.1ext......................................................................................................................................10

4.1 Copy and untar installation files...........................................................................................................10
4.2 Customize and run ConfigSiteOmcar script.........................................................................................10
4.3 Install Omega........................................................................................................................................12
4.4 Check installations and update configurations......................................................................................12
4.5 Run Setup and CheckInstall to check 2017.1ext installations..............................................................14

5 Start Omega services...........................................................................................................................................15

5.1 Run Setup and start services.................................................................................................................15
5.2 Check Oracle/OPM server status..........................................................................................................15
5.3 Start omegacorba and omegawsn services............................................................................................16
5.4 Start omegaopm_2017.1extp service....................................................................................................17
5.5 Create RDM schema and start omegardm_2017.1ext####p service on xxos001 (Oracle and OPM
server)..........................................................................................................................................................17
5.6 Start InVa, Mass and Jobq services......................................................................................................18
5.7 Start other services on different hosts...................................................................................................19

6 Configure RDM...................................................................................................................................................21
6.1 Prepare file servers................................................................................................................................21
6.2 Start rdmadmin GUI..............................................................................................................................21
6.3 Config Site and Add Node Groups.......................................................................................................22
6.4 Config File System Groups and Add File Systems...............................................................................23

i
 Table of Contents
6 Configure RDM
6.5 Config file system pools.......................................................................................................................25
6.6 Config RDM quota used space updater................................................................................................25
6.7 RDM Pool Reservation Check (optional).............................................................................................28

7 Install 2017.1ext patches.....................................................................................................................................29

8 Push Out Updates to the Cluster.......................................................................................................................30

8.1 Change \"auto-setup status\" to \"on\" in /wg/omega/setup/Configuration.xml...................................30
8.2 Setup rsync on xxoc001 and push out updates to EWS nodes with local /wg (optional).....................30
8.3 Run Setup on all hosts...........................................................................................................................31

9 Omega Acceptance Tests....................................................................................................................................32

9.1 create test group and user......................................................................................................................32
9.2 Create directories for test project zz98.................................................................................................32
9.3 Start Omega and create project zz98.....................................................................................................32
9.4 Assign quota to project zz98 in RDMADMIN.....................................................................................34
9.5 Import test data to zz98 in Omega and test...........................................................................................34
Glossary......................................................................................................................................................35
Omega terminology..............................................................................................................................35
Omega services.....................................................................................................................................36
Table: Important Omega Configuration Entries...................................................................................37

ii
Note
• This quick-start covers full Omega installation on Linux side. For a transition installation, please refer to
the 2017.1ext Transition Guide, also available on the 2017.1ext DVD and the external client support
portal.

• Please follow the 2017.1ext-System-Preparation-Quick-Start to prepare hosts and system side first.

• This Quick-Start will set up Omega licenses, install Oracle 11.2, Omega 2017.1ext on Linux side,
configure RDM, start all services and perform the acceptance tests.

• Please follow 2017.1ext-Omega-Windows-Installation-Quick-Start to install Omega on Windows side.

• Please follow OCM2.5-Installation-Quick-Start to install OCM.

• Please follow the MMS and WHSM guides if your site plan to use tape and WHSM with Omega.

• This quick-start is an illustration only. It does not cover all options and may not apply to all different
sites. Please adjust to your own needs and refer to the 2017.1ext Omega2 Admin Guide for options.

• The server configuration in this sample is for a mid-size site (compute nodes 50 to 500). Small site (total
compute nodes less than 50) can combine several roles of different hosts in this quick-start into one or
two hosts. And large site (compute nodes more than 500) may split some roles or services in this guide to
extra hosts. Please refer to the 2017.1ext Omega2 Admin Guide to learn all options.

• Omega system is a complex system that involves multiple hosts that communicate closely with each
other. Please try to follow Schlumberger recommendations as much as possible, to ease future support
and maintenance complexity. Please consult Schlumberger on the optimal host configuration and
hardware requirements as earlier as possible.

• Some brief explanations of Omega Configuration.omcdb entries and crons are attached at the end of this
document.

Schlumberger Private - Customer Use 1

1 Omega license installation
As mentioned in the system preparation quick start, we can use any less burdened server that has USB port as a
license server for a small to mid-size center. Here assume we will use the OCM server as license server.

Please note we do not recommend sharing the same license server for Omega 2017.1 and Petrel 2017.1. Here we
will focus on the Omega license server.

You should get a license dongle and license file from Schlumberger sales contacts.

Plug in the dongle to the license server.

# as root on the server

# assume we copied the DVD OmegaAndOCM to /wg/omega/installations
# assume OS on this server is RHEL 6.4
cd /wg/omega/installations/01-OmegaLinux/03-Miscellaneous/RPMs
./installLicenseServerRPMs.csh

# copy new 2017.1ext license file to /opt/licensing/flexlm/licenses/

# rename the license file to include expiration date
cp /path/to/licenseFile /opt/licensing/flexlm/licenses/omega2017.1ext_yyyy_mmdd.lic

# check the services are turned in chkconfig

chkconfig --list | grep -iE 'flex|code'

# start flexlm service on the license server

service flexlm restart
less /var/log/flexlm/flexlm
# inside the log, you will see tcp port 27000 is used

Note: when restarting license services, always use command service flexlm restart , instead of service flexlm
stop;service flexlm start . The restart will wait for 70 seconds for tcp port to free up. After license restarted,
always check /var/log/flexlm/flexlm and make sure it listens on default port 27000.

Schlumberger Private - Customer Use 2

2 Oracle Installation
2.1 System check
Please limit the number of alias names for the Oracle server. The immediate name that follows the oracle server
IP will be used in Oracle configuration.

Try to use long name for Oracle. This name needs to be ping-able by all hosts (both Linux and Windows side;
both public and private network).

Check hostname and hostname -f . Command hostname -f should give us the full host name. If not, add
the preferred IP and long host name in /etc/hosts.

Also be careful if we have duo IPs for the Oracle host. The public IP should be used by Oracle service.

If we have public and private network and dual network ports on the Oracle/Corba server, we can force Corba to
register with the primary (public) IP address. And in such case, all private nodes need to be able to ping the public
IP address of the Corba host.

To force Corba to register with public IP address (only needed if Corba server has both public and private IP):

# on Corba server xxos001

su - root
vi /etc/omniORB.cfg
# add this line, use the correct public IP of the Corba host in place of xxx.xxx.xxx.xxx
# pay attend to the : at the end of the line!
endPoint = giop:tcp:xxx.xxx.xxx.xxx:

It s best to have oracle account local. Check oracle account and home directory as instructed in step 2.1 of
2017.1ext-System-Preparation-Quick-Start. Make sure root has write permission to ~oracle home directory.

Check /oracle, /oracle_data, /oracle_data/archive exist. Make sure we have enough space for each. Partition
/oracle_data/archive should be on a different disk/partition than /oracle. These directories are owned by
oracle:dba.

Schlumberger Private - Customer Use 3

2.1 System check

Check oracle account file descriptor setting in /etc/security/limits.conf in step 3.6 of

2017.1ext-System-Preparation-Quick-Start.

The 2017 DVD sets include both oracle SE and EE versions. Please install the SE version. The Oracle Standard
Edition license fee is included in the Omega package.

2.2 Known issues with Oracle on RHEL 7.2

On RHELS 7.2 system, when Oracle user logs out, all of the IPC resources (such as semaphores and shared
memory) are removed. The issue can be fixed by adding two ways:

Add the 'RemoveIPC=no' to /etc/system/logind.conf:

# as root on the RHELS 7.2 oracle server

cat /etc/systemd/logind.conf | grep -vE '#|^$'
[Login]
RemoveIPC=no

Or upgrade sytemd RPM to version systemd-219-19.el7.x86_64.

RHEL/CentOS 7.x sets a limit of max number of user processes in /etc/security/limits.d/20-nproc.conf. This limit
be default is set to 4096 which is not enough for running Omega services without interruptions. To fix the issue,
either delete /etc/security/limits.d/20-nproc.conf or comment out the two nproc lines. Then stop and re-start all
processes belonging to the OPM user.

# as root on the RHELS 7.2 oracle server

vi /etc/security/limits.d/20-nproc.conf
# comment out the two nproc lines
#* soft nproc 4096
#root soft nproc unlimited

2.3 Copy, untar installation files and install Oracle

Note: there is a bug of gpg on RHEL/CentOS 6.2; the easiest solution is to unset DISPLAY environment variable
before gpg.

Schlumberger Private - Customer Use 4

2.3 Copy, untar installation files and install Oracle

# on xxos001
# assume OracleSE installation kit is copied to /wg/omega/installations/OracleSE
# passphrases are provided by Schlumberger Sales.
# ignore the warning on can t connect to /root/.gnupg/s.gpg-agent :
su - root
# for bsh
unset DISPLAY
# for csh
# unsetenv DISPLAY
echo $DISPLAY
cd /wg/omega/installations/OracleSE
gpg oracle.bin-12.1.0.2.5-SE-64.tgz.gpg
gpg oracle-scripts-5.4-ext.tgz.gpg

# when prompted for Oracle binary kit directory, enter: /wg/omega/installations/OracleSE

cd /oracle
tar xzf /wg/omega/installations/OracleSE/oracle-scripts-5.4-ext.tgz
cd /oracle/scripts
./install-oracle

# in the end we will see The oracle installation was successful

Note: An Oracle schema account opmadmin was created in Oracle by the installation. Default password is
opmadmin! By default all Omega projects use project short name (like zz98) as Oracle account name and
password.

2.4 Post Oracle installation check

The installation program will automatically add some entries to /etc/sysctl.conf to match Oracle requirements.
The following parameters are not set by the Oracle installation program and you will need to verify that they are
set to the specified values (or larger). If the server you are using has an OS that has been installed by
Schlumberger to Schlumberger standards, then these will have been set at OS installation time and these
parameters should already be present:

net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144

Schlumberger Private - Customer Use 5

2.5 Create OPM instance

2.5 Create OPM instance

# on xxos001

su -oracle
cd /oracle/scripts
./create-instance

# choose 1 to create OPM instance

# instance name: xxopm001
# naming standard: xx=sitecode opm = OPM instance 001 goes with oracle server serial number xxos00
# when asked for size of the instance, choose Standard.

2.6 Create InVA instance

# on xxos001

su - oracle
cd /oracle/scripts
./create-instance

# choose 2 to create InVA instance

# instance name: xxin5001
# naming standard: xx=sitecode in5 = InVA 5 instance 001 goes with oracle server serial number xxo
# when asked for size of the instance, choose Standard.

2.7 Create OCM instance (optional)

Assume we will install OCM and we have OCM instance on the same Oracle server.

Skip this if we won t install OCM or OCM instance won t be created on this host.

# on xxos001

su - oracle
cd /oracle/scripts
./create-instance

Schlumberger Private - Customer Use 6

2.7 Create OCM instance (optional)

# choose 5 to create OCM instance

# instance name: xxocm001
# naming standard: xx=sitecode ocm = OCM instance 001 goes with oracle server serial number xxos00
# when asked for size of the instance, choose Standard.

2.8 Create WHSM instance (optional)

Assume we will install WHSM later on and we have WHSM instance on the same Oracle server

Skip this if we won t install WHSM or WHSM instance won t be created on this host

# on xxos001
su - oracle
cd /oracle/scripts
./create-instance

# choose 3 to create WHSM instance

# instance name: xxwhs001
# naming standard: xx=sitecode whs = WHSM instance 001 goes with oracle server serial number xxos0
# when asked for size of the instance, choose Standard.

Note: SLM is for Storage Library Manager. Please consult Schlumberger Sales for assistance on setting up SLM
if your site plans to use it.

Schlumberger Private - Customer Use 7

3 Prepare to install Omega
3.1 System check
Double-check /wg, /wglogs, /local1, /local1/scr, /local1/data, /tmp exist on the Omega installation server xxoc001.
Without /wglogs, Omega won t install. Directory names of /local1 need to be specifically followed as they will
be cleaned up by the /etc/cron.d/omegafsclean cron.

Directory permission for /wglogs, /local1, /local1/scr, /local1/data should be 777.

Refer to 2017.1ext system preparation quick start step 3.2 for partitions and directories. Check file descriptor
setting in /etc/security/limits.conf as specified in step 3.6 of 2017.1ext system preparation quick start.

# as root on the xxoc001

mkdir -p /local1/scr /local1/data; chmod 777 /local1/scr /local1/data
mkdir -p /wgjss/omega2; chmod 777 /wgjss/omega2; chown jssmgr:jssadmin /wgjss/omega2
mkdir -p /wg/omega/installations;chown -R omadmin:omadmin /wg; chmod -R 2755 /wg;

# check file descriptors, refer to system prepation quick start 3.6

tail /etc/security/limits.conf

3.2 Set up alias ulog for omadmin to log Omega system

changes (optional)
Alias ulog is a simple way to log Omega updates.

# on xxoc001
# create ~omadmin/ulog_updates directory
su - omadmin
mkdir ulog_updates
vi .cshrc
# assume omadmin use csh as default, as specified in step 2 of 2017.1ext system preparation quick sta
# add below entries

#!/bin/csh -f

Schlumberger Private - Customer Use 8

3.2 Set up alias ulog for omadmin to log Omega systemchanges (optional)

#---------------------------------------------------------------------------
# ulog aliases
alias ulog 'set a1=`date '+%Y''%m''%d''%H''%M''%S'`;cp -p ~omadmin/ulog_updates/ulog ~omadmin/ulo
alias ulogv 'less ~omadmin/ulog_updates/ulog'

3.3 Sample ulog format

WED 07/1/2016 FirstName LastName
==================================
------------begin-----------
#Installed 2017.1ext Patch 01, per requestNo 0001
..
# install the patch

------------end-------------

Schlumberger Private - Customer Use 9

4 Install Omega 2017.1ext
4.1 Copy and untar installation files
Note: there is a bug of gpg on RHEL/CentOS 6.2. The easiest solution is to unset DISPLAY environment variable
before gpg. Also the 2017.1ext#### Omega kit needs about 20G free space in /wg/omega.

# on xxoc001
# Copy directory 01-OmegaLinux/02-Installation/omega2017.1ext####.tgz.gpg from DVD OmegaAndOCM and
# Copy directory 02-Installation/omegasfm2017.1ext####.tgz.gpg from DVD OmegaSFMs
# to /wg/omega/installations/

# then decrypt the file, passphrase should be provided by Schlumberger

su - omadmin
unsetenv DISPLAY
echo $DISPLAY
cd /wg/omega/installations/
gpg omega2017.1ext####.tgz.gpg
# enter <passphrase> which is provided by Schlumberger Sales
gpg omegasfm2017.1ext####.tgz.gpg
# enter <passphrase> which is provided by Schlumberger Sales
# it may takes about 1 minute to decrypt each file. Ignore the warning on can t connect to /omadmi
cd /wg/omega
tar -xzvpf installations/omega2017.1ext####.tgz
tar -xzvpf installations/omegasfms2017.1ext####.tgz

If you run short of free space in /wg/omega, you can delete the tgz file at this moment

rm -f /wg/omega/installations/omega2017.1ext###.tgz
rm -f /wg/omega/installations/omegasfms2017.1ext####.tgz
rm -f /wg/omega/installations/omega2017.1ext####.tgz.gpg
rm -f /wg/omega/installations/omegasfm2017.1ext####.tgz.gpg

4.2 Customize and run ConfigSiteOmcar script

# backup the original script; as omadmin on xxoc001
su - omadmin

Schlumberger Private - Customer Use 10

4.2 Customize and run ConfigSiteOmcar script

cd /wg/omega/install_64_2017.1ext####
unzip 2017.1ext####_Installer.zip
cd Installer/
cp ConfigSiteOmcar ConfigSiteOmcar.Orig

# original file
[omadmin@xxoc001 install_64_2017.1ext####]# head -22 ConfigSiteOmcar | grep -vE '^#'
set SITE="MYSITE"
set SITECODE="ss"
set FQDN="client.com"
set OPM="ssos001"
set JSS="ssjs001"
set LICENSESERVER="licenseserver.city.region.area.company.com"
set AdministratorMail="omadmin@city.region.area.company.com"
set WHSM_EVENT_DBINSTANCE="SSWHS001"

vi ConfigSiteOmcar

# customize this file and replace the entry with your setting
# OPM entry need to be the oracle server short name, like xxos001
# JSS entry need to be the OCM/Omega installation server, short name, like xxoc001
# WHSM_EVENT_DBINSTANCE can be "NONE" for now;
# we can update the related entries when we set up WHSM
# don t touch the remaining of the file

# run the script, to generate /wg/omega/install_64_2017.1ext####/Installer/Config/Site.omcar

./ConfigSiteOmcar

Note: this ConfigSiteOmcar just updated a few critical entries. We will need to update other Configuration entries
later.

Alternatively you can use GUI to edit Config/Site.omcar file manually, which may take more time.

su - omadmin
cd /wg/omega/install_64_2017.1ext####/Installer/
./ConfigSite &
# open /wg/omega/install_64_2017.1ext####/Installer/Config/Site.omcdb
# please refer to the initial Omega Configuration Entries table attached at the end of this quick s
# change the entries interactively
# save the file and then right click omega and then export to
# /wg/omega/install_64_2017.1ext####/Installer/Config/Site.omcar

Schlumberger Private - Customer Use 11

4.3 Install Omega

4.3 Install Omega

Important: please use omadmin UID on the installation server to install Omega and all patches!

# on xxoc001
su - omadmin
cd /wg/omega/install_64_2017.1ext####/Installer/

./InstallOmega -a -d 2017.1extp#### -o Config/Site.omcar

# -i: provide the installation name. This is a mandatory argument.

# -p: Provide the location to install Omega in double-quotes. This is a mandatory argument
# -a: use default omega name (2017.1ext####) and installation directory (/wg/omega/2017.1ext####)
# -d 2017.1ext####p: set 2017.1ext#### as the default-installation;
# -o Config/Site.omcar: import customized Omega configurations from Config/Site.omcar file
# -h usage helps

4.4 Check installations and update configurations

Review changes in /wg/omega/setup/Configuration.xml

# on the omega installation server xxoc001

su - omadmin
# create a backup of Configuration.xml
cp -p /wg/omega/setup/Configuration.xml /wg/omega/setup/Configuration.xml.2017.1ext.bak
view /wg/omega/setup/Configuration.xml

# check default-installation name and setup-installation name at the top of the file.
# setup-installation name should be 2017.1ext#### and default-installation name should be 2017.1e

# Important: we can change <auto-setup status="on" /> to off at the beginning

# so that other hosts won t be updated automatically by the cron /etc/cron.d/omegasetup.
# and the omegawindowsupdate_problem_check cron on the Windows Update Server (WUS)
# won t keep sending alerts every 10 minutes

# check whsmeventconsumer entry in the file, if we don t have WHSM set up on the site, we can remove
# check webserver entry; usually we use the Omega installation server (OCM server);

# check OPM and RDM server name under the new 2017.1ext####p entry.

Schlumberger Private - Customer Use 12

4.4 Check installations and update configurations

# for sites that have separate Oracle server and OPM server, the InstallOmega script may not pick up
# when everything done, save the file and compare the changes

diff /wg/omega/setup/Configuration.xml /wg/omega/setup/Configuration.xml.2017.1ext.bak

Review and update Omega configurations in /wg/omega/2017.1ext####/share/config/Configuration.omcdb.

The important Configuration entries are listed at the end of this guide.

We will set WHSM related host names to NONE for now. We will also skip the MMS and OCM entries. We
can update the related entries later, when we set up these components.

# on xxoc001
su - omadmin
# make sure we have display here
xterm
cp -p /wg/omega/2017.1ext####/share/config/Configuration.omcdb /wg/omega/2017.1ext####/share/config/C
cd /wg/omega/install_64_2017.1ext####/Installer/
./ConfigSite&

# browse through the directories and open /wg/omega/2017.1ext####/share/config/Configuration.omcdb

# Update entries listed in table "Important Omega Configuration Entries"
# when done, please save and close the database.

Move tnsnames.ora on Oracle host (optional):

# on xxos001 as root
ll /oracle/11.2/network/admin/tnsnames.ora*
mkdir -p /wg/omega/setup/oracle
chown omadmin:omadmin /wg/omega/setup/oracle
cp /oracle/11.2/network/admin/tnsnames.ora /wg/omega/setup/oracle
chown oracle:dba /wg/omega/setup/oracle/tnsnames.ora
mv /oracle/11.2/network/admin/tnsnames.ora /oracle/11.2/network/admin/tnsnames.ora.original
cd /oracle/11.2/network/admin
ln -s /wg/omega/setup/oracle/tnsnames.ora tnsnames.ora
ll tnsnames.ora*

Note: This step is needed for WHSM. If you do not have WHSM, you can ingore this step. If your Oracle server
is not exclusively for Omega and tnsnames.ora cannot be moved, you can copy the file to /wg/omega/setup/oracle.

Schlumberger Private - Customer Use 13

4.5 Run Setup and CheckInstall to check 2017.1ext installations

Copy QCViewer key from DVD OmegaAndOCM on xxoc001:

# as omadmin on xxoc001
mkdir -p /wg/omega/support/licenses/Omega/QCViewer
cp /wg/omega/installations/01-OmegaLinux/03-Miscellaneous/QCViewer/keydbase /wg/omega/support/license

4.5 Run Setup and CheckInstall to check 2017.1ext

installations
Omega 2017.1ext provided a script to check fresh installations. We have to run Setup before using the
CheckInstall script.

su - root
/wg/omega/setup/Setup
omegainst

su - omadmin
cd /wg/omega/install_64_2017.1ext####/Installer/
./CheckInstall 2017.1ext####

# review the errors, add the missing directories and update Omega configurations in
# /wg/omega/2017.1ext/share/config/Configuration.omcdb

Note: Please note this tool is meant for experienced admins. This script does not tell the role of the host. So not all
missing directories are needed on your host, for instance, WGC related entries can be ignored.

Schlumberger Private - Customer Use 14

5 Start Omega services
5.1 Run Setup and start services
# on xxoc001
su - root
/wg/omega/setup/Setup
chkconfig --list | grep omega

# we may have omegalauncher, omegahttpd, omegaupdaterepository and omegawindowsudpate in chkconfig

# we will check and start omegalauncher and omegahttpd status

service omegalauncher status

service omegalauncher restart
service omegahttpd status
service omegahttpd start
service omegahttpd status

Note: omegahttpd is for omega2 web service. Web site is http://xxoc001.dnsdomain.com:8080/ (if we designate
xxoc001 as omega2 web server).

We will work on omegaupdaterepository and omegawindowsupdate services in the Omega Installation on

Windows section.

5.2 Check Oracle/OPM server status

# on xxos001, Oracle server
su - root
/wg/omega/setup/Setup
# first check if oracle is ready
ps -ef | grep smon
# we should see one process for each Oracle instance we created earlier
su - oracle
lsnrctl status
exit
# we should see messages about xxopm001, xxocm001 and xxin5001 ready

Schlumberger Private - Customer Use 15

5.2 Check Oracle/OPM server status

# if no oracle process started

su - root
service oracle start
cat /oracle/11.2/network/admin/tnsnames.ora
cat /oracle/11.2/network/admin/listener.ora
cat /etc/oratab

Note 1: Please note Omega created OPMAdminLogin, RDMAdminLogin, and InVaAdminLogin in /etc/omega/
on the Oracle/OPM host. These three files have Oracle user name and password in them.

Note 2: Please check the host name in the ora files. The host name should be xxos001.dnsdomain.com.

5.3 Start omegacorba and omegawsn services

To start Corba and WSN service:

# on Corba server xxos001

su - root
service omegacorba status
service omegacorba restart
service omegacorba status

# if service down, check omninames.err and omninames-xxos001.oil.log under /wglogs/omega/nameserver;

service omegawsn status

service omegawsn restart
service omegawsn status

# ignore warning "Could Not Load Catalog Cache [/tmp/WSCatalogCache.xxxx.3003.wscache (No such file o

Note: these two services are critical and are needed by all other Omega services. They are independent of
baselines. All baselines share the same two services. No need to restart after installation of each new Omega
baseline.

If omegacorba fails, then omegacorba and all other Omega services need to be restarted. If omegawsn fails,
Omega and Petrel on windows side may have issue talking to Omega.

Schlumberger Private - Customer Use 16

5.4 Start omegaopm_2017.1extp service

5.4 Start omegaopm_2017.1extp service

# on OPM server xxos001
su - root
# first make sure we can talk to Omega license server
omega2017.1ext####p CheckExpirationDates
# or use omega2017.1ext####p lmstat -a to check license status
# second check /etc/omega/OPMAdminLogin file
ls /etc/omega/OPMAdminLogin
# this file is created by Omega
# it contains schema id and password for Oracle xxopm001 database
# it s needed by omegaopm_2017.1ext####p service
# the file should be owned by opm and file permission is 600
cat /etc/omega/OPMAdminLogin
# it should have opmadmin opmadmin!, in two lines

# start service
service omegaopm_2017.1ext####p restart
sleep 5
service omegaopm_2017.1ext####p status
# if service down, check /wglogs/omega/opm/2017.1ext####p for errors

Note: omegaopm_2017.1ext####p is the most important Omega service. If omegaopm_2017.1ext####p is down,

users won t see any projects when they launch Omega.

5.5 Create RDM schema and start omegardm_2017.1ext####p

service on xxos001 (Oracle and OPM server)
# check /etc/omega/RDMAdminLogin file
ls /etc/omega/RDMAdminLogin
# this file is created by Omega
# it contains username and password for Oracle xxopm001 database
# it s needed when we start omegardm_2017.1ext####p service
# the file should be owned by opm and file permission is 600

cat /etc/omega/RDMAdminLogin
# it should have RDMDB RDMDB, in two lines

Schlumberger Private - Customer Use 17

5.5 Create RDM schema and start omegardm_2017.1ext####pservice on xxos001 (Oracle and OPM server)

# create RDM schema

# please note this is only needed for fresh 2017.1ext#### installation
# site that upgrade from 2016.1ext### to 2017.1ext#### does not need to create RDM schema again!

# on OPM server xxos001

su - opm
omega2017.1ext####p createrdmschema
exit

# ignore warning of not finding password file OSMAdminLogin. It s not needed

# this RDM schema will be shared by all projects across all Omega baselines

su - root
service omegardm_2017.1extp restart
service omegardm_2017.1extp status
# if service down, check log at /wglogs/omega/RDM/2017.1extp

# the RDM schema can be recreated using -r option if first creation is incorrect.
# Warning: do not recreate RDM for a working RDM schema!
su - opm
omega2017.1extp createrdmschema -r
exit

5.6 Start InVa, Mass and Jobq services

# on OPM server xxos001
# check /etc/omega/InVaAdminLogin file
ls /etc/omega/InVaAdminLogin

# this file is created by Omega

# it contains username and password for Oracle xxin5001 database
# it s needed when we start omegainva_2017.1ext####p service
# the file should be owned by opm and file permission is 600

cat /etc/omega/InVaAdminLogin
# it should have opmadmin opmadmin!, in two lines

service omegainva_2017.1ext####p restart

service omegainva_2017.1ext####p status
# if service down, check log at /wglogs/omega/inva/2017.1ext####p

Schlumberger Private - Customer Use 18

5.6 Start InVa, Mass and Jobq services

service omegamass_2017.1ext####p restart

service omegamass_2017.1ext####p status
# if service down, check log at /wglogs/omega/mass/2017.1ext####p

# To start omegajobqconsumer_2017.1ext####p the first time, we need to start it with a single thread
su - opm
mkdir /wglogs/omega/jobq
# Note the command below is one long line; \ is a separate symbol
omega2017.1ext####p jobqconsumer -threads 1 -prompt < /etc/omega/OPMAdminLogin \
| & omega2017.1ext####p timelog -f /wglogs/omega/jobq/2017.1ext####p &
ps -ef | grep 2017.1ext#### | grep -i jobq
# verify the service started with 1 thread
exit

service omegajobqconsumer_2017.1ext####p status

# restart jobq service with 4 threads
service omegajobqconsumer_2017.1ext####p restart
service omegajobqconsumer_2017.1ext####p status
# if service down, check log at /wglogs/omega/jobq/2017.1ext####p

5.7 Start other services on different hosts

There are a few other services on the OPM server and OCM server. Please refer to System Preparation Quick
Start 1.4 for the services running on each host.

On OCM server xxoc001, we may have omegalauncher, omegahttpd, omegaupdaterepository and

omegawindowsupdate.

Service omegalauncher is started automatically on all hosts when we run /wg/omega/setup/Setup.

Service omegaupdaterepository and omegawindowsudpate are for Windows Omega Desktop. We will explain
these two in the 2017.1ext Omega Windows Installation Quick Start.

Start these services this way:

# as root on OPM server or OCM server

chkconfig --list | grep omega | grep -v _
service xxxx status

Schlumberger Private - Customer Use 19

5.7 Start other services on different hosts

service xxxx restart

Schlumberger Private - Customer Use 20

6 Configure RDM
6.1 Prepare file servers
Each file server need to have Omega installed and file system share set up.

# as root on each server (NetApp server may be a little different)

# check the directories
ls -ald /wg/omega /wglogs /wgdisk /ud
# run Setup
/wg/omega/setup/Setup
# make sure Omega Launcher service is started
# Omega Launcher is the communication agent between the file server and other Omega hosts
ps -ef | grep Launcher
# check file system path, capacity and available space
df -hl
# check exports to Linux side
cat /etc/exports
# check SAMBA setting for Windows side
# /ud, /inter01, /xx0100, /xx0200 need to be exported to Windows
cat /etc/samba/smb.conf | grep -vE ^#

Note: /wg and /wgjss do not need to be exported to Windows side; and won t be defined in RDM.

6.2 Start rdmadmin GUI

RDM pools small disks into big pools and manages file system access, I/O delegation and project quota.

RDM also manages interactive backend Linux nodes and support directory mapping to Windows computers. This
is a requirement for Omega on Windows deployment.

Account omadmin is used to configure RDM . All host names in RDM are short names. We used the sample hosts
from the 2017.1ext#### System Preparation Quick Start as examples here.

# as omadmin on xxoc001

Schlumberger Private - Customer Use 21

6.2 Start rdmadmin GUI

# make sure we have display here

omega2 rdmadmin&
# omega2 always refer to the default Omega baseline, in this case omega2=omega2017.1extp
# select site xxSITE

6.3 Config Site and Add Node Groups

At upper left, click on site name xxSITE , then we will see site information at the bottom half. Check Host
Domain , enter dnsdomain.com and click Apply . If you don't see the bottom section, resize the lower
section to show the information.

We will create 7 node groups:

• FileServices (group type: data server): xxoc001 (node type: data server; Node enabled); this group
include file I/O proxy role servers;
• CandCServers (group type: data server): xxfs001 (node type: data server; Node enabled); this group
include all cheap and cheerful servers;
• StorNextServers (group type: data server): xxfs00[2-3] (node type: data server; Node enabled); this group
include all StorNext servers;
• NetAppServers (group type: data server): xxna001 (node type: data server; Node enabled); this group
include file NetApp servers;
• LoginServers (group type: login server): consist of xxlg00[1-2] (node type: login server; Node enabled;
Computing enabled); this group includes linux backend login nodes for Windows and interactive
applications
• OCI Masters (group type: compute): consist of xxmm00[1-2] (node type: compute; Node enabled;
Computing enabled); this group include master nodes;
• ComputeA (group type: compute): consist of xxa00[01-50] (node type: compute; Node enabled;
Computing enabled); this group includes compute nodes; if we have more clusters, we can create one
node group for each cluster of compute nodes

To add node to each node group, right click the group name and select Add Node

Schlumberger Private - Customer Use 22

6.4 Config File System Groups and Add File Systems

6.4 Config File System Groups and Add File Systems

Next we will create 3 file system groups (disk capacity numbers are just examples).

• NetAppGroup (group type: Data Server), which has two file systems:

/ud (file system type: shared file system, host node: xxoc001, node group: FileServices, storage capacity: 1000G,
active capacity: 1000G, local path: /ud, export path: /ud)

• CandCGroup (group type: Data Server), which has two file systems:

/wgdisk/xx0100 (file system type: shared file system, host node: xxoc001, node group: FileServices, storage
capacity: 100000G, active capacity: 90000G, local path: /xx0100, export path: /xx0100) /inter01 (file system type:
shared file system, host node: xxoc001, node group: FileServices, storage capacity: 1000G, active capacity:
1000G, local path: /inter01, export path: /inter01)

• StorNextGroup (group type: Data Server), which has one file system:

/wgdisk/xx0200 (file system type: shared file system, host node: xxoc001, node group: FileServices, storage
capacity: 100000G, active capacity: 90000G, local path: /xx0200, export path: /xx0200)

There are three 'Service Type' when we define accessed by nodes:

• Server: the host that will check/create/delete project directories on the file system
• Delegate: the host that will read or write files from the file system; usually we use the file system hosts as
their own \"Delegate\"
• Samba: the host that will export linux file systems to the Windows side; usually we use the system hosts
as their own \"Samba\" host

Next we will define access node group and accessed-by nodes.

• Right click on NetAppGroup and click Define access node groups , choose Remote Disk in Access
Mode column for NetAppServers group; choose NFS for FileServices and LoginServers group; leave
other group Not Used ;

Schlumberger Private - Customer Use 23

6.4 Config File System Groups and Add File Systems

• Next right click on /ud, click Define Accessed-by Nodes , select xxna001 as Samba and xxoc001 as
Server or Delegate ; leave other hosts Not Used
• Right click on CandCGroup and click Define access node groups , choose Remote Disk in Access
Mode column for NetAppServers, StorNextServers, CandCServers, LonginServers, Masters and
ComputeA group; choose NFS for FileServices group;
• Next right click on /wgdisk/xx0100, click Define Accessed-by Nodes , select xxfs001 as Delegate or
Samba and xxoc001 as Server ; leave other hosts Not Used
• Next right click on /inter01, click Define Accessed-by Nodes , select xxfs001 as Delegate or Samba
and xxoc001 as Server ; leave other hosts Not Used
• right click on StorNextGroup and click Define access node groups , choose NFS for Masters and
Remote Disk for NetAppServers, StorNextServers, CandCServers, LonginServers and ComputeA
group;

Please note here we assume the masters have SNFS access to /wgdisk/xx0200

• next right click on /wgdisk/xx0200, click Define Accessed-by Nodes , select xxoc001 as Server , and
xxfs002 and xxfs003 as Delegate or Samba ; leave other hosts Not Used

Note:

• Host Node for each file system does not mean the actual file server that hosts the file system; Host node
here is the host that will run the RDM space usage scan;
• Local path in RDM is not used; Export path is only for Windows machines. Export path value should
match the path that Windows machines see. For instance, if xxfs001:/xx0100 is shared through SAMBA
as \\xxfs001\winshare0100, then export path for xx0100 should be /winshare0100. The SAMBA server
that share the file system to windows need to have Samba role in RDM for this file system in Define
Accessed-by Nodes .
• Usually compute nodes will use Remote Disk to access file systems, instead of NFS, as Remote Disk use
rtf and rtf is faster than NFS to read or write large files. Masters that have SNFS access to the StorNext
file systems need to have NFS access mode. In this case SNFS will be used and it s faster than rtf or
NFS.

Schlumberger Private - Customer Use 24

6.5 Config file system pools

6.5 Config file system pools

Next we will create 2 file system pools.

• Click on Pools tab and right click on File System Pools , select Add File System Pool
• First create StorNextPool , type Bulk Seismic Data pool. Change File System Allocator to
Space / Age Weighted.
• Then right click on StorNextPool -> Add Pool Partition -> select StorNextGroup on the File
System Group field -> select /wgdisk/xx0200 on the File System Name filed-> Allocate 100000G->
check Pool partition enabled -> OK

• Then create CandCPool , type Workstation Data pool. Change File System Allocator to Space /
Age Weighted.
• Then right click on CandCPool -> Add Pool Partition -> select CandCGroup on the File System
Group field -> select /wgdisk/xx0100 on the File System Name filed-> Allocate 1000G-> check Pool
partition enabled -> OK

Note 1: We can have multiple pools with same data type, say Bulk Seismic Data . But each project can only be
assigned quota to one pool of each type.

Note 2: It's recommended that one file system partition only be assigned to one pool. Otherwise the RDM disk
space scan script will report the total disk usage of the same file system partition to multiple pools and make disk
space usage numbers inaccurate.

Note 3: It will be difficult to manage if one project has quota on several pools of different types. So it s best to
create one big pool for all projects.

Later in acceptance test section, we will create a project first and then assign quota in rdmadmin GUI.

6.6 Config RDM quota used space updater

When a user submits jobs, Omega will check with RDM if the project has enough space in the assigned pool. And
when omega jobs output files to assigned file system pool, Omega will check with RDM again if the assigned

Schlumberger Private - Customer Use 25

6.6 Config RDM quota used space updater

RDM quota is full or not.

All Omega data input and output sizes are recorded into OPM database. But the OPM space usage numbers may
not be accurate when user copy data outside Omega or when OPM did not register the files correctly.

To get usage numbers, Omega relies on three scripts to update project space usage, the first two scanning each file
system on project space usage, and the third updating RDM on the most recent usage number. All three scripts are
set up in cron.

• startDiskScan

The startDiskScan script needs to run on 'host' role hosts that are defined in RDM for each file system. Usually we
config just one 'host' role in RDM for all file systems.

This script uses 'du' to scan space usage on cheap and cheerful file servers.

This script is included in the Omega build.

The script needs to run as omadmin.

This script requires a subdirectory rdm in each project directory. This rdm directory needs to be owned by
omamdin.

Scanning result will be written to rdm/filesystem.info on each file system.

• StartSNDiskScan script

This script works on StorNext file servers only and pass scan results to startDiskScan.

The reason we need a separate script for StorNext servers is this script will run faster on StorNext metadata server
than the startDiskScan script.

The script name is StartSNDiskScan.csh. The script is under /Omega2_Miscellaneous_Files.

Schlumberger Private - Customer Use 26

6.6 Config RDM quota used space updater

This script will write a file .skipOmegaDiskScan under each project directory on the StorNext disks. This
.skipOmegaDiskScan has the usage number of each project group.

This script needs to run on all StorNext mdetadata servers.

As the StartSNDiskScan only check group usage, files need to be orginized by group. Each group has a directory
and all files in the directory need to be owned by the same group. Otherwise this scrip is not able to get accurate
numbers.

This script needs to run and finish before startDiskScan runs.

The startDiskScan will use the number in .skipOmegaDiskScan instead of running 'du' on the StorNext disks
again.

• rdmdbusedspaceupdater script

This script will go to each project directory on all file system disks and get the space usage numbers.

These numbers are then updated in the RDM project space usage tables.

This script is included in the Omega build.

This script needs to be run as omadmin on only one server (usally the xxoc001).

• Configuration samples of StorNext servers xxfs00[2-3]

# copy the StartSNDiskScan.csh script from DVD to /usr/local/bin on each StorNext metadata ser
# then add following entry in crontab
[root@xxfs002 ~]# crontab -l
00 1,3,5,7,9,11,13,15,17,19,21,23 * * * /usr/local/bin/StartSNDiskScan.csh 1>/dev/null 2>/dev/

• Configuration samples of startDiskScan and rdmdbusedspaceupdater on xxoc001

su - root
mkdir /wgdisk/xx0100/rdm /wgdisk/xx0200/rdm
chown omadmin:omadmin /wgdisk/xx0100/rdm /wgdisk/xx0200/rdm

Schlumberger Private - Customer Use 27

6.7 RDM Pool Reservation Check (optional)

chmod 755 /wgdisk/xx0100/rdm /wgdisk/xx0200/rdm

ls -ald /wgdisk/xx0100/rdm /wgdisk/xx0200/rdm

su - omadmin
crontab -e
# add these two lines
30 1,3,5,7,9,11,13,15,17,19,21,23 * * * omega2017.1ext####p startDiskScan 1>/dev/null 2>/dev/n
30 0,2,4,6,8,10,12,14,16,18,20,22 * * * omega2017.1ext####p rdmdbusedspaceupdater -v -n -t 100

6.7 RDM Pool Reservation Check (optional)

The Pool Reservation Check is a program to fix problems with the RDM Project Quota Reserved and Reserved
Submit totals. The Reserved Submit value is the estimated space required to run all the jobs on the OCM queues.
It sometimes became inaccurate due to premature job cancellations or failure during job submission.

Run the poolreservationcheck script as an opm UID crontab on the RDM server. The crontab entry below is a
long line without line-break.

# on xxoc001
su - opm
crontab -e
# please repalce xxSite with your site name here
43 12 * * * omega2017.1extp poolreservationcheck -old -days 20 -site xxSite -pool StorNextPool -updat
# we need one line for each pool we created above

Schlumberger Private - Customer Use 28

7 Install 2017.1ext patches
Download all the services packs and patches from Schlumberger support portal http://support.software.slb.com.
Schlumberger employees can login with LDAP user name and password. Clients need to register and then log in.

From the home page, go to Product -> Foundation-> Omega -> Software Download-> Patches. You will be
redirected to https://www.sdc.oilfeild.slb.com. From here, click on Seismic & Electromagnetics on the top left,
then click on Omega -> Patches and Applications on the top middle. You should see 2017.1 patches at the bottom
of the page. Download all the 2017 patches.

Install lower patches first. Each patch has a readme file when unzipped. Follow instructions in the readme to
install. Install the patches on xxoc001 as omadmin.

Note: The warning DeprecationWarning: os.popen3 is deprecated during installation on RHEL6x system can
be ignored. The patches should be installed correctly.

Schlumberger Private - Customer Use 29

8 Push Out Updates to the Cluster
8.1 Change \"auto-setup status\" to \"on\" in
/wg/omega/setup/Configuration.xml
Edit file /wg/omega/setup/Configuration.xml on the OCM server and change <auto-setup status=\"off\" /> to
<auto-setup status=\"on\" />. This will trigger all Omega hosts to be updated with most recent Omega baseline.

# on OCM host
su - omadmin
vi /wg/omega/setup/Configuration.xml

cat /etc/cron.d/omegasetup | grep -v "#"

# you will see the cron will run Setup every 20 minutes when /wg/omega/setup/Configuration.xml file i

8.2 Setup rsync on xxoc001 and push out updates to EWS

nodes with local /wg (optional)
This step is optional. We only need to set up rsync if we have Omega nodes with local /wg partition. Such nodes
are only needed when a large site has many users on the login nodes, or the network connection between each
Omega nodes and the /wg file system is slow.

# install rsync on xxoc001

su - omadmin
ls /wg/omega/installations/wg/omega/installations/01-OmegaLinux/03-Miscellaneous/RsyncPush
cd /wg/omega/support
tar xvpf /wg/omega/installations/01-OmegaLinux/03-Miscellaneous/RsyncPush/rsync.tgz
ls rsync
cd rsync/configs
cp -p mail_list-example mail_list
cp -p push_machine_list-example push_machine_list
cp -p push_throttle-example push_throttle
vi mail_list
# update omega admin email here
vi push_machine_list

Schlumberger Private - Customer Use 30

8.2 Setup rsync on xxoc001 and push out updates to EWSnodes with local /wg (optional)

# add xxlg001 and xxlg002, assume xxlg001 and xxlg002 have local /wg

cd ..
cp -p scripts/rsync_push_example scripts/rsync_push
cp -p scripts/rsync_push_child_example scripts/rsync_push_child

mkdir status logs

# by default 2017.1ext is included in configs/push_include file

# push updates down to the Linux nodes.
su - omadmin
/wg/omega/support/scripts/rsync/rsync_push &
watch ls /wg/omega/support/scripts/rsync/status

8.3 Run Setup on all hosts

All Omega hosts need to run /wg/omega/setup/Setup. If you have an xcat server, push /wg/omega/setup/Setup to
run on all hosts.

To check each host:

# as root on each Omega host

omegainst
# you should see 2017.1ext####p
ls -ald /wglogs /local1/scr /local1/data /tmp /wg/omega/2017.1ext /wgjss /ud /wgdisk
# these are the directories each host needs to have
# if you are miss any of the directories, refer to the 2017.1ext System Preparation Quick Start.
ps -ef | grep Launcher
# you should see Omega Launcher process running

Schlumberger Private - Customer Use 31

9 Omega Acceptance Tests
9.1 create test group and user
# zz98 is the project name for acceptance test
# group zz98 must be created in NIS before project zz98 is created

# on the NIS master as root, assume we will use GID 150001 to 159999 for Omega projects
cd /var/yp
groupadd -g 12212298 zz98

# create a test account-omuser1;

# omuser1 needs to be a member of zz98 to access project zz98 directories
# please use csh for all users

useradd -u 50001 -s /bin/csh -d /NFSMNTS/home/omuser1 -g zz98 omuser1

id omuser1
# push out updates to NIS clients
make

9.2 Create directories for test project zz98

# zz98 is the project name for acceptance test
# /ud/zz98 is the place to save project setups files
# assume we will use /wgdisk/xx0200/ to save bulk seismic data
# these directories need to be created before we create project zz98

# on xxoc001 as root
su - root
mkdir -p /ud/zz98 /wgdisk/xx0200/zz98
chown -R omuser1:zz98 /ud/zz98 /wgdisk/xx0200/zz98
chmod 2775 /ud/zz98 /wgdisk/xx0200/zz98

9.3 Start Omega and create project zz98

# on xxlg001 as omuser1
# make sure we have DISPLAY set

Schlumberger Private - Customer Use 32

9.3 Start Omega and create project zz98

su - omuser1
xterm
# check omega installation
omegainst
# check directories
ls -ald /wglogs /local1/scr /local1/data /tmp /wg/omega/2017.1ext#### /wgjss /ud /wgdisk
# check Omega launcher
ps -ef | grep Launcher

# set up SSH key for omuser1, and bypass host key checking when SSH other hosts
omega2 genuserkeys
ls .ssh
[omuser1@xxoc001 ~]$ cat .ssh/config
Host xx* *.dnsdomain.com
ForwardX11 yes
StrictHostKeyChecking no
ConnectTimeout 5
ConnectionAttempts 3
Ciphers arcfour,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc
GlobalKnownHostsFile /dev/null
UserKnownHostsFile /dev/null
CheckHostIP no
LogLevel Error

# in this config file, this line StrictHostKeyChecking no will bypass host key checking
# on all host defined in Host line
# add * to the Host line if we don t have all hosts with the same prefixes

# start Omega; assume 2017.1ext####p is the default baseline in /wg/omega/setup/Configuration.xml

omega2&

Note: all users need to run omega2 genuserkeys to generate SSH keys. Otherwise, when we submit jobs using
fixed pool mode, the omega user will be prompted for host authentication and password. Any jobs that copy data
using scp or ssh will need SSH key to be set up.

Now we will create zz98 new project using Omega desktop interface. Start Omega 2017.1extp first, choose
New , then type in project name, base directory (/ud) and check Create project admin directory . This way,
Omega will create a few administrative directories under /ud/zz98 directory.

Alternative command line to create new project (as omadmin or omuser1 on any host):

Schlumberger Private - Customer Use 33

9.4 Assign quota to project zz98 in RDMADMIN

omega2017.1ext####p opmadmin create zz98 /ud

9.4 Assign quota to project zz98 in RDMADMIN

# as omadmin on xxoc001, make sure we have display here
su - omuser1
xterm
omega2 rdmadmin&
# click on Pools tab and right click on the first blank row in the Project Quotas window, select A
# Project Name = zz98, File System Pool = SeismicPool1, Quota = 10G, Maximum Percent Use = 100, Maxim
# Apply and Exit

9.5 Import test data to zz98 in Omega and test

*This step can be taken after we install OCM.

If we test here without OCM, we need to set Omega.WAN.Sites.Default.JobDirectory to be /wgjss/omega2 and

submit job using immediate submit to local host.*

# as omadmin on the installation server xxoc001

su - omadmin
cd /wg/omega/install_64_2017.1ext####/AcceptanceTest
tar -xvf acc2017.1

# start Omega and import test data into zz98

# as omuser1 on xxoc001, make sure we have display here
su - omuser1
omega2017.1ext####p&
# Click on project zz98 and log in to Omega.

Start acceptance test on the login node xxlg001.

# as omuser1 on xxlg001
# make sure we have DISPLAY
su - omuser1
xterm
omega2017.1ext####p&
# Click on project zz98 and log in to Omega.

Schlumberger Private - Customer Use 34

9.5 Import test data to zz98 in Omega and test

Follow the acceptance test instruction in

/wg/omega/install_64_2017.1ext####/AcceptanceTest/acc2017.1/Omega2_Acceptance_Test_2017.1.pdf or
Omega2_Acceptance_Test_2017.1.docx (copy over to Windows and print)

Please import the project into zz98 and check GPD variables

If you have not installed OCM yet, submit job J01,J02, J04-J07 in 'immediate submit' mode to the EWS machine
(in this example xxlg001). If yes, submit job J01,J02, J04-J07 in batch mode and OCM will assign nodes to the
jobs.

Submit J03 in interactive mode

Submit the tape jobs and WHSM jobs if you have MMS and WHSM set up.

Trouble-shoot issues if jobs do not run. One common issue is /local1/scr permission on each compute node. It
needs to be open to all (777 mode).

Note 1:The resulting output impulse response MKD_OUT_ + gpd(Loc7) can be QC d in SeisView using the
following display parameters: a) Normalization value = 1E-4 b) Sample Spacing = 0.5 inches/second c) Trace
Spacing = 72 traces/inch d) Plot Type = Interpolated Density e) Density Plot Color Bar (on Colors tab) =
Grayscale f) Gathers per page = 810

Note 2:The resulting impulse response WEM_OUT_ + gpd(Loc7) can be QC d in SeisView using the
following display parameters: a) Normalization value = 1E-10 b) Sample Spacing = 0.5 inches/sec c) Trace
Spacing = 72 traces/inch d) Plot Type = Interpolated Density e) Density Plot Color Bar (on Colors tab) =
Greyshades f) Gathers per page = 801

Glossary
Omega terminology
OPM
OPM stands for Omega Project Model. All omega project files and job status are stored in Oracle OPM

Schlumberger Private - Customer Use 35

Omega terminology

instance.
RDM
RDM stands for Resource Data Model. The RDM database has file system and quota usage information
for all Omega job I/O files.
MASS
MASS stands for Multiple Attribute Storage Server Services. It s needed by Multiple Attribute Display
(MAD) interactive applications
InVa
Interactive velocity analysis
Jobqconsumer
Job Queue Consumer Services. These services handle triggered job queues. Only needed when user
triggers jobs.
MMS
Schlumberger Media Management System. MMS allows Omega to use tapes.
WHSM
WesternGeco Hierarchical Storage Management. WHSM treat tapes in tape library as extended storage.
File can be archived to tapes or restored from tapes from Omega directly.
MPI
Message Passing Interface, a standard communications protocol used for parallel applications.
JSS
Omega Job Scheduling System, a legacy tool to schedule Omega jobs.
OCM
Omega Cluster Manager. New tool to manage nodes and schedule Omega jobs.
OCI
Omega Cluster Infrastructure
EWS
Engineering Workstation. Pure Linux node that serve as login node and immediate Omega job host.
Usually, EWS has local /wg partition.

Omega services
omegacorba
Omegacorba serves like an exchange center for most Omega connections and communications. Most
other omega services depend on it.

Schlumberger Private - Customer Use 36

Omega services

omegawsn
WSN stands for Web Services Name. It s needed by Windows side applications like Omega Desktop and
Petrel.
omegaopm_2017.1ext####p
omegaopm_2017.1ext####p service is the service that manages omega projects and jobs.
omegardm_2017.1ext####p
omegardm_2017.1ext####p service is the service that manages file systems, project quotas and hosts.
omegainva_2017.1ext####p
omegainva_2017.1ext####p is the service for InVa data and projects.
omegamass_2017.1ext####p
omegamass_2017.1ext####p is needed for Multiple Attribute Display interactive application.
omegajobqconsumer_2017.1ext####p
omegajobqconsumer_2017.1ext####p service handles triggered jobs queues
omegahttpd
this service is for Omega2 Web Server, which enable OCM to view printouts directly and provide disk
usage visualization chart
omegaupdaterepository
this service is hosted on Omega Global Repository server and facilitates communication between the
Omega Global Repository server and the Omega Windows Update server
omegawindowsupdate
this service is hosted on the Omega Windows Update server. It pushes Omega updates from Linux to
Windows machines.
omegalauncher
this service serves as communication agent between different Omega hosts (Omega servers, master,
compute nodes, file servers and etc.)

Table: Important Omega Configuration Entries

Name Explanation Suggested Value

Omega baseline name to use when starting
Omega.Baseline Omega services; value need to be unique for Leave default (2017.1ext)
each Omega baseline
Omega.Corba.ORBInitialHost Corba host, port and Oracle OPM instance xxos001.dnsdomain.com

Schlumberger Private - Customer Use 37

Table: Important Omega Configuration Entries

name
Omega.DiskUsageScan.
Bulk seismic data local, default to /wgdisk /wgdisk
BulkDiskLocation
Omega.DiskUsageScan.
Project setup files location, default to /ud /ud
ProjectDiskLocation
Environment variable for Intel MPI. In
Ethernet-based networks, this will need to be
Omega.Environment. set. Setting this variable to 512 or smaller is If TCP/IP, set to 512;
I_MPI_EAGER_THRESHOLD crucial for large ZTOMO jobs to work else leave Default/0 = 131072
properly to cope with congestion in Ethernet
based networks.
Environment variable for Intel MPI. Define a If TCP/IP, set this to shm:tcp;
Omega.Environment. network fabric. The default value is set to for clusters with Qlogic Infiniba
I_MPI_FABRICS shm:ofa to use IBVerbs for clusters with set this to shm:tmi;
Mellanox Infiniband HCAs Default/0 = shm:ofa
Environment variable for Intel MPI. This
controls whether to fall back to Ethernet if
Omega.Environment. Infiniband is not available. Since 2013 If TCP/IP, set to yes;
I_MPI_FALLBACK_DEVICE baseline, the default is to disable the fallback else leave Default/0 = no
fabric. If the attempt to initialize the default
fabric fails, the MPI job will terminate.
Environment variable for Intel MPI to specify
the location of the library to use for IBVerbs. If Mellanox Infiniband, set it to
Omega.Environment. This library is installed by OFED rpms. Please /usr/lib64/libverbs.so.1;
I_MPI_OFA_LIBRARY set the value of I_MPI_OFA_LIBRARY to else leave Default/0 =
/usr/lib64/libverbs.so.1 if it is not set. There /usr/lib64/libibverbs.so.1
should not be any trailing spaces.
Omega.Environment. Environment variable for Intel MPI. When Default/0 = 1
I_MPI_ADJUST_ALLTOALLV I_MPI_ADJUST_ALLTOALLV is set to 1,
the Intel MPI library uses the Isend/Irecv +
waitall algorithm. When
I_MPI_ADJUST_ALLTOALLV is set to 2,
the Intel MPI library uses Plum's algorithm.

Schlumberger Private - Customer Use 38

Table: Important Omega Configuration Entries

This causes ZTOMO to hang in 2017.1.

Environment variable for Intel MPI. This
Omega.Environment. prints out detailed information of the MPI
Default/0 in 2016 = 100
I_MPI_DEBUG tasks. More detail can be obtained by
increasing the value.
Omega.Environment.
Omega license server @xxls001.dnsdomain.com
SLBSLS_LICENSE_FILE
Omega.Environment.
Site domain dnsdomain.com
SSH_SITE_DOMAIN
Oracle TNS Admin path; Needed by WHSM
to communicate to Oracle; needs to be
accessed by all hosts; recommend to move
/oracle/1#.#/network/admin/tnsnames.ora
Omega.Environment.
(from Oracle server) over to default = /wg/omega/setup/orac
TNS_ADMIN
/wg/omega/setup/oracle; then create a
symbolic link of
/wg/omega/setup/oracle/tnsnames.ora back to
/oracle/1#.#/network/admin/tnsnames.ora
License key file for WGC QCViewer, this file
Omega.Environment. is under /wg/omega/support/
WGC_QCVIEWER_ENCRYPT_DBASE 01-OmegaLinux/03-Miscellaneous/QCViewer licenses/Omega/QCViewer/key
on OmegaAndOCM DVD
Omega.InVA.Database. InVA host, port and Oracle OPM instance
xxos001.dnsdomain.com:1521:x
ConnectionString name
OPM host, port and Oracle OPM instance
Omega.OpmDatabase xxos001.dnsdomain.com:1521:x
name
RDM host, port and Oracle OPM instance
Omega.RdmDatabase xxos001.dnsdomain.com:1521:x
name
Temporary data directory used by Omega;
Omega.Resource. default value include /local1 and /local2;
/local1/scr
ScratchDisk recommend to delete /local2 in the
Configuration.omcdb

Schlumberger Private - Customer Use 39

Table: Important Omega Configuration Entries

Omega.Security.
Root path for Linux side jobs, default to /ud /ud
ProjectsRootPath
Omega.Security. Root path for Windows interactive jobs,
/ud
InteractiveRootPath default to /ud
Option to use RDM to manage /wgdisk/xxxx
Omega.WAN. file systems remote access or
yes
RDMDefinesDiskServers Omega.Wan.DiskServers to manage disks.
Default is to use RDM.
Omega.WAN. Mass Manager Server Host, by default the
xxos001.dnsdomain.com
MassManagerHost OPM server host
Site name, suggest to use City name or campus
Omega.WAN.LocalSite xxSITE
name, one word
Omega.WAN.Sites.Default
Site name, suggest to use City name or campus
.Name xxSITE
name, one word
.JobSubmitHost OCM server xxoc001.dnsdomain.com
.JobDirectory Where jobs are submitted /wgjss/ocm/workorder (*note)
.ORBInitialHost OPM/Corba server name xxos001.dnsdomain.com
.ORBInitialPort Default Corba port 2003 2003
.GroupAdminHost OCM server xxoc001.dnsdomain.com
.GroupAdminPort Not used Not used
.DirAdminHost OCM server xxoc001.dnsdomain.com
.DirAdminPort Not used Not used
Only needed when two sites interoperate with
.AdminSiteGroup Leave default
each other
.XtermHost Leave default
.SiteAccessDelay Leave default
.JobStatDatabase Host for job statistics database Leave default
.WSInitialHost WSN server host xxos001.dnsdomain.com
.WSInitialPort WSN port 3003

Schlumberger Private - Customer Use 40

Table: Important Omega Configuration Entries

.IsOFE Is this site a local site or OFE site false

Omega.WebServer.
Omega2 Web Server host xxoc001.dnsdomain.com
WebServerHost
Omega Global Repository Server host; right
Omega.WindowsUpdate. click and delete the two default entries and add
xxoc001.dnsdomain.com
GlobalRepositories your own entry; usually we can use the OCM
server
Omega.WindowsUpdate.
Omega Windows Update Server host xxoc001.dnsdomain.com
LocalServers
Omega.WindowsUpdate.
NIS server for all Omega system accounts NIS master server name
NISServers
Omega.WindowsUpdate.
Port number for Windows update service 56000 (default)
PortNumber
Omega.WSNServer. omegawsn service host, by default the Corba
xxos001.dnsdomain.com
WSInitialHost host

Note: Omega.WAN.Sites.Default.JobDirectory: this directory is where Omega or OCM pick up the job files. If
we have OCM, the directory should be /wgjss/ocm/workorder. If we do not have OCM, the directory should be
/wgjss/omega2. In this guide, we will use /wgjss/ocm/workorder.

Schlumberger Private - Customer Use 41