[jira] [Commented] (MESOS-5038) Added a any mechanism for futures
[
https://issues.apache.org/jira/browse/MESOS-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213869#comment-15213869
]
haosdent commented on MESOS-5038:
-
As you see, we use {{any}} in https://reviews.apache.org/r/45085/diff/
{code}
any(futures).onAny(defer(PID(this),
&CgroupsIsolatorProcess::__prepare,
containerId,
lambda::_1));
{code}
> Added a any mechanism for futures
> -
>
> Key: MESOS-5038
> URL: https://issues.apache.org/jira/browse/MESOS-5038
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
>Reporter: haosdent
>Assignee: haosdent
>
> Now we already have {{collect}} and {{await}} mechanisms which would wait for
> a list of {{Future}}. However, we would like to return immediately if any of
> the list of {{Future}} complete instead of wait for the whole list finished
> in {{collect}}. The interface of this any mechanism could be
> {code}
> template
> Future any(const std::list>& futures);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5038) Added a any mechanism for futures
[
https://issues.apache.org/jira/browse/MESOS-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213864#comment-15213864
]
Jay Guo commented on MESOS-5038:
[~haosd...@gmail.com] Do you mind giving an example where we may use this in
current codebase?
> Added a any mechanism for futures
> -
>
> Key: MESOS-5038
> URL: https://issues.apache.org/jira/browse/MESOS-5038
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
>Reporter: haosdent
>Assignee: haosdent
>
> Now we already have {{collect}} and {{await}} mechanisms which would wait for
> a list of {{Future}}. However, we would like to return immediately if any of
> the list of {{Future}} complete instead of wait for the whole list finished
> in {{collect}}. The interface of this any mechanism could be
> {code}
> template
> Future any(const std::list>& futures);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5038) Added a any mechanism for futures
[
https://issues.apache.org/jira/browse/MESOS-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213856#comment-15213856
]
haosdent commented on MESOS-5038:
-
[~guoger] For example, you wait for a list of futures. You want to continue if
any of them status becomes ready.
> Added a any mechanism for futures
> -
>
> Key: MESOS-5038
> URL: https://issues.apache.org/jira/browse/MESOS-5038
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
>Reporter: haosdent
>Assignee: haosdent
>
> Now we already have {{collect}} and {{await}} mechanisms which would wait for
> a list of {{Future}}. However, we would like to return immediately if any of
> the list of {{Future}} complete instead of wait for the whole list finished
> in {{collect}}. The interface of this any mechanism could be
> {code}
> template
> Future any(const std::list>& futures);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5038) Added a any mechanism for futures
[
https://issues.apache.org/jira/browse/MESOS-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213808#comment-15213808
]
Jay Guo commented on MESOS-5038:
what's the use case of this one?
> Added a any mechanism for futures
> -
>
> Key: MESOS-5038
> URL: https://issues.apache.org/jira/browse/MESOS-5038
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
>Reporter: haosdent
>Assignee: haosdent
>
> Now we already have {{collect}} and {{await}} mechanisms which would wait for
> a list of {{Future}}. However, we would like to return immediately if any of
> the list of {{Future}} complete instead of wait for the whole list finished
> in {{collect}}. The interface of this any mechanism could be
> {code}
> template
> Future any(const std::list>& futures);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3976) C++ HTTP Scheduler Library does not work with SSL enabled
[ https://issues.apache.org/jira/browse/MESOS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-3976: -- Sprint: Mesosphere Sprint 32 > C++ HTTP Scheduler Library does not work with SSL enabled > - > > Key: MESOS-3976 > URL: https://issues.apache.org/jira/browse/MESOS-3976 > Project: Mesos > Issue Type: Bug > Components: framework, HTTP API >Reporter: Joseph Wu >Assignee: Anand Mazumdar > Labels: mesosphere, security > > The C++ HTTP scheduler library does not work against Mesos when SSL is > enabled (without downgrade). > The fix should be simple: > * The library should detect if SSL is enabled. > * If SSL is enabled, connections should be made with HTTPS instead of HTTP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4950) Implement reconnect funtionality in the scheduler library.
[
https://issues.apache.org/jira/browse/MESOS-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-4950:
--
Sprint: Mesosphere Sprint 32
> Implement reconnect funtionality in the scheduler library.
> --
>
> Key: MESOS-4950
> URL: https://issues.apache.org/jira/browse/MESOS-4950
> Project: Mesos
> Issue Type: Bug
>Reporter: Anand Mazumdar
> Labels: mesosphere
>
> Currently, there is no way for the schedulers to force a reconnection attempt
> with the master using the scheduler library {{src/scheduler/scheduler.cpp}}.
> It is specifically useful in scenarios where there is a one way network
> partition with the master. Due to this, the scheduler has not received any
> {{HEARTBEAT}} events from the master. In this case, the scheduler might want
> to force a reconnection attempt with the master instead of relying on the
> {{disconnected}} callback.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3559) Make the Command Scheduler use the HTTP Scheduler Library
[
https://issues.apache.org/jira/browse/MESOS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-3559:
--
Sprint: Mesosphere Sprint 32
> Make the Command Scheduler use the HTTP Scheduler Library
> -
>
> Key: MESOS-3559
> URL: https://issues.apache.org/jira/browse/MESOS-3559
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere
>
> We should make the Command Scheduler in {{src/cli/executor.cpp}} use the
> Scheduler Library {{src/scheduler/scheduler.cpp}} instead of the Scheduler
> Driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3782) Replace Master/Slave Terminology Phase I - Add duplicate binaries (or create symlinks)
[
https://issues.apache.org/jira/browse/MESOS-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213741#comment-15213741
]
zhou xing commented on MESOS-3782:
--
[~klueska], here is a plan that we want to try:
1. Add a new program named {{mesos-agent}} in {{mesos/src/Makefile.am}} which
has the similar make rules to {{mess-slave}}. This will generate a duplicate
executable file named {{mesos-agent}} in {{mesos/build/.libs}} after {{make}}
(or in {{/usr/local/sbin}} after {{make install}})
2. For the shell scripts in {{mesos/bin}} or {{mesos/src/deploy}}, firstly, we
can rename them to use the word "agent", e.g. {{mesos-slave.sh}} to
{{mesos-agent.sh}}; secondly, change the invocation of all the {{mesos-slave}}
call to {{mesos-agent}} call in the shell scripts content.
3. Change the {{mesos/configure.ac}} and add symlink creation to create link
files named like **mesos-slave.sh** to link them to the **mesos-agent.sh**.
After step 3, there will be **mesos-slave.sh** and **mesos-agent.sh** in the
{{mesos/build/bin}} folder at the same time, so use can both use
{{mesos-slave.sh}} or {{mesos-agent.sh}} to start the slave node
> Replace Master/Slave Terminology Phase I - Add duplicate binaries (or create
> symlinks)
> --
>
> Key: MESOS-3782
> URL: https://issues.apache.org/jira/browse/MESOS-3782
> Project: Mesos
> Issue Type: Task
>Reporter: Diana Arroyo
>Assignee: zhou xing
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-1739) Allow slave reconfiguration on restart
[ https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213730#comment-15213730 ] Deshi Xiao commented on MESOS-1739: --- in first try patch: https://reviews.apache.org/r/25525/diff/13#1 i only found a superset logic, if we want to change the attributes, how can i do it? so i think resources cannot be changed without kill old tasks. only attributes is satisfied with mutable purpose. > Allow slave reconfiguration on restart > -- > > Key: MESOS-1739 > URL: https://issues.apache.org/jira/browse/MESOS-1739 > Project: Mesos > Issue Type: Epic >Reporter: Patrick Reilly > Labels: external-volumes, mesosphere, myriad > > Make it so that either via a slave restart or a out of process "reconfigure" > ping, the attributes and resources of a slave can be updated to be a superset > of what they used to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1739) Allow slave reconfiguration on restart
[ https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213720#comment-15213720 ] Deshi Xiao edited comment on MESOS-1739 at 3/28/16 2:18 AM: -Based on Vinod Kone's Comments on MESOS-1739, i suggest only update Attributes only. the Resources is very host-relative parameters, use currently restart policy is enough to support our purpose- read design docs again and review Vinod's comments. we just need implement the slave restart to update the configuration without kill task. was (Author: xds2000): Based on Vinod Kone's Comments on MESOS-1739, i suggest only update Attributes only. the Resources is very host-relative parameters, use currently restart policy is enough to support our purpose. > Allow slave reconfiguration on restart > -- > > Key: MESOS-1739 > URL: https://issues.apache.org/jira/browse/MESOS-1739 > Project: Mesos > Issue Type: Epic >Reporter: Patrick Reilly > Labels: external-volumes, mesosphere, myriad > > Make it so that either via a slave restart or a out of process "reconfigure" > ping, the attributes and resources of a slave can be updated to be a superset > of what they used to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1739) Allow slave reconfiguration on restart
[ https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213720#comment-15213720 ] Deshi Xiao commented on MESOS-1739: --- Based on Vinod Kone's Comments on MESOS-1739, i suggest only update Attributes only. the Resources is very host-relative parameters, use currently restart policy is enough to support our purpose. > Allow slave reconfiguration on restart > -- > > Key: MESOS-1739 > URL: https://issues.apache.org/jira/browse/MESOS-1739 > Project: Mesos > Issue Type: Epic >Reporter: Patrick Reilly > Labels: external-volumes, mesosphere, myriad > > Make it so that either via a slave restart or a out of process "reconfigure" > ping, the attributes and resources of a slave can be updated to be a superset > of what they used to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4369) Enhance DockerExecuter to support Docker's user-defined networks
[
https://issues.apache.org/jira/browse/MESOS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213656#comment-15213656
]
Avinash Sridharan commented on MESOS-4369:
--
Hi [~ezrasilvera] don't see an update on the RB for the patch that you
submitted. Just checking if you are still working on this?
Thanks!!
> Enhance DockerExecuter to support Docker's user-defined networks
>
>
> Key: MESOS-4369
> URL: https://issues.apache.org/jira/browse/MESOS-4369
> Project: Mesos
> Issue Type: Improvement
> Components: docker
>Reporter: Qian Zhang
>Assignee: Ezra Silvera
> Labels: mesosphere
>
> Currently DockerContainerizer supports the following network options which
> are Docker built-in networks:
> {code}
> message DockerInfo {
> ...
> // Network options.
> enum Network {
> HOST = 1;
> BRIDGE = 2;
> NONE = 3;
> }
> ...
> {code}
> However, since docker 1.9, Docker now supports user-defined networks (both
> local and overlays) - e.g., {{docker network create --driver bridge
> my-network}},. The user can then create containers that need to be attached
> to these networks e.g., {{docker run --net=my-network}},
> We need to enhance DockerExecuter to support such network option so that the
> Docker container that can connect into such network.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5042) Add cpu subsystem support in cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5042:
Component/s: cgroups
> Add cpu subsystem support in cgroups unified isolator
> -
>
> Key: MESOS-5042
> URL: https://issues.apache.org/jira/browse/MESOS-5042
> Project: Mesos
> Issue Type: Task
> Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Add cgroups cpu subsystem support in cgroups unified isolator. And we need to
> port the test cases of {{CgroupsCpushareIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5041) Add cgroups unified isolator
[ https://issues.apache.org/jira/browse/MESOS-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5041: Component/s: cgroups > Add cgroups unified isolator > > > Key: MESOS-5041 > URL: https://issues.apache.org/jira/browse/MESOS-5041 > Project: Mesos > Issue Type: Task > Components: cgroups, isolation >Reporter: haosdent >Assignee: haosdent > > Implement the cgroups unified isolator and enable it in Mesos containerizer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5040) Add cgroups_subsystems flag for cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5040:
Component/s: cgroups
> Add cgroups_subsystems flag for cgroups unified isolator
>
>
> Key: MESOS-5040
> URL: https://issues.apache.org/jira/browse/MESOS-5040
> Project: Mesos
> Issue Type: Task
> Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> In past, we specify the cgroups subsystems we used in Mesos containerizer in
> {{--isolation}} flag. In cgroups unified isolator, we need to add this
> separate flag to control which subsystems we enable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5039) Add Subsystem abstraction for cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5039:
Component/s: cgroups
> Add Subsystem abstraction for cgroups unified isolator
> --
>
> Key: MESOS-5039
> URL: https://issues.apache.org/jira/browse/MESOS-5039
> Project: Mesos
> Issue Type: Task
> Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> In cgroups unified isolator, we introduce {{Subsystem}} abstraction as the
> base class of other cgroups subsystem implementation classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5045) Add memory subsystem support in cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5045:
Component/s: cgroups
> Add memory subsystem support in cgroups unified isolator
>
>
> Key: MESOS-5045
> URL: https://issues.apache.org/jira/browse/MESOS-5045
> Project: Mesos
> Issue Type: Task
> Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Add cgroups memory subsystem support in cgroups unified isolator. And we need
> to port the test cases of {{CgroupsMemIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5043) Add cpuacct subsystem support in cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5043:
Component/s: cgroups
> Add cpuacct subsystem support in cgroups unified isolator
> -
>
> Key: MESOS-5043
> URL: https://issues.apache.org/jira/browse/MESOS-5043
> Project: Mesos
> Issue Type: Task
> Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Add cgroups cpuacct subsystem support in cgroups unified isolator. And we
> need to port the test cases of {{CgroupsCpushareIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5045) Add memory subsystem support in cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213515#comment-15213515
]
haosdent commented on MESOS-5045:
-
Patch:
| Add `cgroups::memory::pressure::Counter::snapshot` method. |
https://reviews.apache.org/r/45362/ |
| Add `MemorySubsystem` for cgroups unified isolator. |
https://reviews.apache.org/r/45363/ |
| Migrate test cases for `memory` subsystem to cgroups unified isolator. |
https://reviews.apache.org/r/45364/ |
> Add memory subsystem support in cgroups unified isolator
>
>
> Key: MESOS-5045
> URL: https://issues.apache.org/jira/browse/MESOS-5045
> Project: Mesos
> Issue Type: Task
> Components: isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Add cgroups memory subsystem support in cgroups unified isolator. And we need
> to port the test cases of {{CgroupsMemIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5047) Add perf_event subsystem support in cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5047:
Description: Add cgroups perf_event subsystem support in cgroups unified
isolator. And we need to port the test cases of
{{CgroupsPerfEventIsolatorProcess}} as well. (was: Add cgroups memory
subsystem support in cgroups unified isolator. And we need to port the test
cases of {{CgroupsMemIsolatorProcess}} as well.)
> Add perf_event subsystem support in cgroups unified isolator
>
>
> Key: MESOS-5047
> URL: https://issues.apache.org/jira/browse/MESOS-5047
> Project: Mesos
> Issue Type: Task
> Components: isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Add cgroups perf_event subsystem support in cgroups unified isolator. And we
> need to port the test cases of {{CgroupsPerfEventIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5046) Add net_cls subsystem support in cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5046:
Description: Add cgroups net_cls subsystem support in cgroups unified
isolator. And we need to port the test cases of
{{CgroupsNetClsIsolatorProcess}} as well. (was: Add cgroups memory subsystem
support in cgroups unified isolator. And we need to port the test cases of
{{CgroupsMemIsolatorProcess}} as well.)
> Add net_cls subsystem support in cgroups unified isolator
> -
>
> Key: MESOS-5046
> URL: https://issues.apache.org/jira/browse/MESOS-5046
> Project: Mesos
> Issue Type: Task
> Components: isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Add cgroups net_cls subsystem support in cgroups unified isolator. And we
> need to port the test cases of {{CgroupsNetClsIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5047) Add perf_event subsystem support in cgroups unified isolator
haosdent created MESOS-5047:
---
Summary: Add perf_event subsystem support in cgroups unified
isolator
Key: MESOS-5047
URL: https://issues.apache.org/jira/browse/MESOS-5047
Project: Mesos
Issue Type: Task
Components: isolation
Reporter: haosdent
Assignee: haosdent
Add cgroups memory subsystem support in cgroups unified isolator. And we need
to port the test cases of {{CgroupsMemIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5046) Add net_cls subsystem support in cgroups unified isolator
haosdent created MESOS-5046:
---
Summary: Add net_cls subsystem support in cgroups unified isolator
Key: MESOS-5046
URL: https://issues.apache.org/jira/browse/MESOS-5046
Project: Mesos
Issue Type: Task
Components: isolation
Reporter: haosdent
Assignee: haosdent
Add cgroups memory subsystem support in cgroups unified isolator. And we need
to port the test cases of {{CgroupsMemIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5045) Add memory subsystem support in cgroups unified isolator
[
https://issues.apache.org/jira/browse/MESOS-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-5045:
Description: Add cgroups memory subsystem support in cgroups unified
isolator. And we need to port the test cases of {{CgroupsMemIsolatorProcess}}
as well. (was: Add cgroups cpuacct subsystem support in cgroups unified
isolator. And we need to port the test cases of
{{CgroupsCpushareIsolatorProcess}} as well.)
> Add memory subsystem support in cgroups unified isolator
>
>
> Key: MESOS-5045
> URL: https://issues.apache.org/jira/browse/MESOS-5045
> Project: Mesos
> Issue Type: Task
> Components: isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Add cgroups memory subsystem support in cgroups unified isolator. And we need
> to port the test cases of {{CgroupsMemIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5045) Add memory subsystem support in cgroups unified isolator
haosdent created MESOS-5045:
---
Summary: Add memory subsystem support in cgroups unified isolator
Key: MESOS-5045
URL: https://issues.apache.org/jira/browse/MESOS-5045
Project: Mesos
Issue Type: Task
Components: isolation
Reporter: haosdent
Assignee: haosdent
Add cgroups cpuacct subsystem support in cgroups unified isolator. And we need
to port the test cases of {{CgroupsCpushareIsolatorProcess}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4610) MasterContender/MasterDetector should be loadable as modules
[ https://issues.apache.org/jira/browse/MESOS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213483#comment-15213483 ] Shuai Lin commented on MESOS-4610: -- It would be much helpful if you could write a short summary after each link so that people can quickly decide which one they want to look at first. > MasterContender/MasterDetector should be loadable as modules > > > Key: MESOS-4610 > URL: https://issues.apache.org/jira/browse/MESOS-4610 > Project: Mesos > Issue Type: Improvement > Components: master >Reporter: Mark Cavage >Assignee: Mark Cavage > Labels: mesosphere > > Currently mesos depends on Zookeeper for leader election and notification to > slaves, although there is a C++ hierarchy in the code to support alternatives > (e.g., unit tests use an in-memory implementation). From an operational > perspective, many organizations/users do not want to take a dependency on > Zookeeper, and use an alternative solution to implementing leader election. > Our organization in particular, very much wants this, and as a reference > there have been several requests from the community (see referenced tickets) > to replace with etcd/consul/etc. > This ticket will serve as the work effort to modularize the > MasterContender/MasterDetector APIs such that integrators can build a > pluggable solution of their choice; this ticket will not fold in any > implementations such as etcd et al., but simply move this hierarchy to be > fully pluggable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4576) Introduce a stout helper for "which"
[
https://issues.apache.org/jira/browse/MESOS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joris Van Remoortere updated MESOS-4576:
Sprint: Mesosphere Sprint 29, Mesosphere Sprint 30 (was: Mesosphere Sprint
29, Mesosphere Sprint 30, Mesosphere Sprint 31)
> Introduce a stout helper for "which"
>
>
> Key: MESOS-4576
> URL: https://issues.apache.org/jira/browse/MESOS-4576
> Project: Mesos
> Issue Type: Improvement
> Components: stout
>Reporter: Joseph Wu
>Assignee: Disha Singh
> Labels: mesosphere
>
> We may want to add a helper to {{stout/os.hpp}} that will natively emulate
> the functionality of the Linux utility {{which}}. i.e.
> {code}
> Option which(const string& command)
> {
> Option path = os::getenv("PATH");
> // Loop through path and return the first one which os::exists(...).
> return None();
> }
> {code}
> This helper may be useful:
> * for test filters in {{src/tests/environment.cpp}}
> * a few tests in {{src/tests/containerizer/port_mapping_tests.cpp}}
> * the {{sha512}} utility in {{src/common/command_utils.cpp}}
> * as runtime checks in the {{LogrotateContainerLogger}}
> * etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4576) Introduce a stout helper for "which"
[
https://issues.apache.org/jira/browse/MESOS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joris Van Remoortere updated MESOS-4576:
Shepherd: (was: Joris Van Remoortere)
> Introduce a stout helper for "which"
>
>
> Key: MESOS-4576
> URL: https://issues.apache.org/jira/browse/MESOS-4576
> Project: Mesos
> Issue Type: Improvement
> Components: stout
>Reporter: Joseph Wu
>Assignee: Disha Singh
> Labels: mesosphere
>
> We may want to add a helper to {{stout/os.hpp}} that will natively emulate
> the functionality of the Linux utility {{which}}. i.e.
> {code}
> Option which(const string& command)
> {
> Option path = os::getenv("PATH");
> // Loop through path and return the first one which os::exists(...).
> return None();
> }
> {code}
> This helper may be useful:
> * for test filters in {{src/tests/environment.cpp}}
> * a few tests in {{src/tests/containerizer/port_mapping_tests.cpp}}
> * the {{sha512}} utility in {{src/common/command_utils.cpp}}
> * as runtime checks in the {{LogrotateContainerLogger}}
> * etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
