Add perfSONAR Toolkit (RPM) installation guide#55
Merged
ShawnMcKee merged 1 commit intomasterfrom Dec 10, 2025
Merged
Conversation
This commit adds a comprehensive installation guide for perfSONAR Toolkit using RPM packages, complementing the existing container-based Testpoint guide. New content: - docs/personas/quick-deploy/install-perfsonar-toolkit.md: Complete toolkit installation guide adapted from testpoint guide with RPM-specific instructions * Step 2: DNF repo configuration and perfsonar-toolkit bundle installation * Step 5: Native service management, web UI setup, and dnf-automatic updates * Steps 6-8: Adapted all container commands to native systemctl/filesystem access Updated documentation: - docs/personas/quick-deploy/landing.md: Added deployment type comparison (Testpoint vs Toolkit) with feature lists and links to both guides - mkdocs.yml: Restructured navigation with 'Installation Guides' submenu - docs/index.md: Updated to mention both deployment options - docs/perfsonar-in-osg.md: Added links to both installation guides - docs/perfsonar/deployment-models.md: Enhanced Toolkit vs Testpoint comparison with installation guide links - docs/perfsonar/installation.md: Updated legacy notice to reference both guides Key differences in toolkit guide: - RPM package installation instead of containers - Local web UI at https://hostname/toolkit - Local measurement archive (OpenSearch + Logstash) - Native systemd service management - dnf-automatic for updates instead of container image pulls - All /opt/perfsonar-tp paths changed to /opt/perfsonar-toolkit Site builds successfully with no rendering issues (verified with check_site_for_backticks.py). Addresses the need for clear documentation of both deployment models, allowing sites to choose between lightweight container-based testpoints and full-featured RPM-based toolkit installations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR adds a comprehensive installation guide for perfSONAR Toolkit using RPM packages, complementing the existing container-based Testpoint guide. Sites can now choose between two deployment models based on their requirements.
What's New
New Documentation
docs/personas/quick-deploy/install-perfsonar-toolkit.md(1,305 lines)dnf install perfsonar-toolkithttps://hostname/toolkitUpdated Documentation
docs/personas/quick-deploy/landing.md: Added deployment type comparison with feature listsmkdocs.yml: Restructured navigation with 'Installation Guides' submenudocs/index.md: Updated to mention both deployment optionsdocs/perfsonar-in-osg.md: Added links to both installation guidesdocs/perfsonar/deployment-models.md: Enhanced Toolkit vs Testpoint comparisondocs/perfsonar/installation.md: Updated legacy notice to reference both guidesKey Differences: Testpoint vs Toolkit
https://hostname/toolkitStructure
The toolkit guide follows the same 8-step structure as testpoint:
Testing
✅ Site builds successfully:
check_site_for_backticks.py --buildreturns OK✅ No visible backticks in generated HTML
✅ All navigation links updated and working
✅ 1,418 insertions across 7 files
Reviewers
Please review:
Related Issues
This addresses the need for clear documentation of both deployment models, allowing sites to choose the appropriate option based on their requirements (lightweight testpoint vs full-featured toolkit).