Simple Lookup Service Bootstrap

Software for determining the state of a set of lookup services, publishing that information and then having a client use that information to choose a lookup service to contact. This code contains a server portion that handles generating a bootstrap file with the lookup service state information. It also includes a client for reading that file and sorting them based on request latency and user-defined preference.

##Getting the Code You may checkout the code with the following command:

git clone --recursive https://github.com/perfsonar/simple-ls-bootstrap.git

Note the use of the --recursive option to ensure any submodule trees are included in the clone.

##Building and Installing

To install the code on your system run:

make install

##Packaging You may create a source tarball of this code with the following:

make dist

##Running

###Server To start the service run:

/etc/init.d/simple_ls_bootstrap_server start

To stop the service run:

/etc/init.d/simple_ls_bootstrap_server stop

To restart the service run:

/etc/init.d/simple_ls_bootstrap_server restart

###Client To start the service run:

/etc/init.d/simple_ls_bootstrap_client start

To stop the service run:

/etc/init.d/simple_ls_bootstrap_client stop

To restart the service run:

/etc/init.d/simple_ls_bootstrap_client restart

##Using the shared Submodule This repository contains a git submodule to the perfSONAR shared repository. This submodule is used to access common perfSONAR libraries. You will find a number of symbolic links to these modules under lib. The use of a submodule has a few implications when working with the code in this repository:

• As previously noted, when you clone the repository for the first time, you will want to use the --recursive option to make sure the submodule tree is included. If you do not, any symbolic links under lib will be broken in your local copy. If you forget the --recursive option, you can pull the submodule tree with the following commands:

  git submodule init
  git submodule update

• When you are editing files under lib be sure to check if you are working on an actual file or whether it's a link to something under shared. In general it is better to make changes to the shared submodule by editing the shared repository directly. If however you do make changes while working in this repository, see the git submodule page for more details on pushing those changes to the server.

• Keep in mind that a submodule points at a specific revision of the repository it is referencing. As such if a new commit is made to the shared submodule's repository, this project will not get the change automatically. Instead it will still point at the old revision. To update to the latest revision of the shared submodule repository run the following commands:

  git submodule foreach git pull origin master
  git commit -a -m "Updating to latest shared"
  git push

• If you want to include a new file from the shared submodule, create a symbolic link under lib. For example, if you were to add a reference to the perfSONAR_PS::Utils::DNS module you would run the following:

  mkdir -p lib/perfSONAR_PS/Utils/
  cd lib/perfSONAR_PS/Utils/
  ln -s ../../../shared/lib/perfSONAR_PS/Utils/DNS.pm DNS.pm

For more information on using the submodule, see the shared/README.md file or access it here