-
Notifications
You must be signed in to change notification settings - Fork 0
DLT Install
- Note: for further assistance, please email data-logistics@googlegroups.com
- Add the Data Logistics and EPEL repositories (for extra dependencies)
su -c 'rpm -Uvh http://data-logistics.org/yum/data-logistics-release-1-0.noarch.rpm'
su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm'
- Add the Data Logistics and EPEL repositories (for extra dependencies)
su -c 'rpm -Uvh http://data-logistics.org/yum/data-logistics-release-1-0.noarch.rpm'
su -c 'rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm'
In case you already have this repository installed, make sure that your repository cache is up to date.
my_host> yum clean all
my_host> yum check-update
- To get all the packages in the DLT, run:
my_host> yum install dlt
- This will install the IBP depot, Periscope monitoring, and Phoebus/XSP components.
- Individual component installation and configuration instructions are below.
- If you have an existing configuration file, replace /etc/ibp.cfg and start the ibp_server:
my_host> /etc/init.d/ibp-server start
or
my_host> service ibp-server start
- The ibp_server RPM comes with a configuration script that can create depot resources and install an initial ibp.cfg:
my_host> ibp_configure.py --help
- The script will walk you through a number of configuration options, with suggested defaults, including:
- IBP server settings
- UNIS registration with a BLiPP monitoring option
- Phoebus Gateway specification
- Once the script completes, configuration files will be written to the filesystem and any existing files will be backed up with a .ibp_configure_save extension.
- The UNIS registration section includes SSL configuration as the global DLT UNIS instance requires that clients present valid certificates to perform queries. The default settings point to a certificate and key pair that are installed along with the RPM. Adjust these settings as necessary if you have different SSL requirements or are registering to a different UNIS service.
- Consult the IBP server configuration guide for more information on customizing the IBP server settings.
Verify running ibp_server
- Confirm that the server has started correctly by checking log at /var/log/ibp-server.log
- You can check ibp_server stats using get_version command
my_host> get_version <interface_IP> <port_number>
Verify depot has registered with UNIS
- With the UNIS configuration defaults, the ibp_server will register itself with UNIS automatically. This makes the new depot instance discoverable within the DLT network and allows for status monitoring: http://dlt.crest.iu.edu/status
- Install BLiPP from repository if not already present. This package is included with the DLT meta-package install.
my_host> yum install blipp
-
The ibp_configure.py script described above will create a BliPP configuration file if desired. Select 'Y' when prompted. When BLiPP monitoring is selected, a config file will be written to /etc/periscope/blipp_dlt.json by default.
-
Start BLiPP:
my_host> sudo service blippd start
- Check that BLiPP has started correctly.
my_host> tail -f /var/log/blippd.log
- Check status of new depot here:
Refer [Installation & configuration guide] (https://github.com/periscope-ps/unis/blob/master/README.org). Refer SSL configuration tutorial to enable SSL on UNIS.
In order to access UNIS when protected by SSL, you need to install UNIS CA generated client certificate. Most of the modern browser, now, understand PKCS format. Obtain dlt-client.pfx file from dlt mailing list and import in your browser. Now try to access https://dlt.crest.iu.edu:9000/