[
https://issues.apache.org/jira/browse/MESOS-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933907#comment-14933907
]
Timothy Chen commented on MESOS-2972:
-------------------------------------
I see, we don't adapt JsonSchema yet and not sure how that integration looks
like.
This is actually recommended by other commiters from Twitter, as they already
modeled AppC json with Protobf.
The conversion and modeling is actually quite straightforward using the JSON
<-> Protobuf tools we have.
I still think we should conform to what's being practiced for now, and look
into JsonSchema if it's a better alternative to convert all others.
What I'd like to avoid is to have a complicated way that's harder to maintain
and at least conform to the best practice we have as for now.
Does that sounds good [~marco-mesos]?
> 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: Gilbert Song
> 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)
