AI search deployment follow-up: kitconcept.solr upgrade step + cluster reindex docs (#433) - #443
Open
reekitconcept wants to merge 2 commits into
Open
AI search deployment follow-up: kitconcept.solr upgrade step + cluster reindex docs (#433)#443reekitconcept wants to merge 2 commits into
reekitconcept wants to merge 2 commits into
Conversation
On existing deployments only the distribution's own upgrade steps run, so the new kitconcept.solr profile version (1004: rag_enabled registry record + RAG indexing queue processor) would never be applied. Cascade it from a kitconcept.intranet upgrade step, following the existing collective.person pattern (v20250909001). Bails out when kitconcept.solr was never installed (sites created without Solr support). Tested without a Solr server: the default test site has setup_solr false (bail-out path); the upgrade path installs the profile and rolls its version back to 1003 to simulate an existing deployment.
The make targets are dev-only; in the docker image the reindex runs as ./docker-entrypoint.sh run ./scripts/solr_activate_and_reindex.py --rag-enable --clear Documents the required order: LLM credentials on the container first (the RAG processor silently skips embedding without them), then the site upgrade (cascades the kitconcept.solr profile upgrade), then the reindex. Notes the site id and the --rag-disable rollback switch.
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
1 participant
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.
Follow-up to #436 addressing the deployment review points (refs gitlab #433 / deployment ticket #515).
Upgrade step v20260729001: upgrade kitconcept.solr if installed
On existing deployments only the distribution's own upgrade steps run, so the new kitconcept.solr profile version (1004:
rag_enabledregistry record + RAG indexing queue processor) would never be applied. This cascades it from a kitconcept.intranet upgrade step, following the existing collective.person pattern (v20250909001). Bails out when kitconcept.solr was never installed (sites created without Solr support).Note this is required for the deploy command to work at all on the existing io site: its kitconcept.solr profile is still at 1003, so the
rag_enabledrecord does not exist yet andsolr_activate_and_reindex.py --rag-enablewould fail onset_registry_recorduntil the site upgrade has run.Testing (no Solr server needed): the default test site is created with
setup_solr: false, which is the bail-out scenario; the upgrade scenario installskitconcept.solr:defaultin-test (registry import only) and rolls its version back to 1003 to simulate an existing deployment. Seebackend/tests/upgrades/test_v20260729001.py.Docs: cluster deployment of the AI search reindex
The make targets are dev-only; in the docker image the reindex runs as
Documents the required order: LLM credentials on the container first (the RAG processor silently skips embedding without them — the reindex "succeeds" with an empty chunk index), then the site upgrade, then the reindex. Also notes the site id and the
--rag-disablerollback switch.