Skip to content

Feature/mvp integration design#2

Draft
oehmends wants to merge 11 commits into
developfrom
feature/mvp-integration-design
Draft

Feature/mvp integration design#2
oehmends wants to merge 11 commits into
developfrom
feature/mvp-integration-design

Conversation

@oehmends
Copy link
Copy Markdown
Collaborator

Changelog Description

This is a PR in order to Review / Comment the current design discussions on how to implement Deadline Cloud in AYON.

…ide via OpenJD

- Replace TBD in Component 5 with resolved decision and trade-off analysis
- Update architecture diagram to show MVP on-prem post-render flow
- Update sequence diagrams for render-only job submission
- Add fileshare access analysis by fleet type (CMF, SMF via VPC Lattice)
- Add post-MVP target state: OpenJD templates for portable post-render
- Simplify SubmissionResult for render-only MVP
- Move farm-side post-render to Deferred scope
- Replace flat CondaConfig with per-DCC DCCCondaConfig model
- Add project-level conda overrides to ProjectDeadlineCloudSettings
- Support custom conda packages with explicit S3 channel configuration
- Add Publisher UI visibility for editable conda packages on render instances
- Update resolve_conda_packages algorithm for project → server → auto-detection chain
- Add ValidateCondaPackages validation plugin and correctness property
- Update examples, tests, and formal specs to reflect new model
- Replace external on-prem publish with in-job PUBLISH step on CMF worker
- Two-step job: RENDER (SMF) → PUBLISH (on-prem CMF) via OJD step dependencies
- Per-step hostRequirements route steps to different fleets on same queue
- On-prem worker accesses S3 via Deadline Cloud credential chain (no VPN)
- Submission hooks (deadline-cloud PR #986) for job template assembly
- IAM Roles Anywhere for on-prem worker bootstrap credentials
- Publish dependencies can be conda-packaged for multi-node scaling
- Path to fully cloud-based publishing when fileshare access available
@oehmends oehmends marked this pull request as draft April 21, 2026 10:22
oehmends added 2 commits May 26, 2026 19:36
Map out CMF/SMF distribution options for AYON Launcher with mermaid diagrams. Questions conda's immutability assumption and whether auto-update belongs on render workers, then compares stable conda package, per-job conda package, S3-staged centralized mode, and pre-baked AMI as SMF paths.
Add TL;DR and closing section reflecting Ondrej's bootstrap idea and Leon's working ayon-publish recipe. SMF target is a headless conda package, separate from PR #303's full launcher which targets CMF and on-prem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants