perfsonar 2.0 Administration Guide Version 2.1

Transcription

1 perfsonar 2.0 Administration Guide Version 2.1

2 Document History Product/Version Number: perfsonar 2.0 Date of Release: 23/07/07 Activity: JRA1 Dissemination Level PP

3 Table of Contents 1 Introduction How To Use This Guide Document Conventions Introducing perfsonar Points To Consider perfsonar 2.0 Prerequisites Manual Installation of pre-requisites Automatic Installation of pre-requisites Using the perfsonar 2.0 Bundle Installer Interactive Questions RRD Measurement Archive (Java) SQL Measurement Archive Lookup Service SSH/Telnet Measurement Point Command Line Measurement Point BWCTL Measurement Point Advanced Installation With the help of the bundle installer With the help of ant or perl scripts which are part of each service Re-configuration 40 3 Stitching What is Stitching? RRD MA Stitching SQL MA Stitching (utilisation and lightpath status) SSH Telnet MP Stitching 42 4 Backing up your configurations 43 perfsonar 2.1 i

4 Introduction 5 Upgrading your existing RRD MA and SQL MA metadata configurations 44 6 Upgrading existing (<2.0) perfsonar software 46 7 Uninstallation Uninstalling perfsonar 1.0 bundle Uninstalling older versions (<2.0 but >1.0) of perfsonar services Uninstalling services bundled in Uninstalling JAVA Services Uninstalling Perl Services Uninstalling perfsonar 2.0 bundle 49 perfsonar 2.1 ii

5 1 Introduction This guide describes the installation and configuration processes for perfsonar 2.0. It includes: A brief introduction to perfsonar 2.0. Prerequisites needed before installing perfsonar 2.0. Instructions for the installation and configuration process. Instructions for implementing Stitching. Uninstalling perfsonar How To Use This Guide This guide is aimed at the perfsonar System Administrator. As such it assumes detailed knowledge of operating system software (Windows, Linux and Unix) and of the software required for perfsonar to be installed and operate (see 2.2 perfsonar 2.0 Prerequisites on page 4). Note: It is crucial that you are familiar with the operating systems and software requirements before you attempt to install perfsonar Document Conventions This documentation uses the following typographic conventions for menus, commands, keyboard keys, and items in the program interface: Boldface Commands and names of interface items. For example option buttons, menu options, and so on. Italics Placeholders for information or parameters that you provide. For example, filename in a procedure means you type the actual name of a file. Italics are also used for new terms and the titles of books. > Used to indicate selecting an option in a hierarchical menu structure. For example: perfsonar 2.1 1

6 Introduction Select Insert > Picture > From File This instructs you to select the Insert option, followed by the Picture option, and finally the From File option. 1.2 Introducing perfsonar 2.0 perfsonar (Performance focused Service Oriented Network monitoring Architecture) is now released as the perfsonar 2.0 software bundle. The bundle has a number of enhancements to the original release: Each service is a separate product/project. The bundle contains only the bundle installer, which downloads tar balls of services that the user wishes to install Multiple Services can be installed on same tomcat New installer script: Menu based interactive installation, on-demand download of services Improved robustness with four steps for installation (pre-install, configure, deploy, test) Java and perl services compatibility Installer written in perl (requires perl), but requires Apache Ant to install Java services Includes four new services and two improved services: New Services:: Command Line MP (Java), SSH/Telnet MP (Java), BWCTL MP (Perl), SQL MA (Java) Improved Services RRD MA (Java), Lookup Service (Java) New features in all Services include: Result codes used extensively; converted most java exceptions returned to client into xml result codes Echo functionality on all java services; functions as a ping message to the service, and helps in determining status of deployments Automatic download and installation of Tomcat (all Java services) and exist XML database (RRD MA and SQL MA only) Lookup Service registrations and keep-alives across all six services perfsonar 2.0 also contains the building blocks for NRENs to provide a Multi-Domain Monitoring (MDM) service. This guide describes the installation process for personar 2.0. The sections that follow describe: The prerequisites for perfsonar 2.0 installation An overview of the personar 2.0 installation process Detailed instructions of the individual steps of the process perfsonar 2.1 2

7 2 To install perfsonar 2.0 you must: 1. Download the perfsonar 2.0 bundle into an appropriate location on your system. Check the requirements section for the service that you wish to install. See Only Java services can be installed in tomcat 2. perfsonar 2.0 Prerequisites on page 4. At a minimum, check the manual installation requirements section and install any necessary pre-requisites. See Manual Installation of pre-requisites on page Unzip and untar the bundle installer, perfsonar-2.0.tar.gz 4. Unset/remove your existing CLASSPATH variable before starting. Make sure that the variable $CLASSPATH is empty. You can do this by either removing from your.bash_profile file or executing export CLASSPATH= in the command prompt before continuing with the next step 5. Execute the bundle installer using the command perl install.pl: a. Make sure you are in the perfsonar-bundle directory (for example /home/perfsonar/perfsonar-2.0-bundle) b. If perl is not on your PATH, you will have to give the complete path to the perl binary - PERL_PATH/perl install.pl See 2.3 Using the perfsonar 2.0 Bundle Installer on page Follow the on-screen instructions. Before you start installing a service, be prepared for the questions that you will be asked. The on-screen dialogue will help you in the installation. We recommend that you familiarise yourself with the questions and answers that the installer will ask you when you install a service. See 2.4Interactive Questions on page At the end of the installation, the installer will perform tests on the installation. You must verify the results to check your installation was successful. 8. The Measurement Archives (RRD and SQL) require some stitching after installation. See 3 Stitching on page 41. perfsonar 2.1 3

8 Note: For RRD MA it is important that you set the LD_LIBRARY_PATH variable, ideally in the profile where the service is installed. This will make sure that whenever you restart tomcat or reboot the machine, the variable is applied before tomcat is restarted. If this is not done, the service will not be able to read the configured RRD Files 2.1 Points To Consider With perfsonar 2.0 you can install any number of services on the same tomcat instance. Apart from installations of different service types, these installations could also include new instances of the same service type (you can install two SQL MA services on the same tomcat along with any other service type). To make use of this feature, be aware that: If the service requires XML database (RRD MA, SQL MA and LS), please make sure that you configure each service to use a different username and password. Do not use exist XML Database USERNAMES AND COLLECTIONS across two installations. You must have a different document base for each service. To do this, choose a different service name than the one already in use. (ex: XML-LS-1.1 and XML-LS2-1.1 if they are on the same tomcat). Only Java services can be installed in tomcat 2.2 perfsonar 2.0 Prerequisites The perfsonar bundle contains six services (Web Services Applications). The prerequisites for installing each of these services are different. Some of these requirements have to be manually installed, while others can by automatically installed during the perfsonar installation process. However, you can manually install all the requirements (including the automatic ones) if required Manual Installation of pre-requisites Depending on the application/service you wish to deploy, you may be required to manually install some required software. The lists below define general prerequisites for all services, followed by specific prerequisites for the individual service. Note: Time durations given as rough estimates only, and are given only as an indication of the effort involved. They do not include stitching or installing operating systems. perfsonar 2.1 4

9 General Requirements Required for all services: Operating System: Redhat Linux/Fedora Other versions of unix are supported for most services, but not all. See the requirements for the service that you want to install Installations on Windows not supported (some services, RRD MA for example, will not work) 'wget' command should be available on the OS. This is required by the installer to download dependency software. Perl - version or higher The Perl Module, LWP RRD Measurement Archive (Java) - (Effort: ~1.5 hr) JAVA (JDK 5 version 1.5) Apache Ant (Version 1.6.x) RRDTool to read your RRD files (version 1.2.x) Make sure you have the following files related to RRDTool on your workstation. rrd.h - Usually found in $RRDTOOL_HOME/include directory. Approximately 10 files starting with the name librrd. They are usually found in $RRDTOOL_HOME/lib directory. Note: During the installation and deployment process you will be required to setup LD_LIBRARY_PATH environment variable. It is extremely important that this environment variable is set before every restart of Tomcat We suggest that the LD_LIBRARY_PATH environment variable declaration be added to the profile information of the account where this service is installed. The installation process will suggest the value to be used for this variable SQL Measurement Archive - (Effort: ~2 hr) JAVA (JDK 5 - version 1.5) Apache Ant (version 1.6.x) MySQL or PostgreSQL Relational Database Mysql (version 5.0) PostgreSQL (version 8.x) perfsonar 2.1 5

10 Lookup Service - (Effort: ~1.5 hr) JAVA (JDK 5 - version 1.5 or later) Apache Ant (1.6.x) exist XML Database (version or 1.1.1) Note: You can re-use an already installed exist XML database. However, if you are installing a new database we recommend installing it in tomcat as a webapp (download war file). Some configuration may be required after installation (see wiki/index.php/exist_db_installation_guide_for_ls for a short tutorial) SSH/Telnet Measurement Point - (Effort: ~2.0 hr*) JAVA (JDK 5 - version 1.5 or later - available here) Apache Ant - version 1.6.x - available here You will also need to know the list of routers/devices and the commands on the routers that you wish to make available via this tool Command Line Measurement Point - (Effort: ~2.0 hr*) JAVA (JDK 5 - version 1.5 or later) Apache Ant (version 1.6.x) OWAMP tool (version xx) BWCTL tool (version xx) Ping tool Traceroute tool BWCTL Measurement Point (Perl) Operating System - Redhat Linux/Fedora BWCTL MP not tested/won't work on other flavors of unix OS Perl - version or higher BWCTL tool (version 1.1b or later) Iperf tool (version or later) Perl Modules that are required to be installed manually None (unless automatic installations of the required modules fail) Automatic Installation of pre-requisites The following requirements can be installed automatically. perfsonar 2.1 6

11 Note: Even if two services have common requirements, it is not necessary to install the same software twice on the same workstation. However, you may want to record the directory where the software has been automatically installed RRD Measurement Archive (Java) Tomcat Application Server - Jakarta Tomcat exist XML Database (Version 1.0 or later - available here) RRDJtool (as JNI) SQL Measurement Archive Tomcat Application Server - Jakarta Tomcat exist XML Database (Version 1.0 or later) Lookup Service Tomcat Application Server - Jakarta Tomcat exist XML Database (Version 1.0 or later) SSH/Telnet Measurement Point Tomcat Application Server - Jakarta Tomcat Command Line Measurement Point Tomcat Application Server - Jakarta Tomcat BWCTL Measurement Point Perl Modules that will be installed automatically Bit-Vector Carp-Clan Compress-Zlib Date-Calc Date-Manip HTML-Parser HTML-Tagset IO-Tty IPC-Run libwww-perl Log-Dispatch perfsonar 2.1 7

12 Module-Build Params-Validate SOAP-Lite (version 0.66) URI XML-LibXML XML-LibXML-Common XML-NamespaceSupport XML-SAX XML-Writer XML-Writer-String 2.3 Using the perfsonar 2.0 Bundle Installer After you have downloaded and unzipped the perfsonar 2.0 bundle, you can start the installer by: 9. Execute the bundle installer using the command perl install.pl: a. Make sure you are in the perfsonar-bundle directory (for example /home/perfsonar/perfsonar-2.0-bundle) b. If perl is not on your PATH, you will have to give the complete path to the perl binary - PERL_PATH/perl install.pl The installer starts. Note: You can exit the installer at any time using the Exit command form the main menu, or typing CTRL+C. 10. The installer beginning screen displays three options: 1. Install a new service: Choose this option if you want to install a new service. You can also use this option if you have already installed an instance of the same service (for example RRD MA) but would like to install another instance on the same machine. 2: Modify or test an existing installation: Choose this option to modify configuration details or test existing installations of perfsonar services. This option will not work if you have not already installed any of the services using the perfsonar 2.0 bundle. 3: Give feedback to the perfsonar team: Your feedback will be sent to us by the installer. If you re installing a new service (and therefore select Option 1): If you chose the first option, the bundle installer provides a list of six services that can be installed. Simply choose the service that you would like to install from this list. The bundle installer automatically downloads installation files for each service and executes the installation steps in sequence for the chosen service. Before downloading the installer files for a service, the bundle installer will search to see if it can find existing downloads of installation files. If you want to install two instances of the same service on the same workstation, you can re-use the already downloaded installation files. This will not affect the first instance. perfsonar 2.1 8

13 If the bundle installer cannot find installation files, it will give you the option to either ask it to download the files and install, or you can specify an alternate path where the files have been downloaded previously. If files have to be downloaded, the installer will automatically download and extract the required files. It will ask you if you want it to extract to location different from the default one. We suggest that you choose the default location. After downloading the required files (or accepting an existing installation files directory), the bundle installer will ask you if you want to do a basic installation or an advanced one. Choose the basic installation unless you are feeling adventurous. See 2.5 Advanced Installation on page 38. The steps below are for basic installation Depending on the service chosen, you will be asked several questions. If you make a mistake at any time, quit (CTRL+C) and you can start again (bundle installer will ask you). If you experience some problems or have some questions, try out the support pages (FAQs) or contact the mailing list 2.4 Interactive Questions The perfsonar installer prompts you for the information required to install the bundled software. Below are the prompts and questions you need to answer, subdivided by service. Note: Please review these questions and have all the required information ready to hand before installing the software. Explanations for each question are given below, and appropriate defaults are included whenever possible RRD Measurement Archive (Java) Pre-installation Enter the name of the service [perfsonar-rrd-ma-2.0]: Explanation: The script asks for symbolic name. This name will be present in the address URL of the service. Default: perfsonar-rrd-ma-2.0 Enter the path where you want to install the service [/root/webapps] Explanation: Location of the service files to be stored. Default: <current_directory>/webapps Do you want me to download and install the application server Tomcat (apache-tomcat-6.0.7) for you? (y,n) perfsonar 2.1 9

14 Explanation: Application server Tomcat is a container for the service. It contains the implementation of HTTP protocol which is used by the service to send and receive messages (NMWG). If you already have it in your system you can answer 'n'. Recommendation: Tomcat version is suggested. IF answer is 'y': Enter the path for the Tomcat installation: [/root/apachetomcat-6.0.7]: Explanation: If you wanted to download Tomcat, then the script asks you where to put it. Default: <current_directory>/apache-tomcat IF answer is 'y' : Enter a URL of the Tomcat download (mirrors can be found on [1] Explanation: If you wanted to download Tomcat, then the script suggests mirror server to be used for downloading. Default: IF answer is 'n' : Enter the path for the Tomcat installation: [/usr/local/tomcat]: Explanation: If you already have Tomcat in your system, the script asks you where it is located. Default: /usr/local/tomcat Enter the port which will be used by your application server Tomcat [8080] Explanation: This is the port number that will be used by Tomcat and the service to send and receive messages (HTTP). Default: 8080 Recommendation: If you need another port number then you must also setup Tomcat to use this new number. To do this, open Tomcat's configuration file conf/server.xml and alter the port number in the Connector element :<Connector port="8080" protocol="http/1.1" maxthreads="150" connectiontimeout="20000"redirectport="8443" /> Do you want me to compile rrdjtool library for you (if not you will have to do it manually in /root/perfsonar-rrd-ma-2.0/perfsonar/contrib/rrdjtool after pre-install step)? (y,n) Explanation: The service needs the library of rrdjtool, which is an interface to RRD files. The script can build the library for you, if the answer is 'y'.. IF answer is 'y': Enter operating system type: (linux,linux- 64bit,freebsd,solaris,other) perfsonar

15 Explanation: If you wanted the script to build the library of rrdjtool, then you must provide the information what OS do you have on your machine. You can find a list of accepted operating systems in round brackets.. IF answer is 'y': Enter the directory path where header file of the rrdtool (rrd.h) can be found [/usr/local/rrdtool/include]: Explanation: If you wanted the script to build the library of rrdjtool then you must provide the information where the header file of rrdtool is located. Default: /usr/local/rrdtool/include Recommendation: The path in square brackets in only an example. IF answer is 'y': Enter the directory path where library files of the rrdtool (librrd*) can be found [/usr/local/rrdtool/lib]: Explanation: If you wanted the script to build the library of rrdjtool then you must provide the information where library files of rrdtool are located. Default: /usr/local/rrdtool/lib Recommendation: The path in square brackets in only an example. IF answer is 'y': Enter the home directory where the Java is installed (I need the home directory and not the directory where the executable binary is present) [/usr/local/jdk1.5.0]: Explanation: If you wanted the script to build the library of rrdjtool then you must provide the information where Java installation is located (rrdjtool is a java library so Java is required for building). Default: /usr/local/jdk1.5.0 Recommendation: The path in square brackets in only an example. Usage of exist xml database is recommended for the service. Installing/configuring this database as a web application in your Tomcat is also suggested. Do you want me to do this for you? (y,n) Explanation: The service contains the metadata configuration which is suggested to be stored in the xml database exist. If you want to have the metadata configuration as a plain text file you may expect that the service will be slower in generating responses. Using exist as a web application you can use your Tomcat to install the xml database. IF answer is 'y': Do you want me to download exist web application package (if not you have to do it manually)? (y,n) Explanation: The script can download xml database exist as a web application package automatically. It is possible that the time of downloading might be long. In such case download exist manually. perfsonar

16 IF answer is 'y': Enter a URL of exist web application package (exist war) [2]: Explanation: If you wanted the script to download exist, then you can see a suggested server to be used for downloading. Default: IF answer is 'y': Enter the path of directory where exist war file will be located [/root]: Explanation: If you wanted the script to download exist then you can see the suggested location where exist will be stored. Default: <current_directory> [echo] Please, insert now the following xml tag 'Context' [echo] into Tomcat configuration file server.xml [echo] (/root/apache-tomcat-6.0.7/conf/server.xml) [echo] inside existing xml tag 'Host': [echo] <Context path='/exist' [echo] docbase='/root/exist war'> [echo] </Context> Please do it now and press Enter when finished Explanation: The Context element represents a web application, which is run within a particular virtual host. Each web application is based on a Web Application Archive (WAR) file. Here, we nest a Context element within a HOST element in <TOMCAT>/conf/server.xml. Do the change on the file as described, on another window, then press Enter so that the script can continue the installation. Enter the exist user name: Explanation: The script asks for xml database user name (it could be for example rrdmaservice). Enter the password for exist user name : Explanation: The script asks for the password for xml database user. Enter the password for admin exist user []: Explanation: The script asks for the password for xml database admin user. Default: If this is the first installation of exist then the password is empty. Recommendation: We suggest you change/set up the password for admin user of exist database after the service installation procedure. When the exist database password is not set (blank), perfsonar

17 everyone can alter the content of the database using exist client application (of course if a firewall does not block the access) Configuration: Enter the path of rrd metadata configuration file [/root/perfsonar-rrd-ma- 2.0/perfsonar/conf/rrd-database_TEST.xml]: Explanation: The script asks for the metadata configuration file. This file contains the description of measurement data in RRD files. If you wanted to use the xml database in the pre-install step then the metadata configuration file will be stored there later on during the Deployment. Default: The test file in square brackets is suggested only for test purposes (you can use it for the first test service installation). Do you want the service to accept messages with measurement data and store them? (y,n) Explanation: The service can receive messages with measurement data and store them in RRD files.. Enter location of new RRD files created when measurement data is sent to the service [/root/webapps]? Explanation: The service can receive messages with measurement data and store them in RRD files. Here the script asks for the location where the service will create new RRD files. Default: <current_directory>/webapps Turn on service registration to Lookup Service? (y,n) Explanation: The service can register itself to the Lookup Service. The Lookup Service stores the information about running perfsonar services in the network. IF answer is 'y': Enter the URL of LS []: Explanation: The service can register itself to a Lookup Service. The script asks for the url of the Lookup Service on which the service will register itself. Default: no url Deployment: Do you want me to start the application server Tomcat for you? (y,n) Explanation: The script can start Tomcat with the service inside, but there is also a possibility to do it manually. perfsonar

18 Recommendation: If your Tomcat is already running before Deployment, you should answer 'n'. [echo] Please, insert now the following xml tag 'Context' [echo] into Tomcat configuration file server.xml [echo] (/root/apache-tomcat-6.0.7/conf/server.xml) [echo] inside existing xml tag 'Host': [echo] <Context path='/perfsonar-rrd-ma-2.0' [echo] docbase='/root/webapps/perfsonar-rrd-ma-2.0'> [echo] </Context> Please do it now and press Enter when finished Explanation: The Context element represents a web application, which is run within a particular virtual host. Each web application is based on a Web Application Archive (WAR) file. Here, we nest a Context element within a HOST element in <TOMCAT>/conf/server.xml. Do the change on the file as described, on another window, then press Enter so that the script can continue the installation. [echo] Please, make sure that Tomcat is running. [echo] You can do it using your web browser and connect the address [echo] or looking at Tomcat's log file (/root/apache-tomcat /logs/catalina.out). Press Enter when finished Explanation: The script will ask you to check if Tomcat has finished its startup phase. You can use web browser and connect to your Tomcat's web page or take a look at Tomcat's log file logs/catalina.out (after startup phase you should find there a line 'INFO: Server startup in xxx ms'), then press Enter so that the script can continue the installation. Do you want me to add new user (provided in the pre-install step) and initiate the xml database exist (If your exist is already configured and initialized for RRD MA answer 'n'. But probably it's your first run of this installation script so you have not added this user and initialized the database yet.)? (y,n) Explanation: In case of use of the xml database exist, it needs to be set up (this means it must have an account and the metadata configuration specified in the pre-install and configure steps of the installation procedure). Recommendation: If the xml database already has been set up the answer should be 'n'. perfsonar

19 2.4.2 SQL Measurement Archive Pre-install step: Enter the name of the service [perfsonar-sql-ma-1.0]: Explanation - The script asks for symbolic name. This name will be present in the address URL of the service. Default: perfsonar-sql-ma-1.0 Enter the path where you want to install the service [/root/webapps] Explanation: location of the service files to be stored. Default: <current_directory>/webapps Do you want me to download and install the application server Tomcat (apache-tomcat-6.0.7) for you? (y,n) Explanation: Application server Tomcat is a container for the service. It contains the implementation of HTTP protocol which is used by the service to send and receive messages (NMWG). If you already have it in your system you can answer 'n'. Recommendation: Tomcat version is suggested. IF answer is 'y': Enter the path for the Tomcat installation: [/root/apachetomcat-6.0.7]: Explanation: If you wanted to download Tomcat, then the script asks you where to put it. Default: <current_directory>/apache-tomcat IF answer is 'y' : Enter a URL of the Tomcat download (mirrors can be found on [3] Explanation: If you wanted to download Tomcat, then the script suggests mirror server to be used for downloading. Default: IF answer is 'n' : Enter the path for the Tomcat installation: [/usr/local/tomcat]: Explanation: If you already have Tomcat in your system, the script asks you where it is located. Default: /usr/local/tomcat Enter the port which will be used by your application server Tomcat [8080] Explanation: The script asks for port number which will be used by Tomcat and the service to send and receive messages (HTTP). perfsonar

20 Default: 8080 Recommendation: If you want to have other port number then you have to setup Tomcat to use this new one as well. To do it open Tomcat's configuration file conf/server.xml and alter the port number in the Connector element :<Connector port="8080" protocol="http/1.1" maxthreads="150" connectiontimeout="20000"redirectport="8443" /> Usage of exist xml database is recommended for the service. Installing/configuring this database as a web application in your Tomcat is also suggested. Do you want me to do this for you? (y,n) Explanation: The service contains the metadata configuration which is suggested to be stored in the xml database exist. If you want to have the metadata configuration as a plain text file you may expect that the service will be slower in generating responses. Using exist as a web application you can use your Tomcat to install the xml database. IF answer is 'y': Do you want me to download exist web application package (if not you have to do it manually)? (y,n) Explanation: The script can download xml database exist as a web application package automatically. It is possible that the time of downloading might be long. In such case download exist manually. IF answer is 'y': Enter a URL of exist web application package (exist war) [4]: Explanation: If you wanted the script to download exist, then you can see a suggested server to be used for downloading. Default: IF answer is 'y': Enter the path of directory where exist war file will be located [/root]: Explanation: If you wanted the script to download exist then you can see the suggested location where exist will be stored. Default: <current_directory> [echo] Please, insert now the following xml tag 'Context' [echo] into Tomcat configuration file server.xml [echo] (/root/apache-tomcat-6.0.7/conf/server.xml) [echo] inside existing xml tag 'Host': [echo] <Context path='/exist' [echo] docbase='/root/exist war'> [echo] </Context> Please do it now and press Enter when finished perfsonar

21 Explanation: The Context element represents a web application, which is run within a particular virtual host. Each web application is based on a Web Application Archive (WAR) file. Here, we nest a Context element within a HOST element in <TOMCAT>/conf/server.xml. Do the change on the file as described, on another window, then press Enter so that the script can continue the installation. Enter the exist user name: Explanation: The script asks for xml database user name (it could be for example sqlmaservice). Enter the password for exist user name : Explanation: The script asks for the password for xml database user. Enter the password for admin exist user []: Explanation: The script asks for the password for xml database admin user. Default: If this is the first installation of exist then the password is empty. Recommendation: We suggest you change/set up the password for admin user of exist database after the service installation procedure. When the exist database password is not set (blank), everyone can alter the content of the database using exist client application (of course if a firewall does not block the access) Configuration: [echo] This service requires access to the relational database [echo] (mysql or postgesql but others can be used as well). [echo] Make sure that you have one or install it from scratch. Please do it now and press Enter when finished Explanation: The script wants to know if a relational database is installed on the system. If you already have one installed, just press Enter. If not, please install one at this point, and then press Enter so that the script can continue the installation of the service.. [echo] In order to maintain data of utilization metric and/or L2 path status metric, [echo] please, prepare your relational database. [echo] In case of mysql use simple script file mysql-sqlma-dbsetup.sql [echo] that you can find in conf directory (/root/perfsonar-sql-ma- 1.0/perfsonar/conf) [echo] of perfsonar SQL MA installation package. perfsonar

22 [echo] In case of postgresql use psql-sqlma-dbsetup.sql. [echo] (Warning: remember to change the password for perfsonar_ma user!) Please do it now and press Enter when finished Explanation: The script wants the relational database to be ready to receive the data of the metrics that work with the service. If the database is mysql, the user should use the script mysqlsqlma-dbsetup.sql. In case of a postgresql database, use psql-sqlma-dbsetup.sql. Then press Enter so that the script can continue the installation of the service.. Enter the path of sql metadata config file [/root/perfsonar-sql-ma- 1.0/perfsonar/conf/sql-database_TEST.xml]: Explanation: The script asks for the location of the metadata configuration file. This file contains the description of measurement data stored in relation database. Default: The test file in square brackets is suggested only for test purposes (you can use it for the first test service installation). Do you want to use data of L2 path status metric in domain scope which are or will be stored in your relational database? (y,n) [echo] Provide correct jdbc connection parameters [echo] for relational database where data of L2 path status metric - domain scope [echo] are stored. Explanation: The script asks if the user wants to use the L2 path status metric. Enter the name of database you are going to use? (mysql,postgresql) Explanation: The script wants to know the relational database that is going to be used. Enter database jdbc address URL [jdbc:mysql:// /perfsonar_ma]? Explanation: The script wants to know the jdbc address URL to the relational database. Default: jdbc:mysql:// /perfsonar_ma Enter database user name [perfsonar_ma]? Explanation: The script asks for relational database user name. Default: it could be for example perfsonar_ma Enter the password of user name perfsonar_ma [testpass]? Explanation: The script asks for relational database password for the username chosen in the previous step. perfsonar

23 Default: it could be for example testpass Do you want to use data of L2 path status metric in interdomain scope which are or will be stored in your relational database? (y,n) [echo] Provide correct jdbc connection parameters [echo] for relational database where data of L2 path status metric - interdomain scope [echo] are stored. Explanation: The script asks if the user wants to use the L2 path status metric in intradomain scope. Do you want to use data of utilization metric which are or will be stored in your relational database? (y,n) Explanation: The script asks if the user wants to use the utilization metric. [echo] If you want to change provided jdbc connection parameters manually, [echo] because of some reasons, [echo] you can do this in configuration files (ibatis-sqlmapconfig-*.xml) [echo] in /root/perfsonar-sql-ma-1.0-rc5/perfsonar/conf directory. [echo] After such change, when the service is already deployed, you must [echo] redeploy the service (undeploy and deploy again). Press Enter to continue Explanation: The script asks if the user wants to change jdbc parameters manually. Do you want the service to accept messages with measurement data and store them? (y,n) Explanation: The service can receive messages with measurement data and store them in relational database. Turn on service registration to Lookup Service? (y,n) Explanation: The service can register itself to the Lookup Service. The Lookup Service stores the information about running perfsonar services in the network. IF answer is 'y': Enter the URL of LS []: perfsonar

24 Explanation: The service can register itself to a Lookup Service. The script asks for the url of the Lookup Service on which the service will register itself. Default: no url. Enter the registration interval [30000]: Explanation: The service can register itself to a Lookup Service. The script asks for the registration interval that the service will use. Default: Enter IP or DNS address of the host you are using now to deploy the service []: Explanation: The service can register itself to a Lookup Service. The script asks for the IP address or name of the server where the SQL-MA installation is being done, and from where the service will register to the Lookup Service. Enter the description of service that will be send to the LS [perfsonar service]: Explanation: The description of the service that will be sent when registering to a Lookup Service. Default: perfsonar service Deployment: Do you want me to start the application server Tomcat for you? (y,n) Explanation: The script can start Tomcat with the service inside, but there is also a possibility to do it manually. Recommendation: If your Tomcat is already running before Deployment, you should answer 'n'. [echo] Please, insert now the following xml tag 'Context' [echo] into Tomcat configuration file server.xml [echo] (/root/apache-tomcat-6.0.7/conf/server.xml) [echo] inside existing xml tag 'Host': [echo] <Context path='/perfsonar-sql-ma-1.0' [echo] docbase='/root/webapps/perfsonar-sql-ma-1.0'> [echo] </Context> Please do it now and press Enter when finished Explanation: The Context element represents a web application, which is run within a particular virtual host. Each web application is based on a Web Application Archive (WAR) file. Here, we nest a Context element within a HOST element in <TOMCAT>/conf/server.xml. Do the change on the perfsonar

25 file as described, on another window, then press Enter so that the script can continue the installation. [echo] (Re)Start the Tomcat. [echo] Please, make sure that Tomcat is running. Please do it now and press Enter when finished Explanation: The script will ask you to check if Tomcat has finished its startup phase. You can use web browser and connect to your Tomcat's web page or take a look at Tomcat's log file logs/catalina.out (after startup phase you should find there a line 'INFO: Server startup in xxx ms'), then press Enter so that the script can continue the installation Lookup Service Pre-installation [echo] Requirements: [echo] 1. Java 1.5.x [echo] 2. Ant 1.6.x (we're sure you've already got it installed as you run the installation process) [echo] 3. exist DB XML - see Exist DB Installation Guide for LS: [echo] wiki/index.php/exist_db_installation_guide_for_ls [echo] 4. JAVA_HOME environment variable set to your Java directory Do you want to proceed? Just press ENTER to continue. Otherwise CTRL-C stops the process immediately Explanation: The script will ask you to check if you have all the required software pre-installed in the host. If you don't, please install it and then press Enter. Recommendation: We suggest users to change/set up the password for admin user of exist database after the service installation procedure. When the exist has been installed, by default, the password is not set (blank). This way every one can alter the content of the database using exist client application (of course if the firewall does not block open access). Do you want to download Tomcat webserver automatically (say N if you've already got Tomcat)?(y,n) Explanation: Application server Tomcat is a container for the service. It contains the implementation of HTTP protocol which is used by the service to send and receive messages (NMWG). If you already have it in your system you can answer 'n'. Recommendation: Tomcat version is suggested. perfsonar

26 Enter webserver (Tomcat) home directory. If answered Y for previous question, this directory will be the target directory where to install Tomcat. If answered N, Tomcat will be installed there [/usr/local/tomcat_ls] Explanation: If you wanted to download Tomcat, then the script asks you where to put it. Default: /usr/local/tomcat_ls Enter webserver port [8080] Explanation: The script asks for port number which will be used by Tomcat and the service to send and receive messages (HTTP). Default: 8080 Recommendation: If you want to have other port number then you have to setup Tomcat to use this new one as well. To do it open Tomcat's configuration file conf/server.xml and alter the port number in the Connector element :<Connector port="8080" protocol="http/1.1" maxthreads="150" connectiontimeout="20000"redirectport="8443" /> Service directory is suffix is [XML-LS-1.1]. Enter service prefix directory (where target directory XML-LS-1.1 will be installed) Default is [/root/ps/webapps] Explanation: location of the service files to be stored. Default: <current_directory>/webapps [echo] [echo] Your settings: [echo] [echo] Tomcat home directory: [/usr/local/tomcat_ls] [echo] Tomcat address: [5] [echo] Service destination directory: [/root/ps/webapps/xml-ls-1.1-rc6] Proceed with these settings? (y,n) Explanation: The script will ask you to check the selected settings Configuration: [echo] 2. Lookup Information configuration [echo] ===================================== Enter hostname and domainname of your machine. Not localhost. [mycomputer.mydomain.com] Explanation: The script will ask you to enter the hostname and domain name of your machine for Lookup service information. Default: mycomputer.mydomain.com perfsonar

27 Recommendation: This should be your full host.domain, such as alfa.domain.com Lookup Information of service -- access point (URL) [6] Explanation: The script will ask you to enter the url for accessing the Lookup service. Default: Lookup Information of service -- service name [Test Lookup Service] Explanation: The script will ask you to enter the identification name for the Lookup service. Default: Test Lookup Service Lookup Information of service -- service type [LS] Explanation: The script will ask you to enter the service type. Default: LS Lookup Information of service -- service description [Test Lookup Service, perfsonar] Explanation: The script will ask you to enter the service description. Default: Test Lookup Service, perfsonar [echo] 3. LS Storage [echo] ===================================== LS Storage -- XML database type (preferred one is HTTP, because it's much faster)(http,xmlrpc) Explanation: The script will ask you to enter XLM database type that the service will use. LS Storage -- XML database collection [7] Explanation: The script will ask you to enter the location of the XLM database collection, which will be set automatically. Default: Recommendation: Be sure to choose right protocol:// for your previous choice ( for http, exist:xmldb:// for xmlrpc) LS Storage -- XML database username [lookupservice] Explanation: The script asks for xml database user name (it could be for example lookupservice). Default: lookupservice LS Storage -- XML database password [sonar] perfsonar

28 Explanation: The script asks for the password for xml database user (it could be for example sonar). Default: sonar [echo] 4. LS Cleanup [echo] ===================================== LS Cleanup -- enable LS Cleanup (removing old entries when TTL exceeded)?(y,n) Explanation: Choose y if you want to enable LSCleanup, that will remove old entries of services that register with the Lookup Service, if their TTL (time to live) is exceeded. LS Cleanup -- cleanup interval: how often to search old entries in DB [300] (seconds) Explanation: The script asks for how often, in seconds, the Lookup service will search for old entries among the registered services. Default: 300 seconds (5 minutes) LS Cleanup -- TTL of lookup information [3600] (seconds) Explanation: The script asks for the value of the TTL (time to live), that is the time interval in which registered services have to renew their registration information on the Lookup service. If they don't, they will be considered "old entries". Default: 3600 seconds (1 hour) Deployment: Do you want me to start the application server Tomcat for you? (y,n) Explanation: The script can start Tomcat with the service inside, but there is also a possibility to do it manually. Recommendation: If your Tomcat is already running before Deploy step, you should answer 'n'. [echo] Please, insert now the following xml tag 'Context' [echo] into Tomcat configuration file server.xml [echo] (/usr/local/tomcat_ls/conf/server.xml) [echo] inside existing xml tag 'Host': [echo] (You may copy XML part (without [echo]): [echo] <Context path='/xml-ls-1.1-rc6' docbase='/root/ps/webapps/xml-ls- 1.1-RC6'> </Context> [echo] Please, do it now. I will wait for you. Press Return key... perfsonar

29 Explanation: The Context element represents a web application, which is run within a particular virtual host. Each web application is based on a Web Application Archive (WAR) file. Here, we nest a Context element within a HOST element in <TOMCAT>/conf/server.xml. Perform the change on the file in another window, as described, and then press Enter so that the script can continue the installation. [echo] Execute: sh /usr/local/tomcat_ls/bin/startup.sh [echo] Please, make sure that the Tomcat is running. Use the address Press Return key.. Explanation: The script will ask you to check if Tomcat has finished its startup phase. You can use web browser and connect to your Tomcat's web page or take a look at Tomcat's log file logs/catalina.out (after startup phase you should find there a line 'INFO: Server startup in xxx ms'), then press Enter so that the script can continue the installation SSH/Telnet Measurement Point Pre-installation: Enter the name of the service [JAVA-SSHTELNET-MP-1.0]: Explanation: The script asks for symbolic name. This name will be present in the address URL of the service. Default: JAVA-SSHTELNET-MP-1.0 Enter the path where you want to install the service [/root/webapps]: Explanation: Location of the service files to be stored Default: <current_directory>/webapps Do you want me to download and install the application server Tomcat (apache-tomcat-6.0.7) for you? (y,n) Explanation: Application server Tomcat is a container for the service. It contains the implementation of HTTP protocol which is used by the service to send and receive messages (NMWG). If you already have it in your system you can answer 'n'. Recommendation: Tomcat version is suggested. IF answer is 'y': Enter the path for the Tomcat installation: [/root/apachetomcat-6.0.7]: perfsonar

30 Explanation: If you wanted to download Tomcat, then the script asks you where to put it. Default: <current_directory>/apache-tomcat IF answer is 'y' : Enter a URL of the Tomcat download (mirrors can be found on [8] Explanation: If you wanted to download Tomcat, then the script suggests mirror server to be used for downloading. Default: IF answer is 'n' : Enter the path for the Tomcat installation: [/usr/local/tomcat]: Explanation: If you already have Tomcat in your system, the script asks you where it is located. Default: /usr/local/tomcat Enter the port which will be used by your application server Tomcat [8080] Explanation: The script asks for port number which will be used by Tomcat and the service to send and receive messages (HTTP). Default: 8080 Recommendation: If you want to have other port number then you have to setup Tomcat to use this new one as well. To do it open Tomcat's configuration file conf/server.xml and alter the port number in the Connector element :<Connector port="8080" protocol="http/1.1" maxthreads="150" connectiontimeout="20000"redirectport="8443" /> [echo] Make sure that your application server Tomcat has the same port [echo] for the http communication. If not then configure the Tomcat in order [echo] to use this port number. Please do it now and press Enter when finished Configuration: Do you already have a manually edited service.configuration files available? (yes/no) Explanation: The service asks for a previously available configuration file. If you answer yes, the service will ask for the path to the file, and use that one as configuration file. If the answer is negative, a new configuration file will be created based on the answers provided on the following questions. IF answer is 'yes': Please enter the path to this configuration file perfsonar

31 Explanation: One has to enter the path to the manually edited configuration file. The configuration now moves on to the register-functionality-question. IF answer is 'no': Enter the name of the devices one by one, end the list with "STOP"! Explanation: First the names of the devices that have to be supported will be asked. Here you can specify anything you like, but mostly this is the URL or the hostname of the machine. Choose one of the following types of equipment for every device specified previously... 1) Quagga - Password Login (Telnet) 2) Cisco - Password Login (Telnet) 3) Cisco - Password Login (SSH) 4) Cisco - Key-based Login (SSH) 5) Juniper - Password Login (Telnet) 6) Juniper - Password Login (SSH) 7) Juniper - Key-based Login (SSH) Explanation: For every device previously specified, you have to choose one of the provided types of equipment. According to the chosen type of device and access method, some more questions will be asked to configure the URL, port, username, password or key, prompt and access-rate. IF device is of type '1': Please give the url for device: Explanation: Enter the URL for the device specified. Please give the port for device: Explanation: Enter the port for the device specified. Please give the prompt for device: Explanation: Enter the prompt for the device specified. Please give the access rate for device: perfsonar