Installing LSF
Simulator requires Docker CE (docker-ce).
Before you begin
Consider the following prerequisites when selecting a host for installing LSF Simulator:
- LSF
Simulator supports the following Linux operating systems running on x64 platforms:
- Red Hat Enterprise Linux 7.2, or later.
- CentOS 7.2, or later.
- Ubuntu 18.04.
- Docker CE (docker-ce) 19.03, or later, must be installed and running.
- The following ports must not be in use: 2222, 5050, 9200, 20022.
- Internet access to download the Docker-in-Docker (dind) and CentOS 7
(centos:7) images for starting the LSF
simulation Docker container.
- LSF server
or client in a production environment to directly load the LSF
configuration files.
- The intended host for LSF
Simulator must have at least 32 GB of memory.
- The installation directory that you use to extract the installation package will be the working
directory; therefore, ensure that the installation directory has at least 100 GB of free space.
- The LSF
Simulator installer assumes that you agreed to the license terms before starting the LSF
Simulator service. View the license agreement in the License/ directory within
the installation package.
Procedure
-
Log into the intended host as root.
-
Add the user for LSF
Simulator to the docker user group.
For example, to add lsfadmin to the user group,
# usermod -aG docker lsfadmin
-
Increase the limits on the mmap counts to allow the Elasticsearch features
to run correctly.
The default operating system limits on mmap counts is too low for
Elasticsearch to start correctly, which requires a limit of at least 262144. Run the following
command to increase the limit for Elasticsearch:
# sysctl -w vm.max_map_count=262144
-
Edit the /etc/sysctl.conf file.
-
Define the vm.max_map_count parameter to a value of at least
262144.
-
Save the sysctl.conf file and run the sysctl -p command
to apply your changes.
-
Log back in to the intended host as the user for LSF
Simulator.
For example, log in to the intended host as lsfadmin.
-
Navigate to the intended installation directory and extract the
lsf-cognitive installation package.
Important: The installation directory must be an absolute file path. Do not navigate to
a symbolic link to use as the installation directory. LSF
Simulator uses Docker containers and symbolic links do not work inside Docker containers.
For example,
$ cd /sharedir
$ tar -zxvf lsf_cognitive_v1.tar.gz
-
If you are running simulations for large parallel jobs, increase the share memory for
simulation containers.
The share memory for simulator containers is 62 MB, which might not be enough for a large
parallel job environment. To resolve this issue, increase the share memory for the simulation
container to 2 GB.
-
Verify that the /dev/shm device on your host has sufficient space to
increase the memory to 2 GB.
-
Navigate to the installation directory and edit the
lsf_cognitive_v1/work/lsf_simulator/sim_run/run.sh file.
-
Navigate to the lines that start with "docker run" near the end of the
file.
-
Add the --shm-size=2g option to the docker run
commands to increase the share memory to 2 GB.
For example:
if [[ "$DOCKER_DIND" == "no dind" ]]; then
docker run --privileged=true --shm-size=2g --cap-add=ALL $RUN_OPTIONS ...
else
docker run --privileged=true --link lsf_cognitive --shm-size=2g --cap-add=ALL $RUN_OPTIONS ...
fi
-
Start the LSF
Simulator service.
For example, start the LSF
Simulator service with directory mapping like the following:
$ ./bcogn start -v "$LSF_TOP:$LSF_TOP"
The first $LSF_TOP is the real LSF
cluster top level file path and the second $LSF_TOP is the mapping point from
inside the Docker container that is created automatically when starting the simulation. You must
specify the same file path both times.
-
Log in to the LSF
Simulator Console from a web browser.
-
Import the LSF
Simulator certificate to the web browser as a Trusted Root Certificate.
The certificate is located in
lsf_cognitive_v1/config/https/cacert_lsf.pem.
-
From the web browser, log in to the LSF
Simulator Console.
https://<lsf_simulator_host>:5050
Use Admin as the default user name and password.