perfSONAR User Q&A and Other Discussion

[Zhi-Wei Lu <>]

Thanks Andy!

 

I have hit with so many issues migrating (with data) from CentOS 6 (PS 4.0.2) -> CentOS7 (PS 4.1.1), I got really confused!

 

It turns out that my maddash on a migrated system is actually working!

http://grx.noc.ucdavis.edu/maddash-webui

 

Throughput tests on un-migrated systems are working properly, getting both forward and reverse tests. However, for migrated system (4.1.1), I got very inconsistent results, skipped tests, no reverse results etc.  

 

I need to carefully read and digest the documentation you provided.  Thanks again!

 

Zhi-Wei Lu,

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

 

From: Andrew Lake <>
Sent: Monday, September 10, 2018 12:36 PM
To: Zhi-Wei Lu <>
Cc:
Subject: Re: [perfsonar-user] Setting up maddash mesh on a CentOS7 perfsonar 4.1.1 systems

 

Hi,

 

I am having a little trouble following as it sounds like maybe you are mixing up psconfig and pscheduler. Fresh installs of 4.1.1 do not contain BWCTL, so if you have other hosts that are still on 3.5.x or older, your tests to them will not work out of the box. To make those tests work you need to either 1) upgrade the old systems or 2) on the 4.1.1 systems install the perfsonar-bwctl-compat package as described in http://docs.perfsonar.net/manage_update.html#bwctl-support

 

As for you dashboard, if you updated an existing dashboard system it should have migrated all your files on update to 4.1.1. If you did a fresh install of maddash and perfsonar-psconfig-maddash, then you just need to point it at your mesh file using "psconfig remote add URL" as described in http://docs.perfsonar.net/psconfig_maddash_agent.html#remote-templates. See the entirety of that page for full details on the types of things you can do with the pSconfig MaDDash agent. 

 

As with your measurement hosts, you can point at your existing central MeshConfig JSON file and it will be able to read it. If you want to convert to the new pSConfig format see http://docs.perfsonar.net/psconfig_meshconfig_migrate.html#translating-an-old-meshconfig-json-file-to-psconfig-format, but this is not required to get things working.

 

Thanks,
Andy

 

 

 

On Mon, Sep 10, 2018 at 12:59 AM, Zhi-Wei Lu <> wrote:

Hi all,

 

Now that I have migrated a few of our perfsonar boxes to CentOS7 with perfsonar 4.1.1, I need to convert our small maddash grid on the new systems.  Since our new systems do not have bwctl daemon running, tests between the new hosts (CentOS7 perfsonar 4.1.1) do not work properly for thoroughputs. 

 

Since we have a small grid, I would like to set up a new maddash (2.0.3) grid with the new pscheduler format, I just wonder if there is any example file and guide that I can follow.  I set up the old grid a while ago and the only guide for maddash (1.1) setup was for the old bwctl format.

 

This page talks about migration of maddash, but I am still very lost at details

http://docs.perfsonar.net/release_candidates/4.1b1/psconfig_meshconfig_migrate.html

 

I would love to hear someone who has successfully established the maddash under the new pscheduler format, I don't want to install and enable bwctl, since it is deprecated.

 

Thank you.

Zhi-Wei Lu

 

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user