[jira] [Commented] (MESOS-5227) Implement HTTP Docker Executor that uses the Executor Library
[ https://issues.apache.org/jira/browse/MESOS-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350409#comment-15350409 ] Jay Guo commented on MESOS-5227: It would be great if you could put a few words on each review link to summarize. > Implement HTTP Docker Executor that uses the Executor Library > - > > Key: MESOS-5227 > URL: https://issues.apache.org/jira/browse/MESOS-5227 > Project: Mesos > Issue Type: Bug >Reporter: Vinod Kone >Assignee: Yong Tang > > Similar to what we did with the HTTP command executor in MESOS-3558 we should > have a HTTP docker executor that can speak the v1 Executor API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5714) Specify soname for libmesos.so to major release
Tim Harper created MESOS-5714:
-
Summary: Specify soname for libmesos.so to major release
Key: MESOS-5714
URL: https://issues.apache.org/jira/browse/MESOS-5714
Project: Mesos
Issue Type: Improvement
Components: build
Affects Versions: 0.28.2
Reporter: Tim Harper
I've installed mesos using the CentOS 7 package, and am building the Ceph-Mesos
framework. I've noticed when running {{ldd}} that {{ceph-mesos}} is depending
on too specific of a version of libmesos, which means that the build will be
broken on subsequent point releases.
This seems to be because the {{soname}} for libmesos is set to a very
unforgiving value. If {{libmesos-0.28.2}} truly isn't ABI compatible with
{{libmesos-0.28.x}}, then I suppose this is set correctly and this ticket
should be closed summarily, albeit unfortunate.
Here is the {{readelf}} output for {{libmesos}}
{code}
[root@6e189e07b470 /]# readelf -d /usr/local/lib/libmesos-0.28.2.so
Dynamic section at offset 0x194cd18 contains 43 entries:
TagType Name/Value
0x0001 (NEEDED) Shared library: [libcrypt.so.1]
0x0001 (NEEDED) Shared library: [libexpat.so.1]
0x0001 (NEEDED) Shared library: [libdb-5.3.so]
0x0001 (NEEDED) Shared library: [libsasl2.so.3]
0x0001 (NEEDED) Shared library: [libsvn_delta-1.so.0]
0x0001 (NEEDED) Shared library: [libsvn_subr-1.so.0]
0x0001 (NEEDED) Shared library: [libaprutil-1.so.0]
0x0001 (NEEDED) Shared library: [libapr-1.so.0]
0x0001 (NEEDED) Shared library: [libpthread.so.0]
0x0001 (NEEDED) Shared library: [libdl.so.2]
0x0001 (NEEDED) Shared library: [libcurl.so.4]
0x0001 (NEEDED) Shared library: [libz.so.1]
0x0001 (NEEDED) Shared library: [librt.so.1]
0x0001 (NEEDED) Shared library: [libstdc++.so.6]
0x0001 (NEEDED) Shared library: [libm.so.6]
0x0001 (NEEDED) Shared library: [libc.so.6]
0x0001 (NEEDED) Shared library: [ld-linux-x86-64.so.2]
0x0001 (NEEDED) Shared library: [libgcc_s.so.1]
0x000e (SONAME) Library soname: [libmesos-0.28.2.so]
0x000f (RPATH) Library rpath: [/usr/lib/mesos]
0x000c (INIT) 0x92a1f0
0x000d (FINI) 0x13a8e94
0x0019 (INIT_ARRAY) 0x1ae
0x001b (INIT_ARRAYSZ) 1712 (bytes)
0x001a (FINI_ARRAY) 0x1ae8f38
0x001c (FINI_ARRAYSZ) 8 (bytes)
0x6ef5 (GNU_HASH) 0x228
0x0005 (STRTAB) 0x1b0be8
0x0006 (SYMTAB) 0x66a08
0x000a (STRSZ) 6130210 (bytes)
0x000b (SYMENT) 24 (bytes)
0x0003 (PLTGOT) 0x1b66000
0x0002 (PLTRELSZ) 387000 (bytes)
0x0014 (PLTREL) RELA
0x0017 (JMPREL) 0x8cba38
0x0007 (RELA) 0x7a5018
0x0008 (RELASZ) 1206816 (bytes)
0x0009 (RELAENT)24 (bytes)
0x6ffe (VERNEED)0x7a4e38
0x6fff (VERNEEDNUM) 8
0x6ff0 (VERSYM) 0x78960a
0x6ff9 (RELACOUNT) 1357
0x (NULL) 0x0
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5514) Implement LIST_FILES Call in v1 agent API.
[
https://issues.apache.org/jira/browse/MESOS-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350379#comment-15350379
]
Anand Mazumdar commented on MESOS-5514:
---
{noformat}
commit 97ee7e475bfcccb0b7e6aabf3d1929731a1dffbb
Author: Anand Mazumdar
Date: Sun Jun 26 20:06:44 2016 -0700
Added `FileInfo` protobuf for describing a File.
This change would be needed later for implementing the `LIST_FILES`
call for the Master/Agent v1 API.
Review: https://reviews.apache.org/r/49214/
{noformat}
> Implement LIST_FILES Call in v1 agent API.
> --
>
> Key: MESOS-5514
> URL: https://issues.apache.org/jira/browse/MESOS-5514
> Project: Mesos
> Issue Type: Task
>Reporter: Vinod Kone
>Assignee: Abhishek Dasgupta
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5705) ZK credential is exposed in /flags and /state
[ https://issues.apache.org/jira/browse/MESOS-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-5705: -- Assignee: Alexander Rojas > ZK credential is exposed in /flags and /state > - > > Key: MESOS-5705 > URL: https://issues.apache.org/jira/browse/MESOS-5705 > Project: Mesos > Issue Type: Task > Components: master, security >Reporter: Adam B >Assignee: Alexander Rojas >Priority: Critical > Labels: mesosphere, security > Fix For: 1.0.0 > > > Mesos allows zk credentials to be embedded in the zk url, but exposes these > credentials in the /flags and /state endpoint. Even though /state is > authorized, it only filters out frameworks/tasks, so the top-level flags are > shown to any authenticated user. > "zk": "zk://dcos_mesos_master:my_secret_password@127.0.0.1:2181/mesos", > We need to find some way to hide this data, or even add a first-class > VIEW_FLAGS acl that applies to any endpoint that exposes flags. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5705) ZK credential is exposed in /flags and /state
[ https://issues.apache.org/jira/browse/MESOS-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350314#comment-15350314 ] Adam B commented on MESOS-5705: --- The more I think about it, there's no good reason (besides backwards compatibility) to show the flags in /state when they're already available in /flags. Anything that's important enough to belong in /state should be pulled up into /state proper, rather than getting dragged in with the rest of the flags. We obviously can't just stop showing flags in /state, but we could add a `--hide_flags` flag (or protect_flags, etc.) that is disabled by default, so that clusters upgrading aren't hit by the behavior change, and they can explicitly set the legacy mode if they want it to survive the future upgrade (>6mo) when we change to hiding flags by default. Eventually (2.0?) we can change to an API where we only have a dedicated endpoint for flags. Note that this means that MESOS-5706 would no longer be needed, as we can recommend that users hide_flags, and then use GET_ENDPOINT_WITH_PATH=/flags to protect their master/agent flags. > ZK credential is exposed in /flags and /state > - > > Key: MESOS-5705 > URL: https://issues.apache.org/jira/browse/MESOS-5705 > Project: Mesos > Issue Type: Task > Components: master, security >Reporter: Adam B >Priority: Critical > Labels: mesosphere, security > Fix For: 1.0.0 > > > Mesos allows zk credentials to be embedded in the zk url, but exposes these > credentials in the /flags and /state endpoint. Even though /state is > authorized, it only filters out frameworks/tasks, so the top-level flags are > shown to any authenticated user. > "zk": "zk://dcos_mesos_master:my_secret_password@127.0.0.1:2181/mesos", > We need to find some way to hide this data, or even add a first-class > VIEW_FLAGS acl that applies to any endpoint that exposes flags. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-970) Upgrade bundled leveldb to 1.18
[ https://issues.apache.org/jira/browse/MESOS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350272#comment-15350272 ] Tomasz Janiszewski commented on MESOS-970: -- Ping. What more is required? > Upgrade bundled leveldb to 1.18 > --- > > Key: MESOS-970 > URL: https://issues.apache.org/jira/browse/MESOS-970 > Project: Mesos > Issue Type: Improvement > Components: replicated log >Reporter: Benjamin Mahler >Assignee: Tomasz Janiszewski > > We currently bundle leveldb 1.4, and the latest version is leveldb 1.18. > Upgrade to 1.18 could solve the problems when build Mesos in some non-x86 > architecture CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5710) The /logging/toggle endpoint accepts requests with any http method
[ https://issues.apache.org/jira/browse/MESOS-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-5710: -- Fix Version/s: (was: 1.0.0) > The /logging/toggle endpoint accepts requests with any http method > -- > > Key: MESOS-5710 > URL: https://issues.apache.org/jira/browse/MESOS-5710 > Project: Mesos > Issue Type: Task >Reporter: Adam B >Assignee: Adam B >Priority: Minor > Labels: mesosphere, security > > Any of a GET, POST, PUT, or DELETE to > `/logging/toggle?level=INFO=5mins` will set the log level > and return 200. To be consistent with REST-like syntax, DELETE, GET, and even > POST are wrong and should return a MethodNotAllowed. > Once this endpoint no longer accepts GET, it is no longer appropriate to use > the GET_ENDPOINT acl here. Instead we could create a new > PUT_ENDPOINT_WITH_PATH acl (which hopefully ignores query params), or add a > first-class TOGGLE_LOGGING acl. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5710) The /logging/toggle endpoint accepts requests with any http method
[ https://issues.apache.org/jira/browse/MESOS-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-5710: -- Sprint: (was: Mesosphere Sprint 38) > The /logging/toggle endpoint accepts requests with any http method > -- > > Key: MESOS-5710 > URL: https://issues.apache.org/jira/browse/MESOS-5710 > Project: Mesos > Issue Type: Task >Reporter: Adam B >Priority: Minor > Labels: mesosphere, security > > Any of a GET, POST, PUT, or DELETE to > `/logging/toggle?level=INFO=5mins` will set the log level > and return 200. To be consistent with REST-like syntax, DELETE, GET, and even > POST are wrong and should return a MethodNotAllowed. > Once this endpoint no longer accepts GET, it is no longer appropriate to use > the GET_ENDPOINT acl here. Instead we could create a new > PUT_ENDPOINT_WITH_PATH acl (which hopefully ignores query params), or add a > first-class TOGGLE_LOGGING acl. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5710) The /logging/toggle endpoint accepts requests with any http method
[ https://issues.apache.org/jira/browse/MESOS-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-5710: -- Assignee: (was: Adam B) > The /logging/toggle endpoint accepts requests with any http method > -- > > Key: MESOS-5710 > URL: https://issues.apache.org/jira/browse/MESOS-5710 > Project: Mesos > Issue Type: Task >Reporter: Adam B >Priority: Minor > Labels: mesosphere, security > > Any of a GET, POST, PUT, or DELETE to > `/logging/toggle?level=INFO=5mins` will set the log level > and return 200. To be consistent with REST-like syntax, DELETE, GET, and even > POST are wrong and should return a MethodNotAllowed. > Once this endpoint no longer accepts GET, it is no longer appropriate to use > the GET_ENDPOINT acl here. Instead we could create a new > PUT_ENDPOINT_WITH_PATH acl (which hopefully ignores query params), or add a > first-class TOGGLE_LOGGING acl. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5710) The /logging/toggle endpoint accepts requests with any http method
[ https://issues.apache.org/jira/browse/MESOS-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B reassigned MESOS-5710: - Assignee: Adam B > The /logging/toggle endpoint accepts requests with any http method > -- > > Key: MESOS-5710 > URL: https://issues.apache.org/jira/browse/MESOS-5710 > Project: Mesos > Issue Type: Task >Reporter: Adam B >Assignee: Adam B >Priority: Minor > Labels: mesosphere, security > Fix For: 1.0.0 > > > Any of a GET, POST, PUT, or DELETE to > `/logging/toggle?level=INFO=5mins` will set the log level > and return 200. To be consistent with REST-like syntax, DELETE, GET, and even > POST are wrong and should return a MethodNotAllowed. > Once this endpoint no longer accepts GET, it is no longer appropriate to use > the GET_ENDPOINT acl here. Instead we could create a new > PUT_ENDPOINT_WITH_PATH acl (which hopefully ignores query params), or add a > first-class TOGGLE_LOGGING acl. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5710) The /logging/toggle endpoint accepts requests with any http method
[ https://issues.apache.org/jira/browse/MESOS-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350138#comment-15350138 ] Adam B commented on MESOS-5710: --- This is not new, and is not limited just to /logging/toggle, so I think we can defer this past 1.0. > The /logging/toggle endpoint accepts requests with any http method > -- > > Key: MESOS-5710 > URL: https://issues.apache.org/jira/browse/MESOS-5710 > Project: Mesos > Issue Type: Task >Reporter: Adam B >Assignee: Adam B >Priority: Minor > Labels: mesosphere, security > Fix For: 1.0.0 > > > Any of a GET, POST, PUT, or DELETE to > `/logging/toggle?level=INFO=5mins` will set the log level > and return 200. To be consistent with REST-like syntax, DELETE, GET, and even > POST are wrong and should return a MethodNotAllowed. > Once this endpoint no longer accepts GET, it is no longer appropriate to use > the GET_ENDPOINT acl here. Instead we could create a new > PUT_ENDPOINT_WITH_PATH acl (which hopefully ignores query params), or add a > first-class TOGGLE_LOGGING acl. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5700) Benchmark for Resource class (protobuf vs. C++)
[ https://issues.apache.org/jira/browse/MESOS-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaus Ma updated MESOS-5700: Summary: Benchmark for Resource class (protobuf vs. C++) (was: Benchmark for Resource class) > Benchmark for Resource class (protobuf vs. C++) > --- > > Key: MESOS-5700 > URL: https://issues.apache.org/jira/browse/MESOS-5700 > Project: Mesos > Issue Type: Bug >Reporter: Klaus Ma >Assignee: Klaus Ma > > Add benchmark of Resource class for Allocation Performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5692) Add helper function "begin_with/end_with" to strings
[ https://issues.apache.org/jira/browse/MESOS-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350062#comment-15350062 ] Klaus Ma commented on MESOS-5692: - https://reviews.apache.org/r/49140/ > Add helper function "begin_with/end_with" to strings > > > Key: MESOS-5692 > URL: https://issues.apache.org/jira/browse/MESOS-5692 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Klaus Ma >Priority: Minor > Labels: newbie > > Add helper function to check whether a string is start/end with special char. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
