perfSONAR User Q&A and Other Discussion

[Renan PHILIPPE <>]

Hello Szymon,

Thanks for this quicky answer :-)

So I did what you asked to me, I added measurements archive parts in the mesh configuration.

My is called confmesh.conf and stored in /etc/maddash/(in your previous mail, you say that it was present in /etc/maddash/maddash-server, I don't know if it's important)

This one has been attached in this email.

I have generated a new JSON successfully.

Now, the command  /usr/lib/perfsonar/bin/generate_gui_configuration don't return me any errors and the dashboard has been updated !!!

Take a look ;-)

Thanks a lot,

Regarding the second issue, I'm still not able to generate the fesh configuration to be published.

Below, the error message:

[root@ix1-pp-c6-perfsonar-01 opt]# /usr/lib/perfsonar/bin/generate_configuration
Use of uninitialized value $mesh_id in substitution (s///) at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/MeshConfig/Generators/perfSONARRegularTesting.pm line 157.
[root@ix1-pp-c6-perfsonar-01 opt]#

Thanks for your help,

Renan.

---

De: "Szymon Trocha" <>
À: "renan philippe" <>
Cc:
Envoyé: Vendredi 24 Mars 2017 12:22:04
Objet: Re: [perfsonar-user] Triying to configure Centralil configuration for Beacon and Maddash

Hi Renan,

W dniu 24.03.2017 o 11:28, Renan PHILIPPE pisze:

Both, Dashboard and configuration beacon are based on the same JSON file, correct?

I have created a JSON file called confmesh.json available on https://193.49.159.188/confmesh.json.

You can see in it that I created 3 entry for hosts(193.49.159.188 on which I have installed persfonar and maddash, 195.221.27.242 which the remote beacon of a partner, and the last called th2-pp-c6-perfsonar-01.renater.fr which will be one on my futur beacon to deployed)

When I execute the generation of configuration for dashboard and configuration to be published for beacon, I have the following errors.

• [root@ix1-pp-c6-perfsonar-01 /]# /usr/lib/perfsonar/bin/generate_gui_configuration
  2017/03/24 11:24:04 (135313) ERROR> GUIAgent.pm:285 perfSONAR_PS::MeshConfig::GUIAgent::__generate_maddash_config - Problem generating maddash configuration: Couldn't find ma for host: perfSONAR_PS::MeshConfig::Config::Address=HASH(0x43877e0) at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/MeshConfig/Generators/MaDDash.pm line 291.
  2017/03/24 11:24:04 (135313) ERROR> GUIAgent.pm:231 perfSONAR_PS::MeshConfig::GUIAgent::__configure_guis - Problem generating maddash configuration: Problem generating maddash configuration: Couldn't find ma for host: perfSONAR_PS::MeshConfig::Config::Address=HASH(0x43877e0) at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/MeshConfig/Generators/MaDDash.pm line 291.
  [root@ix1-pp-c6-perfsonar-01 /]#

your json file is missing "measurement_archives" section. json file is generated on a central server (Maddash server in your case) based on your mesh description in /etc/maddash/maddash-server/YOUR_MESH_mesh_config.conf (using /usr/lib/perfsonar/bin/build_json -o /YOUR_JSON_LOCATION/YOUR_JSON_FILE.json /etc/maddash/maddash-server/YOUR_MESH_mesh_config.conf). Can you show the YOUR_MESH_mesh_config.conf file?

Then you generate Maddash GUI configuration with /usr/lib/perfsonar/bin/generate_gui_configuration which result in .yaml file consumed by GUI

To make things easier before generating GUI config it's good to clear th default yaml file (/etc/maddash/maddash-server/maddash.yaml) and put there just this content:

# Set the directory where the database will be stored
database: /var/lib/maddash/
##
# Set the host where the REST server listens
serverHost: "localhost"
##
# Activate http and set the port where it listens
http:
    port: 8881
serverHost: localhost


Regards,

-- 
Szymon Trocha

Poznań Supercomputing & Networking Center
Tel. +48 618582022 ::: http://noc.pcss.pl

<administrator>
  name       Renan Philippe
  email      

</administrator>

<organization>
    description     Renater

    <site>
        <location>
                city     France
                state    Paris
                latitude   48.881324
                longitude  2.311353
        </location>
        <host>
              description Renater Beacon Perfsonar IX
              address 193.49.159.188
              <measurement_archive>
               type        traceroute
               read_url    http://193.49.159.188/esmond/perfsonar/archive
               write_url   http://193.49.159.188/esmond/perfsonar/archive
              </measurement_archive>

              <measurement_archive>
               type        perfsonarbuoy/owamp
               read_url    http://193.49.159.188/esmond/perfsonar/archive
               write_url   http://193.49.159.188/esmond/perfsonar/archive
              </measurement_archive>

              <measurement_archive>
               type        perfsonarbuoy/bwctl
               read_url    http://193.49.159.188/esmond/perfsonar/archive
               write_url   http://193.49.159.188/esmond/perfsonar/archive
              </measurement_archive>

              <measurement_archive>
               type       pinger
               read_url   http://193.49.159.188/esmond/perfsonar/archive
               write_url  http://193.49.159.188/esmond/perfsonar/archive
              </measurement_archive>
        </host>
    </site>

    <site>
        <location>
                city     France
                state    Paris
                latitude   48.855915
                longitude  2.383681
        </location>
        <host>
              description Renater Beacon Perfsonar TH2
              address th2-pp-c6-perfsonar-01.renater.fr

              <measurement_archive>
               type        traceroute
               read_url    
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
               write_url   
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
              </measurement_archive>


              <measurement_archive>
               type        perfsonarbuoy/owamp
               read_url    
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
               write_url   
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
              </measurement_archive>

              <measurement_archive>
               type        perfsonarbuoy/bwctl
               read_url    
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
               write_url   
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
              </measurement_archive>

              <measurement_archive>
               type       pinger
               read_url   
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
               write_url  
http://th2-pp-c6-perfsonar-01.renater.fr/perfsonar/archive
              </measurement_archive>
        </host>
    </site>

    <site>
        <host>
              description Crihan Beacon calcul-sonde.crihan.fr
              address calcul-sonde.crihan.fr

              <measurement_archive>
               type        traceroute
               read_url    
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
               write_url   
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
              </measurement_archive>


              <measurement_archive>
               type        perfsonarbuoy/owamp
               read_url    
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
               write_url   
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
              </measurement_archive>

              <measurement_archive>
               type        perfsonarbuoy/bwctl
               read_url    
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
               write_url   
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
              </measurement_archive>

              <measurement_archive>
               type       pinger
               read_url   
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
               write_url  
http://calcul-sonde.crihan.fr/esmond/perfsonar/archive
              </measurement_archive>
        </host>
    </site>
</organization>

<test_spec bwctl_renater>
  type              perfsonarbuoy/bwctl  # Perform a bwctl test (i.e. 
achievable bandwidth)
  tool              bwctl/iperf3         # Use 'iperf' to do the bandwidh test
  protocol          tcp                  # Run a TCP bandwidth test
  interval          21600                # Run the test every 6 hours
  duration          20                   # Perform a 20 second test
  force_bidirectional 1                  # do bidirectional test
  random_start_percentage 10             # randomize start time
  omit_interval     5                    # ignore first few seconds of test
</test_spec>

<test_spec owamp_renater>
  type              perfsonarbuoy/owamp  # Perform a constant low-bandwidth 
OWAMP test
  packet_interval   0.1                  # Send 10 packets every second (i.e. 
pause 0.1 seconds between each packet)
  loss_threshold    10                   # Wait no more than 10 seconds for a 
response
  session_count     10800                # Refresh the test every half hour 
(once every 18000 packets)
  sample_count      600                  # Send results back every 60 seconds 
(once every 600 packets)
  packet_padding    0                    # The size of the packets (not 
including the IP/UDP headers)
  bucket_width      0.0001               # The granularity of the measurements
  force_bidirectional 1                  # do bidirectional test
</test_spec>


<group renater_bwctl_group>
    type       mesh

    member     th2-pp-c6-perfsonar-01.renater.fr
    member     193.49.159.188
    member     calcul-sonde.crihan.fr
</group>

<group renater_owamp_group>
    type       mesh

    member     th2-pp-c6-perfsonar-01.renater.fr
    member     193.49.159.188
    member     calcul-sonde.crihan.fr
</group>

<test>
  description       Example Throughput Testing
  group             renater_bwctl_group
  test_spec         bwctl_renater
</test>

<test>
  description       Example OWAMP Testing
  group             renater_owamp_group
  test_spec         owamp_renater
</test>