perfsonar-user - [perfsonar-user] MaDDash node labels for hosts in multiple meshes/dashboards
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: "Christopher J. Tengi" <>
- To: perfsonar-user <>
- Subject: [perfsonar-user] MaDDash node labels for hosts in multiple meshes/dashboards
- Date: Fri, 11 Dec 2015 19:18:07 +0000
- Accept-language: en-US
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
- [perfsonar-user] MaDDash node labels for hosts in multiple meshes/dashboards, Christopher J. Tengi, 12/11/2015
- Re: [perfsonar-user] MaDDash node labels for hosts in multiple meshes/dashboards, Andrew Lake, 12/11/2015
- Re: [perfsonar-user] MaDDash node labels for hosts in multiple meshes/dashboards, Christopher J. Tengi, 12/11/2015
- Re: [perfsonar-user] MaDDash node labels for hosts in multiple meshes/dashboards, Andrew Lake, 12/11/2015
Archive powered by MHonArc 2.6.16.