Repository navigation
deploy-guide: drop the archived node-image - #1145
Merged
Merged
Conversation
The osism/node-image repository is archived. Its README says the images are no longer used and that nodes are provisioned with the MetalBox instead, but the deploy guide still recommends the node image ISOs as the preferred way to provision the initial nodes and refers to them in the manager and bootstrap steps. Remove the node-image section from the provisioning page and point to the MetalBox node deployment for automated provisioning, with the manual installation as the alternative. Drop the node-image notes from the manager and bootstrap pages. They were the only place that explained the user osism in the examples, and the remaining text said a manual installation usually has the user ubuntu, which contradicts the manual provisioning section. State instead that the manual provisioning creates the user osism. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Roger Luethi <luethi@osism.tech>
✅
|
| Descriptor | Linter | Files | Fixed | Errors | Max errors | Warnings | Elapsed time |
|---|---|---|---|---|---|---|---|
| ✅ ACTION | actionlint | 5 | 0 | 0 | 0.05s | ||
| ✅ JSON | jsonlint | 4 | 0 | 0 | 0.07s | ||
| ✅ JSON | prettier | 4 | 0 | 0 | 0.23s | ||
| ✅ JSON | v8r | 4 | 0 | 0 | 8.4s | ||
| ✅ MARKDOWN | markdownlint | 184 | 0 | 0 | 2.87s | ||
| ✅ MARKDOWN | markdown-table-formatter | 184 | 0 | 0 | 0.39s | ||
| ✅ REPOSITORY | betterleaks | yes | no | no | 0.58s | ||
| ✅ REPOSITORY | checkov | yes | no | no | 15.71s | ||
| ✅ REPOSITORY | git_diff | yes | no | no | 0.04s | ||
| ✅ REPOSITORY | secretlint | yes | no | no | 1.07s | ||
| ✅ REPOSITORY | trufflehog | yes | no | no | 2.43s | ||
| ✅ SPELL | codespell | 194 | 0 | 0 | 0.5s | ||
| lychee | 194 | 7 | 0 | 21.2s | |||
| ✅ YAML | prettier | 6 | 0 | 0 | 0.36s | ||
| ✅ YAML | v8r | 6 | 0 | 0 | 5.49s | ||
| ✅ YAML | yamllint | 6 | 0 | 0 | 0.34s |
Detailed Issues
⚠️ SPELL / lychee - 7 errors
📝 Summary
---------------------
🔍 Total.........1304
🔗 Unique.........958
✅ Successful....1174
⏳ Timeouts.........3
🔀 Redirected.......9
👻 Excluded.......120
❓ Unknown..........0
🚫 Errors...........7
⛔ Unsupported......7
Errors in .claude/skills/security-advisory/reference/style.md
[ERROR] file://.claude/skills/guides/operations-guide/openstack/security-updates.md (at 189:3) | File not found. Check if file exists and path is correct
Errors in .claude/skills/security-advisory/SKILL.md
[400] https://cveawg.mitre.org/api/cve/ (at 16:18) | Rejected status code: 400 Bad Request
[404] https://raw.githubusercontent.com/osism/ (at 17:18) | Rejected status code: 404 Not Found
[400] https://registry.osism.tech/service/token (at 18:19) | Rejected status code: 400 Bad Request
Errors in docs/concepts/cluster-network.md
[TIMEOUT] https://stordis.com/basic-configuration-and-management-of-sonic-devices/ (at 196:3) | Request timed out
[TIMEOUT] https://stordis.com/bgp-unnumbered-in-enterprise-sonic/ (at 66:1) | Request timed out
[TIMEOUT] https://stordis.com/deploying-bgp-underlay-in-enterprise-sonic/ (at 197:3) | Request timed out
Errors in docs/guides/developer-guide/style-guide.md
[ERROR] https://wiki.openstack.org/wiki/GitCommitMessages (at 79:1) | Network unreachable. Check internet connection or VPN settings
Errors in docs/release-notes/osism-10.md
[ERROR] https://docs.openstack.org/releasenotes/ironic/2025.1.html (at 1044:11) | Connection closed before response completed
Errors in docs/release-notes/osism-7.md
[ERROR] https://docs.openstack.org/releasenotes/horizon/2023.2.html (at 990:12) | Connection closed before response completed
Hint: Followed 9 redirects. You might want to consider replacing redirecting URLs with the resolved URLs. Use verbose mode (`-v`/`-vv`) to see redirection details.
See detailed reports in MegaLinter artifacts
Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)
- Documentation: Custom Flavors
- Command:
npx mega-linter-runner@10.2.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository
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.
The osism/node-image repository is archived. Its README says the images are no longer used and that nodes are provisioned with the MetalBox instead. The deploy guide still recommends the node image ISOs as the preferred way to provision the initial nodes, and refers to them in the manager and bootstrap steps.
osismin the examples, and the remaining text said a manual installation usually has the userubuntu, which contradicts the manual provisioning section. The notes now say that the manual provisioning creates the userosism.🤖 Generated with Claude Code