Added Project scope and intent for AI workflow interoperability#2163
Open
nataliesea wants to merge 9 commits into
Open
Added Project scope and intent for AI workflow interoperability#2163nataliesea wants to merge 9 commits into
nataliesea wants to merge 9 commits into
Conversation
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
github-actions
Bot
added
needs-triage
danieloh30
reviewed
May 17, 2026
danieloh30
reviewed
May 17, 2026
danieloh30
reviewed
May 17, 2026
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
nataliesea
commented
May 18, 2026
nataliesea
left a comment
nataliesea
left a comment
Author
There was a problem hiding this comment.
Resolved feedback from @danieloh30
Member
|
@caldeirav - do you have time for a quick review? thanks |
sabre1041
reviewed
Jun 8, 2026
| Focus on the developer inner loop, everything an AI engineer does on a laptop/desktop before code or models ever reach CI/CD in a cloud native environment: | ||
|
|
||
| * Local container workspaces: Reference inner loop workflow using desktop tooling such as Podman Desktop / Podman AI Lab for root-less, GPU-aware experimentation, including template images for PyTorch/LLM stacks and volume-mounted datasets. | ||
| * Unified model build & run CLI: Hardening inference on developer machine and agentic frameworks to leverage container-based tooling so engineers can easily spin-up inference, RAG and multi-agent services locally with one command. |
There was a problem hiding this comment.
Unified model build & run CLI sounds awkward. Recommend a different set of terms for this goal
| * **A Published Interoperability Spec:** A validated specification that existing tools can adopt to ensure cloud native readiness. | ||
| * **Cross-Tool Portability:** Demonstrated ability for an artifact built by one tool to be verified and deployed by a different runtime. | ||
| * **The "10-Minute Flow":** A successful reference implementation demonstrating the journey from a local idea to a running inference service on Kubernetes. | ||
| * **Ecosystem Alignment:** Broad adoption of the "Compliance Profile" metadata across CNCF and LF AI & Data communities. |
There was a problem hiding this comment.
Would a blog post highlighting the outputs of this effort also be a desired success criteria?
Member
There was a problem hiding this comment.
+1. My hope is that this initiative will lead to more smaller and focussed initiatives within ecosystem and/or more opportunities to collaborate outside of CNCF ecosystem. A blog post with future direction/goals will be really helpful.
angellk
requested changes
Jun 9, 2026
|
dragonfly contributor here, i work on the model distribution side (the hf + modelscope backends). packaging and the gitops handoff look well covered. the thing i didn't see much on is actually getting the weights down onto the nodes, which is usually the step that bites in prod. a 30gb model pulled by a few hundred pods at once basically melts the registry, and air-gapped makes it worse. dragonfly handles that with p2p so most of the bytes come from peers instead of hammering the registry every time. is that in scope for the profile, or are you treating it as a registry/oci concern? if it's in scope i can write up the distribution piece. |
TerryHowe
reviewed
Jun 11, 2026
|
I support the goal of defining a lightweight OCI-based interoperability profile for AI artifacts. From an Argo CD perspective, I'd like more clarity around the deployment unit, versioning and promotion semantics, signature verification requirements, and the minimal required metadata set. The proposal will be strongest if it stays narrowly focused on interoperability metadata and avoids overlapping responsibilities with ModelPack and other packaging specifications. |
|
Transferring a note/todo from our Slack channel related to OpenMDW:
Thanks to @caldeirav for these thoughts |
Co-authored-by: Andrew Block <andy.block@gmail.com> Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
Co-authored-by: Andrew Block <andy.block@gmail.com> Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
TerryHowe
reviewed
Jun 18, 2026
| ## Project Scope & Intent - Cloud Native AI Developer Workflow Interoperability | ||
|
|
||
| ### Overview and Intent | ||
| AI developers today frequently work in fragmented local environments that are disconnected from cloud native operational workflows. While emerging standards like ModelPack and OCI-aligned AI artifact initiatives provide the “packaging” foundations, there is no unified interoperability specification that defines how these artifacts must be structured, secured, and described to move seamlessly from a developers environments into a Kubernetes-based production system. |
There was a problem hiding this comment.
Many other places here, the British spelling artefact is used here.
…pliant-inner-loop/README.md Co-authored-by: Terry Howe <terrylhowe@gmail.com> Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
Co-authored-by: Andrew Block <andy.block@gmail.com> Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
Updated from feedback provided Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
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
9 participants
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.
Updating the README to provide more detail on the project's scope, goals, and interoperability requirements.