FYI: "The Wasm OCI Image Specification"

[Chris Aniszczyk]

https://www.solo.io/blog/announcing-the-webassembly-wasm-oci-image-spec/

https://github.com/solo-io/wasm/tree/master/spec

--

Chris Aniszczyk (@cra) | +1-512-961-6719

[Steve Lasker]

Very cool to see OCI Artifacts extended to support new types.

--
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@opencontainers.org.

[Sebastiaan van Stijn]

I was/am somewhat confused by the announcement; the announcement mentions "Wasm OCI Image Specification”,

but it’s driven by solo.io (not OCI), and both the specification (on GitHub), and the Slack channel are

not on the OCI.

I must admit, I haven’t looked deeply into the specs, but should this be considered a “proposal” to be

included in the OCI specs? If so should it already carry “OCI” in the name before it’s accepted?

[Steve Lasker]

I think there’s a bit of confusion in the specific branding. If I understand it correctly, It’s technically not an OCI Image, rather am OCI Artifact type. It can be stored in a registry, like Singularity, Helm, OPA, etc. But, you don’t run it in directly on a containerd host, or maybe you do. I need to look closer  Either way, I wouldn’t call it an OCI Image as that does have a specific meaning. 

On Sep 11, 2020, at 6:26 AM, Sebastiaan van Stijn <thaj...@gmail.com> wrote:



[Scott McCarty]

I'm glad I was not the only one confused by the naming. I just couldn't find the language to vocalize my confusion, so thank you Sebastiaan. Yeah, my vague understanding is that it's a extra meta data that "could" be read by a container engine to hand the blob off to the right WASM runtime to be executed. I "think" the challenge is, knowing which program and which version to hand the binary off to run it. I believe it's kind of like picking the right version of Java back in the day. Other might know more, but that was what I got out of it.

I already asked the Podman team to take a look and see if it's something we would want to support, as if I'm understanding it correctly, it shouldn't be "that" difficult to read the meta data, and check if the system has the right WASM runtime to run it.

Anybody, please correct me if my understanding is completely confused, as I don't understand WASM that well yet.

Best Regards

Scott M

--

A First Look at The Podman 2.0 API: http://crunchtools.com/a-first-look-at-the-podman-2-0-api/--
--

Scott McCarty
Product Management - Containers, Red Hat Enterprise Linux & OpenShift
Email: smcc...@redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com

[Frederick F. Kautz IV]

Agreed, messaging here is confusing. Based on the post, is this an OCI initiative? Doesn't seem so. Is it an OCI compliant image with tooling to run wasm? Or perhaps a proposal which they intend to bring to the community? I am worried that it may be hijacking the OCI term if it is something different. I don't think there is malicious intent here though. Instead, we should be proactive and see if there is a community based approach we can converge on. Having a wasm OCI spec I think would be of significant value to the community and they are clearly thinking in the same line.

Cheers,

Frederick

[Steve Lasker]

Qualifier: I don’t mean to squash the feedback and the concern for how the messaging was rolled out.

I reached out to the Solo folks, and they were surprised and felt bad it was taken negatively, as that wasn’t their intent, and are actively working to resolve concerns…

[Erick Carty]

Would it be possible to have someone from their team perhaps join one of the OCI meetings and present some of their work, highlighting the intersection/overlap?

I do believe they meant to highlight that their WASM modules can be uploaded to OCI-compliant registries and handled as another artifact type.

[Steve Lasker]

Great idea. I’ll ask…

[Zhipeng Huang]

I think the wasmer team was also working on something similar to this

Zhipeng (Howard) Huang

Principle Engineer

OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C