Open
Conversation
Python demo of orchestrator pattern dispatching JSON tasks to specialized MTC action servers (print, move). Includes: - hello_orchestrator_py: orchestrator server, action servers, client - hello_orchestrator_py_interfaces: action definitions
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
Adds
hello_orchestrator_py- a minimal Python demo of the orchestrator pattern for dispatching JSON tasks to specialized MTC action servers.Packages:
hello_orchestrator_py- orchestrator server, print/move action servers, clienthello_orchestrator_py_interfaces- action definitionsArchitecture
Base Action Server / Stages
Common patterns are extracted into base classes to avoid redundant code across action servers:
BaseActionServer- All action servers share the same lifecycle (goal acceptance, execution, error handling).BaseStages- All MTC stages share the same initialization and plan-execute flow. Subclasses only implement task-specific logic.