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

Qian Zhang commented on MESOS-4312:
-----------------------------------

Had some off-line discussion with [~hartem] and [~vinodkone], here is the final 
plan we all agree:
# Porting Mesos on Power by upgrading/patching some 3rd party libraries.
#* Update leveldb to v1.18, libev to v4.22, and protobuf to v2.6.1, 
ry-http-parser-1c3624a to nodejs/http-parser v2.6.1 for all platforms, since 
these are their latest upstream stable releases which has officially supported 
Power. Create JIRA ticket for each of them and link them to this JIRA ticket.
#* Patch zookeeper, glog, protobuf only for Power.
#* Change "src/linux/fs.cpp" for all platforms as what I did in 
https://reviews.apache.org/r/42551/.
# Verify SSL, perf and docker related test cases work as expected on all 
platforms.
# Do the validation on all platforms by "sudo make dist check" and "sudo make 
check --benchmark --gtest_filter="*Benchmark*"" and make sure the perf numbers 
are OK.
# Run compatibility tests between scheduler <-> master <-> slave <-> executor 
where each of the components is running either the patched/upgraded version or 
not. Will contact with Niklas/Kapil for their script and improve it if needed.

> Porting Mesos on Power (ppc64le)
> --------------------------------
>
>                 Key: MESOS-4312
>                 URL: https://issues.apache.org/jira/browse/MESOS-4312
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Qian Zhang
>            Assignee: Qian Zhang
>
> The goal of this ticket is to make IBM Power (ppc64le) as a supported 
> hardware platform of Mesos. Currently the latest Mesos code can not be 
> successfully built on ppc64le, we will resolve the build errors in this 
> ticket, and also make sure Mesos test suite ("make check") can be ran 
> successfully on ppc64le. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to