Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Setting up maddash mesh on a CentOS7 perfsonar 4.1.1 systems

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Setting up maddash mesh on a CentOS7 perfsonar 4.1.1 systems


Chronological Thread 
  • From: Mark Feit <>
  • To: Zhi-Wei Lu <>, "" <>
  • Subject: Re: [perfsonar-user] Setting up maddash mesh on a CentOS7 perfsonar 4.1.1 systems
  • Date: Mon, 10 Sep 2018 19:35:05 +0000
  • Accept-language: en-US
  • Authentication-results: ucdavis.edu; dkim=none (message not signed) header.d=none;ucdavis.edu; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:YvFiLxFpRRSims5u0/V9i51GYnF86YWxBRYc798ds5kLTJ7yo86wAkXT6L1XgUPTWs2DsrQY07WQ6/iocFdDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXdrXKo8DEdBAj0OxZrKeTpAI7SiNm82/yv95HJbAhEmDiwbaluIBmqsA7cqtQYjYx+J6gr1xDHuGFIe+NYxWNpIVKcgRPx7dqu8ZBg7ipdpesv+9ZPXqvmcas4S6dYDCk9PGAu+MLrrxjDQhCR6XYaT24bjwBHAwnB7BH9Q5fxri73vfdz1SWGIcH7S60/VDK/5KlpVRDokj8KOT4n/m/Klsx+gqFVoBO9qBNw2IPbep2ZNP9kc6/BYd8XR2xMVdtRWSxbBYO8apMCAe0bMuZCrIn2ulsAogW/BQmwGejizTpIhnHo0q07z+QsCgDG3Ao8H90QqnTUqsv6NLsMXeyv0qbH0CjDYupQ1Dzg5obIdRUhruuNXbJ2acfR1FUgGB7fgVWOqIzlJCmZ2foQvGiG6edrSOGhi3Y/pg1vvzSix90gh4fXio4P11zJ9jl1zJwrKdGmUEJ3fMKoHZhKuyyVN4Z6WMAvT3xytCony7ALuIa3fCYUx5kk2xLSbvmKfJSI7xLtWuucJC13iXJmdb+/ghu/81Wsx+7iWcSx1FtGsjZJncLKu3sQzRLc8NKHReF4/kq52TaAyQTT6uZcLE4siafVLIItzqApmpQOqUrPAzb6mELtg6CIbEkk/fWo6/j8bbXhu5+cMZJ7hhvmMqQ0ncy/Hfo3PRQSX2ia/uS80qfv/UrkQLVWiv02la7ZsJPAKcsHoa65BhdZ0ocl6xmhEzeryMoUkWQGIV5fdh+LkZLlN0zNLfzkF/uznUqgnC9ux//cP73hBpvNLmLEkLfkZbt97kBcxxQyzdBD/J9UC7cBIO7tVU/rstzXEAM5PxKuz+n5Fdp9y5sSWXiTDa+BLKPSrViI6/o3I+aSfo8Vti39K/8j5/H0l381gEIdfbK30psNc324GvVmI16FYXr3nNsNC2YKvgwiTOP0kl2CVyBcZ2qsU64m+D40FZ+mXs//QdWfgL3E4yq6VrlLLjRUFVSROWrje4yaWuxKZS6PdIsp2CQJT7a6TIkoz1SzrwLg47thMufO/CAE79Tu2MU/r7nLmAs87jtyBt7YznqAVUl1mH8FXTk7wPo5rEBgnASty6991tlRD98byf5ITk9uMJDRzvBSCtbuVxjHc8vTDluqX4P1UnkKUtstzopWMA5GENK4g0WbhXD4CqIJl7GNGJ0/+77d2H60Pctm1nLaz/B71Qs7ScdGK2y9wKNz6lubC43IlhCfkKCnPeQZ0TXW/WiOhWyJoAlDUQF2XKmEOBJXZkbfodnjoE+XSbioBOc6OQdI18+ZbKZGd46hgVBPXvy2PtPYbiq4kHuxAhDdwLSKYcLqdmwR0T+bBlIDllUS+2qLLw4zGn3nrm7DXzE=
  • Spamdiagnosticoutput: 1:0

Zhi-Wei Lu writes:

 

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. 

 

Throughput is one of two tests that require one perfSONAR node to talk to another to schedule a run.  (The other is simplestream, which is used for development and troubleshooting.)  One of the things included in pScheduler as shipped with perfsonar 4.x is some backward compatibility code that would allow throughput tests to transparently fall back to BWCTL if pScheduler can’t be reached.  If something is preventing access to the HTTPS port, the fallback happens quietly and you wouldn’t have noticed it.  With BWCTL gone on your systems, it fails entirely.

 

The way to check that pScheduler on one host can talk to another host is with the “pscheduler ping other-host.ucdavis.edu” command.  This does a HTTPS request to the pScheduler API and is a good indicator of whether or not connectivity and the API are working.  You can also do a more-detailed check with “pscheduler troubleshoot other-host.ucdavis.edu”.

 

The backward-compatibility code is still present in 4.1.x and will be removed in the first feature release after February, 2019.

 

 

I’m not the right person to ask about migrating from MeshConfig to pSConfig, so I’ll let someone else cover that.

 

--Mark

 


Archive powered by MHonArc 2.6.19.

Top of Page