Re: protbuf to json not compatible

2017-03-23 Thread James Peach
> On Mar 23, 2017, at 7:58 PM, James Peach wrote: > >> >> On Mar 23, 2017, at 1:54 AM, Olivier Sallou wrote: >> >> Hi, >> >> when transforming a protobug message to json with MessageToJson, the >> json is not compatible with the json format

Re: protbuf to json not compatible

2017-03-23 Thread James Peach
> On Mar 23, 2017, at 1:54 AM, Olivier Sallou wrote: > > Hi, > > when transforming a protobug message to json with MessageToJson, the > json is not compatible with the json format expected by Mesos master. This is because you generated the protobuf bindings with

Re: protbuf to json not compatible

2017-03-23 Thread Benjamin Mahler
+anand, vinod On Thu, Mar 23, 2017 at 2:09 AM, Tomek Janiszewski wrote: > I have a similar problem with protobuf and json. In my case numbers were > incorrectly unmarshaled. Here is an issue > https://issues.apache.org/jira/browse/MESOS-970 and review >

Re: protbuf to json not compatible

2017-03-23 Thread Benjamin Mahler
+gilbert On Thu, Mar 23, 2017 at 1:54 AM, Olivier Sallou wrote: > Hi, > > when transforming a protobug message to json with MessageToJson, the > json is not compatible with the json format expected by Mesos master. > > For example, for volumes it generates > > >

Re: [Design Doc] Improve Storage Support in Mesos using Resources Provider

2017-03-23 Thread Jie Yu
Yes, the idea is to make this general in the future. In fact, the whole resource provider design keeps that in mind. We could add a general "CONVERT" operation in the future with a free formed key value pairs (as well as the source resources) as the parameters. And it's up to the corresponding

Re: Mesos Developer Community Meeting (Mar 23)

2017-03-23 Thread Michael Park
Alright, I still see no agenda items. We'll cancel this time around as well. Please reach out to me if you have things you would like to present! It can be anything from a feature announcement/walk-through, short tech-talk, a little lesson learned, a bug you'd like to share, etc. Thanks, MPark

Re: CNI: Mesos containers need to access Mesos agent

2017-03-23 Thread tommy xiao
+1 2017-03-21 7:16 GMT+08:00 Marcus Sorensen : > > Thanks. Good to see it is already being tracked. > > On 2017-03-20 14:39 (-0600), Avinash Sridharan > wrote: > > Hi Marcus, > > The reason we need connectivity from the container's network namespace

Re: protbuf to json not compatible

2017-03-23 Thread Tomek Janiszewski
I have a similar problem with protobuf and json. In my case numbers were incorrectly unmarshaled. Here is an issue https://issues.apache.org/jira/browse/MESOS-970 and review https://reviews.apache.org/r/50851/ czw., 23.03.2017, 09:54 użytkownik Olivier Sallou napisał: >

protbuf to json not compatible

2017-03-23 Thread Olivier Sallou
Hi, when transforming a protobug message to json with MessageToJson, the json is not compatible with the json format expected by Mesos master. For example, for volumes it generates volumes: [ {'hostPath': '', 'containerPath': '...', ... } ] but HTTP API expects

Re: [Design Doc] Improve Storage Support in Mesos using Resources Provider

2017-03-23 Thread Sargun Dhillon
Is the intent to make this generic beyond disks? I can see the concepts apply beyond volumes, and blocks. Perhaps a generic Create{generation} -- where larger generation numbers descend from smaller ones? I can also see this valuable in networking. My use case is ENIs in AWS. I would like to have