[jira] [Commented] (MYRIAD-264) Upgrade Mesos API to 1.5.x
[ https://issues.apache.org/jira/browse/MYRIAD-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610461#comment-16610461 ] Juan Pedro commented on MYRIAD-264: --- Hi [~yufeldman], thanks for the help, I had not thought about shading and it could be a good option > Upgrade Mesos API to 1.5.x > -- > > Key: MYRIAD-264 > URL: https://issues.apache.org/jira/browse/MYRIAD-264 > Project: Myriad > Issue Type: Task > Components: Executor, Scheduler >Affects Versions: Myriad 0.2.0 >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Critical > > Apache Myriad is based on Apache Mesos API 0.28.x [Upgrading > Mesos|https://mesos.apache.org/documentation/latest/upgrades/]. > In order to align with current Apache Mesos deployments we have to upgrade to > "at least" Apache Mesos 1.5.x API (this is the Mesos version shipped in DC/OS > 1.11.1, in particular 1.5.1-dev) [DC/OS 1.11.1 > Mesos|https://github.com/dcos/dcos/blob/1.11.1/packages/mesos/buildinfo.json] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MYRIAD-264) Upgrade Mesos API to 1.5.x
[ https://issues.apache.org/jira/browse/MYRIAD-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605958#comment-16605958 ] Yuliya Feldman commented on MYRIAD-264: --- Just initial thought - did you think about shading - this way you can use multiple protobuf versions for different purposes > Upgrade Mesos API to 1.5.x > -- > > Key: MYRIAD-264 > URL: https://issues.apache.org/jira/browse/MYRIAD-264 > Project: Myriad > Issue Type: Task > Components: Executor, Scheduler >Affects Versions: Myriad 0.2.0 >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Critical > > Apache Myriad is based on Apache Mesos API 0.28.x [Upgrading > Mesos|https://mesos.apache.org/documentation/latest/upgrades/]. > In order to align with current Apache Mesos deployments we have to upgrade to > "at least" Apache Mesos 1.5.x API (this is the Mesos version shipped in DC/OS > 1.11.1, in particular 1.5.1-dev) [DC/OS 1.11.1 > Mesos|https://github.com/dcos/dcos/blob/1.11.1/packages/mesos/buildinfo.json] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MYRIAD-264) Upgrade Mesos API to 1.5.x
[ https://issues.apache.org/jira/browse/MYRIAD-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605945#comment-16605945 ] Juan Pedro commented on MYRIAD-264: --- Hello, I am working on version alignment with DCOS. The version of protobuf that Yarn uses and the one that uses Mesos are not compatible. The jar of Mesos is compiled for 3.x and Yarn charges 2.5. This causes Myriad to find the protobuf classes already loaded in a version that is not correct for Mesos. In this context, I have developed two lines of work: 1. I have developed a proprietary driver to manage the connection with Mesos so that we can compile with the appropriate protobuf version. This supposes freedom but also supposes an additional maintenance (abandoned in favor of the second option). https://github.com/jpgilaberte/incubator-myriad/tree/httpapi (compile without test - only developed the scheduler driver) 2. Reuse all the code of the original mesos driver, compile our protobuf objects and continue to take advantage of the binding with libmesos.so. The current state of this branch is that it is already running with Mesos 1.5. I continue to work on adding the new features that have been integrated into the latest versions of Mesos (StatusUpdateAcknoweledge, etc...). https://github.com/jpgilaberte/incubator-myriad/tree/upgrademesos1.5 What do you think? > Upgrade Mesos API to 1.5.x > -- > > Key: MYRIAD-264 > URL: https://issues.apache.org/jira/browse/MYRIAD-264 > Project: Myriad > Issue Type: Task > Components: Executor, Scheduler >Affects Versions: Myriad 0.2.0 >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Critical > > Apache Myriad is based on Apache Mesos API 0.28.x [Upgrading > Mesos|https://mesos.apache.org/documentation/latest/upgrades/]. > In order to align with current Apache Mesos deployments we have to upgrade to > "at least" Apache Mesos 1.5.x API (this is the Mesos version shipped in DC/OS > 1.11.1, in particular 1.5.1-dev) [DC/OS 1.11.1 > Mesos|https://github.com/dcos/dcos/blob/1.11.1/packages/mesos/buildinfo.json] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
