[jira] [Updated] (MESOS-5839) Mesos docker image can't be started by docker-py

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5839:
---
Description: 
I can use `docker run` command to start a Mesos Agent container, but can't use 
docker-py to start.

When I use docker-py to start the Mesos Agent container, the mesos agent error 
message:
{quote}
I0713 02:07:55.161175 24808 logging.cpp:193] INFO level logging started!
I0713 02:07:55.162096 24808 main.cpp:264] Build: 2016-06-22 05:16:01 by root
I0713 02:07:55.162303 24808 main.cpp:266] Version: 1.0.0
I0713 02:07:55.162593 24808 main.cpp:269] Git tag: 1.0.0-rc1
I0713 02:07:55.162782 24808 main.cpp:273] Git SHA: 
dfe62665df67162e4c1064f524d6c0180100a9d2
I0713 02:07:55.169150 24808 systemd.cpp:237] systemd version `229` detected
I0713 02:07:55.277576 24808 containerizer.cpp:198] Using isolation: 
posix/cpu,posix/mem,filesystem/posix,network/cni
I0713 02:07:55.298914 24808 linux_launcher.cpp:101] Using 
/sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
I0713 02:07:55.302297 24808 main.cpp:406] Starting Mesos agent
I0713 02:07:55.302889 24820 slave.cpp:203] Agent started on 1)@9.21.60.205:5051
I0713 02:07:55.303081 24820 slave.cpp:204] Flags at startup: 
--appc_simple_discovery_uri_prefix="http://; 
--appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="false" 
--authenticatee="crammd5" --authorizer="local" 
--cgroups_cpu_enable_pids_and_tids_count="false" --cgroups_enable_cfs="false" 
--cgroups_hierarchy="/sys/fs/cgroup" --cgroups_limit_swap="false" 
--cgroups_root="mesos" --container_disk_watch_interval="15secs" 
--containerizers="docker,mesos" --default_role="*" 
--disk_watch_interval="1mins" --docker="docker" --docker_kill_orphans="true" 
--docker_registry="https://registry-1.docker.io; --docker_remove_delay="6hrs" 
--docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns" 
--docker_store_dir="/tmp/mesos/store/docker" 
--docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume" 
--enforce_container_disk_quota="false" --executor_registration_timeout="1mins" 
--executor_shutdown_grace_period="5secs" --fetcher_cache_dir="/tmp/mesos/fetch" 
--fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks" 
--gc_disk_headroom="0.1" --hadoop_home="" --help="false" 
--hostname_lookup="true" --http_authenticators="basic" 
--http_command_executor="false" --image_provisioner_backend="copy" 
--initialize_driver_logging="true" --isolation="posix/cpu,posix/mem" 
--launcher_dir="/usr/libexec/mesos" --log_dir="/var/log/mesos" --logbufsecs="0" 
--logging_level="INFO" --master="9.21.60.90:5050" 
--oversubscribed_resources_interval="15secs" --perf_duration="10secs" 
--perf_interval="1mins" --port="5051" --qos_correction_interval_min="0ns" 
--quiet="false" --recover="reconnect" --recovery_timeout="15mins" 
--registration_backoff_factor="1secs" --revocable_cpu_low_priority="true" 
--sandbox_directory="/mnt/mesos/sandbox" --strict="true" --switch_user="false" 
--systemd_enable_support="false" 
--systemd_runtime_directory="/run/systemd/system" --version="false" 
--work_dir="/var/lib/mesos"
..
W0713 02:07:55.481570 24808 logging.cpp:91] {color:blue}*RAW: Received signal 
SIGTERM from process 19221 of user 0; exiting*{color}
{quote}

The process 19221 is the docker-containerd daemon. I am not sure if this issue 
if related to this fix: https://issues.apache.org/jira/browse/MESOS-4279 , but 
mesosphere/mesos:0.28.2 has no this issue.

Following is the Docker daemon log:

{quote}{code}
Jul 12 22:07:54 ubuntu5 docker[19214]: 
time="2016-07-12T22:07:54.954452857-04:00" level=warning msg="Security options 
with `:` as a separator are deprecated and will be completely unsupported in 
1.13, use `=` instead."
Jul 12 22:07:54 ubuntu5 kernel: [141068.247724] aufs 
au_opts_verify:1597:docker[26535]: dirperm1 breaks the protection by the 
permission bits on the lower branch
Jul 12 22:07:54 ubuntu5 kernel: [141068.269016] aufs 
au_opts_verify:1597:docker[26535]: dirperm1 breaks the protection by the 
permission bits on the lower branch
Jul 12 22:07:54 ubuntu5 kernel: [141068.287598] aufs 
au_opts_verify:1597:docker[19714]: dirperm1 breaks the protection by the 
permission bits on the lower branch
Jul 12 22:07:55 ubuntu5 docker[19214]: 
time="2016-07-12T22:07:55.509756825-04:00" level=info msg="Container 
ea0f9128d489f56f3b9f64a24926a53e499b4b6e5243301a01c69e171d4f054b failed to exit 
within 0 seconds of signal 15 - using the force"
Jul 12 22:07:55 ubuntu5 docker[19214]: 
time="2016-07-12T22:07:55.568161690-04:00" level=warning msg="container 
ea0f9128d489f56f3b9f64a24926a53e499b4b6e5243301a01c69e171d4f054b restart 
canceled"
{code}{quote}

h2. Docker run commands:
{code}
docker run -d --net=host --pid=host --privileged -e 
MESOS_MASTER=9.21.60.192:5050 -e MESOS_SWITCH_USER=0 -e 
MESOS_CONTAINERIZERS=docker,mesos -e MESOS_LOG_DIR=/var/log/mesos -e 
MESOS_WORK_DIR=/var/lib/mesos 

[jira] [Commented] (MESOS-5839) Mesos docker image can't be started by docker-py

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5839:


[~jieyu] [~vinodkone] Could you take a look? I found this issue also appears in 
mesos 1.0.0-rc2.

> Mesos docker image can't be started by docker-py
> 
>
> Key: MESOS-5839
> URL: https://issues.apache.org/jira/browse/MESOS-5839
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>
> I can use `docker run` command to start a Mesos Agent container, but can't 
> use docker-py to start.
> When I use docker-py to start the Mesos Agent container, the mesos agent 
> error message:
> {quote}
> I0713 02:07:55.161175 24808 logging.cpp:193] INFO level logging started!
> I0713 02:07:55.162096 24808 main.cpp:264] Build: 2016-06-22 05:16:01 by root
> I0713 02:07:55.162303 24808 main.cpp:266] Version: 1.0.0
> I0713 02:07:55.162593 24808 main.cpp:269] Git tag: 1.0.0-rc1
> I0713 02:07:55.162782 24808 main.cpp:273] Git SHA: 
> dfe62665df67162e4c1064f524d6c0180100a9d2
> I0713 02:07:55.169150 24808 systemd.cpp:237] systemd version `229` detected
> I0713 02:07:55.277576 24808 containerizer.cpp:198] Using isolation: 
> posix/cpu,posix/mem,filesystem/posix,network/cni
> I0713 02:07:55.298914 24808 linux_launcher.cpp:101] Using 
> /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
> I0713 02:07:55.302297 24808 main.cpp:406] Starting Mesos agent
> I0713 02:07:55.302889 24820 slave.cpp:203] Agent started on 
> 1)@9.21.60.205:5051
> I0713 02:07:55.303081 24820 slave.cpp:204] Flags at startup: 
> --appc_simple_discovery_uri_prefix="http://; 
> --appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="false" 
> --authenticatee="crammd5" --authorizer="local" 
> --cgroups_cpu_enable_pids_and_tids_count="false" --cgroups_enable_cfs="false" 
> --cgroups_hierarchy="/sys/fs/cgroup" --cgroups_limit_swap="false" 
> --cgroups_root="mesos" --container_disk_watch_interval="15secs" 
> --containerizers="docker,mesos" --default_role="*" 
> --disk_watch_interval="1mins" --docker="docker" --docker_kill_orphans="true" 
> --docker_registry="https://registry-1.docker.io; --docker_remove_delay="6hrs" 
> --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns" 
> --docker_store_dir="/tmp/mesos/store/docker" 
> --docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume" 
> --enforce_container_disk_quota="false" 
> --executor_registration_timeout="1mins" 
> --executor_shutdown_grace_period="5secs" 
> --fetcher_cache_dir="/tmp/mesos/fetch" --fetcher_cache_size="2GB" 
> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1" 
> --hadoop_home="" --help="false" --hostname_lookup="true" 
> --http_authenticators="basic" --http_command_executor="false" 
> --image_provisioner_backend="copy" --initialize_driver_logging="true" 
> --isolation="posix/cpu,posix/mem" --launcher_dir="/usr/libexec/mesos" 
> --log_dir="/var/log/mesos" --logbufsecs="0" --logging_level="INFO" 
> --master="9.21.60.90:5050" --oversubscribed_resources_interval="15secs" 
> --perf_duration="10secs" --perf_interval="1mins" --port="5051" 
> --qos_correction_interval_min="0ns" --quiet="false" --recover="reconnect" 
> --recovery_timeout="15mins" --registration_backoff_factor="1secs" 
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox" 
> --strict="true" --switch_user="false" --systemd_enable_support="false" 
> --systemd_runtime_directory="/run/systemd/system" --version="false" 
> --work_dir="/var/lib/mesos"
> ..
> W0713 02:07:55.481570 24808 logging.cpp:91] {color:blue}*RAW: Received signal 
> SIGTERM from process 19221 of user 0; exiting*{color}
> {quote}
> The process 19221 is the docker-containerd daemon. I am not sure if this 
> issue if related to this fix: 
> https://issues.apache.org/jira/browse/MESOS-4279 , but 
> mesosphere/mesos:0.28.2 has no this issue.
> Following is the Docker daemon log:
> {quote}{code}
> Jul 12 22:07:54 ubuntu5 docker[19214]: 
> time="2016-07-12T22:07:54.954452857-04:00" level=warning msg="Security 
> options with `:` as a separator are deprecated and will be completely 
> unsupported in 1.13, use `=` instead."
> Jul 12 22:07:54 ubuntu5 kernel: [141068.247724] aufs 
> au_opts_verify:1597:docker[26535]: dirperm1 breaks the protection by the 
> permission bits on the lower branch
> Jul 12 22:07:54 ubuntu5 kernel: [141068.269016] aufs 
> au_opts_verify:1597:docker[26535]: dirperm1 breaks the protection by the 
> permission bits on the lower branch
> Jul 12 22:07:54 ubuntu5 kernel: [141068.287598] aufs 
> au_opts_verify:1597:docker[19714]: dirperm1 breaks the protection by the 
> permission bits on the lower branch
> Jul 12 22:07:55 ubuntu5 docker[19214]: 
> time="2016-07-12T22:07:55.509756825-04:00" level=info msg="Container 
> 

[jira] [Created] (MESOS-5839) Mesos docker image can't be started by docker-py

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-5839:
--

 Summary: Mesos docker image can't be started by docker-py
 Key: MESOS-5839
 URL: https://issues.apache.org/jira/browse/MESOS-5839
 Project: Mesos
  Issue Type: Bug
Reporter: Chen Zhiwei


I can use `docker run` command to start a Mesos Agent container, but can't use 
docker-py to start.

When I use docker-py to start the Mesos Agent container, the mesos agent error 
message:
{quote}
I0713 02:07:55.161175 24808 logging.cpp:193] INFO level logging started!
I0713 02:07:55.162096 24808 main.cpp:264] Build: 2016-06-22 05:16:01 by root
I0713 02:07:55.162303 24808 main.cpp:266] Version: 1.0.0
I0713 02:07:55.162593 24808 main.cpp:269] Git tag: 1.0.0-rc1
I0713 02:07:55.162782 24808 main.cpp:273] Git SHA: 
dfe62665df67162e4c1064f524d6c0180100a9d2
I0713 02:07:55.169150 24808 systemd.cpp:237] systemd version `229` detected
I0713 02:07:55.277576 24808 containerizer.cpp:198] Using isolation: 
posix/cpu,posix/mem,filesystem/posix,network/cni
I0713 02:07:55.298914 24808 linux_launcher.cpp:101] Using 
/sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
I0713 02:07:55.302297 24808 main.cpp:406] Starting Mesos agent
I0713 02:07:55.302889 24820 slave.cpp:203] Agent started on 1)@9.21.60.205:5051
I0713 02:07:55.303081 24820 slave.cpp:204] Flags at startup: 
--appc_simple_discovery_uri_prefix="http://; 
--appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="false" 
--authenticatee="crammd5" --authorizer="local" 
--cgroups_cpu_enable_pids_and_tids_count="false" --cgroups_enable_cfs="false" 
--cgroups_hierarchy="/sys/fs/cgroup" --cgroups_limit_swap="false" 
--cgroups_root="mesos" --container_disk_watch_interval="15secs" 
--containerizers="docker,mesos" --default_role="*" 
--disk_watch_interval="1mins" --docker="docker" --docker_kill_orphans="true" 
--docker_registry="https://registry-1.docker.io; --docker_remove_delay="6hrs" 
--docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns" 
--docker_store_dir="/tmp/mesos/store/docker" 
--docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume" 
--enforce_container_disk_quota="false" --executor_registration_timeout="1mins" 
--executor_shutdown_grace_period="5secs" --fetcher_cache_dir="/tmp/mesos/fetch" 
--fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks" 
--gc_disk_headroom="0.1" --hadoop_home="" --help="false" 
--hostname_lookup="true" --http_authenticators="basic" 
--http_command_executor="false" --image_provisioner_backend="copy" 
--initialize_driver_logging="true" --isolation="posix/cpu,posix/mem" 
--launcher_dir="/usr/libexec/mesos" --log_dir="/var/log/mesos" --logbufsecs="0" 
--logging_level="INFO" --master="9.21.60.90:5050" 
--oversubscribed_resources_interval="15secs" --perf_duration="10secs" 
--perf_interval="1mins" --port="5051" --qos_correction_interval_min="0ns" 
--quiet="false" --recover="reconnect" --recovery_timeout="15mins" 
--registration_backoff_factor="1secs" --revocable_cpu_low_priority="true" 
--sandbox_directory="/mnt/mesos/sandbox" --strict="true" --switch_user="false" 
--systemd_enable_support="false" 
--systemd_runtime_directory="/run/systemd/system" --version="false" 
--work_dir="/var/lib/mesos"
..
W0713 02:07:55.481570 24808 logging.cpp:91] {color:blue}*RAW: Received signal 
SIGTERM from process 19221 of user 0; exiting*{color}
{quote}

The process 19221 is the docker-containerd daemon. I am not sure if this issue 
if related to this fix: https://issues.apache.org/jira/browse/MESOS-4279 , but 
mesosphere/mesos:0.28.2 has no this issue.

Following is the Docker daemon log:

{quote}{code}
Jul 12 22:07:54 ubuntu5 docker[19214]: 
time="2016-07-12T22:07:54.954452857-04:00" level=warning msg="Security options 
with `:` as a separator are deprecated and will be completely unsupported in 
1.13, use `=` instead."
Jul 12 22:07:54 ubuntu5 kernel: [141068.247724] aufs 
au_opts_verify:1597:docker[26535]: dirperm1 breaks the protection by the 
permission bits on the lower branch
Jul 12 22:07:54 ubuntu5 kernel: [141068.269016] aufs 
au_opts_verify:1597:docker[26535]: dirperm1 breaks the protection by the 
permission bits on the lower branch
Jul 12 22:07:54 ubuntu5 kernel: [141068.287598] aufs 
au_opts_verify:1597:docker[19714]: dirperm1 breaks the protection by the 
permission bits on the lower branch
Jul 12 22:07:55 ubuntu5 docker[19214]: 
time="2016-07-12T22:07:55.509756825-04:00" level=info msg="Container 
ea0f9128d489f56f3b9f64a24926a53e499b4b6e5243301a01c69e171d4f054b failed to exit 
within 0 seconds of signal 15 - using the force"
Jul 12 22:07:55 ubuntu5 docker[19214]: 
time="2016-07-12T22:07:55.568161690-04:00" level=warning msg="container 
ea0f9128d489f56f3b9f64a24926a53e499b4b6e5243301a01c69e171d4f054b restart 
canceled"
{code}{quote}

h2. Docker run commands:
{code}
docker run -d --net=host --pid=host --privileged -e 
MESOS_MASTER=9.21.60.192:5050 -e 

[jira] [Commented] (MESOS-5287) boto is no longer a Mesos dependency.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5287:


Thanks, I also planed to update this patch to include the getting-started.md 
updates.

> boto is no longer a Mesos dependency.
> -
>
> Key: MESOS-5287
> URL: https://issues.apache.org/jira/browse/MESOS-5287
> Project: Mesos
>  Issue Type: Bug
>Reporter: Yan Xu
>Assignee: Chen Zhiwei
>  Labels: easyfix, newbie
> Fix For: 0.29.0
>
>
> Since 'mesos-ec2' has been removed from the repo in MESOS-2640.



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

[jira] [Issue Comment Deleted] (MESOS-5201) Accessibility Enhancement For HTML page

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5201:
---
Comment: was deleted

(was: https://reviews.apache.org/r/47003/)

> Accessibility Enhancement For HTML page
> ---
>
> Key: MESOS-5201
> URL: https://issues.apache.org/jira/browse/MESOS-5201
> Project: Mesos
>  Issue Type: Task
>Reporter: Chen Nan Li
>Assignee: Chen Nan Li
>Priority: Minor
>  Labels: ibm
>




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

[jira] [Assigned] (MESOS-5287) boto is no longer a Mesos dependency.

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-5287:
--

Assignee: Chen Zhiwei

> boto is no longer a Mesos dependency.
> -
>
> Key: MESOS-5287
> URL: https://issues.apache.org/jira/browse/MESOS-5287
> Project: Mesos
>  Issue Type: Bug
>Reporter: Yan Xu
>Assignee: Chen Zhiwei
>  Labels: easyfix, newbie
>
> Since 'mesos-ec2' has been removed from the repo in MESOS-2640.



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

[jira] [Commented] (MESOS-5287) boto is no longer a Mesos dependency.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5287:


I submitted a patch, could you be a shepherd?

https://reviews.apache.org/r/47056/

> boto is no longer a Mesos dependency.
> -
>
> Key: MESOS-5287
> URL: https://issues.apache.org/jira/browse/MESOS-5287
> Project: Mesos
>  Issue Type: Bug
>Reporter: Yan Xu
>  Labels: easyfix, newbie
>
> Since 'mesos-ec2' has been removed from the repo in MESOS-2640.



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

[jira] [Commented] (MESOS-5287) boto is no longer a Mesos dependency.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5287:


I can fix this in this review: https://reviews.apache.org/r/46958/

> boto is no longer a Mesos dependency.
> -
>
> Key: MESOS-5287
> URL: https://issues.apache.org/jira/browse/MESOS-5287
> Project: Mesos
>  Issue Type: Bug
>Reporter: Yan Xu
>  Labels: easyfix, newbie
>
> Since 'mesos-ec2' has been removed from the repo in MESOS-2640.



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

[jira] [Commented] (MESOS-5288) Update leveldb patch file to suport s390x

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5288:


Is upgrading leveldb to new version can solve this issue?

> Update leveldb patch file to suport s390x
> -
>
> Key: MESOS-5288
> URL: https://issues.apache.org/jira/browse/MESOS-5288
> Project: Mesos
>  Issue Type: Bug
>Reporter: Bing Li
>Assignee: Bing Li
>
> There're 2 issues in leveldb-1.4.
> 1. Leveldb didn't build. Have to define MemoryBarrier() for s390x.
> I got the patch form https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644336 
> .
> 2. A number of unit tests failed due to 1.4 doesn't detect endianness 
> properly. And s390x is big-endian.
> Got error messages like "Failed to recover the log: Corruption: checksum 
> mismatch".
> I have a backport patch which is part of the leveldb commit
> https://github.com/google/leveldb/commit/075a35a6d390167b77b687e067dd0ba593e7f624



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

[jira] [Commented] (MESOS-5311) Calling `make install` fails if `include/mesos/slave/agent` already exists.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5311:


I can fix this issue in: https://issues.apache.org/jira/browse/MESOS-5326

> Calling `make install` fails if `include/mesos/slave/agent` already exists.
> ---
>
> Key: MESOS-5311
> URL: https://issues.apache.org/jira/browse/MESOS-5311
> Project: Mesos
>  Issue Type: Bug
>Affects Versions: 0.29.0
>Reporter: Jie Yu
> Fix For: 0.29.0
>
>
> People might be calling `make install` multiple times during development.
> The second `make install` will fail:
> {noformat}
> make[4]: Entering directory `/home/jie/workspace/dist/mesos/build/src'
> cp //home/jie/workspace/dist/mesos/etc/mesos/mesos-agent-env.sh.template \
>   //home/jie/workspace/dist/mesos/etc/mesos/mesos-slave-env.sh.template &&\
> ln -s //home/jie/workspace/dist/mesos/include/mesos/agent \
>   //home/jie/workspace/dist/mesos/include/mesos/slave
> ln: failed to create symbolic link 
> ‘//home/jie/workspace/dist/mesos/include/mesos/slave/agent’: File exists
> make[4]: *** [copy-template-and-create-symlink] Error 1
> {noformat}



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

[jira] [Commented] (MESOS-5201) Accessibility Enhancement For HTML page

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5201:


https://reviews.apache.org/r/47003/

> Accessibility Enhancement For HTML page
> ---
>
> Key: MESOS-5201
> URL: https://issues.apache.org/jira/browse/MESOS-5201
> Project: Mesos
>  Issue Type: Task
>Reporter: Chen Nan Li
>Assignee: Chen Nan Li
>Priority: Minor
>  Labels: ibm
>




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

[jira] [Updated] (MESOS-5201) Accessibility Enhancement For HTML page

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5201:
---
Labels: ibm  (was: )

> Accessibility Enhancement For HTML page
> ---
>
> Key: MESOS-5201
> URL: https://issues.apache.org/jira/browse/MESOS-5201
> Project: Mesos
>  Issue Type: Task
>Reporter: Chen Nan Li
>Assignee: Chen Nan Li
>Priority: Minor
>  Labels: ibm
>




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

[jira] [Commented] (MESOS-4943) Reduce the size of LinuxRootfs in tests.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4943:


alpine has no ppc64le version, so I suggest no to use alpine.

> Reduce the size of LinuxRootfs in tests.
> 
>
> Key: MESOS-4943
> URL: https://issues.apache.org/jira/browse/MESOS-4943
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Reporter: Jie Yu
>  Labels: mesosphere
>
> Right now, LinuxRootfs copies files from the host filesystem to construct a 
> chroot-able rootfs. We copy a lot of unnecessary files, making it very large. 
> We can potentially strip a lot files.



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

[jira] [Commented] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4312:


Let's discuss packaging issue here: 
https://github.com/deric/mesos-deb-packaging/pull/21

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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)

[jira] [Commented] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4312:


Hey guys, could you find another place to discuss this?

I think there is no differences in building DEB/RPM on Power and x86_64 since 
they use the same OS.

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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)

[jira] [Updated] (MESOS-5326) Error symbolic link of include/slave

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5326:
---
Labels: ibm  (was: )

> Error symbolic link of include/slave
> 
>
> Key: MESOS-5326
> URL: https://issues.apache.org/jira/browse/MESOS-5326
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>  Labels: ibm
>
> The symbolic link of include/slave to include/agent uses an absolute path to 
> $(DESTDIR)/include. But $(DESTDIR) is the tmp dir in build time, it will not 
> exist in target machine.



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

[jira] [Updated] (MESOS-5326) Error symbolic link of include/slave

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5326:
---
Shepherd:   (was: Vinod Kone)

> Error symbolic link of include/slave
> 
>
> Key: MESOS-5326
> URL: https://issues.apache.org/jira/browse/MESOS-5326
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> The symbolic link of include/slave to include/agent uses an absolute path to 
> $(DESTDIR)/include. But $(DESTDIR) is the tmp dir in build time, it will not 
> exist in target machine.



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

[jira] [Assigned] (MESOS-5326) Error symbolic link of include/slave

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-5326:
--

Assignee: Chen Zhiwei

> Error symbolic link of include/slave
> 
>
> Key: MESOS-5326
> URL: https://issues.apache.org/jira/browse/MESOS-5326
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> The symbolic link of include/slave to include/agent uses an absolute path to 
> $(DESTDIR)/include. But $(DESTDIR) is the tmp dir in build time, it will not 
> exist in target machine.



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

[jira] [Created] (MESOS-5326) Error symbolic link of include/slave

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-5326:
--

 Summary: Error symbolic link of include/slave
 Key: MESOS-5326
 URL: https://issues.apache.org/jira/browse/MESOS-5326
 Project: Mesos
  Issue Type: Bug
Reporter: Chen Zhiwei


The symbolic link of include/slave to include/agent uses an absolute path to 
$(DESTDIR)/include. But $(DESTDIR) is the tmp dir in build time, it will not 
exist in target machine.



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

[jira] [Created] (MESOS-5321) Add Ubuntu 16.04 to getting started document

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-5321:
--

 Summary: Add Ubuntu 16.04 to getting started document
 Key: MESOS-5321
 URL: https://issues.apache.org/jira/browse/MESOS-5321
 Project: Mesos
  Issue Type: Documentation
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei
Priority: Minor


Ubuntu 16.04 LTS released and should add it to getting started document.



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

[jira] [Updated] (MESOS-5244) Compilation failure on Ubuntu 16.04

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5244:
---
Labels: ibm mesosphere  (was: mesosphere)

> Compilation failure on Ubuntu 16.04
> ---
>
> Key: MESOS-5244
> URL: https://issues.apache.org/jira/browse/MESOS-5244
> Project: Mesos
>  Issue Type: Bug
>  Components: python api
>Reporter: Kapil Arya
>Assignee: Chen Zhiwei
>Priority: Blocker
>  Labels: ibm, mesosphere
> Fix For: 0.29.0
>
>
> I saw the following error when trying to compile Mesos on Ubuntu 16.04:
> {code}
> dekaksi:...mesos/build/src> make 
> ../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg
> Building protobuf Python egg ...
> cd ../3rdparty/protobuf-2.6.1/python && \
>   CC="gcc"  \
>   CXX="g++" \
>   CFLAGS="-g -O2 -Wno-unused-local-typedefs -g1 -O0"  
>   \
>   CXXFLAGS="-g -O2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
> -std=c++11 -g1 -O0"   \
>   PYTHONPATH=/home/kapil/mesos/build/3rdparty/distribute-0.6.26 \
>   /usr/bin/python setup.py build bdist_egg
> Traceback (most recent call last):
>   File "setup.py", line 11, in 
> from setuptools import setup, Extension
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/__init__.py", 
> line 2, in 
> from setuptools.extension import Extension, Library
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/extension.py", 
> line 5, in 
> from setuptools.dist import _get_unpatched
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/dist.py", line 
> 6, in 
> from setuptools.command.install import install
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/__init__.py",
>  line 8, in 
> from setuptools.command import install_scripts
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/install_scripts.py",
>  line 3, in 
> from pkg_resources import Distribution, PathMetadata, ensure_directory
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 704, in subscribe
> callback(dist)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2231, in activate
> self.insert_on(path)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2332, in insert_on
> "with distribute. Found one at %s" % str(self.location))
> ValueError: A 0.7-series setuptools cannot be installed with distribute. 
> Found one at /usr/lib/python2.7/dist-packages
> Makefile:10869: recipe for target 
> '../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg' failed
> make: *** [../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg] 
> Error 1
> {code}



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

[jira] [Commented] (MESOS-5244) Compilation failure on Ubuntu 16.04

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5244:


https://reviews.apache.org/r/46813/

> Compilation failure on Ubuntu 16.04
> ---
>
> Key: MESOS-5244
> URL: https://issues.apache.org/jira/browse/MESOS-5244
> Project: Mesos
>  Issue Type: Bug
>  Components: python api
>Reporter: Kapil Arya
>Assignee: Chen Zhiwei
>Priority: Blocker
>  Labels: mesosphere
> Fix For: 0.29.0
>
>
> I saw the following error when trying to compile Mesos on Ubuntu 16.04:
> {code}
> dekaksi:...mesos/build/src> make 
> ../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg
> Building protobuf Python egg ...
> cd ../3rdparty/protobuf-2.6.1/python && \
>   CC="gcc"  \
>   CXX="g++" \
>   CFLAGS="-g -O2 -Wno-unused-local-typedefs -g1 -O0"  
>   \
>   CXXFLAGS="-g -O2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
> -std=c++11 -g1 -O0"   \
>   PYTHONPATH=/home/kapil/mesos/build/3rdparty/distribute-0.6.26 \
>   /usr/bin/python setup.py build bdist_egg
> Traceback (most recent call last):
>   File "setup.py", line 11, in 
> from setuptools import setup, Extension
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/__init__.py", 
> line 2, in 
> from setuptools.extension import Extension, Library
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/extension.py", 
> line 5, in 
> from setuptools.dist import _get_unpatched
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/dist.py", line 
> 6, in 
> from setuptools.command.install import install
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/__init__.py",
>  line 8, in 
> from setuptools.command import install_scripts
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/install_scripts.py",
>  line 3, in 
> from pkg_resources import Distribution, PathMetadata, ensure_directory
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 704, in subscribe
> callback(dist)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2231, in activate
> self.insert_on(path)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2332, in insert_on
> "with distribute. Found one at %s" % str(self.location))
> ValueError: A 0.7-series setuptools cannot be installed with distribute. 
> Found one at /usr/lib/python2.7/dist-packages
> Makefile:10869: recipe for target 
> '../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg' failed
> make: *** [../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg] 
> Error 1
> {code}



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

[jira] [Commented] (MESOS-5244) Compilation failure on Ubuntu 16.04

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5244:


Since distribute was merged to setuptools, so I plan to replace it with 
setuptools.

> Compilation failure on Ubuntu 16.04
> ---
>
> Key: MESOS-5244
> URL: https://issues.apache.org/jira/browse/MESOS-5244
> Project: Mesos
>  Issue Type: Bug
>  Components: python api
>Reporter: Kapil Arya
>Assignee: Chen Zhiwei
>Priority: Blocker
>  Labels: mesosphere
> Fix For: 0.29.0
>
>
> I saw the following error when trying to compile Mesos on Ubuntu 16.04:
> {code}
> dekaksi:...mesos/build/src> make 
> ../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg
> Building protobuf Python egg ...
> cd ../3rdparty/protobuf-2.6.1/python && \
>   CC="gcc"  \
>   CXX="g++" \
>   CFLAGS="-g -O2 -Wno-unused-local-typedefs -g1 -O0"  
>   \
>   CXXFLAGS="-g -O2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
> -std=c++11 -g1 -O0"   \
>   PYTHONPATH=/home/kapil/mesos/build/3rdparty/distribute-0.6.26 \
>   /usr/bin/python setup.py build bdist_egg
> Traceback (most recent call last):
>   File "setup.py", line 11, in 
> from setuptools import setup, Extension
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/__init__.py", 
> line 2, in 
> from setuptools.extension import Extension, Library
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/extension.py", 
> line 5, in 
> from setuptools.dist import _get_unpatched
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/dist.py", line 
> 6, in 
> from setuptools.command.install import install
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/__init__.py",
>  line 8, in 
> from setuptools.command import install_scripts
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/install_scripts.py",
>  line 3, in 
> from pkg_resources import Distribution, PathMetadata, ensure_directory
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 704, in subscribe
> callback(dist)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2231, in activate
> self.insert_on(path)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2332, in insert_on
> "with distribute. Found one at %s" % str(self.location))
> ValueError: A 0.7-series setuptools cannot be installed with distribute. 
> Found one at /usr/lib/python2.7/dist-packages
> Makefile:10869: recipe for target 
> '../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg' failed
> make: *** [../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg] 
> Error 1
> {code}



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

[jira] [Assigned] (MESOS-5244) Compilation failure on Ubuntu 16.04

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-5244:
--

Assignee: Chen Zhiwei

> Compilation failure on Ubuntu 16.04
> ---
>
> Key: MESOS-5244
> URL: https://issues.apache.org/jira/browse/MESOS-5244
> Project: Mesos
>  Issue Type: Bug
>  Components: python api
>Reporter: Kapil Arya
>Assignee: Chen Zhiwei
>Priority: Blocker
>  Labels: mesosphere
> Fix For: 0.29.0
>
>
> I saw the following error when trying to compile Mesos on Ubuntu 16.04:
> {code}
> dekaksi:...mesos/build/src> make 
> ../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg
> Building protobuf Python egg ...
> cd ../3rdparty/protobuf-2.6.1/python && \
>   CC="gcc"  \
>   CXX="g++" \
>   CFLAGS="-g -O2 -Wno-unused-local-typedefs -g1 -O0"  
>   \
>   CXXFLAGS="-g -O2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
> -std=c++11 -g1 -O0"   \
>   PYTHONPATH=/home/kapil/mesos/build/3rdparty/distribute-0.6.26 \
>   /usr/bin/python setup.py build bdist_egg
> Traceback (most recent call last):
>   File "setup.py", line 11, in 
> from setuptools import setup, Extension
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/__init__.py", 
> line 2, in 
> from setuptools.extension import Extension, Library
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/extension.py", 
> line 5, in 
> from setuptools.dist import _get_unpatched
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/dist.py", line 
> 6, in 
> from setuptools.command.install import install
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/__init__.py",
>  line 8, in 
> from setuptools.command import install_scripts
>   File 
> "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/setuptools/command/install_scripts.py",
>  line 3, in 
> from pkg_resources import Distribution, PathMetadata, ensure_directory
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 704, in subscribe
> callback(dist)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2731, in 
> add_activation_listener(lambda dist: dist.activate())
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2231, in activate
> self.insert_on(path)
>   File "/home/kapil/mesos/build/3rdparty/distribute-0.6.26/pkg_resources.py", 
> line 2332, in insert_on
> "with distribute. Found one at %s" % str(self.location))
> ValueError: A 0.7-series setuptools cannot be installed with distribute. 
> Found one at /usr/lib/python2.7/dist-packages
> Makefile:10869: recipe for target 
> '../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg' failed
> make: *** [../3rdparty/protobuf-2.6.1/python/dist/protobuf-2.6.1-py2.7.egg] 
> Error 1
> {code}



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

[jira] [Commented] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4312:


Thanks Samuel, we have our daily build on Power for both RHEL and Ubuntu.

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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)

[jira] [Commented] (MESOS-4879) Update glog patch to support PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4879:


Yes, thanks for you work on this.

> Update glog patch to support PowerPC LE
> ---
>
> Key: MESOS-4879
> URL: https://issues.apache.org/jira/browse/MESOS-4879
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
> Fix For: 0.29.0
>
>
> This is a part of PowerPC LE porting



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

[jira] [Commented] (MESOS-5063) SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5063:


Should disable HTTP_PARSER_STRICT mode to get it this work.

I dont know how to add macro HTTP_PARSER_STRICT=0 to CMakefile, so I only 
update the Makefile.am:

https://reviews.apache.org/r/45917/

> SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail
> -
>
> Key: MESOS-5063
> URL: https://issues.apache.org/jira/browse/MESOS-5063
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.29.0
> Environment: Configured with SSL enabled
>Reporter: Greg Mann
>Assignee: Chen Zhiwei
>Priority: Critical
>  Labels: mesosphere, ssl, tests
> Fix For: 0.29.0
>
>
> These tests fail, with minimal logging output:
> {code}
> [ RUN  ] SSLTest.HTTPSGet
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:663: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSGet (137 ms)
> [ RUN  ] SSLTest.HTTPSPost
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:704: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSPost (243 ms)
> {code}
> It's worth noting that the 3rdparty http-parser library was recently 
> upgraded: 
> https://github.com/apache/mesos/commit/94df63f72146501872a06c6487e94bdfd0f23025



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

[jira] [Commented] (MESOS-5145) protobuf vendored but its depencencies are not

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5145:


I am confused, since enable Python and Java needs access to internet(or setup 
local mirror of pypi and maven).

And there is already a series of PRs for mesos-3rdparty repo 
(https://github.com/3rdparty/mesos-3rdparty/pulls/chenzhiwei).

> protobuf vendored but its depencencies are not
> --
>
> Key: MESOS-5145
> URL: https://issues.apache.org/jira/browse/MESOS-5145
> Project: Mesos
>  Issue Type: Bug
>  Components: build
>Reporter: David Robinson
>
> Updating [protobuf from 2.5 to 
> 2.6.1|https://github.com/apache/mesos/commit/51872fba7f94d80e55c9cc9b46f96780a938f626]
>  has caused Mesos builds to fail if pypi.python.org is unreachable. 
> Protobuf-2.6.1 requires 
> [google-apputils|https://pypi.python.org/pypi/google-apputils] and if it's 
> not available the build process will attempt to download it from pypi.
> Prior to this change it was possible to build Mesos without Internet access. 
> If the build process reaches out to arbitrary things on the Internet it's 
> impossible to guarantee build reproducibility.
> {noformat:title=snippet from setup.py in protobuf-2.6.1.tar.gz}
>   setup(name = 'protobuf',
> version = '2.6.1',
> ...
> setup_requires = ['google-apputils'],
> ...
> )
> {noformat}
> {noformat:title=snippet from build log}
> 08:20:49 DEBUG: Building protobuf Python egg ...
> 08:20:49 DEBUG: cd ../3rdparty/libprocess/3rdparty/protobuf-2.6.1/python &&   
> \
> 08:20:49 DEBUG: CC="gcc"  \
> 08:20:49 DEBUG: CXX="g++" \
> 08:20:49 DEBUG: CFLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic 
> -Wno-unused-local-typedefs"   \
> 08:20:49 DEBUG: CXXFLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic 
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized -std=c++11"   
>   \
> 08:20:49 DEBUG: 
> PYTHONPATH=/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26  
> \
> 08:20:49 DEBUG: /usr/bin/python2.7 setup.py build bdist_egg
> 08:20:49 DEBUG: Download error on 
> http://pypi.python.org/simple/google-apputils/: [Errno 111] Connection 
> refused -- Some packages may not be found!
> 08:20:49 DEBUG: Download error on 
> http://pypi.python.org/simple/google-apputils/: [Errno 111] Connection 
> refused -- Some packages may not be found!
> 08:20:49 DEBUG: Couldn't find index page for 'google-apputils' (maybe 
> misspelled?)
> 08:20:49 DEBUG: Download error on http://pypi.python.org/simple/: [Errno 111] 
> Connection refused -- Some packages may not be found!
> 08:20:49 DEBUG: No local packages or download links found for google-apputils
> 08:20:49 DEBUG: Traceback (most recent call last):
> 08:20:49 DEBUG:   File "setup.py", line 200, in 
> 08:20:49 DEBUG: "Protocol Buffers are Google's data interchange format.",
> 08:20:49 DEBUG:   File "/usr/lib64/python2.7/distutils/core.py", line 111, in 
> setup
> 08:20:49 DEBUG: _setup_distribution = dist = klass(attrs)
> 08:20:49 DEBUG:   File 
> "/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26/setuptools/dist.py",
>  line 221, in __init__
> 08:20:49 DEBUG: self.fetch_build_eggs(attrs.pop('setup_requires'))
> 08:20:49 DEBUG:   File 
> "/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26/setuptools/dist.py",
>  line 245, in fetch_build_eggs
> 08:20:49 DEBUG: parse_requirements(requires), 
> installer=self.fetch_build_egg
> 08:20:49 DEBUG:   File 
> "/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26/pkg_resources.py",
>  line 580, in resolve
> 08:20:49 DEBUG: dist = best[req.key] = env.best_match(req, self, 
> installer)
> 08:20:49 DEBUG:   File 
> "/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26/pkg_resources.py",
>  line 825, in best_match
> 08:20:49 DEBUG: return self.obtain(req, installer) # try and 
> download/install
> 08:20:49 DEBUG:   File 
> "/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26/pkg_resources.py",
>  line 837, in obtain
> 08:20:49 DEBUG: return installer(requirement)
> 08:20:49 DEBUG:   File 
> "/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26/setuptools/dist.py",
>  line 294, in fetch_build_egg
> 08:20:49 DEBUG: return cmd.easy_install(req)
> 08:20:49 DEBUG:   File 
> "/builddir/build/BUILD/mesos-0.29.0/3rdparty/distribute-0.6.26/setuptools/command/easy_install.py",
>  line 584, in easy_install
> 08:20:49 DEBUG: raise 

[jira] [Commented] (MESOS-4897) Update test cases to support PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4897:


[~vinodkone] Could you help setup the powerpc CI?

ENVIRONMENT='GLOG_v=0' CONFIGURATION='--enable-libevent --enable-ssl' 
OS='ppc64le/ubuntu:14.04' COMPILER=gcc ./support/docker_build.sh

> Update test cases to support PowerPC LE
> ---
>
> Key: MESOS-4897
> URL: https://issues.apache.org/jira/browse/MESOS-4897
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> Some docker related test cases will be failed on PowerPC LE, since the Docker 
> image 'alpine' can't be able to run on PowerPC LE platform.
> On PowerPC LE platform, the test cases can use Docker image 'ppc64le/busybox'.



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

[jira] [Comment Edited] (MESOS-4897) Update test cases to support PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei edited comment on MESOS-4897 at 4/6/16 9:35 AM:


I updated the support/docker_build.sh script to make it can work on Power 
machine. 

For the Docker related test cases, the default hardcoded Docker image name is 
`alpine`, [~vinodkone] could you give me some tips about how to change this?

There is a commit[1] to create base Docker image on runtime, just create a base 
Docker image before running Docker related test cases, and in Docker related 
test cases using this base Docker image.

[1]: https://reviews.apache.org/r/43956/

The patch for `support/docker_build.sh`: https://reviews.apache.org/r/45803/


was (Author: chenzhiwei):
I updated the support/docker_build.sh script to make it can work on Power 
machine. https://reviews.apache.org/r/45803/

> Update test cases to support PowerPC LE
> ---
>
> Key: MESOS-4897
> URL: https://issues.apache.org/jira/browse/MESOS-4897
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> Some docker related test cases will be failed on PowerPC LE, since the Docker 
> image 'alpine' can't be able to run on PowerPC LE platform.
> On PowerPC LE platform, the test cases can use Docker image 'ppc64le/busybox'.



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

[jira] [Commented] (MESOS-4897) Update test cases to support PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4897:


I updated the support/docker_build.sh script to make it can work on Power 
machine. https://reviews.apache.org/r/45803/

> Update test cases to support PowerPC LE
> ---
>
> Key: MESOS-4897
> URL: https://issues.apache.org/jira/browse/MESOS-4897
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> Some docker related test cases will be failed on PowerPC LE, since the Docker 
> image 'alpine' can't be able to run on PowerPC LE platform.
> On PowerPC LE platform, the test cases can use Docker image 'ppc64le/busybox'.



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

[jira] [Commented] (MESOS-4897) Update test cases to support PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4897:


Please check this patch: https://reviews.apache.org/r/45734/ and ignore 
-https://reviews.apache.org/r/42551/-.

> Update test cases to support PowerPC LE
> ---
>
> Key: MESOS-4897
> URL: https://issues.apache.org/jira/browse/MESOS-4897
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> Some docker related test cases will be failed on PowerPC LE, since the Docker 
> image 'alpine' can't be able to run on PowerPC LE platform.
> On PowerPC LE platform, the test cases can use Docker image 'ppc64le/busybox'.



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

[jira] [Updated] (MESOS-5121) pivot_root is not available

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5121:
---
Shepherd: Vinod Kone

> pivot_root is not available
> ---
>
> Key: MESOS-5121
> URL: https://issues.apache.org/jira/browse/MESOS-5121
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> When compile on ppc64le, it will through error message: 
> src/linux/fs.cpp:443:2: error: #error "pivot_root is not available"
> The current code logic in src/linux/fs.cpp is:
> {code}
> #ifdef __NR_pivot_root
>   int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
> #elif __x86_64__
>   // A workaround for systems that have an old glib but have a new
>   // kernel. The magic number '155' is the syscall number for
>   // 'pivot_root' on the x86_64 architecture, see
>   // arch/x86/syscalls/syscall_64.tbl
>   int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
> #else
> #error "pivot_root is not available"
> #endif
> {code}
> There is no old glib version and the new kernel version, it will never run 
> code in *#ifdef __NR_pivot_root* condition, and when I build on Ubuntu 
> 16.04(It has the latest linux kernel and glibc), it still can't step into the 
> *#ifdef __NR_pivot_root* condition.
> For powerpc case, I added another condition:
> {code}
> #elif __powerpc__ || __ppc__ || __powerpc64__ || __ppc64__
>   // A workaround for powerpc. The magic number '203' is the syscall
>   // number for 'pivot_root' on the powerpc architecture, see
>   // https://w3challs.com/syscalls/?arch=powerpc_64
>   int ret = ::syscall(203, newRoot.c_str(), putOld.c_str());
> {code}



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

[jira] [Commented] (MESOS-5121) pivot_root is not available

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5121:


Review URL: https://reviews.apache.org/r/45734/

> pivot_root is not available
> ---
>
> Key: MESOS-5121
> URL: https://issues.apache.org/jira/browse/MESOS-5121
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> When compile on ppc64le, it will through error message: 
> src/linux/fs.cpp:443:2: error: #error "pivot_root is not available"
> The current code logic in src/linux/fs.cpp is:
> {code}
> #ifdef __NR_pivot_root
>   int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
> #elif __x86_64__
>   // A workaround for systems that have an old glib but have a new
>   // kernel. The magic number '155' is the syscall number for
>   // 'pivot_root' on the x86_64 architecture, see
>   // arch/x86/syscalls/syscall_64.tbl
>   int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
> #else
> #error "pivot_root is not available"
> #endif
> {code}
> There is no old glib version and the new kernel version, it will never run 
> code in *#ifdef __NR_pivot_root* condition, and when I build on Ubuntu 
> 16.04(It has the latest linux kernel and glibc), it still can't step into the 
> *#ifdef __NR_pivot_root* condition.
> For powerpc case, I added another condition:
> {code}
> #elif __powerpc__ || __ppc__ || __powerpc64__ || __ppc64__
>   // A workaround for powerpc. The magic number '203' is the syscall
>   // number for 'pivot_root' on the powerpc architecture, see
>   // https://w3challs.com/syscalls/?arch=powerpc_64
>   int ret = ::syscall(203, newRoot.c_str(), putOld.c_str());
> {code}



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

[jira] [Updated] (MESOS-5121) pivot_root is not available

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5121:
---
Description: 
When compile on ppc64le, it will through error message: src/linux/fs.cpp:443:2: 
error: #error "pivot_root is not available"

The current code logic in src/linux/fs.cpp is:

{code}
#ifdef __NR_pivot_root
  int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
#elif __x86_64__
  // A workaround for systems that have an old glib but have a new
  // kernel. The magic number '155' is the syscall number for
  // 'pivot_root' on the x86_64 architecture, see
  // arch/x86/syscalls/syscall_64.tbl
  int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
#else
#error "pivot_root is not available"
#endif
{code}

There is no old glib version and the new kernel version, it will never run code 
in *#ifdef __NR_pivot_root* condition, and when I build on Ubuntu 16.04(It has 
the latest linux kernel and glibc), it still can't step into the *#ifdef 
__NR_pivot_root* condition.

For powerpc case, I added another condition:

{code}
#elif __powerpc__ || __ppc__ || __powerpc64__ || __ppc64__
  // A workaround for powerpc. The magic number '203' is the syscall
  // number for 'pivot_root' on the powerpc architecture, see
  // https://w3challs.com/syscalls/?arch=powerpc_64
  int ret = ::syscall(203, newRoot.c_str(), putOld.c_str());
{code}

  was:
When compile on ppc64le, it will through error message: src/linux/fs.cpp:443:2: 
error: #error "pivot_root is not available"

The current code logic in src/linux/fs.cpp is:

{code}
#ifdef __NR_pivot_root
  int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
#elif __x86_64__
  // A workaround for systems that have an old glib but have a new
  // kernel. The magic number '155' is the syscall number for
  // 'pivot_root' on the x86_64 architecture, see
  // arch/x86/syscalls/syscall_64.tbl
  int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
#else
#error "pivot_root is not available"
#endif
{code}

There is no old glib version and the new kernel version, it will never run code 
in *#ifdef __NR_pivot_root* condition, and when I build on Ubuntu 16.04(It has 
the latest linux kernel and glibc), it still can't step into the *#ifdef 
__NR_pivot_root* condition.


> pivot_root is not available
> ---
>
> Key: MESOS-5121
> URL: https://issues.apache.org/jira/browse/MESOS-5121
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> When compile on ppc64le, it will through error message: 
> src/linux/fs.cpp:443:2: error: #error "pivot_root is not available"
> The current code logic in src/linux/fs.cpp is:
> {code}
> #ifdef __NR_pivot_root
>   int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
> #elif __x86_64__
>   // A workaround for systems that have an old glib but have a new
>   // kernel. The magic number '155' is the syscall number for
>   // 'pivot_root' on the x86_64 architecture, see
>   // arch/x86/syscalls/syscall_64.tbl
>   int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
> #else
> #error "pivot_root is not available"
> #endif
> {code}
> There is no old glib version and the new kernel version, it will never run 
> code in *#ifdef __NR_pivot_root* condition, and when I build on Ubuntu 
> 16.04(It has the latest linux kernel and glibc), it still can't step into the 
> *#ifdef __NR_pivot_root* condition.
> For powerpc case, I added another condition:
> {code}
> #elif __powerpc__ || __ppc__ || __powerpc64__ || __ppc64__
>   // A workaround for powerpc. The magic number '203' is the syscall
>   // number for 'pivot_root' on the powerpc architecture, see
>   // https://w3challs.com/syscalls/?arch=powerpc_64
>   int ret = ::syscall(203, newRoot.c_str(), putOld.c_str());
> {code}



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

[jira] [Updated] (MESOS-5121) pivot_root is not available

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5121:
---
Description: 
When compile on ppc64le, it will through error message: src/linux/fs.cpp:443:2: 
error: #error "pivot_root is not available"

The current code logic in src/linux/fs.cpp is:

{code}
#ifdef __NR_pivot_root
  int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
#elif __x86_64__
  // A workaround for systems that have an old glib but have a new
  // kernel. The magic number '155' is the syscall number for
  // 'pivot_root' on the x86_64 architecture, see
  // arch/x86/syscalls/syscall_64.tbl
  int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
#else
#error "pivot_root is not available"
#endif
{code}

There is no old glib version and the new kernel version, it will never run code 
in *#ifdef __NR_pivot_root* condition, and when I build on Ubuntu 16.04(It has 
the latest linux kernel and glibc), it still can't step into the *#ifdef 
__NR_pivot_root* condition.

  was:When compile on ppc64le, it will through error message: 
src/linux/fs.cpp:443:2: error: #error "pivot_root is not available"


> pivot_root is not available
> ---
>
> Key: MESOS-5121
> URL: https://issues.apache.org/jira/browse/MESOS-5121
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> When compile on ppc64le, it will through error message: 
> src/linux/fs.cpp:443:2: error: #error "pivot_root is not available"
> The current code logic in src/linux/fs.cpp is:
> {code}
> #ifdef __NR_pivot_root
>   int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
> #elif __x86_64__
>   // A workaround for systems that have an old glib but have a new
>   // kernel. The magic number '155' is the syscall number for
>   // 'pivot_root' on the x86_64 architecture, see
>   // arch/x86/syscalls/syscall_64.tbl
>   int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
> #else
> #error "pivot_root is not available"
> #endif
> {code}
> There is no old glib version and the new kernel version, it will never run 
> code in *#ifdef __NR_pivot_root* condition, and when I build on Ubuntu 
> 16.04(It has the latest linux kernel and glibc), it still can't step into the 
> *#ifdef __NR_pivot_root* condition.



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

[jira] [Created] (MESOS-5121) pivot_root is not available

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-5121:
--

 Summary: pivot_root is not available
 Key: MESOS-5121
 URL: https://issues.apache.org/jira/browse/MESOS-5121
 Project: Mesos
  Issue Type: Bug
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei


When compile on ppc64le, it will through error message: src/linux/fs.cpp:443:2: 
error: #error "pivot_root is not available"



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

[jira] [Commented] (MESOS-4897) Update test cases to support PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4897:


[~vinodkone] Yes, this is the last issue. Could you help submit this patch? 
It's part of power porting.https://reviews.apache.org/r/42551/

> Update test cases to support PowerPC LE
> ---
>
> Key: MESOS-4897
> URL: https://issues.apache.org/jira/browse/MESOS-4897
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> Some docker related test cases will be failed on PowerPC LE, since the Docker 
> image 'alpine' can't be able to run on PowerPC LE platform.
> On PowerPC LE platform, the test cases can use Docker image 'ppc64le/busybox'.



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

[jira] [Updated] (MESOS-5069) Upgrade http-parser to v2.6.2

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-5069:
---
Shepherd: Vinod Kone

> Upgrade http-parser to v2.6.2
> -
>
> Key: MESOS-5069
> URL: https://issues.apache.org/jira/browse/MESOS-5069
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>




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

[jira] [Created] (MESOS-5069) Upgrade http-parser to v2.6.2

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-5069:
--

 Summary: Upgrade http-parser to v2.6.2
 Key: MESOS-5069
 URL: https://issues.apache.org/jira/browse/MESOS-5069
 Project: Mesos
  Issue Type: Improvement
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei






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

[jira] [Updated] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4312:
---
Description: 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.   (was: 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. 

The review list:
* Protobuf: https://reviews.apache.org/r/44257/
* Glog: https://reviews.apache.org/r/44252/
* Libev: https://reviews.apache.org/r/44378/
* Http-parser: https://reviews.apache.org/r/44372/
* Zookeeper: https://reviews.apache.org/r/44376/
* Leveldb: https://reviews.apache.org/r/44382/
* Mesos: https://reviews.apache.org/r/42551/)

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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)

[jira] [Commented] (MESOS-5063) SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5063:


https://reviews.apache.org/r/45471/

> SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail
> -
>
> Key: MESOS-5063
> URL: https://issues.apache.org/jira/browse/MESOS-5063
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.28.0
> Environment: Configured with SSL enabled
>Reporter: Greg Mann
>Assignee: Chen Zhiwei
>Priority: Critical
>  Labels: mesosphere, ssl, tests
> Fix For: 0.29.0
>
>
> These tests fail, with minimal logging output:
> {code}
> [ RUN  ] SSLTest.HTTPSGet
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:663: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSGet (137 ms)
> [ RUN  ] SSLTest.HTTPSPost
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:704: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSPost (243 ms)
> {code}
> It's worth noting that the 3rdparty http-parser library was recently 
> upgraded: 
> https://github.com/apache/mesos/commit/94df63f72146501872a06c6487e94bdfd0f23025



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

[jira] [Assigned] (MESOS-5063) SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-5063:
--

Assignee: Chen Zhiwei  (was: Greg Mann)

> SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail
> -
>
> Key: MESOS-5063
> URL: https://issues.apache.org/jira/browse/MESOS-5063
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.28.0
> Environment: Configured with SSL enabled
>Reporter: Greg Mann
>Assignee: Chen Zhiwei
>Priority: Critical
>  Labels: mesosphere, ssl, tests
> Fix For: 0.29.0
>
>
> These tests fail, with minimal logging output:
> {code}
> [ RUN  ] SSLTest.HTTPSGet
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:663: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSGet (137 ms)
> [ RUN  ] SSLTest.HTTPSPost
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:704: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSPost (243 ms)
> {code}
> It's worth noting that the 3rdparty http-parser library was recently 
> upgraded: 
> https://github.com/apache/mesos/commit/94df63f72146501872a06c6487e94bdfd0f23025



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

[jira] [Commented] (MESOS-4805) Update ry-http-parser-1c3624a to nodejs/http-parser 2.6.1

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4805:


Fix test case issues: https://reviews.apache.org/r/45471/

Details: https://issues.apache.org/jira/browse/MESOS-5063

> Update ry-http-parser-1c3624a to nodejs/http-parser 2.6.1
> -
>
> Key: MESOS-4805
> URL: https://issues.apache.org/jira/browse/MESOS-4805
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
> Fix For: 0.29.0
>
>
> See https://github.com/nodejs/http-parser/releases/tag/v2.6.1.
> The motivation is that nodejs/http-parser 2.6.1 has officially supported IBM 
> Power (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].



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

[jira] [Comment Edited] (MESOS-5063) SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei edited comment on MESOS-5063 at 3/30/16 4:55 AM:
-

It's a bug in http-parser 2.6.1, but was fixed in 2.6.2.

When there are white spaces between HTTP header fields and the colon, it will 
cause this issue.

`Content-Length : 123` will failed, but `Content-Length: 123` will be ok.

Details:

https://github.com/nodejs/http-parser/pull/189

https://github.com/nodejs/http-parser/commit/0b433671316ef7e6b73cae4ac23b8149fa0b9b24


was (Author: chenzhiwei):
It's a bug in http-parser 2.6.1, but was fixed in 2.6.2.

When there are white spaces between HTTP header fields and the semicolon, it 
will cause this issue.

`Content-Length : 123` will failed, but `Content-Length: 123` will be ok.

Details:

https://github.com/nodejs/http-parser/pull/189

https://github.com/nodejs/http-parser/commit/0b433671316ef7e6b73cae4ac23b8149fa0b9b24

> SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail
> -
>
> Key: MESOS-5063
> URL: https://issues.apache.org/jira/browse/MESOS-5063
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.28.0
> Environment: Configured with SSL enabled
>Reporter: Greg Mann
>Assignee: Greg Mann
>Priority: Critical
>  Labels: mesosphere, ssl, tests
> Fix For: 0.29.0
>
>
> These tests fail, with minimal logging output:
> {code}
> [ RUN  ] SSLTest.HTTPSGet
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:663: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSGet (137 ms)
> [ RUN  ] SSLTest.HTTPSPost
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:704: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSPost (243 ms)
> {code}
> It's worth noting that the 3rdparty http-parser library was recently 
> upgraded: 
> https://github.com/apache/mesos/commit/94df63f72146501872a06c6487e94bdfd0f23025



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

[jira] [Commented] (MESOS-5063) SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-5063:


It's a bug in http-parser 2.6.1, but was fixed in 2.6.2.

When there are white spaces between HTTP header fields and the semicolon, it 
will cause this issue.

`Content-Length : 123` will failed, but `Content-Length: 123` will be ok.

Details:

https://github.com/nodejs/http-parser/pull/189

https://github.com/nodejs/http-parser/commit/0b433671316ef7e6b73cae4ac23b8149fa0b9b24

> SSLTest.HTTPSPost and SSLTest.HTTPSGet tests fail
> -
>
> Key: MESOS-5063
> URL: https://issues.apache.org/jira/browse/MESOS-5063
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.28.0
> Environment: Configured with SSL enabled
>Reporter: Greg Mann
>Assignee: Greg Mann
>Priority: Critical
>  Labels: mesosphere, ssl, tests
> Fix For: 0.29.0
>
>
> These tests fail, with minimal logging output:
> {code}
> [ RUN  ] SSLTest.HTTPSGet
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:663: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSGet (137 ms)
> [ RUN  ] SSLTest.HTTPSPost
> ../../../3rdparty/libprocess/src/tests/ssl_tests.cpp:704: Failure
> (response).failure(): Failed to decode response
> [  FAILED  ] SSLTest.HTTPSPost (243 ms)
> {code}
> It's worth noting that the 3rdparty http-parser library was recently 
> upgraded: 
> https://github.com/apache/mesos/commit/94df63f72146501872a06c6487e94bdfd0f23025



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

[jira] [Commented] (MESOS-4805) Update ry-http-parser-1c3624a to nodejs/http-parser 2.6.1

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4805:


The 'flags_enum' was not submitted yet.




> Update ry-http-parser-1c3624a to nodejs/http-parser 2.6.1
> -
>
> Key: MESOS-4805
> URL: https://issues.apache.org/jira/browse/MESOS-4805
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
> Fix For: 0.29.0
>
>
> See https://github.com/nodejs/http-parser/releases/tag/v2.6.1.
> The motivation is that nodejs/http-parser 2.6.1 has officially supported IBM 
> Power (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].



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

[jira] [Commented] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4312:


[~vinodkone] Could you take a look about my new patches? Thanks.

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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. 
> The review list:
> * Protobuf: https://reviews.apache.org/r/44257/
> * Glog: https://reviews.apache.org/r/44252/
> * Libev: https://reviews.apache.org/r/44378/
> * Http-parser: https://reviews.apache.org/r/44372/
> * Zookeeper: https://reviews.apache.org/r/44376/
> * Leveldb: https://reviews.apache.org/r/44382/
> * Mesos: https://reviews.apache.org/r/42551/



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

[jira] [Commented] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4312:


Hi Vinod, I have rebased and tested the patches, please take a look.

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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. 
> The review list:
> * Protobuf: https://reviews.apache.org/r/44257/
> * Glog: https://reviews.apache.org/r/44252/
> * Libev: https://reviews.apache.org/r/44378/
> * Http-parser: https://reviews.apache.org/r/44372/
> * Zookeeper: https://reviews.apache.org/r/44376/
> * Leveldb: https://reviews.apache.org/r/44382/
> * Mesos: https://reviews.apache.org/r/42551/



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

[jira] [Commented] (MESOS-4879) Update glog patch to support PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4879:


Thanks, it seems this patch can't catch up your PR now. Maybe in next glog 
release.

> Update glog patch to support PowerPC LE
> ---
>
> Key: MESOS-4879
> URL: https://issues.apache.org/jira/browse/MESOS-4879
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> This is a part of PowerPC LE porting



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

[jira] [Commented] (MESOS-4802) Update leveldb patch file to suport PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4802:


Upgrade to 1.18 will not need to carry power related patches, but still need a 
patch file to remove dependencies just like now. Should I upgrade it?

> Update leveldb patch file to suport PowerPC LE
> --
>
> Key: MESOS-4802
> URL: https://issues.apache.org/jira/browse/MESOS-4802
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> See: https://github.com/google/leveldb/releases/tag/v1.18 for improvements / 
> bug fixes.
> The motivation is that leveldb 1.18 has officially supported IBM Power 
> (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].
> Update: Since someone updated leveldb to 1.4, so I only update the patch file 
> to support PowerPC LE. Because I don't think upgrade 3rdparty library 
> frequently is a good thing.



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

[jira] [Updated] (MESOS-4612) Update vendored ZooKeeper to 3.4.8

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4612:
---
Description: 
See: http://zookeeper.apache.org/doc/r3.4.8/releasenotes.html for improvements 
/ bug fixes

Added a new patch that solved 
[ZOOKEEPER-1643](https://issues.apache.org/jira/browse/ZOOKEEPER-1643)

The original patch: 


  was:See: http://zookeeper.apache.org/doc/r3.4.8/releasenotes.html for 
improvements / bug fixes


> Update vendored ZooKeeper to 3.4.8
> --
>
> Key: MESOS-4612
> URL: https://issues.apache.org/jira/browse/MESOS-4612
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Cody Maloney
>Assignee: Chen Zhiwei
>  Labels: mesosphere, tech-debt, zookeeper
>
> See: http://zookeeper.apache.org/doc/r3.4.8/releasenotes.html for 
> improvements / bug fixes
> Added a new patch that solved 
> [ZOOKEEPER-1643](https://issues.apache.org/jira/browse/ZOOKEEPER-1643)
> The original patch: 
> 



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

[jira] [Updated] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4312:
---
Description: 
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. 

The review list:
* Protobuf: https://reviews.apache.org/r/44257/
* Glog: https://reviews.apache.org/r/44252/
* Libev: https://reviews.apache.org/r/44378/
* Http-parser: https://reviews.apache.org/r/44372/
* Zookeeper: https://reviews.apache.org/r/44376/
* Leveldb: https://reviews.apache.org/r/44382/
* Mesos: https://reviews.apache.org/r/42551/

  was: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. 


> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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. 
> The review list:
> * Protobuf: https://reviews.apache.org/r/44257/
> * Glog: https://reviews.apache.org/r/44252/
> * Libev: https://reviews.apache.org/r/44378/
> * Http-parser: https://reviews.apache.org/r/44372/
> * Zookeeper: https://reviews.apache.org/r/44376/
> * Leveldb: https://reviews.apache.org/r/44382/
> * Mesos: https://reviews.apache.org/r/42551/



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

[jira] [Updated] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4312:
---
Shepherd: Vinod Kone  (was: Vinod Kone)

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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)

[jira] [Updated] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4312:
---
Shepherd: Vinod Kone  (was: Benjamin Mahler)

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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)

[jira] [Created] (MESOS-4897) Update test cases to support PowerPC LE

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-4897:
--

 Summary: Update test cases to support PowerPC LE
 Key: MESOS-4897
 URL: https://issues.apache.org/jira/browse/MESOS-4897
 Project: Mesos
  Issue Type: Improvement
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei


Some docker related test cases will be failed on PowerPC LE, since the Docker 
image 'alpine' can't be able to run on PowerPC LE platform.

On PowerPC LE platform, the test cases can use Docker image 'ppc64le/busybox'.



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

[jira] [Updated] (MESOS-4879) Update glog patch to suport PowerPC LE

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4879:
---
Description: This is a part of PowerPC LE porting

> Update glog patch to suport PowerPC LE
> --
>
> Key: MESOS-4879
> URL: https://issues.apache.org/jira/browse/MESOS-4879
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> This is a part of PowerPC LE porting



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

[jira] [Commented] (MESOS-4879) Update glog patch to suport PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4879:


https://reviews.apache.org/r/44252/

> Update glog patch to suport PowerPC LE
> --
>
> Key: MESOS-4879
> URL: https://issues.apache.org/jira/browse/MESOS-4879
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>




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

[jira] [Created] (MESOS-4879) Update glog patch to suport PowerPC LE

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-4879:
--

 Summary: Update glog patch to suport PowerPC LE
 Key: MESOS-4879
 URL: https://issues.apache.org/jira/browse/MESOS-4879
 Project: Mesos
  Issue Type: Improvement
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei






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

[jira] [Commented] (MESOS-4802) Update leveldb patch file to suport PowerPC LE

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4802:


https://reviews.apache.org/r/44382/

> Update leveldb patch file to suport PowerPC LE
> --
>
> Key: MESOS-4802
> URL: https://issues.apache.org/jira/browse/MESOS-4802
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> See: https://github.com/google/leveldb/releases/tag/v1.18 for improvements / 
> bug fixes.
> The motivation is that leveldb 1.18 has officially supported IBM Power 
> (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].
> Update: Since someone updated leveldb to 1.4, so I only update the patch file 
> to support PowerPC LE. Because I don't think upgrade 3rdparty library 
> frequently is a good thing.



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

[jira] [Updated] (MESOS-4802) Update leveldb patch file to suport PowerPC LE

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4802:
---
Description: 
See: https://github.com/google/leveldb/releases/tag/v1.18 for improvements / 
bug fixes.
The motivation is that leveldb 1.18 has officially supported IBM Power 
(ppc64le), so this is needed by 
[MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].

Update: Since someone updated leveldb to 1.4, so I only update the patch file 
to support PowerPC LE. Because I don't think upgrade 3rdparty library 
frequently is a good thing.

  was:
See: https://github.com/google/leveldb/releases/tag/v1.18 for improvements / 
bug fixes.
The motivation is that leveldb 1.18 has officially supported IBM Power 
(ppc64le), so this is needed by 
[MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].


> Update leveldb patch file to suport PowerPC LE
> --
>
> Key: MESOS-4802
> URL: https://issues.apache.org/jira/browse/MESOS-4802
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> See: https://github.com/google/leveldb/releases/tag/v1.18 for improvements / 
> bug fixes.
> The motivation is that leveldb 1.18 has officially supported IBM Power 
> (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].
> Update: Since someone updated leveldb to 1.4, so I only update the patch file 
> to support PowerPC LE. Because I don't think upgrade 3rdparty library 
> frequently is a good thing.



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

[jira] [Commented] (MESOS-4803) Update vendored libev to 4.22

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4803:


https://reviews.apache.org/r/44378/

> Update vendored libev to 4.22
> -
>
> Key: MESOS-4803
> URL: https://issues.apache.org/jira/browse/MESOS-4803
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> The motivation is that libev 4.22 has officially supported IBM Power 
> (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].



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

[jira] [Updated] (MESOS-4802) Update leveldb patch file to suport PowerPC LE

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-4802:
---
Summary: Update leveldb patch file to suport PowerPC LE  (was: Update 
vendored leveldb to 1.18)

> Update leveldb patch file to suport PowerPC LE
> --
>
> Key: MESOS-4802
> URL: https://issues.apache.org/jira/browse/MESOS-4802
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> See: https://github.com/google/leveldb/releases/tag/v1.18 for improvements / 
> bug fixes.
> The motivation is that leveldb 1.18 has officially supported IBM Power 
> (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].



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

[jira] [Commented] (MESOS-4678) Upgrade vendored Protobuf

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4678:


Thanks, I think I need to create a PR on 
https://github.com/3rdparty/mesos-3rdparty

> Upgrade vendored Protobuf
> -
>
> Key: MESOS-4678
> URL: https://issues.apache.org/jira/browse/MESOS-4678
> Project: Mesos
>  Issue Type: Improvement
>  Components: general
>Reporter: Neil Conway
>Assignee: Chen Zhiwei
>  Labels: 3rdParty, mesosphere, protobuf, tech-debt
>
> We currently vendor Protobuf 2.5.0. We should upgrade to Protobuf 2.6.1. This 
> introduces various bugfixes, performance improvements, and at least one new 
> feature we might want to eventually take advantage of ({{map}} data type). 
> AFAIK there should be no backward compatibility concerns.



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

[jira] [Assigned] (MESOS-4312) Porting Mesos on Power (ppc64le)

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-4312:
--

Assignee: Chen Zhiwei  (was: Qian Zhang)

> Porting Mesos on Power (ppc64le)
> 
>
> Key: MESOS-4312
> URL: https://issues.apache.org/jira/browse/MESOS-4312
> Project: Mesos
>  Issue Type: Epic
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> 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)

[jira] [Commented] (MESOS-4678) Upgrade vendored Protobuf

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4678:


https://reviews.apache.org/r/44257/

> Upgrade vendored Protobuf
> -
>
> Key: MESOS-4678
> URL: https://issues.apache.org/jira/browse/MESOS-4678
> Project: Mesos
>  Issue Type: Improvement
>  Components: general
>Reporter: Neil Conway
>  Labels: 3rdParty, mesosphere, protobuf, tech-debt
>
> We currently vendor Protobuf 2.5.0. We should upgrade to Protobuf 2.6.1. This 
> introduces various bugfixes, performance improvements, and at least one new 
> feature we might want to eventually take advantage of ({{map}} data type). 
> AFAIK there should be no backward compatibility concerns.



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

[jira] [Assigned] (MESOS-4678) Upgrade vendored Protobuf

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-4678:
--

Assignee: Chen Zhiwei

> Upgrade vendored Protobuf
> -
>
> Key: MESOS-4678
> URL: https://issues.apache.org/jira/browse/MESOS-4678
> Project: Mesos
>  Issue Type: Improvement
>  Components: general
>Reporter: Neil Conway
>Assignee: Chen Zhiwei
>  Labels: 3rdParty, mesosphere, protobuf, tech-debt
>
> We currently vendor Protobuf 2.5.0. We should upgrade to Protobuf 2.6.1. This 
> introduces various bugfixes, performance improvements, and at least one new 
> feature we might want to eventually take advantage of ({{map}} data type). 
> AFAIK there should be no backward compatibility concerns.



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

[jira] [Commented] (MESOS-4805) Update ry-http-parser-1c3624a to nodejs/http-parser 2.6.1

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4805:


https://reviews.apache.org/r/44372/

> Update ry-http-parser-1c3624a to nodejs/http-parser 2.6.1
> -
>
> Key: MESOS-4805
> URL: https://issues.apache.org/jira/browse/MESOS-4805
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Qian Zhang
>Assignee: Chen Zhiwei
>
> See https://github.com/nodejs/http-parser/releases/tag/v2.6.1.
> The motivation is that nodejs/http-parser 2.6.1 has officially supported IBM 
> Power (ppc64le), so this is needed by 
> [MESOS-4312|https://issues.apache.org/jira/browse/MESOS-4312].



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

[jira] [Commented] (MESOS-4774) Wrong symbolic link of some Mesos libraries

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-4774:


https://reviews.apache.org/r/43999/

> Wrong symbolic link of some Mesos libraries
> ---
>
> Key: MESOS-4774
> URL: https://issues.apache.org/jira/browse/MESOS-4774
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chen Zhiwei
>Assignee: Chen Zhiwei
>
> When installing Mesos by `make install`, it will create symbolic links from 
> $(DESTDIR)/$(pkgmoduledir)/$$lib to $$lib.
> As we can see it uses absolute path, but when building RPM/Debian package the 
> $(DESTDIR) is $BUILD_ROOT_DIR. Installing the RPM/Debian package on a target 
> host will broken the symbolic links since there is no $BUILD_ROOT_DIR on 
> target host.



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

[jira] [Commented] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-:


Hi Greg, you can take it over. Thank you very much.

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Commented] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-:


Hi Greg, you can take it over. Thank you very much.

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Commented] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-:


Hi Greg, you can take it over. Thank you very much.

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Commented] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-:


Hi Greg, you can take it over. Thank you very much.

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Issue Comment Deleted] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-:
---
Comment: was deleted

(was: Hi Greg, you can take it over. Thank you very much.)

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Issue Comment Deleted] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-:
---
Comment: was deleted

(was: Hi Greg, you can take it over. Thank you very much.)

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Issue Comment Deleted] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-:
---
Comment: was deleted

(was: Hi Greg, you can take it over. Thank you very much.)

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Commented] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-:


Hi Greg, you can take it over. Thank you very much.

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Issue Comment Deleted] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-:
---
Comment: was deleted

(was: Hi Greg, you can take it over. Thank you very much.)

> Add ACLs for the maintenance HTTP endpoints.
> 
>
> Key: MESOS-
> URL: https://issues.apache.org/jira/browse/MESOS-
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Chen Zhiwei
>
> In order to authorize the HTTP endpoints for maintenance (to be added in 
> MESOS-2067), we will need to add an ACL definition for performing maintenance 
> operations.



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

[jira] [Commented] (MESOS-2239) MasterAuthorizationTest.DuplicateRegistration is flaky

[Chen Zhiwei (JIRA)]

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

Chen Zhiwei commented on MESOS-2239:


Can't reproduce on OS X(yosemite), and from the getting started doc, Mesos does 
not support CentOS 5.x.

So should we close this bug?

> MasterAuthorizationTest.DuplicateRegistration is flaky
> --
>
> Key: MESOS-2239
> URL: https://issues.apache.org/jira/browse/MESOS-2239
> Project: Mesos
>  Issue Type: Bug
>  Components: test
> Environment: CentOS5 gcc-4.8
>Reporter: Jie Yu
>Assignee: Chen Zhiwei
>  Labels: flaky
>
> {noformat}
> 19:30:44 DEBUG: [ RUN  ] MasterAuthorizationTest.DuplicateRegistration
> 19:30:44 DEBUG: Using temporary directory 
> '/tmp/MasterAuthorizationTest_DuplicateRegistration_lTKlxz'
> 19:30:44 DEBUG: I0121 19:30:44.583595 54842 leveldb.cpp:176] Opened db in 
> 2.002477ms
> 19:30:44 DEBUG: I0121 19:30:44.584470 54842 leveldb.cpp:183] Compacted db in 
> 848351ns
> 19:30:44 DEBUG: I0121 19:30:44.584492 54842 leveldb.cpp:198] Created db 
> iterator in 3830ns
> 19:30:44 DEBUG: I0121 19:30:44.584506 54842 leveldb.cpp:204] Seeked to 
> beginning of db in 962ns
> 19:30:44 DEBUG: I0121 19:30:44.584519 54842 leveldb.cpp:273] Iterated through 
> 0 keys in the db in 598ns
> 19:30:44 DEBUG: I0121 19:30:44.584537 54842 replica.cpp:744] Replica 
> recovered with log positions 0 -> 0 with 1 holes and 0 unlearned
> 19:30:44 DEBUG: I0121 19:30:44.584684 54873 recover.cpp:449] Starting replica 
> recovery
> 19:30:44 DEBUG: I0121 19:30:44.584774 54859 recover.cpp:475] Replica is in 
> EMPTY status
> 19:30:44 DEBUG: I0121 19:30:44.586305 54881 replica.cpp:641] Replica in EMPTY 
> status received a broadcasted recover request
> 19:30:44 DEBUG: I0121 19:30:44.586943 54866 recover.cpp:195] Received a 
> recover response from a replica in EMPTY status
> 19:30:44 DEBUG: I0121 19:30:44.587247 54872 recover.cpp:566] Updating replica 
> status to STARTING
> 19:30:44 DEBUG: I0121 19:30:44.587838 54867 leveldb.cpp:306] Persisting 
> metadata (8 bytes) to leveldb took 393697ns
> 19:30:44 DEBUG: I0121 19:30:44.587862 54867 replica.cpp:323] Persisted 
> replica status to STARTING
> 19:30:44 DEBUG: I0121 19:30:44.587920 54877 recover.cpp:475] Replica is in 
> STARTING status
> 19:30:44 DEBUG: I0121 19:30:44.588341 54868 replica.cpp:641] Replica in 
> STARTING status received a broadcasted recover request
> 19:30:44 DEBUG: I0121 19:30:44.588577 54877 recover.cpp:195] Received a 
> recover response from a replica in STARTING status
> 19:30:44 DEBUG: I0121 19:30:44.589040 54863 recover.cpp:566] Updating replica 
> status to VOTING
> 19:30:44 DEBUG: I0121 19:30:44.589344 54871 leveldb.cpp:306] Persisting 
> metadata (8 bytes) to leveldb took 268257ns
> 19:30:44 DEBUG: I0121 19:30:44.589361 54871 replica.cpp:323] Persisted 
> replica status to VOTING
> 19:30:44 DEBUG: I0121 19:30:44.589426 54858 recover.cpp:580] Successfully 
> joined the Paxos group
> 19:30:44 DEBUG: I0121 19:30:44.589735 54858 recover.cpp:464] Recover process 
> terminated
> 19:30:44 DEBUG: I0121 19:30:44.593657 54866 master.cpp:262] Master 
> 20150121-193044-1711542956-52053-54842 (atlc-bev-05-sr1.corpdc.twttr.net) 
> started on 172.18.4.102:52053
> 19:30:44 DEBUG: I0121 19:30:44.593690 54866 master.cpp:308] Master only 
> allowing authenticated frameworks to register
> 19:30:44 DEBUG: I0121 19:30:44.593699 54866 master.cpp:313] Master only 
> allowing authenticated slaves to register
> 19:30:44 DEBUG: I0121 19:30:44.593708 54866 credentials.hpp:36] Loading 
> credentials for authentication from 
> '/tmp/MasterAuthorizationTest_DuplicateRegistration_lTKlxz/credentials'
> 19:30:44 DEBUG: I0121 19:30:44.593808 54866 master.cpp:357] Authorization 
> enabled
> 19:30:44 DEBUG: I0121 19:30:44.594319 54871 master.cpp:1219] The newly 
> elected leader is master@172.18.4.102:52053 with id 
> 20150121-193044-1711542956-52053-54842
> 19:30:44 DEBUG: I0121 19:30:44.594336 54871 master.cpp:1232] Elected as the 
> leading master!
> 19:30:44 DEBUG: I0121 19:30:44.594343 54871 master.cpp:1050] Recovering from 
> registrar
> 19:30:44 DEBUG: I0121 19:30:44.594403 54867 registrar.cpp:313] Recovering 
> registrar
> 19:30:44 DEBUG: I0121 19:30:44.594558 54858 log.cpp:660] Attempting to start 
> the writer
> 19:30:44 DEBUG: I0121 19:30:44.595000 54859 replica.cpp:477] Replica received 
> implicit promise request with proposal 1
> 19:30:44 DEBUG: I0121 19:30:44.595340 54859 leveldb.cpp:306] Persisting 
> metadata (8 bytes) to leveldb took 319942ns
> 19:30:44 DEBUG: I0121 19:30:44.595360 54859 replica.cpp:345] Persisted 
> promised to 1
> 19:30:44 DEBUG: I0121 19:30:44.595700 54878 coordinator.cpp:230] Coordinator 
> attemping to fill missing position
> 19:30:44 DEBUG: I0121 

[jira] [Created] (MESOS-4094) Enable Mesos build on ppc64le platform

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-4094:
--

 Summary: Enable Mesos build on ppc64le platform
 Key: MESOS-4094
 URL: https://issues.apache.org/jira/browse/MESOS-4094
 Project: Mesos
  Issue Type: Improvement
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei
Priority: Minor


Update the Mesos third party libs to enable Mesos build on ppc64le platform.



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

[jira] [Assigned] (MESOS-2239) MasterAuthorizationTest.DuplicateRegistration is flaky

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-2239:
--

Assignee: Chen Zhiwei

> MasterAuthorizationTest.DuplicateRegistration is flaky
> --
>
> Key: MESOS-2239
> URL: https://issues.apache.org/jira/browse/MESOS-2239
> Project: Mesos
>  Issue Type: Bug
>  Components: test
> Environment: CentOS5 gcc-4.8
>Reporter: Jie Yu
>Assignee: Chen Zhiwei
>  Labels: flaky, flaky-test
>
> {noformat}
> 19:30:44 DEBUG: [ RUN  ] MasterAuthorizationTest.DuplicateRegistration
> 19:30:44 DEBUG: Using temporary directory 
> '/tmp/MasterAuthorizationTest_DuplicateRegistration_lTKlxz'
> 19:30:44 DEBUG: I0121 19:30:44.583595 54842 leveldb.cpp:176] Opened db in 
> 2.002477ms
> 19:30:44 DEBUG: I0121 19:30:44.584470 54842 leveldb.cpp:183] Compacted db in 
> 848351ns
> 19:30:44 DEBUG: I0121 19:30:44.584492 54842 leveldb.cpp:198] Created db 
> iterator in 3830ns
> 19:30:44 DEBUG: I0121 19:30:44.584506 54842 leveldb.cpp:204] Seeked to 
> beginning of db in 962ns
> 19:30:44 DEBUG: I0121 19:30:44.584519 54842 leveldb.cpp:273] Iterated through 
> 0 keys in the db in 598ns
> 19:30:44 DEBUG: I0121 19:30:44.584537 54842 replica.cpp:744] Replica 
> recovered with log positions 0 -> 0 with 1 holes and 0 unlearned
> 19:30:44 DEBUG: I0121 19:30:44.584684 54873 recover.cpp:449] Starting replica 
> recovery
> 19:30:44 DEBUG: I0121 19:30:44.584774 54859 recover.cpp:475] Replica is in 
> EMPTY status
> 19:30:44 DEBUG: I0121 19:30:44.586305 54881 replica.cpp:641] Replica in EMPTY 
> status received a broadcasted recover request
> 19:30:44 DEBUG: I0121 19:30:44.586943 54866 recover.cpp:195] Received a 
> recover response from a replica in EMPTY status
> 19:30:44 DEBUG: I0121 19:30:44.587247 54872 recover.cpp:566] Updating replica 
> status to STARTING
> 19:30:44 DEBUG: I0121 19:30:44.587838 54867 leveldb.cpp:306] Persisting 
> metadata (8 bytes) to leveldb took 393697ns
> 19:30:44 DEBUG: I0121 19:30:44.587862 54867 replica.cpp:323] Persisted 
> replica status to STARTING
> 19:30:44 DEBUG: I0121 19:30:44.587920 54877 recover.cpp:475] Replica is in 
> STARTING status
> 19:30:44 DEBUG: I0121 19:30:44.588341 54868 replica.cpp:641] Replica in 
> STARTING status received a broadcasted recover request
> 19:30:44 DEBUG: I0121 19:30:44.588577 54877 recover.cpp:195] Received a 
> recover response from a replica in STARTING status
> 19:30:44 DEBUG: I0121 19:30:44.589040 54863 recover.cpp:566] Updating replica 
> status to VOTING
> 19:30:44 DEBUG: I0121 19:30:44.589344 54871 leveldb.cpp:306] Persisting 
> metadata (8 bytes) to leveldb took 268257ns
> 19:30:44 DEBUG: I0121 19:30:44.589361 54871 replica.cpp:323] Persisted 
> replica status to VOTING
> 19:30:44 DEBUG: I0121 19:30:44.589426 54858 recover.cpp:580] Successfully 
> joined the Paxos group
> 19:30:44 DEBUG: I0121 19:30:44.589735 54858 recover.cpp:464] Recover process 
> terminated
> 19:30:44 DEBUG: I0121 19:30:44.593657 54866 master.cpp:262] Master 
> 20150121-193044-1711542956-52053-54842 (atlc-bev-05-sr1.corpdc.twttr.net) 
> started on 172.18.4.102:52053
> 19:30:44 DEBUG: I0121 19:30:44.593690 54866 master.cpp:308] Master only 
> allowing authenticated frameworks to register
> 19:30:44 DEBUG: I0121 19:30:44.593699 54866 master.cpp:313] Master only 
> allowing authenticated slaves to register
> 19:30:44 DEBUG: I0121 19:30:44.593708 54866 credentials.hpp:36] Loading 
> credentials for authentication from 
> '/tmp/MasterAuthorizationTest_DuplicateRegistration_lTKlxz/credentials'
> 19:30:44 DEBUG: I0121 19:30:44.593808 54866 master.cpp:357] Authorization 
> enabled
> 19:30:44 DEBUG: I0121 19:30:44.594319 54871 master.cpp:1219] The newly 
> elected leader is master@172.18.4.102:52053 with id 
> 20150121-193044-1711542956-52053-54842
> 19:30:44 DEBUG: I0121 19:30:44.594336 54871 master.cpp:1232] Elected as the 
> leading master!
> 19:30:44 DEBUG: I0121 19:30:44.594343 54871 master.cpp:1050] Recovering from 
> registrar
> 19:30:44 DEBUG: I0121 19:30:44.594403 54867 registrar.cpp:313] Recovering 
> registrar
> 19:30:44 DEBUG: I0121 19:30:44.594558 54858 log.cpp:660] Attempting to start 
> the writer
> 19:30:44 DEBUG: I0121 19:30:44.595000 54859 replica.cpp:477] Replica received 
> implicit promise request with proposal 1
> 19:30:44 DEBUG: I0121 19:30:44.595340 54859 leveldb.cpp:306] Persisting 
> metadata (8 bytes) to leveldb took 319942ns
> 19:30:44 DEBUG: I0121 19:30:44.595360 54859 replica.cpp:345] Persisted 
> promised to 1
> 19:30:44 DEBUG: I0121 19:30:44.595700 54878 coordinator.cpp:230] Coordinator 
> attemping to fill missing position
> 19:30:44 DEBUG: I0121 19:30:44.596330 54859 replica.cpp:378] Replica received 
> explicit promise request for position 0 with proposal 2
> 19:30:44 DEBUG: I0121 

[jira] [Commented] (MESOS-2712) When trying to install mesos 0.22.0 version on Redhat Enterprise Linux 6.0 , i am getting error configure error cannot find libsvn_subr-1 headers . I tried with ./con

[Chen Zhiwei (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716271#comment-14716271
 ] 

Chen Zhiwei commented on MESOS-2712:


Hi, I encountered the same error on RHEL  7.1, simply install the 
subversion-devel package can solve this issue.

http://rpmfind.net/linux/rpm2html/search.php?query=subversion-develsubmit=Search+...system=arch=

 When trying to install mesos 0.22.0 version on Redhat Enterprise Linux 6.0 , 
 i am getting error configure error cannot find libsvn_subr-1 headers . I 
 tried with ./configure --with-svn option also but still the same. 
 --

 Key: MESOS-2712
 URL: https://issues.apache.org/jira/browse/MESOS-2712
 Project: Mesos
  Issue Type: Bug
  Components: general
Affects Versions: 0.22.0
Reporter: Sujit
Priority: Minor

 When trying to install mesos 0.22.0 version on Redhat Enterprise Linux 6.0 , 
 i am getting error configure error cannot find libsvn_subr-1 headers . I 
 tried with ./configure --with-svn option also but still the same. 



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

[jira] [Commented] (MESOS-2712) When trying to install mesos 0.22.0 version on Redhat Enterprise Linux 6.0 , i am getting error configure error cannot find libsvn_subr-1 headers . I tried with ./con

[Chen Zhiwei (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716275#comment-14716275
 ] 

Chen Zhiwei commented on MESOS-2712:


Here is the official SVN package repo: http://pkgs.repoforge.org/subversion/

 When trying to install mesos 0.22.0 version on Redhat Enterprise Linux 6.0 , 
 i am getting error configure error cannot find libsvn_subr-1 headers . I 
 tried with ./configure --with-svn option also but still the same. 
 --

 Key: MESOS-2712
 URL: https://issues.apache.org/jira/browse/MESOS-2712
 Project: Mesos
  Issue Type: Bug
  Components: general
Affects Versions: 0.22.0
Reporter: Sujit
Priority: Minor

 When trying to install mesos 0.22.0 version on Redhat Enterprise Linux 6.0 , 
 i am getting error configure error cannot find libsvn_subr-1 headers . I 
 tried with ./configure --with-svn option also but still the same. 



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

[jira] [Commented] (MESOS-3218) Enhance the bootstrap script

[Chen Zhiwei (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661194#comment-14661194
 ] 

Chen Zhiwei commented on MESOS-3218:


Yes, but I think this enhancement is still needed. We can't avoid accident 
things.

 Enhance the bootstrap script
 

 Key: MESOS-3218
 URL: https://issues.apache.org/jira/browse/MESOS-3218
 Project: Mesos
  Issue Type: Improvement
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei
Priority: Trivial

 Running bootstrap command in Mesos root directory will create some link files.
 But it can't handle below case:
 1. Users accidently create an invalid link file
 $ ln -s .gitignore-templat .gitignore
 2. Then running bootstrap command will show an error message
 $ ./bootstrap 
 ln: failed to create symbolic link ‘.gitignore’: File exists
 The `test -e` command can't recognize invalid link file.



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

[jira] [Created] (MESOS-3218) Enhance the bootstrap script

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-3218:
--

 Summary: Enhance the bootstrap script
 Key: MESOS-3218
 URL: https://issues.apache.org/jira/browse/MESOS-3218
 Project: Mesos
  Issue Type: Improvement
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei
Priority: Trivial


Running bootstrap command in Mesos root directory will create some link files.

But it can't handle below case:

1. Users accidently create an invalid link file
$ ln -s .gitignore-templat .gitignore

2. Then running bootstrap command will show an error message
$ ./bootstrap 
ln: failed to create symbolic link ‘.gitignore’: File exists

The `test -e` command can't recognize invalid link file.



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

[jira] [Assigned] (MESOS-2932) There is a typo in docs/docker-containerizer.md file

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei reassigned MESOS-2932:
--

Assignee: Chen Zhiwei

 There is a typo in docs/docker-containerizer.md file
 

 Key: MESOS-2932
 URL: https://issues.apache.org/jira/browse/MESOS-2932
 Project: Mesos
  Issue Type: Bug
  Components: documentation
Affects Versions: 0.22.1
Reporter: Chen Zhiwei
Assignee: Chen Zhiwei
Priority: Minor
  Labels: documentation

 A docker image currently supports having a entrypoint and/or a default 
 command.
 The `a entrypoint` should be `an entrypoint`.



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

[jira] [Updated] (MESOS-2932) There is a typo in docs/docker-containerizer.md file

[Chen Zhiwei (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Zhiwei updated MESOS-2932:
---
Assignee: (was: Chen Zhiwei)

 There is a typo in docs/docker-containerizer.md file
 

 Key: MESOS-2932
 URL: https://issues.apache.org/jira/browse/MESOS-2932
 Project: Mesos
  Issue Type: Bug
  Components: documentation
Affects Versions: 0.22.1
Reporter: Chen Zhiwei
Priority: Minor
  Labels: documentation

 A docker image currently supports having a entrypoint and/or a default 
 command.
 The `a entrypoint` should be `an entrypoint`.



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

[jira] [Created] (MESOS-2932) There is a typo in docs/docker-containerizer.md file

[Chen Zhiwei (JIRA)]

Chen Zhiwei created MESOS-2932:
--

 Summary: There is a typo in docs/docker-containerizer.md file
 Key: MESOS-2932
 URL: https://issues.apache.org/jira/browse/MESOS-2932
 Project: Mesos
  Issue Type: Bug
  Components: documentation
Affects Versions: 0.22.1
Reporter: Chen Zhiwei
Priority: Minor


A docker image currently supports having a entrypoint and/or a default command.

The `a entrypoint` should be `an entrypoint`.



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