Repository navigation
Conversation
Draft design note (no implementation): do not adopt Cloud Pathways (TPU/JAX/GKE runtime), adopt three of its patterns - single-controller orchestration with a durable run manifest, a datapoint completion contract for N-1 fault tolerance, and staging contracts for colocated sidecars. Companion deployment-side doc: NatLabRockies/ openstudio-server-helm PR #163.
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
Draft design note only — no implementation, no code changes.
Google Cloud Pathways went GA on 9 Nov 2026. This note evaluates it for OpenStudio Server and concludes:
Adds
doc/cloud_pathways_patterns_design.md.Companion PR
The deployment-side half of this design (Helm chart Job template, sidecar containers, disruption/backoff settings) is in NatLabRockies/openstudio-server-helm#163: NatLabRockies/openstudio-server-helm#163
The two documents cross-reference each other by repo and path.
Test plan
None — documentation only. The note itself proposes a three-check gate (kill a worker node mid-run, restart the controller mid-run, wall-clock/cost comparison) for any future implementation PR.
Please do not merge on my behalf — opening for review/discussion only.
Also in this series: the OSimFlow mapping/gap note — anchapin/OSimFlow#2133: anchapin/OSimFlow#2133