[
https://issues.apache.org/jira/browse/MESOS-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617411#comment-14617411
]
Marco Massenzio commented on MESOS-2972:
----------------------------------------
Before actually rushing to write up code, can we please have a design doc that
we can review?
I have a concern around trying to model a JSON model (no idea how complex) into
Protobuf (do we really *need* to do this?) - especially if, under current
practice, we also must ensure "automatic" conversion between one format and the
other.
My preference would be for not having to do this.
Also, it's not clear at all the *why* of this requirement (in other words, we
could as well use a {{string}} JSON-serialized format - or a
{{stout::JSON::Object}} - or whatever).
> Serialize Docker image spec as protobuf
> ---------------------------------------
>
> Key: MESOS-2972
> URL: https://issues.apache.org/jira/browse/MESOS-2972
> Project: Mesos
> Issue Type: Improvement
> Reporter: Timothy Chen
> Assignee: Lily Chen
> Labels: mesosphere
>
> The Docker image specification defines a schema for the metadata json that it
> puts into each image. Currently the docker image provisioner needs to be able
> to parse and understand this metadata json, and we should create a protobuf
> equivelent schema so we can utilize the json to protobuf conversion to read
> and validate the metadata.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
