Changes between Version 19 and Version 20 of LAMP/Tutorial

09/21/10 18:47:43 (11 years ago)



  • LAMP/Tutorial

    v19 v20  
     344We have enabled all the I&M services we want for our slice, but the warning message in red is telling us something. Changes made on the portal are saved locally; the user must explicitly request a ''push'' of the local changes to UNIS. This reduces the load on UNIS and also prevents starting services that have not been fully configured (i.e. our current state for the latency and bandwidth services).
     347=== 7. Configuring NTP servers (optional) ===
     349This is an optional step. The LAMP image has default configuration for the NTP server. However this might not be the best configuration (i.e. best servers for the nodes to query), or you might prefer to access your preferred NTP servers.
     351To configure the NTP server on each node we go to the ''Clock Synchronization'' configuration page. In this example we will configure node1 by clicking the 'Select Closest Servers' button and letting the portal select the servers for us.
     355We can see that the configuration tool was unable to contact the server, and has selected 5 of the closest (in terms of latency) servers to our '''lamp''' node (the node running the Portal, not the node being configured). We then save the configuration and move on to configure the actual I&M services. (We will leave the default configuration on the nodes ''lamp'' and ''node2''.)
     357For more information on the NTP configuration tool, see the corresponding section on the [ pS-Performance Toolkit Tutorial].
     360=== 8. Scheduling Latency and Bandwidth Tests ===
     362To configure the latency and bandwidth tests we want for our slice we go to the ''Scheduled Tests'' configuration page. We will not cover the configuration tool in details in this quick start guide. Please refer to the [ Scheduled Testing section] of the pS-Performance Toolkit Tutorial for a detailed explanation of the configuration tool. We will only cover the modifications done to the interface for LAMP.
     364The first difference is the ability to select which node we want to configure. These tests are always scheduled in a '''star''' configuration, with the node where the tests are being configured as the source endpoint of the test. We will configure the following scheduled tests on our slice:
     366* '''node1:'''