MEPO 2020 Installation guide - Schlumberger Software

© 2020 Schlumberger. All rights reserved.

Schlumberger-Private

MEPO 2020 Version 2020.1

Installation guide

MULTIPLE REALIZATION OPTIMIZER

MEPO Installation guide Page 1

© 2020 Schlumberger. All rights reserved. Schlumberger-Private

TABLE OF CONTENTS

Page

1 INTRODUCTION 2

1.1 Audience 2

1.2 Installation packages 3

1.3 System requirements 4

1.4 Licenses 4

1.5 Contacting Schlumberger 6

2 INSTALLATION 7

3 DEPLOYMENT - ALTERNATIVES 9

3.1 Single host deployment – local submission 11

3.2 Single host deployment – remote submission 12

3.3 Multiple host deployment – cross-platform 13

4 DEPLOYMENT – PASSWORD-LESS REMOTE SUBMISSION 15

4.1 Generate and set up private/public SSH keys 15

4.2 Verify the correctness of the setup 16

4.3 MEPO simulation task using password-less remote submission 16

5 MEPO.INI – ADVANCED CONFIGURATION 17

5.1 MEPO.ini settings 17



1 INTRODUCTION

This installation guide provides instructions for installing MEPO on the Windows and Linux platforms.

This chapter gives you a brief introduction to MEPO installation packages, system requirements, licensing, customer support, and contact information.

Included in this chapter is a section describing MEPO program components and options for MEPO deployment and processing.

1.1 Audience

This guide is useful for these people:

• The individual user who installs MEPO on a workstation.

• The system administrator who installs MEPO in a distributed deployment or creates and distributes a global configuration for MEPO.



1.2 Installation packages

MEPO is a client/server JAVA application that supports Windows and Linux platforms.

These are the MEPO installation packages available:

Table 1 MEPO installation packages.

Platform SDC name Package name

WINDOWS MEPO 2020.1 (Windows) Release MEPO 2020.1 Windows.zip

LINUX MEPO 2020.1 (Linux) Release MEPO 2020.1 Linux.zip

A MEPO installation package includes:

• MEPO software

MEPO consists of three program components: MEPOclient, MEPOserver and MEPOns. To use MEPO, you must install all three program components according to a selected deployment scenario for the MEPO software.

MEPOclient is the graphical user interface that manages and controls MEPOserver, the core engine program component.

MEPOns is the naming service component, a communication helper used by MEPO. The installation of MEPOns is required in any MEPO software deployment scenario.

• MEPO documentation

The MEPO documentation included in the installation package contains the MEPO Release Notes, the MEPO User Manual, the MEPO Plugin for Petrel Installation Guide, and the MEPO Plugin for Petrel Release Notes.

• MEPO examples

The MEPO examples are a set of example files including template and user files and Python scripts.

• MEPO Plugin for Petrel

The MEPO Plugin for Petrel features a fully re-designed link between MEPO and Petrel that offers highly integrated workflows. It also features new functionality that enables you to visualize MEPO data in Petrel.

The MEPO installation packages provide a standard installation wizard, which also offers an unattended installation mode.



1.3 System requirements

MEPO is a 64-bit JAVA application that supports 64-bit Windows and Linux platforms.

Table 2 MEPO - supported platforms.

Platform Architecture Operating systems

WINDOWS x86-64 Windows 10 Professional/Enterprise 64-bit

LINUX x86-64 Red Hat Enterprise Linux RHEL 6 Update 9 64-bit, or later Red Hat Enterprise Linux RHEL 7 Update 4 64-bit, or later

Contact MEPO support if you intend to use alternative OS releases.

Additional software requirements for MEPO are listed in the table below:

Table 3 MEPO - software requirements.

Software Version Notes

Flexera™ FlexNet Publisher® license manager

v11.16.5 Provided by Schlumberger Licensing 2020.1 for Linux or Windows

Adobe Acrobat Reader or a compatible PDF Reader

The MEPO online help and the documentation is provided in PDF format

MEPO is a client/server application designed to run on a LAN or high-bandwidth WAN. Because MEPO can store high volumes of data that is sometimes transferred between client and server, overall performance may vary on slower connections.

1.4 Licenses

MEPO requires a valid license. The license can be configured and referenced either locally on your computer or on a central license server.

When MEPOserver starts, it checks out a set of licenses required for it to run. The licenses that are checked out are defined by the MEPO modules that you select when you connect a MEPOclient to a MEPOserver.

The available MEPO modules are:



MEPO Uncertainty Analysis

This module supports:

• Project and simulation management.

• Parallel simulation capabilities.

• Experimental design.

• All MEPO analysis capabilities.

Typical application areas are greenfield uncertainty evaluations and similar brownfield projects where history matching of models is not required.

MEPO History Matching


• Global optimizers.

• Comparison of observed data with simulation results.

Typical application areas are brownfield history matching and production forecasting.

MEPO Field Management


• Global optimizers for forward modelling.

• The MEPO forward modelling toolbox.

Typical application areas are greenfield and brownfield field development projects. The Field Management license is an add-on to the Uncertainty Analysis and History Matching licenses and requires access to such an underlying license.

Each module has a corresponding set of licenses:

MEPO Uncertainty Analysis requires the following licenses:

• mepo-explorer

• mepo-uncertaintyanalysis

MEPO History Matching requires the following licenses:

• mepo-explorer


• mepo-historymatching

MEPO Field Management requires the following licenses:

• mepo-explorer


• mepo-fieldmanagement

When MEPOserver starts, it checks out one license of each available type. This means that MEPOserver initially tries to check out all four licenses:

• mepo-explorer


• mepo-historymatching

• mepo-fieldmanagement



When you start MEPOclient and initially select the MEPOserver that you want to connect to, you can choose what modules you want to activate. When the initial connection is established, unnecessary licenses are released. At this stage, MEPOserver cannot fetch or release licenses. You must restart MEPOserver if you want to make a new module selection.

In addition to the module licenses, you can choose to run MEPOserver with an advanced simulation license (mepo-simulation) which allows for 20 simultaneous simulation runs. The basic module licenses allow for only two simultaneous simulation runs. Using the advanced license also enables you to add extra simulation runs by purchasing mepo-extrasims licenses. The number of simulation runs is potentially unlimited when using mepo-extrasims licenses.

1.5 Contacting Schlumberger

Technical Support

Schlumberger has sales and support offices around the world. For information about contacting Schlumberger, refer to the information below:

For technical support information for Software Integrated Solutions (SIS) software:

• Schlumberger Support Portal: support.software.slb.com

• Customer Care Center email: [email protected]

• Support Contract Details: http://www.software.slb.com/support/contact-details

Select your country to view support phone numbers. If your country is not listed, select the nearest location.

When submitting a support request, provide the following information:

• The MEPO product name, version, and build number. You can find this information in the About window and at the beginning of the current MEPO.log file. MEPO.log, by default, can be located in the user’s home directory.

• The MEPO system information summary. You can find this information at the beginning of the current MEPO.log file. MEPO.log, by default, can be located in the user’s home directory.

• A complete description of the problem, including error messages and steps required to reproduce it.

https://support.software.slb.com/

mailto:[email protected]

http://www.software.slb.com/support/contact-details

http://www.software.slb.com/support/contact-details



2 INSTALLATION

MEPO is a client/server application that supports multiple deployment scenarios on and across the supported platforms. The components installed and the configuration of components are dependent on the target deployment scenario.

The MEPO installation packages provide a standard installation wizard. The default settings aim to support local installation.

To install MEPO:

1 Run the installation package that matches the installation platform to start the installation wizard.

2 On the Welcome page, select to install MEPO for the first time, update an existing MEPO installation, or install the new MEPO version in addition to an existing installation.

3 On the Select destination directory page, select a new installation folder or use the default installation folder.

4 On the Select components page, select which components to install. By default, all components are installed.

5 (For Windows installation only) On the Install services page, select whether to install MEPOns as a service and whether to start it automatically when Windows starts.

6 On the Select start menu folder page, select the start menu folder for the program shortcuts and whether to create the shortcuts for all users.

7 On the Configure MEPO.ini page, specify the MEPO log destination, the license location, the MEPOns host, port, and persistence location. The default settings aim to support running MEPO on the local host.

For details on the settings in this step, refer to the next page.

8 On the Select additional tasks page, create desktop and quick launch icons.

9 Click Finish to complete the installation.



Step 8 - Configure MEPO.ini

On the Configure MEPO.ini page you can define some specific configuration settings. In particular, the MEPOns settings must reflect the selected deployment and distribution of MEPO components.

These settings are written to the application initialization file MEPO.ini, which you can find in the MEPO installation folder:

<MEPO Installation Directory>\etc\MEPO.ini

The default settings aim to support running MEPO on the local host.

• MEPO Log Directory defines the directory in which MEPO writes its log file. MEPO.log contains information which you can use to track issues. If you select the <empty> default setting, the log file is written to your home directory.

• License Location specifies the license server hosting the MEPO license. The syntax for the setting follows the FlexNet <port>@<host> license location definition as described in the Flexera™ FlexNet Publisher® license manager documentation.

• MEPOns Host defines the host name or IP address of the machine running MEPOns.

• MEPOns Port defines the port MEPOns listens to on the machine running MEPOns.

• MEPOns Persistence Folder specifies the folder in which MEPOns persists information on registered MEPOservers to handle a potential shutdown and restart of the MEPOns service. If you select the <empty> default setting, the persistence database is written to the default location.

For more details on all settings in MEPO.ini, refer to 5 MEPO.ini – Advanced configuration.



3 DEPLOYMENT - ALTERNATIVES

MEPO is a client/server application supporting multiple deployment scenarios. MEPO consists of three main program components: MEPOclient, MEPOserver, and MEPOns as the directory or naming service. You must run all three components to use MEPO.

Depending on the selected deployment scenario, MEPOclient, MEPOserver, and MEPOns can be located on the same, single host or can be distributed across separate hosts. The separate hosts can also run different operating systems, namely Windows or Linux. In any deployment scenario, the program components must establish inter-component communication via the TCP/IP network protocol.

The following diagram shows examples of how MEPO program components can be deployed:

Figure 1 Deployment alternatives.



The following diagram illustrates the inter-component communication of MEPO program components:

Figure 2 Inter-component communication.



3.1 Single host deployment – local submission

Overview: This deployment describes a setup in which all three MEPO components and the simulator are installed on the same host. The host can be an isolated machine, or a host integrated in a network. MEPOserver submits the simulation runs to the local system.

Platforms: Windows, Linux

Installation:

Figure 3 Single host deployment. MEPO components on the same host, simulator local.

Usage: MEPOns is typically installed as a service and starts automatically with the system. You can start MEPOserver by clicking Add this local server in the MEPOclient server selection window, or separately before launching MEPOclient. MEPOserver registers itself with the local MEPOns and MEPOclient queries the local MEPOns to then connect the registered MEPOserver.

MEPO.ini: The installation provides the system wide MEPO.ini in the MEPO installation folder. Both MEPOserver and MEPOclient read the same MEPO.ini file.

License: MEPO needs a valid license. The license can be provided locally through the SLB licensing tool or through the network from a central license server. The LM_LICENSE_FILE variable must define the license server location accordingly.

Simulator: The simulator software must be installed locally on the same host. MEPOserver launches the simulation locally.

For the local submission, MEPO calls ECLRUN. In MEPO, you must define the simulation launcher task for a local submission with ECLRUN, for example:

Executable: eclrun Queue: Local Simulator: <simulator> Parameter: Datafile:<data file>

Note: In Windows, you must install MEPO as a user with administrator rights to be able to install and run MEPOns as a service. If you install MEPO on Windows as an administrator, a non-privileged user can also run MEPO.



3.2 Single host deployment – remote submission

Overview: This deployment describes a setup in which all three MEPO components are installed on the same host. The simulator is installed on a remote cluster system managed by a queuing or job distributions system. MEPOserver submits the simulation runs to the remote queuing system.

Platforms: Windows, Linux

Installation:

Figure 4 Single host deployment. MEPO components on the same host, simulator remote

Usage: MEPOns is typically installed as a service and starts automatically with the system. You can start MEPOserver by clicking Add this local server in MEPOclient server selection window, or separately before launching MEPOclient. MEPOserver registers itself with the local MEPOns and MEPOclient queries the local MEPOns to then connect the registered MEPOserver.

MEPO.ini: The installation provides the system wide MEPO.ini in the MEPO installation folder. Both MEPOserver and MEPOclient read the same MEPO.ini file.


Simulator: The same version of the simulator software must be installed locally on the same host and on the remote cluster system. The cluster is typically managed by a queuing or job distributions system. MEPOserver submits the simulation runs to the remote queuing system.

For the remote submission, MEPO utilizes ECLRUN’s remote submission capabilities. In MEPO, you must define the simulation launcher task for remote submission to the queuing system with ECLRUN, for example:

Eclrun: eclrun Queue: Other Simulator: <simulator> Parameter: –s <subserver> -q <queue> -u <userid>

Datafile: <data file>



Note: For more details on password-less remote submission, refer to 4 Deployment – password-less remote submission.


3.3 Multiple host deployment – cross-platform

Overview: This deployment describes a setup in which the MEPOclient component resides on a Windows workstation or laptop. MEPOserver and MEPOns are installed on a Linux cluster system managed by a queuing or job distributions system. MEPOserver submits the simulation runs locally to the queuing system on the Linux cluster system.

Platforms: Windows and Linux cross-platform

Installation:

Figure 5 Multiple host deployment. MEPO components distributed; simulator local

Usage: MEPOns is typically installed as a service and starts automatically with the Linux cluster system. You must start MEPOserver separately on the Linux cluster before launching MEPOclient, either manually or through a program launch helper, for example. MEPOserver registers itself with the naming service on the Linux cluster system, and MEPOclient queries the naming service on the Linux cluster system to then connect the registered MEPOserver.

MEPO.ini: The installation provides the system wide MEPO.ini in the MEPO installation folder. MEPOclient reads the MEPO.ini file on the Windows system, and the file’s MEPOns settings must point to the MEPOns naming service on the Linux cluster system. MEPOserver reads the MEPO.ini file on the Linux cluster system, and the file’s MEPOns settings must also point to the MEPOns naming service on the cluster system.




Simulator: The simulator software is installed on the Linux cluster system managed by a queuing or job distributions system. MEPOserver submits the simulation runs locally to the queuing system on the Linux cluster system.

For the local submission to the queuing system, MEPO utilizes ECLRUN’s submission capabilities. In MEPO, you must define the simulation launcher task for local submission to the queuing system with ECLRUN, for example:

Executable: eclrun Queue: Local Simulator: <simulator>

Parameter: Datafile: <data file>




4 DEPLOYMENT – PASSWORD-LESS REMOTE SUBMISSION

One very typical deployment scenario for MEPO is a setup in which MEPOserver submits the simulation runs to a remote cluster system managed by a queuing or job distributions system.

For the remote submission, MEPO utilizes ECLRUN’s remote submission capabilities. To work correctly, you must install the same version of the simulator software and ECLRUN on both the local machine and the remote cluster system.

To avoid using a password for the remote cluster system, ECLRUN now supports password-less remote submission based on SSH key-based authentication and Putty’s PLINK/PSCP/PUTTYGEN. With password-less remote submission, you are not prompted for a password when submitting, checking, or aborting a job with ECLRUN.

To use password-less remote submission, you must generate and set up a pair of public and private SSH keys on both the local and the remote machine.

4.1 Generate and set up private/public SSH keys

The Putty tool suite is delivered with the third-party resources in the simulator installation source.

1. Generate a public/private SSH key pair using Putty’s Key Generator PUTTYGEN.

2. Copy the public key from the tools Public key for pasting into OpenSSH authorized keys file panel and append it to the authorized keys file on your remote system.

$HOME/.ssh/authorized_keys

3. Save the private key to the default or a custom location on your local system.

• The private key must be stored in your user home or user profile directory which

is by default protected and only accessible to you.

• By default, ECLRUN searches for a private key file named ‘putty.ppk’ in your profile directory.

See: %USERPROFILE% - environment variable

Example: C:\Users\<username>

• ECLRUN searches for a custom-named private key file in a custom location on

your local system when defined using the ‘PrivateSshKey’ variable in ECLRUN’s configuration.



4.2 Verify the correctness of the setup

Use ECLRUN command-line options to verify the correctness of the setup.

1. To check if the private Putty key can be found, use --report-putty- mode=FILE_EXISTS.

eclrun --report-putty-mode=FILE_EXISTS

The result is displayed in the command prompt:

PUTTY KEY FILE EXISTS – the file was found.

PUTTY KEY INVALID – the tool failed to find the file.

2. To check if SSH connection can be opened for a given user to a specified remote server without providing a password, use --report-putty-mode=CONNECT.

eclrun --report-putty-mode=CONNECT -u <username> -s <serverName>

The result is displayed in the command prompt:

PUTTY KEY-BASED CONNECTION OK – the connection was opened.

PUTTY KEY INVALID - the connection could not be opened.

4.3 MEPO simulation task using password-less remote submission

In MEPO, you must define the simulation launcher task for remote submission to the remote queuing system with ECLRUN, for example:

Executable: eclrun Queue: Other Simulator: <simulator> Parameter: –s <subserver> -q <queue> -u userid> Datafile: <data file>

Invoking ECLRUN without the -p password option enables the password-less remote submission.

Invoking ECLRUN with the -p password option disables the password-less remote submission.



5 MEPO.INI – ADVANCED CONFIGURATION

The application initialization file MEPO.ini contains settings used by all MEPO program components when they are started. You can edit the file to set up a more advanced manual configuration.

The installation provides the system wide MEPO.ini in the MEPO installation folder:

<MEPO Installation Directory>\etc\MEPO.ini (Windows)

<MEPO Installation Directory>/etc/MEPO.ini (Linux)

The system wide MEPO.ini settings are active for every MEPO user. If a MEPO user requires individual settings, you can put a user-specific MEPO.ini file in the .mepo subdirectory of the user’s home or user’s profile directory:

%USERPROFILE%\.mepo\MEPO.ini (Windows)

$HOME/.mepo/MEPO.ini (Linux)

A user-specific setting overwrites the corresponding global setting.

5.1 MEPO.ini settings

You can adapt the following settings:

• MEPO_HOME

You can use MEPO_HOME to point to a different MEPO installation directory. By default, MEPO_HOME is not set in MEPO.ini and MEPO simply uses its own installation directory. Use this setting carefully — pointing to an invalid folder, or a folder containing an invalid version of MEPO, prevents certain MEPO functionalities from working properly, such as the ability to add a local MEPOserver from MEPOclient's server selection window.

• LM_LICENSE_FILE LM_LICENSE_FILE defines the license location of the MEPO license. The syntax for the setting follows the FlexNet <port>@<host> license location definition as described in the Flexera™ FlexNet Publisher® license manager documentation.

• MEPOLOGDEST

MEPOLOGDEST defines the directory in which MEPO writes its log file. MEPO.log contains information that you can use to track issues. With the <empty> default setting, the log file is written to the user’s home directory. This is recommended to maintain an individual MEPO.log for each MEPO user.



• LOGFILE_SIZE and LOGFILE_COUNT

You can use LOGFILE_SIZE to define the maximum file size for MEPO.log. When the maximum size is reached, MEPO creates a new log file.

LOGFILE_COUNT limits the number of log files before the oldest one is automatically erased.

If LOGFILE_COUNT is set to 0, then MEPO uses only one file and truncates the oldest log information when LOGFILE_SIZE is reached.

In the following example, MEPO will create up to five log files of 1 MB each before deleting the oldest one:

LOGFILE_SIZE=1MB

LOGFILE_COUNT=5

• FRAMEDECORATION

You can use the FRAMEDECORATION setting to activate or deactivate the MEPO-specific ‘frame’ look and feel. This setting is set to ‘true’ by default on Windows platforms, and ‘false’ by default on the Linux platform. If you are using non-standard MEPO installation platforms or a non-standard remote X11 solution, for example, and you experience abnormally reduced performance, try setting FRAMEDECORATION to false.

• SERVERNAME

You can use the SERVERNAME setting to give a default name to MEPOservers. The name is used in MEPOclient when the user is asked to select which MEPOserver to add and then connect to.

Note: You can also set a server name for a MEPOserver when starting it using the ‘-server’ option, for example:

MEPOserver -server=myMEPO &

• NS_HOST and NS_PORT

NS_HOST defines the host name or IP address of the machine running MEPOns. NS_PORT defines the port MEPOns is listening at on the machine running MEPOns, which is also the port on which MEPOns can be reached. Using invalid settings prevents MEPOclient from connecting to MEPOserver.

• NS_DBHOME

NS_DBHOME specifies the folder in which MEPOns persists information on registered MEPOservers to handle a potential shutdown and restart of the MEPOns service. With the <empty> default setting, the persistence database is written to its default location.

• PORT_MIN and PORT_MAX

You can use PORT_MIN and PORT_MAX to define which port range to use for MEPOclient and MEPOserver to communicate. MEPOclient and MEPOserver establish inter-component communication through the TCP/IP network protocol. The default port range is 2500 to 3000.



• ACTIVATION FLAGS

The following activation flags are set to ‘false’ by default and you can use them to enable certain simulator-specific functionalities:

ACTIVATE_VIP=true ACTIVATE_PSIM=true ACTIVATE_NEXUS=true

MEPO 2020 Installation guide - Schlumberger Software

Documents

Transcript of MEPO 2020 Installation guide - Schlumberger Software