[jira] [Created] (MESOS-10087) Updated master & agent's HTTP endpoints for showing resource limits
Qian Zhang created MESOS-10087: -- Summary: Updated master & agent's HTTP endpoints for showing resource limits Key: MESOS-10087 URL: https://issues.apache.org/jira/browse/MESOS-10087 Project: Mesos Issue Type: Task Reporter: Qian Zhang We need to update Mesos master's `/state`, `/frameworks`, `/tasks` endpoints and agent's `/state` endpoint to show task's resource limits in their outputs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10045) Validate task’s resources limits and the `shared_cgroups` field in Mesos master
[ https://issues.apache.org/jira/browse/MESOS-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann reassigned MESOS-10045: - Assignee: Greg Mann > Validate task’s resources limits and the `shared_cgroups` field in Mesos > master > --- > > Key: MESOS-10045 > URL: https://issues.apache.org/jira/browse/MESOS-10045 > Project: Mesos > Issue Type: Task >Reporter: Qian Zhang >Assignee: Greg Mann >Priority: Major > > When launching a task, we need to validate: > # Only CPU and memory are supported as resource limits. > # Resource limit must be larger than resource request. > ** We need to be careful about the command task case, in which case we add > an allowance (0.1 CPUs and 32MB memory, see > [here|https://github.com/apache/mesos/blob/1.9.0/src/slave/slave.cpp#L6663:L6677] > for details) for the executor, so we need to validate task resource limit is > larger than task resource request + this allowance, otherwise the executor > will be launched with limits < requests. > # `TaskInfo` can only include resource limits when the relevant agent > possesses the TASK_RESOURCE_LIMITS capability. > # The value of the field `shared_cgroups` should be same for all the tasks > launched by a single default executor. > # It is not allowed to set resource limits for the task which has the field > `shared_cgroups` set as true. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10044) Add a new capability `TASK_RESOURCE_LIMITS` into Mesos agent
[ https://issues.apache.org/jira/browse/MESOS-10044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann reassigned MESOS-10044: - Assignee: Greg Mann > Add a new capability `TASK_RESOURCE_LIMITS` into Mesos agent > > > Key: MESOS-10044 > URL: https://issues.apache.org/jira/browse/MESOS-10044 > Project: Mesos > Issue Type: Task >Reporter: Qian Zhang >Assignee: Greg Mann >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10073) Implement SSL downgrade on the native SSL socket
[
https://issues.apache.org/jira/browse/MESOS-10073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu reassigned MESOS-10073:
-
Assignee: Joseph Wu
> Implement SSL downgrade on the native SSL socket
>
>
> Key: MESOS-10073
> URL: https://issues.apache.org/jira/browse/MESOS-10073
> Project: Mesos
> Issue Type: Task
>Reporter: Joseph Wu
>Assignee: Joseph Wu
>Priority: Minor
> Labels: foundations, ssl
>
> The new SSL socket implementation (the non-libevent one) does not currently
> implement the SSL downgrade hack. We could probably use {{peek}} to achieve
> the same result, or modify our socket BIO to look at the first few bytes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MESOS-10034) Agent/executor domain socket communication
[ https://issues.apache.org/jira/browse/MESOS-10034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014308#comment-17014308 ] Benno Evers commented on MESOS-10034: - During implementation, we reduced the scope of this epic to exclude custom executors running in containers with their own rootfs (obsoleting the MESOS-10060 and MESOS-10037 tickets) I've attached the patches implementing that functionality to the respective tickets. The rest of the code has been committed to master and will land in Mesos 1.10. > Agent/executor domain socket communication > -- > > Key: MESOS-10034 > URL: https://issues.apache.org/jira/browse/MESOS-10034 > Project: Mesos > Issue Type: Epic >Reporter: Benno Evers >Assignee: Benno Evers >Priority: Major > Fix For: 1.10 > > > Enable executors to communicate with Mesos agents via unix domain sockets. > Design: > https://docs.google.com/document/d/1FzlIlK8542pgLSLwXBXp7Hf_nI5qQkkMsN3vkJD48L4/edit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10034) Agent/executor domain socket communication
[ https://issues.apache.org/jira/browse/MESOS-10034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benno Evers reassigned MESOS-10034: --- Fix Version/s: 1.10 Target Version/s: 1.10 Assignee: Benno Evers Resolution: Fixed > Agent/executor domain socket communication > -- > > Key: MESOS-10034 > URL: https://issues.apache.org/jira/browse/MESOS-10034 > Project: Mesos > Issue Type: Epic >Reporter: Benno Evers >Assignee: Benno Evers >Priority: Major > Fix For: 1.10 > > > Enable executors to communicate with Mesos agents via unix domain sockets. > Design: > https://docs.google.com/document/d/1FzlIlK8542pgLSLwXBXp7Hf_nI5qQkkMsN3vkJD48L4/edit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10086) Add support for systemd socket activation for mesos domain sockets
[
https://issues.apache.org/jira/browse/MESOS-10086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benno Evers reassigned MESOS-10086:
---
Fix Version/s: 1.10
Assignee: Benno Evers
Resolution: Fixed
{noformat}
commit 8a9eb868ff3979df1cb68ebf56cb451b411e06a9 (HEAD -> master, origin/master)
Author: Benno Evers
Date: Thu Jan 9 15:48:48 2020 +0100
Added systemd support to domain socket agent flag.
Added the ability to specify a unix domain socket
as `systemd:` for the `--domain_socket_location`
agent flag.
This will instruct the agent to expect the domain socket
being passed by systemd with the specified name.
Review: https://reviews.apache.org/r/71977
commit b73965de9874559c02bed42cd597e6ec678a461d
Author: Benno Evers
Date: Thu Jan 9 15:43:29 2020 +0100
Added support for systemd socket activation API.
Added support for the systemd socket activation api,
that allows systemd to pass listening file descriptors
to a given service.
Review: https://reviews.apache.org/r/71976
{noformat}
> Add support for systemd socket activation for mesos domain sockets
> --
>
> Key: MESOS-10086
> URL: https://issues.apache.org/jira/browse/MESOS-10086
> Project: Mesos
> Issue Type: Task
>Reporter: Benno Evers
>Assignee: Benno Evers
>Priority: Major
> Fix For: 1.10
>
>
> We should implement support for systemd socket activation for the domain
> socket used by agents and executors, so that it does not need to be removed
> and re-created on agent startup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MESOS-10086) Add support for systemd socket activation for mesos domain sockets
Benno Evers created MESOS-10086: --- Summary: Add support for systemd socket activation for mesos domain sockets Key: MESOS-10086 URL: https://issues.apache.org/jira/browse/MESOS-10086 Project: Mesos Issue Type: Task Reporter: Benno Evers We should implement support for systemd socket activation for the domain socket used by agents and executors, so that it does not need to be removed and re-created on agent startup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
