[jira] [Commented] (MESOS-7884) Support containerd on Mesos.
[ https://issues.apache.org/jira/browse/MESOS-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123394#comment-17123394 ] xiaowei commented on MESOS-7884: [~qianzhang] by containerd support CRI not Docker CNM, which more commonly, and containerd support plugin runtime like runc or other runtime engine. And the coming CGoup V2. Most importantly, the docker community goes where cannot be make sure. > Support containerd on Mesos. > > > Key: MESOS-7884 > URL: https://issues.apache.org/jira/browse/MESOS-7884 > Project: Mesos > Issue Type: Epic > Components: containerization >Reporter: Gilbert Song >Priority: Major > Labels: containerd, containerizer > > containerd v1.0 is very close (v1.0.0 alpha 4 now) to the formal release. We > should consider support containerd on Mesos, either by refactoring the docker > containerizer or introduce a new containerd containerizer. Design and > suggestions are definitely welcome. > https://github.com/containerd/containerd -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MESOS-7884) Support containerd on Mesos.
[ https://issues.apache.org/jira/browse/MESOS-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106157#comment-17106157 ] xiaowei commented on MESOS-7884: Is there any plan for this? > Support containerd on Mesos. > > > Key: MESOS-7884 > URL: https://issues.apache.org/jira/browse/MESOS-7884 > Project: Mesos > Issue Type: Epic > Components: containerization >Reporter: Gilbert Song >Priority: Major > Labels: containerd, containerizer > > containerd v1.0 is very close (v1.0.0 alpha 4 now) to the formal release. We > should consider support containerd on Mesos, either by refactoring the docker > containerizer or introduce a new containerd containerizer. Design and > suggestions are definitely welcome. > https://github.com/containerd/containerd -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MESOS-9780) Improve "picky" framework resource allocation under random sorter.
[ https://issues.apache.org/jira/browse/MESOS-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16941730#comment-16941730 ] xiaowei commented on MESOS-9780: which means need a mechanism, to allow mesos framework tell mesos allocator their resources constraints. For now, mesos offer have two main features: (1) quota management (2) reserve resource on specified agents. Reserve api is a kind of method, can achieve this target for "picky" framework, but this method will change framework lanuch task behavior, and make too many resources reserved fragments for different roles, and make too many mesos api call for reserve of each applications (e.g. marathon framework), that will also make allocator resources schedule useless. > Improve "picky" framework resource allocation under random sorter. > -- > > Key: MESOS-9780 > URL: https://issues.apache.org/jira/browse/MESOS-9780 > Project: Mesos > Issue Type: Improvement > Components: allocation >Reporter: Meng Zhu >Priority: Major > Labels: resource-management > > Picky frameworks are frameworks that are interested in some particular set of > resources. > With the current offer model, such a framework usually keeps declining and > filter uninterested offers until accepting an offer that meets its needs. > While picky frameworks are always prone to performance issues. These > frameworks are more likely to experience offer starvation issues under random > sorter than the DRF sorter. > Under DRF sorter, declining offers or Mesos side resource filtering do not > affect the framework's dominant resource share. Since other frameworks might > get resource allocated at the same time which brings up their shares > comparatively, a declined/filtered framework would usually have a higher > chance of getting other offers as time goes by (if it keeps declining). This > reduces the time such a framework getting what it wants eventually. > Random sorter, however, is stateless. A decline or filter action has no > effect on the chance of a framework getting offers. A framework declining or > filtering an offer essentially wastes a shot for nothing. It becomes a truly > altruistic act with no perceived gain on the framework side. This makes the > random sorter likely to perform poorly compared to DRF in terms of handling > picky frameworks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-9184) A new API for master information, like the state api but subtract the slaves and task
xiaowei created MESOS-9184:
--
Summary: A new API for master information, like the state api but
subtract the slaves and task
Key: MESOS-9184
URL: https://issues.apache.org/jira/browse/MESOS-9184
Project: Mesos
Issue Type: Improvement
Components: HTTP API
Reporter: xiaowei
Now, Mesos provides two HTTP Endpoints: `/state` & `/state-summary` for the
master status info. In the `/state-summary` API, it report the frameworks and
slaves statistics info. In the `/state` API, the response like this:
{code:java}
// https://github.com/apache/mesos/blob/master/src/master/http.cpp#L2742
// Omitted the flags detail
{
"version" : "0.28.0",
"git_sha" : "9d5889b5a265849886a533965f4aefefd1fbd103",
"git_branch" : "refs/heads/master",
"git_tag" : "0.28.0",
"build_date" : "2016-02-15 10:00:28",
"build_time" : 149228,
"build_user" : "mesos-user",
"start_time" : 1455643643.42422,
"elected_time" : 1455643643.43457,
"id" : "b5eac2c5-609b-4ca1-a352-61941702fc9e",
"pid" : "master@127.0.0.1:5050",
"hostname" : "localhost",
"activated_slaves" : 0,
"deactivated_slaves" : 0,
"cluster" : "test-cluster",
"leader" : "master@127.0.0.1:5050",
"log_dir" : "/var/log",
"external_log_file" : "mesos.log",
"flags" : {...},
"slaves" : [],
"frameworks" : [],
"completed_frameworks" : [],
"orphan_tasks" : [],
"unregistered_frameworks" : []",
}
{code}
These information contains the master program build info, current master
process info and the whole cluster running info like slaves、frameworks、tasks.
Hope :D there is a new api to report the master program build info and process
info, and only contains the master information. it will be much more simply and
fast.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-7479) Add explicit check on URI fetcher docker plugin to reject v1 registry.
[ https://issues.apache.org/jira/browse/MESOS-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514233#comment-16514233 ] xiaowei commented on MESOS-7479: does this still need to be checked? > Add explicit check on URI fetcher docker plugin to reject v1 registry. > -- > > Key: MESOS-7479 > URL: https://issues.apache.org/jira/browse/MESOS-7479 > Project: Mesos > Issue Type: Improvement >Reporter: Gilbert Song >Priority: Major > > Currently, unified containerizer only supports v2 docker registry. The URI > fetcher docker plugin should explicitly check that the registry is v2, and > return failure for v1 with sufficient error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MESOS-7168) Agent should validate that the nested container ID does not exceed certain length.
[ https://issues.apache.org/jira/browse/MESOS-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509032#comment-16509032 ] xiaowei edited comment on MESOS-7168 at 6/12/18 1:16 AM: - the generated id is uuid, include dash, total 36. Normal we can set the limit to 255, did we should consider windows os? [~gilbert] If not only windows 10, the file path will be limit to 260. In Windows 10, the whole path limits to [32767|[https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath].] And I think it does not need to be reconfigured by mesos administrator. was (Author: xiaowei-cuc): the generated id is uuid, include dash, total 36. Normal we can set the limit to 255, did we should consider windows os? [~gilbert] If not just windows 10, the file path will be limit to 260. In Windows 10, the whole path limits to [32767|[https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath].] And I think it does not need to be reconfigured by mesos administrator. > Agent should validate that the nested container ID does not exceed certain > length. > -- > > Key: MESOS-7168 > URL: https://issues.apache.org/jira/browse/MESOS-7168 > Project: Mesos > Issue Type: Bug > Components: containerization >Affects Versions: 1.1.0, 1.2.0 >Reporter: Jie Yu >Assignee: xiaowei >Priority: Major > Labels: newbie > > This is related to MESOS-691. > Since nested container ID is generated by the executor, the agent should > verify that the length of it does not exceed certain length. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-7168) Agent should validate that the nested container ID does not exceed certain length.
[ https://issues.apache.org/jira/browse/MESOS-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509032#comment-16509032 ] xiaowei commented on MESOS-7168: the generated id is uuid, include dash, total 36. Normal we can set the limit to 255, did we should consider windows os? [~gilbert] If not just windows 10, the file path will be limit to 260. In Windows 10, the whole path limits to [32767|[https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath].] And I think it does not need to be reconfigured by mesos administrator. > Agent should validate that the nested container ID does not exceed certain > length. > -- > > Key: MESOS-7168 > URL: https://issues.apache.org/jira/browse/MESOS-7168 > Project: Mesos > Issue Type: Bug > Components: containerization >Affects Versions: 1.1.0, 1.2.0 >Reporter: Jie Yu >Assignee: xiaowei >Priority: Major > Labels: newbie > > This is related to MESOS-691. > Since nested container ID is generated by the executor, the agent should > verify that the length of it does not exceed certain length. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-7168) Agent should validate that the nested container ID does not exceed certain length.
[ https://issues.apache.org/jira/browse/MESOS-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaowei reassigned MESOS-7168: -- Assignee: xiaowei > Agent should validate that the nested container ID does not exceed certain > length. > -- > > Key: MESOS-7168 > URL: https://issues.apache.org/jira/browse/MESOS-7168 > Project: Mesos > Issue Type: Bug > Components: containerization >Affects Versions: 1.1.0, 1.2.0 >Reporter: Jie Yu >Assignee: xiaowei >Priority: Major > Labels: newbie > > This is related to MESOS-691. > Since nested container ID is generated by the executor, the agent should > verify that the length of it does not exceed certain length. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
