deploy-guide: document the seed container#1003
Open
ideaship wants to merge 2 commits into
Open
Conversation
✅
|
| Descriptor | Linter | Files | Fixed | Errors | Warnings | Elapsed time |
|---|---|---|---|---|---|---|
| ✅ ACTION | actionlint | 4 | 0 | 0 | 0.02s | |
| ✅ JSON | jsonlint | 4 | 0 | 0 | 0.08s | |
| ✅ JSON | prettier | 4 | 0 | 0 | 0.37s | |
| ✅ JSON | v8r | 4 | 0 | 0 | 9.06s | |
| markdownlint | 160 | 4 | 0 | 2.91s | ||
| markdown-table-formatter | 160 | 1 | 0 | 0.46s | ||
| ✅ REPOSITORY | checkov | yes | no | no | 19.87s | |
| ✅ REPOSITORY | git_diff | yes | no | no | 0.07s | |
| ✅ REPOSITORY | secretlint | yes | no | no | 1.72s | |
| ✅ REPOSITORY | trufflehog | yes | no | no | 3.85s | |
| ✅ SPELL | codespell | 169 | 0 | 0 | 0.69s | |
| lychee | 169 | 2 | 0 | 40.79s | ||
| ✅ YAML | prettier | 5 | 0 | 0 | 0.42s | |
| ✅ YAML | v8r | 5 | 0 | 0 | 5.99s | |
| ✅ YAML | yamllint | 5 | 0 | 0 | 0.58s |
Detailed Issues
⚠️ SPELL / lychee - 2 errors
📝 Summary
---------------------
🔍 Total..........921
🔗 Unique.........745
✅ Successful.....845
⏳ Timeouts........13
🔀 Redirected......41
👻 Excluded........61
❓ Unknown..........0
🚫 Errors...........2
⛔ Unsupported......2
Errors in docs/guides/configuration-guide/openstack/ceilometer.md
[ERROR] https://docs.openstack.org/ceilometer/latest/admin/index.html (at 7:3) | Connection closed before response completed
Errors in docs/guides/configuration-guide/openstack/designate.md
[ERROR] https://docs.openstack.org/designate/latest/admin/config.html (at 9:3) | Connection closed before response completed
Errors in docs/guides/developer-guide/zuul.md
[TIMEOUT] https://zuul.services.osism.tech/t/osism/builds?project=osism%2Fcontainer-image-ceph-ansible&pipeline=periodic-daily&skip=0 (at 366:3) | Request timed out
[TIMEOUT] https://zuul.services.osism.tech/t/osism/builds?project=osism%2Fcontainer-image-kolla-ansible&pipeline=periodic-daily&skip=0 (at 367:3) | Request timed out
[TIMEOUT] https://zuul.services.osism.tech/t/osism/builds?project=osism%2Fcontainer-image-osism-ansible&pipeline=periodic-daily&skip=0 (at 368:3) | Request timed out
[TIMEOUT] https://zuul.services.osism.tech/t/osism/builds?project=osism%2Fcontainer-images-kolla&pipeline=periodic-midnight&skip=0 (at 369:3) | Request timed out
[TIMEOUT] https://zuul.services.osism.tech/t/osism/builds?project=osism%2Ftestbed&pipeline=periodic-daily&skip=0 (at 370:3) | Request timed out
[TIMEOUT] https://zuul.services.osism.tech/t/osism/buildsets?pipeline=label (at 26:26) | Request timed out
[TIMEOUT] https://zuul.services.osism.tech/t/osism/status (at 14:1) | Request timed out
Errors in docs/index.md
[TIMEOUT] https://tldp.org/ (at 62:1) | Request timed out
Errors in docs/testbed/appendix.mdx
[TIMEOUT] https://regio.digital/ (at 14:58) | Request timed out
[TIMEOUT] https://zuul.services.osism.tech/t/osism/builds?project=osism%2Ftestbed&skip=0 (at 164:21) | Request timed out
Errors in docs/testbed/index.md
[TIMEOUT] https://regio.digital/ (at 20:67) | Request timed out
Errors in docs/testbed/prerequisites.mdx
[TIMEOUT] https://regio.digital/ (at 36:41) | Request timed out
Errors in docs/testbed/usage.mdx
[TIMEOUT] https://regio.digital/ (at 23:20) | Request timed out
Hint: Followed 41 redirects. You might want to consider replacing redirecting URLs with the resolved URLs. Use verbose mode (`-v`/`-vv`) to see redirection details.
⚠️ MARKDOWN / markdown-table-formatter - 1 error
1 files contain markdown tables to format:
- docs/guides/developer-guide/retiring-openstack-releases.md
⚠️ MARKDOWN / markdownlint - 4 errors
docs/guides/developer-guide/retiring-openstack-releases.md:181:450 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/guides/developer-guide/retiring-openstack-releases.md:181:535 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/guides/developer-guide/retiring-openstack-releases.md:183:417 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
docs/guides/developer-guide/retiring-openstack-releases.md:183:502 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
Notices
📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)
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@9.5.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_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository
25c6aa8 to
aa51ffb
Compare
This was referenced Jun 22, 2026
The seed container (registry.osism.tech/osism/seed) has so far been undocumented; the deploy guide only described installing the required packages on the seed node by hand. Document the container as the first option, requiring nothing but Docker (or Podman) on the seed node, and keep the manual package installation as the second option. The seed image is published as a rolling latest tag and rebuilt nightly from the OSISM collections' main branches; there are no versioned tags. Point to this maintained location -- quay.io/osism/seed has not been updated since 2025-02-17 and must no longer be used. Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Roger Luethi <luethi@osism.tech>
run.sh automatically runs the playbooks inside the osism/seed container when a container engine (Docker or Podman) is present on the seed node, bind-mounting the configuration repository. With SEED_CONTAINER=auto (the default) there is nothing extra to set up, so every Manager step is the same plain ./run.sh <playbook> whether it runs in the container or in a local venv. Document the two knobs a deployer actually chooses -- SEED_CONTAINER (auto/true/false) and CONTAINER_ENGINE (docker/podman) -- plus SEED_CONTAINER_MOUNT_OPTS for Podman on enforcing SELinux. The image reference and pull policy default correctly to registry.osism.tech/osism/seed:latest; the SEED_CONTAINER_REGISTRY, SEED_CONTAINER_IMAGE, SEED_CONTAINER_TAG and SEED_CONTAINER_PULL overrides are only mentioned for offline or local-build setups. Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Roger Luethi <luethi@osism.tech>
aa51ffb to
8e4be54
Compare
Contributor
|
LGTM, but we should merge the direct dependencies on the script refactoring first i guess. |
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.
Summary
Documents the seed container (
registry.osism.tech/osism/seed) in the deploy guide, which was previously undocumented — the guide only described installing packages on the seed node by hand.seed.md: presents the seed container as Option 1 (needs nothing but Docker/Podman on the seed node) and keeps the manual package installation as Option 2. Points to the maintained image location and notes thatquay.io/osism/seedis no longer updated.manager.md: explains thatrun.shautomatically runs the playbooks inside the seed container when a container engine is present (SEED_CONTAINER=auto, the default), so every Manager step stays a plain./run.sh <playbook>. Documents the two knobs a deployer actually chooses (SEED_CONTAINER,CONTAINER_ENGINE) plusSEED_CONTAINER_MOUNT_OPTS.Related
run.shSEED_CONTAINERpath the guide describes: run.sh: run playbooks in the seed container generics#596AI-assisted: Claude Code