LS Installation (Elasticsearch)
This document explains the installation of sLS Server.
The SimpleLookupService is used by perfSONAR to search for perfSONAR services, hosts and interfaces. It registers records, which are simply lists of key-value pairs describing the network element. These records can then be searched using one or more key-values.
We provide an rpm and source based install for CentOS. For any other flavor of linux, the installation must be done from source.
Currently, a central instance of perfSONAR Lookup Service runs in Google Cloud Platform.
The following hardware configuration is recommended:
- Hard disk = 50G
- Memory - 10G
- Cores - 2-4
The sLS requires the following ports to be open
- 8090
- 80
The SimpleLookupService rpm is available in yum repo here: Download here
Checkout source: git clone git@github.com:esnet/simple-lookup-service.git
System Requirements: x86_64+CentOS 7 is recommended.
Note:
- The RPM has been tested only on CentOS 7.
This software requires the following:
- elasticsearch
- java-1.8.0-openjdk
In addition,
If you are installing from source, then you will need
- maven
Download and install Elasticsearch. RPM download instructions
Configure Elasticsearch to run on port 9200 and localhost only.
The Java jdk downloads can be found here: http://www.oracle.com/technetwork/java/javase/downloads/index.html
RPM Install
Install the perfSONAR repo rpm .
Run yum install lookup-service
Source Install
After checking out the source, run the following
- cd
<project>/tags/3.0.0/ - mvn install -DskipTests
- Copy the jar file and config files to wherever you wish to install them
To start/stop the lookup-service: Starting/Stopping sLS
The config files are found in /etc/lookup-service.
For configuration details, please refer here
We recommend monitoring the VM/host using Nagios or any other similar system.
- Basic checks - (port - 8090 and ping)
- Custom - perfSONAR project has a custom Nagios plugin. It can be found here: http://github.com/perfsonar/nagios/blob/master/bin/check_sls.pl. The plugin checks the number of records registered in the sLS. The best way to configure the critical and warning threshold values for the plugin will be to let the sLS run in production for a day or two to get an idea of the load on sLS and set the values based on the number of registrations in the sLS.