[jira] [Updated] (MESOS-7707) Compile with newer Boost versions
[ https://issues.apache.org/jira/browse/MESOS-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Carlier updated MESOS-7707: - Description: Hello first look at mesos codebase and tried to compile with boost 1.6.4 shipped with the system thus https://reviews.apache.org/r/60356/ Hope it s useful. was: Hello first lok at mesos and tried to compile with boost 1.6.4 shipped with the system thus https://reviews.apache.org/r/60356/ Hope it s useful. > Compile with newer Boost versions > - > > Key: MESOS-7707 > URL: https://issues.apache.org/jira/browse/MESOS-7707 > Project: Mesos > Issue Type: Bug > Components: c++ api >Reporter: David Carlier >Priority: Minor > Fix For: 1.4.0 > > > Hello first look at mesos codebase and tried to compile with boost 1.6.4 > shipped with the system thus > https://reviews.apache.org/r/60356/ > Hope it s useful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MESOS-7707) Compile with newer Boost versions
[
https://issues.apache.org/jira/browse/MESOS-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058777#comment-16058777
]
David Carlier commented on MESOS-7707:
--
Couple of errors of this kind ... once I fixed one type another error came along
{code:cpp}
./../stout/include/stout/json.hpp:261:30: error: no matching function for call
to 'boost::variant::variant(const
std::__cxx11::basic_string&)'
: internal::Variant(value) {}
{code}
> Compile with newer Boost versions
> -
>
> Key: MESOS-7707
> URL: https://issues.apache.org/jira/browse/MESOS-7707
> Project: Mesos
> Issue Type: Bug
> Components: c++ api
>Reporter: David Carlier
>Priority: Minor
> Fix For: 1.4.0
>
>
> Hello first lok at mesos and tried to compile with boost 1.6.4 shipped with
> the system thus
> https://reviews.apache.org/r/60356/
> Hope it s useful.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-7707) Compile with newer Boost versions
[ https://issues.apache.org/jira/browse/MESOS-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058763#comment-16058763 ] Neil Conway commented on MESOS-7707: Hi [~devnexen] -- can you post the error message you get compiling Mesos against boost 1.64 without this change? > Compile with newer Boost versions > - > > Key: MESOS-7707 > URL: https://issues.apache.org/jira/browse/MESOS-7707 > Project: Mesos > Issue Type: Bug > Components: c++ api >Reporter: David Carlier >Priority: Minor > Fix For: 1.4.0 > > > Hello first lok at mesos and tried to compile with boost 1.6.4 shipped with > the system thus > https://reviews.apache.org/r/60356/ > Hope it s useful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MESOS-7707) Compile with newer Boost versions
David Carlier created MESOS-7707: Summary: Compile with newer Boost versions Key: MESOS-7707 URL: https://issues.apache.org/jira/browse/MESOS-7707 Project: Mesos Issue Type: Bug Components: c++ api Reporter: David Carlier Priority: Minor Fix For: 1.4.0 Hello first lok at mesos and tried to compile with boost 1.6.4 shipped with the system thus https://reviews.apache.org/r/60356/ Hope it s useful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MESOS-7706) Improve master failover time for large clusters.
Benjamin Mahler created MESOS-7706: -- Summary: Improve master failover time for large clusters. Key: MESOS-7706 URL: https://issues.apache.org/jira/browse/MESOS-7706 Project: Mesos Issue Type: Epic Reporter: Benjamin Mahler Currently it takes a significant amount of time for the master to settle after a failover. Some users have reported O(minutes) for large clusters or large numbers of frameworks. This ticket will capture the various performance enhancements to improve master failover performance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MESOS-6213) Build failure on macOS Sierra: Protobuf atomics deprecated.
[
https://issues.apache.org/jira/browse/MESOS-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058553#comment-16058553
]
Deshi Xiao commented on MESOS-6213:
---
[~drcrallen] Hi, this bug seems fix, please check again. thanks a lot.
> Build failure on macOS Sierra: Protobuf atomics deprecated.
> ---
>
> Key: MESOS-6213
> URL: https://issues.apache.org/jira/browse/MESOS-6213
> Project: Mesos
> Issue Type: Bug
> Components: build
>Reporter: Charles Allen
>
> Building on OSX is giving the following error.
> {code}
> In file included from
> ../3rdparty/protobuf-2.6.1/src/google/protobuf/stubs/atomicops.h:184:
> ../3rdparty/protobuf-2.6.1/src/google/protobuf/stubs/atomicops_internals_macosx.h:173:9:
> error: 'OSAtomicCompareAndSwap64Barrier' is deprecated: first
> deprecated in macOS 10.12 - Use std::atomic_compare_exchange_strong()
> from instead [-Werror,-Wdeprecated-declarations]
> if (OSAtomicCompareAndSwap64Barrier(
> ^
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/libkern/OSAtomicDeprecated.h:645:9:
> note:
> 'OSAtomicCompareAndSwap64Barrier' has been explicitly marked deprecated
> here
> boolOSAtomicCompareAndSwap64Barrier( int64_t __oldValue, int64_t
> __newValue,
> ^
> {code}
> Protobuf is not listed as a component so I just set it as {{build}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-7671) Let frameworks specify the task bounding capabilities.
[
https://issues.apache.org/jira/browse/MESOS-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058552#comment-16058552
]
James Peach commented on MESOS-7671:
As discussed with [~jieyu], we will add the framework {{bounding_capabilities}}
to the {{LinuxInfo}} message.
> Let frameworks specify the task bounding capabilities.
> --
>
> Key: MESOS-7671
> URL: https://issues.apache.org/jira/browse/MESOS-7671
> Project: Mesos
> Issue Type: Bug
>Reporter: James Peach
>Assignee: James Peach
>
> Following on from MESOS-7476, we should allow frameworks to specify a
> capabilities bounding set in the {{CapabilityInfo}} by adding a {{repeated
> Capability bounding_capabilities}} field.
> I'm a little torn on making more churn, but we probably should consider the
> {{capabilities}} field to {{effective_capabilities}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-6390) Ensure Python support scripts are linted
[
https://issues.apache.org/jira/browse/MESOS-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058548#comment-16058548
]
Joseph Wu commented on MESOS-6390:
--
Here's a patch to enable linting on the support directory:
https://reviews.apache.org/r/60353/
It should go in after we've updated the style of existing scripts.
> Ensure Python support scripts are linted
>
>
> Key: MESOS-6390
> URL: https://issues.apache.org/jira/browse/MESOS-6390
> Project: Mesos
> Issue Type: Improvement
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
> Labels: newbie, python
>
> Currently {{support/mesos-style.py}} does not lint files under {{support/}}.
> This is mostly due to the fact that these scripts are too inconsistent
> style-wise that they wouldn't even pass the linter now.
> We should clean up all Python scripts under {{support/}} so they pass the
> Python linter, and activate that directory in the linter for future
> additions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MESOS-7705) Reconsider restricting the resource format for frameworks.
Michael Park created MESOS-7705:
---
Summary: Reconsider restricting the resource format for frameworks.
Key: MESOS-7705
URL: https://issues.apache.org/jira/browse/MESOS-7705
Project: Mesos
Issue Type: Bug
Components: master
Reporter: Michael Park
Due to some difficulties in reasoning about the resource validation,
specifically around validation and conversion of the {{Resource}} objects
before they can safely be used by functions that require resources to be
validated and converted to "post-reservation-refinement" format, the
restriction that a framework with a RESERVATION_REFINEMENT capability must
speak "post-reservation-refinement" format was removed. We should probably add
this back shortly, but meanwhile it shouldn't be an issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-6390) Ensure Python support scripts are linted
[
https://issues.apache.org/jira/browse/MESOS-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058479#comment-16058479
]
Joseph Wu commented on MESOS-6390:
--
Committed a chunk of the linting changes:
{code}
commit f030c4bd5e8f3cae780052fe62dc260dd7e6eac9
Author: Armand Grillet
Date: Wed Jun 21 14:54:31 2017 -0700
Linted support/mesos-style.py.
This will allow us to use PyLint on the
entire support directory in the future.
Review: https://reviews.apache.org/r/60227/
commit 09fc35978c77ed0f22df1823f5c9220f1ed098ed
Author: Armand Grillet
Date: Wed Jun 21 15:00:52 2017 -0700
Linted support/apply-reviews.py.
This will allow us to use PyLint on the
entire support directory in the future.
Review: https://reviews.apache.org/r/60228/
commit bb8e738b8e10a8061318d081cf75de2e0d0bc47c
Author: Armand Grillet
Date: Wed Jun 21 15:33:50 2017 -0700
Linted support/generate-endpoint-help.py.
This will allow us to use PyLint on the
entire support directory in the future.
Review: https://reviews.apache.org/r/60229/
commit 635b3ed52c51bfad2d5d1e3ad76a7454a7552baf
Author: Armand Grillet
Date: Wed Jun 21 16:18:32 2017 -0700
Linted support/jsonurl.py.
This will allow us to use PyLint on the
entire support directory in the future.
Review: https://reviews.apache.org/r/60230/
commit 62de760059cd07ea0127a6b58588dd777abfa4d8
Author: Armand Grillet
Date: Wed Jun 21 16:32:16 2017 -0700
Linted support/mesos-gtest-runner.py.
This will allow us to use PyLint on the
entire support directory in the future.
Review: https://reviews.apache.org/r/60231/
commit 95ae610acd5cdd52f561776f9bceb727d8239abc
Author: Armand Grillet
Date: Wed Jun 21 16:34:11 2017 -0700
Linted support/mesos-split.py.
This will allow us to use PyLint on the
entire support directory in the future.
Review: https://reviews.apache.org/r/60232/
{code}
> Ensure Python support scripts are linted
>
>
> Key: MESOS-6390
> URL: https://issues.apache.org/jira/browse/MESOS-6390
> Project: Mesos
> Issue Type: Improvement
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
> Labels: newbie, python
>
> Currently {{support/mesos-style.py}} does not lint files under {{support/}}.
> This is mostly due to the fact that these scripts are too inconsistent
> style-wise that they wouldn't even pass the linter now.
> We should clean up all Python scripts under {{support/}} so they pass the
> Python linter, and activate that directory in the linter for future
> additions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-7703) Mesos fails to exec the custom executor when no shell is used
[
https://issues.apache.org/jira/browse/MESOS-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058390#comment-16058390
]
Aaron Wood commented on MESOS-7703:
---
https://reviews.apache.org/r/60280/
> Mesos fails to exec the custom executor when no shell is used
> -
>
> Key: MESOS-7703
> URL: https://issues.apache.org/jira/browse/MESOS-7703
> Project: Mesos
> Issue Type: Bug
> Components: agent, executor
>Affects Versions: 1.2.0, 1.2.1, 1.3.0
>Reporter: Aaron Wood
>Assignee: Aaron Wood
>
> If a framework specifies use of its own executor and sets shell to false the
> executor is never found.
> {code}
> ...
> I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched
> 'http://10.0.2.2:8081/executor' to
> '/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
> Failed to execute command: No such file or directory
> {code}
> Additionally, the name of the binary is never passed as an argument so
> executors making use of argv[0] will fail. The shell takes care of this for
> you which is why it's not seen when using a shell.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MESOS-7704) Remove use of #pragma comment(lib...
Andrew Schwartzmeyer created MESOS-7704:
---
Summary: Remove use of #pragma comment(lib...
Key: MESOS-7704
URL: https://issues.apache.org/jira/browse/MESOS-7704
Project: Mesos
Issue Type: Bug
Environment: Windows
Reporter: Andrew Schwartzmeyer
Assignee: Andrew Schwartzmeyer
Commits 0a1e94d84, 5a7c8d8ef, and f7f661525 introduced the pattern of linking
to a Windows system library with the {{#pragma comment(lib, "IPHLPAPI.lib")}},
instead of adding the library to the correct place in the CMake build system.
While this works, we should be consistent in the way we link to libraries, so
this code should be removed and {{IPHLPAPI.lib}} should be added to stout's
{{LFLAGS}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (MESOS-7690) The agent can crash when an unknown executor tries to register.
[ https://issues.apache.org/jira/browse/MESOS-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Song reassigned MESOS-7690: --- Assignee: Gilbert Song (was: Benjamin Mahler) > The agent can crash when an unknown executor tries to register. > --- > > Key: MESOS-7690 > URL: https://issues.apache.org/jira/browse/MESOS-7690 > Project: Mesos > Issue Type: Bug > Components: agent >Reporter: Benjamin Mahler >Assignee: Gilbert Song > Fix For: 1.2.2, 1.3.1, 1.4.0, 1.1.3 > > > The agent code will crash when an executor with unknown framework id or > executor id tries to register. The agent should reply to the executor with a > shutdown message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MESOS-7690) The agent can crash when an unknown executor tries to register.
[ https://issues.apache.org/jira/browse/MESOS-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Song reassigned MESOS-7690: --- Assignee: Benjamin Mahler (was: Gilbert Song) > The agent can crash when an unknown executor tries to register. > --- > > Key: MESOS-7690 > URL: https://issues.apache.org/jira/browse/MESOS-7690 > Project: Mesos > Issue Type: Bug > Components: agent >Reporter: Benjamin Mahler >Assignee: Benjamin Mahler > Fix For: 1.2.2, 1.3.1, 1.4.0, 1.1.3 > > > The agent code will crash when an executor with unknown framework id or > executor id tries to register. The agent should reply to the executor with a > shutdown message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MESOS-7703) Mesos fails to exec the custom executor when no shell is used
[
https://issues.apache.org/jira/browse/MESOS-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Wood updated MESOS-7703:
--
Description:
If a framework specifies use of its own executor and sets shell to false the
executor is never found.
{code}
...
I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched
'http://10.0.2.2:8081/executor' to
'/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
Failed to execute command: No such file or directory
{code}
Additionally, the name of the binary is never passed as an argument so
executors making use of argv[0] will fail. The shell takes care of this for you
which is why it's not seen when using a shell.
was:
If a framework specifies use of its own executor and sets shell to false in the
ExecutorInfo the executor is never found.
{code}
...
I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched
'http://10.0.2.2:8081/executor' to
'/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
Failed to execute command: No such file or directory
{code}
Additionally, the name of the binary is never passed as an argument so
executors making use of argv[0] will fail. The shell takes care of this for you
which is why it's not seen when using a shell.
> Mesos fails to exec the custom executor when no shell is used
> -
>
> Key: MESOS-7703
> URL: https://issues.apache.org/jira/browse/MESOS-7703
> Project: Mesos
> Issue Type: Bug
> Components: agent, executor
>Affects Versions: 1.2.0, 1.2.1, 1.3.0
>Reporter: Aaron Wood
>Assignee: Aaron Wood
>
> If a framework specifies use of its own executor and sets shell to false the
> executor is never found.
> {code}
> ...
> I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched
> 'http://10.0.2.2:8081/executor' to
> '/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
> Failed to execute command: No such file or directory
> {code}
> Additionally, the name of the binary is never passed as an argument so
> executors making use of argv[0] will fail. The shell takes care of this for
> you which is why it's not seen when using a shell.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MESOS-7703) Mesos fails to exec the custom executor when no shell is used
[
https://issues.apache.org/jira/browse/MESOS-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Wood updated MESOS-7703:
--
Summary: Mesos fails to exec the custom executor when no shell is used
(was: Mesos fails to execvp a custom executor when no shell is used)
> Mesos fails to exec the custom executor when no shell is used
> -
>
> Key: MESOS-7703
> URL: https://issues.apache.org/jira/browse/MESOS-7703
> Project: Mesos
> Issue Type: Bug
> Components: agent, executor
>Affects Versions: 1.2.0, 1.2.1, 1.3.0
>Reporter: Aaron Wood
>Assignee: Aaron Wood
>
> If a framework specifies use of its own executor and sets shell to false in
> the ExecutorInfo the executor is never found.
> {code}
> ...
> I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched
> 'http://10.0.2.2:8081/executor' to
> '/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
> Failed to execute command: No such file or directory
> {code}
> Additionally, the name of the binary is never passed as an argument so
> executors making use of argv[0] will fail. The shell takes care of this for
> you which is why it's not seen when using a shell.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MESOS-7703) Mesos fails to execvp a custom executor when no shell is used
Aaron Wood created MESOS-7703:
-
Summary: Mesos fails to execvp a custom executor when no shell is
used
Key: MESOS-7703
URL: https://issues.apache.org/jira/browse/MESOS-7703
Project: Mesos
Issue Type: Bug
Components: agent, executor
Affects Versions: 1.3.0, 1.2.1, 1.2.0
Reporter: Aaron Wood
Assignee: Aaron Wood
If a framework specifies use of its own executor and sets shell to false in the
ExecutorInfo the executor is never found.
{code}
...
I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched
'http://10.0.2.2:8081/executor' to
'/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
Failed to execute command: No such file or directory
{code}
Additionally, the name of the binary is never passed as an argument so
executors making use of argv[0] will fail. The shell takes care of this for you
which is why it's not seen when using a shell.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-7302) Support launching standalone containers.
[
https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057970#comment-16057970
]
Joseph Wu commented on MESOS-7302:
--
API hasn't been proposed yet. But it will look very similar to the
{{LAUNCH_NESTED_CONTAINER}} call; minus a {{ContainerID}} and plus a
{{Resources}} field.
> Support launching standalone containers.
>
>
> Key: MESOS-7302
> URL: https://issues.apache.org/jira/browse/MESOS-7302
> Project: Mesos
> Issue Type: Epic
> Components: containerization
>Reporter: Jie Yu
>Assignee: Joseph Wu
> Labels: mesosphere
>
> Containerizer should support launching containers (both top level and nested)
> that are not tied to a particular Mesos task or executor. This is for the
> case where the agent wants to launch some system containers (e.g., for CSI
> plugin) that will be managed by Mesos.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MESOS-7302) Support launching standalone containers.
[
https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057962#comment-16057962
]
Yan Xu edited comment on MESOS-7302 at 6/21/17 6:19 PM:
Thanks. So there's going to be an agent API with a {{Resources}} field in the
call? Is the proposed API documented somewhere?
was (Author: xujyan):
Thanks. So there's going to be an agent API with a {{Resources}} field in the
call? Is the API documented somewhere?
> Support launching standalone containers.
>
>
> Key: MESOS-7302
> URL: https://issues.apache.org/jira/browse/MESOS-7302
> Project: Mesos
> Issue Type: Epic
> Components: containerization
>Reporter: Jie Yu
>Assignee: Joseph Wu
> Labels: mesosphere
>
> Containerizer should support launching containers (both top level and nested)
> that are not tied to a particular Mesos task or executor. This is for the
> case where the agent wants to launch some system containers (e.g., for CSI
> plugin) that will be managed by Mesos.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-7302) Support launching standalone containers.
[
https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057962#comment-16057962
]
Yan Xu commented on MESOS-7302:
---
Thanks. So there's going to be an agent API with a {{Resources}} field in the
call? Is the API documented somewhere?
> Support launching standalone containers.
>
>
> Key: MESOS-7302
> URL: https://issues.apache.org/jira/browse/MESOS-7302
> Project: Mesos
> Issue Type: Epic
> Components: containerization
>Reporter: Jie Yu
>Assignee: Joseph Wu
> Labels: mesosphere
>
> Containerizer should support launching containers (both top level and nested)
> that are not tied to a particular Mesos task or executor. This is for the
> case where the agent wants to launch some system containers (e.g., for CSI
> plugin) that will be managed by Mesos.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-7302) Support launching standalone containers.
[ https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057946#comment-16057946 ] Joseph Wu commented on MESOS-7302: -- For the MVP, containers launched via the (to be implemented) standalone container API will be isolated like any other container. But the Master will not know about them. So if you abuse the Operator API, it would be possible to oversubscribe the Agent. I'd need to add some additional plumbing from the Agent to the Master's allocator in order to properly account for these resources (albeit racily, as standalone containers are launched outside of the offer cycle). > Support launching standalone containers. > > > Key: MESOS-7302 > URL: https://issues.apache.org/jira/browse/MESOS-7302 > Project: Mesos > Issue Type: Epic > Components: containerization >Reporter: Jie Yu >Assignee: Joseph Wu > Labels: mesosphere > > Containerizer should support launching containers (both top level and nested) > that are not tied to a particular Mesos task or executor. This is for the > case where the agent wants to launch some system containers (e.g., for CSI > plugin) that will be managed by Mesos. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MESOS-7302) Support launching standalone containers.
[ https://issues.apache.org/jira/browse/MESOS-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057886#comment-16057886 ] Yan Xu commented on MESOS-7302: --- [~jieyu] [~kaysoky] Could you clarify on how resources consumed by these standalone containers are managed? > Support launching standalone containers. > > > Key: MESOS-7302 > URL: https://issues.apache.org/jira/browse/MESOS-7302 > Project: Mesos > Issue Type: Epic > Components: containerization >Reporter: Jie Yu >Assignee: Joseph Wu > Labels: mesosphere > > Containerizer should support launching containers (both top level and nested) > that are not tied to a particular Mesos task or executor. This is for the > case where the agent wants to launch some system containers (e.g., for CSI > plugin) that will be managed by Mesos. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MESOS-7520) Mesos fails to compile with GCC 7.1
[
https://issues.apache.org/jira/browse/MESOS-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057647#comment-16057647
]
Aaron Wood commented on MESOS-7520:
---
We still need fixes to the Duration class.
> Mesos fails to compile with GCC 7.1
> ---
>
> Key: MESOS-7520
> URL: https://issues.apache.org/jira/browse/MESOS-7520
> Project: Mesos
> Issue Type: Bug
> Components: agent, build, master
>Affects Versions: 1.2.0
>Reporter: Aaron Wood
>Assignee: Aaron Wood
>Priority: Trivial
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80829
> {code}
> error 12-May-2017 15:46:40In file included from
> ../../src/authorizer/authorizer.cpp:29:0:
> error 12-May-2017 15:46:40../../src/master/constants.hpp:45:39: error:
> 'Megabytes(32).Megabytes::' is not a constant expression because
> it refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Bytes MIN_MEM = Megabytes(32);
> error 12-May-2017 15:46:40 ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:49:59: error:
> 'Seconds(15).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration DEFAULT_HEARTBEAT_INTERVAL
> = Seconds(15);
> error 12-May-2017 15:46:40
>^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:57:59: error:
> 'Seconds(15).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration DEFAULT_AGENT_PING_TIMEOUT
> = Seconds(15);
> error 12-May-2017 15:46:40
>^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:67:61: error:
> 'Minutes(10).Minutes::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration
> MIN_AGENT_REREGISTER_TIMEOUT = Minutes(10);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:95:56: error:
> 'Seconds(5).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration WHITELIST_WATCH_INTERVAL =
> Seconds(5);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:100:61: error:
> 'Minutes(15).Minutes::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration
> DEFAULT_REGISTRY_GC_INTERVAL = Minutes(15);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:102:60: error:
> 'Weeks(2).Weeks::' is not a constant expression because it refers
> to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration
> DEFAULT_REGISTRY_MAX_AGENT_AGE = Weeks(2);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:122:58: error:
> 'Seconds(10).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration ZOOKEEPER_SESSION_TIMEOUT =
> Seconds(10);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:131:59: error:
> 'Seconds(1).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration DEFAULT_ALLOCATION_INTERVAL
> = Seconds(1);
> error 12-May-2017 15:46:40
>^
> error 12-May-2017 15:46:40In file included from
> ../../src/authentication/http/basic_authenticator_factory.cpp:27:0:
> error 12-May-2017 15:46:40../../src/master/constants.hpp:45:39: error:
> 'Megabytes(32).Megabytes::' is not a constant expression because
> it refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Bytes MIN_MEM = Megabytes(32);
> error 12-May-2017 15:46:40 ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:49:59: error:
> 'Seconds(15).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr
[jira] [Created] (MESOS-7702) Fix the validation / conversion strategy of `Resources`.
Michael Park created MESOS-7702:
---
Summary: Fix the validation / conversion strategy of `Resources`.
Key: MESOS-7702
URL: https://issues.apache.org/jira/browse/MESOS-7702
Project: Mesos
Issue Type: Bug
Reporter: Michael Park
With reservation refinement, we introduced the "post-reservation-refinement"
format which uses a new {{Resource.reservations}} field to represent the
reservation state of a resource. The "pre-reservation-refinement" format used
the {{Resource.role}} and {{Resource.reservation}}.
In order to avoid writing two code paths for everything in every component, the
general strategy is to convert the resource format at the component boundaries.
That is, convert to the "post-reservation-refinement" format in-bound, and
convert back as necessary out-bound.
While I think this strategy is still good, the mechanism of how this happens
really needs to change.
It's very hard to tell and keep track of the state of {{Resource}} objects and
at what point they've been validated and have been converted.
For example, can we afford to call {{convertResourceFormat}} *after*
{{validation::operation::validate}}? Since {{operation::validate}} calls
{{Resources::validate}} within it, it may seem innocent to convert after the
operation has been validated. The issue though is that after
{{Resources::validate}} has been called within {{operation::validate}}, it
starts to use functions that require resources to be validated, and in the
"post-reservation-refinement" format. What this means is that validation and
conversion has a much tighter relationship than is enforced currently.
Besides the complexity that I added during reservation refinement, I also
believe that we already have some tech-debt in this area. For example, the
{{Resources}} constructor simply __drops__ invalid resources. This is really
subtle, and would be a nightmare to track down. I think a better approach would
be to have a creation function that can fail correctly. Since we live in a
world with no exceptions, this can be solved by having a creation function that
returns a {{Try}}. That is, {{Try createResources(...);}} would do
the validation and return an {{Error}} on failure. Note that we can also bundle
the __conversion__ logic here as well.
* https://reviews.apache.org/r/60253/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MESOS-7520) Mesos fails to compile with GCC 7.1
[
https://issues.apache.org/jira/browse/MESOS-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057267#comment-16057267
]
James Peach commented on MESOS-7520:
[~neilc] This was submitted?
> Mesos fails to compile with GCC 7.1
> ---
>
> Key: MESOS-7520
> URL: https://issues.apache.org/jira/browse/MESOS-7520
> Project: Mesos
> Issue Type: Bug
> Components: agent, build, master
>Affects Versions: 1.2.0
>Reporter: Aaron Wood
>Assignee: Aaron Wood
>Priority: Trivial
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80829
> {code}
> error 12-May-2017 15:46:40In file included from
> ../../src/authorizer/authorizer.cpp:29:0:
> error 12-May-2017 15:46:40../../src/master/constants.hpp:45:39: error:
> 'Megabytes(32).Megabytes::' is not a constant expression because
> it refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Bytes MIN_MEM = Megabytes(32);
> error 12-May-2017 15:46:40 ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:49:59: error:
> 'Seconds(15).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration DEFAULT_HEARTBEAT_INTERVAL
> = Seconds(15);
> error 12-May-2017 15:46:40
>^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:57:59: error:
> 'Seconds(15).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration DEFAULT_AGENT_PING_TIMEOUT
> = Seconds(15);
> error 12-May-2017 15:46:40
>^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:67:61: error:
> 'Minutes(10).Minutes::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration
> MIN_AGENT_REREGISTER_TIMEOUT = Minutes(10);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:95:56: error:
> 'Seconds(5).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration WHITELIST_WATCH_INTERVAL =
> Seconds(5);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:100:61: error:
> 'Minutes(15).Minutes::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration
> DEFAULT_REGISTRY_GC_INTERVAL = Minutes(15);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:102:60: error:
> 'Weeks(2).Weeks::' is not a constant expression because it refers
> to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration
> DEFAULT_REGISTRY_MAX_AGENT_AGE = Weeks(2);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:122:58: error:
> 'Seconds(10).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration ZOOKEEPER_SESSION_TIMEOUT =
> Seconds(10);
> error 12-May-2017 15:46:40
> ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:131:59: error:
> 'Seconds(1).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration DEFAULT_ALLOCATION_INTERVAL
> = Seconds(1);
> error 12-May-2017 15:46:40
>^
> error 12-May-2017 15:46:40In file included from
> ../../src/authentication/http/basic_authenticator_factory.cpp:27:0:
> error 12-May-2017 15:46:40../../src/master/constants.hpp:45:39: error:
> 'Megabytes(32).Megabytes::' is not a constant expression because
> it refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Bytes MIN_MEM = Megabytes(32);
> error 12-May-2017 15:46:40 ^
> error 12-May-2017 15:46:40../../src/master/constants.hpp:49:59: error:
> 'Seconds(15).Seconds::' is not a constant expression because it
> refers to an incompletely initialized variable
> error 12-May-2017 15:46:40 constexpr Duration
[jira] [Comment Edited] (MESOS-7692) Default environment variables defined in docker image are not available in mesos containerizer
[
https://issues.apache.org/jira/browse/MESOS-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057090#comment-16057090
]
Mao Geng edited comment on MESOS-7692 at 6/21/17 7:34 AM:
--
Here is one of the ACCEPT messages sent from framework (capture via tcpdump and
formatted):
{code}
{
"accept": {
"offer_ids": {
"value": "55541916-22e8-41c5-a7fa-acf9a0f5836a-O100854"
},
"operations": [
{
"launch": {
"task_infos": [
{
"agent_id": {
"value":
"f2bcc63d-e887-4e25-b2c0-3772dfb40fb0-S11"
},
"command": {
"environment": {
"variables": [
{
"name": "PYTHONPATH",
"value":
"/usr/local/bin:/:/usr/lib/python2.7:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload:/usr/local/lib/python2.7/dist-packages:/usr/lib/python2.7/dist-packages"
}
]
},
"shell": true,
"value": "/usr/bin/python -m tfmesos.server 1
:"
},
"container": {
"docker": {
"image": "",
"parameters": [
{
"key": "memory-swap",
"value": "-1"
}
]
},
"type": "DOCKER",
"volumes": [
{
"container_path": "/etc/passwd",
"host_path": "/etc/passwd",
"mode": "RO"
},
{
"container_path": "/etc/group",
"host_path": "/etc/group",
"mode": "RO"
}
]
},
"name": "/job:worker/task:0",
"resources": [
{
"name": "cpus",
"scalar": {
"value": 5.0
},
"type": "SCALAR"
},
{
"name": "mem",
"scalar": {
"value": 8192.0
},
"type": "SCALAR"
}
],
"task_id": {
"value": "1"
}
}
]
},
"type": "LAUNCH"
}
]
},
"framework_id": {
"value": "55541916-22e8-41c5-a7fa-acf9a0f5836a-0017"
},
"type": "ACCEPT"
}
{code}
was (Author: gengmao):
Here is one of the ACCEPT messages sent from framework (capture via tcpdump and
formatted):
{code}
{
"accept": {
"offer_ids": {
"value": "55541916-22e8-41c5-a7fa-acf9a0f5836a-O100854"
},
"operations": [
{
"launch": {
"task_infos": [
{
"agent_id": {
"value":
"f2bcc63d-e887-4e25-b2c0-3772dfb40fb0-S11"
},
"command": {
"environment": {
"variables": [
{
"name": "PYTHONPATH",
"value":
"/usr/local/bin:/:/usr/lib/python2.7:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload:/usr/local/lib/python2.7/dist-packages:/usr/lib/python2.7/dist-packages"
[jira] [Commented] (MESOS-7692) Default environment variables defined in docker image are not available in mesos containerizer
[
https://issues.apache.org/jira/browse/MESOS-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057090#comment-16057090
]
Mao Geng commented on MESOS-7692:
-
Here is one of the ACCEPT messages sent from framework (capture via tcpdump and
formatted):
{code}
{
"accept": {
"offer_ids": {
"value": "55541916-22e8-41c5-a7fa-acf9a0f5836a-O100854"
},
"operations": [
{
"launch": {
"task_infos": [
{
"agent_id": {
"value":
"f2bcc63d-e887-4e25-b2c0-3772dfb40fb0-S11"
},
"command": {
"environment": {
"variables": [
{
"name": "PYTHONPATH",
"value":
"/usr/local/bin:/:/usr/lib/python2.7:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload:/usr/local/lib/python2.7/dist-packages:/usr/lib/python2.7/dist-packages"
}
]
},
"shell": true,
"value": "/usr/bin/python -m tfmesos.server 1
:"
},
"container": {
"docker": {
"image": "",
"parameters": [
{
"key": "memory-swap",
"value": "-1"
}
]
},
"type": "DOCKER",
"volumes": [
{
"container_path": "/etc/passwd",
"host_path": "/etc/passwd",
"mode": "RO"
},
{
"container_path": "/etc/group",
"host_path": "/etc/group",
"mode": "RO"
}
]
},
"name": "/job:worker/task:0",
"resources": [
{
"name": "cpus",
"scalar": {
"value": 5.0
},
"type": "SCALAR"
},
{
"name": "mem",
"scalar": {
"value": 8192.0
},
"type": "SCALAR"
}
],
"task_id": {
"value": "1"
}
}
]
},
"framework_id": {
"value": "55541916-22e8-41c5-a7fa-acf9a0f5836a-0017"
},
"type": "ACCEPT"
}
{code}
> Default environment variables defined in docker image are not available in
> mesos containerizer
> --
>
> Key: MESOS-7692
> URL: https://issues.apache.org/jira/browse/MESOS-7692
> Project: Mesos
> Issue Type: Bug
> Components: containerization
>Affects Versions: 1.3.0
>Reporter: Mao Geng
>Assignee: Till Toenshoff
>Priority: Blocker
> Fix For: 1.3.1
>
>
> Found an unexpected change in 1.3.0-2.0.3 - the environment variables defined
> by ENV statements in dockerfile are not available in mesos containerizer any
> more. For example LD_LIBRARY_PATH of tensorflow/tensorflow:latest-gpu image,
> JAVA_HOME of java:8 image, etc.
> The env vars are available in mesos containerizer in 1.2.0. Looks like a
> regression to me, isn't it?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MESOS-7701) Support encoded credentials file
Timothy Chen created MESOS-7701: --- Summary: Support encoded credentials file Key: MESOS-7701 URL: https://issues.apache.org/jira/browse/MESOS-7701 Project: Mesos Issue Type: Improvement Reporter: Timothy Chen Mesos credentials file currently only supports passwords in plain text / JSON files. To support some enterprises that has no clear text passwords policy, the credentials file loading should support reading in an encoded (e.g: Base64) format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
