perfsonar-user - [perfsonar-user] Others with MaDDash grids probably have this question.
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Phil Reese <>
- To: "" <>
- Subject: [perfsonar-user] Others with MaDDash grids probably have this question.
- Date: Tue, 23 Apr 2024 12:35:45 -0700
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=stanford.edu; dmarc=pass action=none header.from=stanford.edu; dkim=pass header.d=stanford.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ygscaEGPwkQj+OCakbTFQbbjctaIGPLxjnSvG1Rpjz4=; b=AmHRGMTL4YvojdE7wtQXgdUzrKxY0aRcwzARUowQa0Ucba1p07lJK+uORtXH6ADsKrGUxTfxwHrB/Ff2IdVUhLYGXTVa99JohhdLQMCawXup28xiBJ2fElfYhemMgUjhtns/h8X5Q4Kek1Ivk7yHnOcgyordRB3rUago2AQRrdrCyr3Q2SGafp7UjLeAVrsJ7d7DO4bOOMelZvcR+KZXz4j+rfeXLlQi2wF4G/Bxb7CpcxuvuxR2r71ivW7WRDDvrxbl5EojqWSnQqFktjEfTeoqS6y2MWmyt7SuUoeIRjCeeAEGY1NMecuim9xKFvaZ2oDZU0AGJ/jUPwMrtYrXpw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EGustTtvJ1PmmKnBaVvT8kkMg8uCnsBLdel2s3cAa/t9ceAGe8HL0D9nGMgdFmdOJj1uneFfqAj1g6moS1Mi4u2SD9zsaPY3W1sc2ZqvvbVtovLogbeqGcTWLBFcxv6cNEWJ5HE0eOQ+SXkE4C76wj9IMj+jrF3qR2qRAwT2vVQZ9QNyya3HVERt0LczJ+msOeh2+N+5QTgvq8gP996ha7WUBs/rDordo3UbBtB+UuoW38P9C2nkZUnkKL6R4zWVtP4D72CcmCVdz91jfUdo3ZBIK9pLdT0ZVlqtN6aZBlcZXcQSXpOTkWzParotDNUPS87YIG/Gsi5EE9ver/hr5Q==
This note is probably for Andy but thought I'd share what I've learned and what questions it has raised.
-----
My original production Maddash Grid is still running and is using v4.3.1. When the initial PS5 came out it had a soon to be deprecated version of Maddash. I didn't want to touch the production but I did want to put the v5 version to work.
I kept the testpoints untouched (and they have moved to v5.0.8 via autoupdate) I did update the production json file. Basically, I added this stanza:
"_meta": {
"esmond_url": "https://ps5-MaDDash.host.edu/esmond/perfsonar/archive/";
Happily, this kept the existing archive happy and allowed a V5MaDDash server to interact with the opensearch data store. For the last several months I've had one MaDDash at v4.3.1 and one at v5.0.x, mirrors of each other.
With PS5.1beta released I wondered if I could keep using this process?
It mostly does work!
I built an Archive v5.1, I then took down the V5MaDDash server, and renamed the new V51Archive system to the old name and let it come up.
My results are that the 'PS Main' dashboard appears to be working just fine. The ' perfSONAR Endpoint Pair Explorer' link from that main dashboard works well too.
What isn't working is 'All perfSONAR Measurements' dashboard. It shows the tests areas, but has a label of 'No Data' in each area. The 'ghost' subwindow is much bigger so some part of Grafana knows there are many Testpoint hosts.
The question is whether there is anything that can be done to update the database or transform the older database to the new version's db format? The data seems to be there but not in the locations that the new dashboard needs.
It might (probably) isn't worth the work to resolve, and I understand that, but it is so close I wanted to at least ask the expert's opinion.
- [perfsonar-user] Others with MaDDash grids probably have this question., Phil Reese, 04/23/2024
Archive powered by MHonArc 2.6.24.