perfSONAR User Q&A and Other Discussion

["Christopher J. Tengi" <>]

Yup:

https://perfsonar-ma.princeton.edu/mesh.json
https://perfsonar-ma.princeton.edu/mesh-ivyplus.json

/Chris


> On Dec 11, 2015, at 3:08 PM, Andrew Lake 
> <>
>  wrote:
> 
> Hi,
> 
> I can’t say that I have tried this, but it’s possible when the MeshConfig 
> software generates the MaDDash configuration the second name overwrites the 
> first. Are your Mesh json files at a URL I can access to test?
> 
> Thanks,
> Andy
> 
> 
> 
> On December 11, 2015 at 2:18:39 PM, Christopher J. Tengi 
> ()
>  wrote:
> 
>> Following up from my last question to the list, I have built a mesh for a 
>> few internal end-points and a bunch of external end-points. This new mesh 
>> has 2 nodes in common with the Princeton-only mesh that was already up and 
>> running. Because the new mesh is intended for an external-to-Princeton 
>> audience, the “description” in the <host> block for these 2 nodes has a 
>> value other than the unqualified hostname that we use for the 
>> Princeton-only mesh. 
>> 
>> The internal mesh results in the “Princeton” dashboard and the external 
>> mesh results in the “IvyPlus” dashboard. After I brought up the 2nd mesh 
>> and dashboard, I was surprised to see that the dashboard names of the 2 
>> nodes in common were now the values from the external mesh. For the 
>> internal mesh, they are defined as perfsonar-87prospect and 
>> perfsonar-hpcrc, but for the external mesh they are “Princeton Net Core” 
>> and “Princeton HPCRC,” respectively. 
>> 
>> Should MaDDash keep the namespaces for the Dashboards separate, or does 
>> the information in the last <mesh> block in the GUI configuration file 
>> win? The latter is what I’m seeing here. 
>> 
>> Thanks, 
>> /Chris