Repository navigation
docs: design the add-on owner as its own role - #12863
Closed
mudler-agent wants to merge 1 commit into
Closed
mudler-agent wants to merge 1 commit into
mudler-agent wants to merge 1 commit into
Conversation
Spec for running the add-on owner as a separately deployed role in distributed mode, sharing code with single mode. Frontends keep reaching it through the existing carrier. Durable owner state moves behind a storage interface with a database backend. The file backend stays the default. Single owner is enforced by owner.lock on files, or by a sticky advisory lock on the database. Assisted-by: Claude:claude-haiku-5-5
Collaborator
Author
|
Closing: the owner will run as a single stateful workload with files only, so the database backend and the storage interface are dropped. The implementation is in #12867. |
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.
Proposes running the add-on owner as its own role in distributed mode, with the same code as single mode.
owner.lockon files, or by a sticky advisory lock on the database.Spec only, no code. Open questions are listed at the end of the document.
🤖 Generated with Claude Code