Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 29 Sep 2015 05:07:04 +0000 (UTC)
From: "Marco Massenzio (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12841857.1435711052000.99222.1443503224479@Atlassian.JIRA>
In-Reply-To: <JIRA.12841857.1435711052000@Atlassian.JIRA>
References: <JIRA.12841857.1435711052000@Atlassian.JIRA>
 <JIRA.12841857.1435711052430@arcas>
Subject: [jira] [Commented] (MESOS-2972) Serialize Docker image spec as
 protobuf
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MESOS-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934629#comment-14934629 ] 

Marco Massenzio commented on MESOS-2972:
----------------------------------------

(We discussed this in person - recording here for future reference.)

It looks as if the structure of the Docker Image spec should be simple enough and amenable to being "represented" in PB format without any conversion/adapter functionality, but just using Mesos' {{JSON::protobuf}} functionality.

I am fine with trying this out, provided the PB structure that comes out is not too gnarly.

> 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)