[jira] [Updated] (MESOS-1704) Mac OS X build breaks in DockerContainerizerProcess::fetch
[
https://issues.apache.org/jira/browse/MESOS-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Hindman updated MESOS-1704:
Description:
{code}
...
../../3rdparty/libprocess/include/process/future.hpp:180:61: note: in
instantiation of function template specialization
'process::_Deferred
(std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &> >::operator function &>' requested here
return onFailed(std::function(deferred));
^
../../src/slave/containerizer/docker.cpp:325:6: note: in instantiation of
function template specialization 'process::Future
>::onFailed
(std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &> >' requested here
.onFailed(defer(self(), &Self::_fetchFailed, containerId, lambda::_1))
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1448:5:
note: candidate constructor not viable: no known conversion from 'const
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>' to 'nullptr_t' for 1st argument
function(nullptr_t) _NOEXCEPT : __f_(0) {}
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1449:5:
note: candidate constructor not viable: no known conversion from 'const
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>' to 'const std::__1::function &)>' for 1st argument
function(const function&);
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1450:5:
note: candidate constructor not viable: no known conversion from 'const
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>' to 'std::__1::function &)>' for 1st argument
function(function&&) _NOEXCEPT;
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1454:41:
note: candidate template ignored: disabled by 'enable_if' [with _Fp =
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>]
{code}
was:
{code}
...
../../3rdparty/libprocess/include/process/future.hpp:180:61: note: in
instantiation of function template specialization
'process::_Deferred
(std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &> >::operator function &>' requested here
return onFailed(std::function(deferred));
^
../../src/slave/containerizer/docker.cpp:325:6: note: in instantiation of
function template specialization 'process::Future
>::onFailed
(std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &> >' requested here
.onFailed(defer(self(), &Self::_fetchFailed, containerId, lambda::_1))
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
[jira] [Created] (MESOS-1704) Mac OS X build breaks in DockerContainerizerProcess::fetch
Niklas Quarfot Nielsen created MESOS-1704:
-
Summary: Mac OS X build breaks in DockerContainerizerProcess::fetch
Key: MESOS-1704
URL: https://issues.apache.org/jira/browse/MESOS-1704
Project: Mesos
Issue Type: Bug
Components: containerization
Environment: Mac OS X / clang
Reporter: Niklas Quarfot Nielsen
{code}
...
../../3rdparty/libprocess/include/process/future.hpp:180:61: note: in
instantiation of function template specialization
'process::_Deferred
(std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &> >::operator function &>' requested here
return onFailed(std::function(deferred));
^
../../src/slave/containerizer/docker.cpp:325:6: note: in instantiation of
function template specialization 'process::Future
>::onFailed
(std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &,
const std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &> >' requested here
.onFailed(defer(self(), &Self::_fetchFailed, containerId, lambda::_1))
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1448:5:
note: candidate constructor not viable: no known conversion from 'const
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>' to 'nullptr_t' for 1st argument
function(nullptr_t) _NOEXCEPT : __f_(0) {}
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1449:5:
note: candidate constructor not viable: no known conversion from 'const
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>' to 'const std::__1::function &)>' for 1st argument
function(const function&);
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1450:5:
note: candidate constructor not viable: no known conversion from 'const
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>' to 'std::__1::function &)>' for 1st argument
function(function&&) _NOEXCEPT;
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/functional:1454:41:
note: candidate template ignored: disabled by 'enable_if' [with _Fp =
std::__1::__bind
(std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>::*)(const mesos::ContainerID &, const
std::__1::basic_string &) const,
std::__1::function (const mesos::ContainerID &, const
std::__1::basic_string &)>, mesos::ContainerID &,
std::__1::placeholders::__ph<1> &>]
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (MESOS-1703) better error message when replicated log hasn't been initialized
Jay Buffington created MESOS-1703:
-
Summary: better error message when replicated log hasn't been
initialized
Key: MESOS-1703
URL: https://issues.apache.org/jira/browse/MESOS-1703
Project: Mesos
Issue Type: Bug
Reporter: Jay Buffington
Priority: Minor
Aurora uses the mesos replicated log.
If you don't run "mesos-log initialize" before starting aurora you'll get INFO
messages in your aurora log:
{code}
I0814 15:18:38.346638 25141 replica.cpp:633] Replica in EMPTY status received a
broadcasted recover request
I0814 15:18:38.346796 25132 recover.cpp:220] Received a recover response from a
replica in EMPTY status
{code}
It is has been deemed too dangerous to automatically run mesos-log initialize
for the user (see AURORA-243).
It would be helpful if that error message was made more friendly and at the
ERROR level. The message could explain what the user should do and the
implications of doing so. Links to the docs would be helpful.
See http://wilderness.apache.org/channels/?f=aurora/2014-08-14#1408055261 for
context
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (MESOS-1702) Add document for network monitoring.
Jie Yu created MESOS-1702: - Summary: Add document for network monitoring. Key: MESOS-1702 URL: https://issues.apache.org/jira/browse/MESOS-1702 Project: Mesos Issue Type: Task Reporter: Jie Yu Assignee: Jie Yu The doc should tell the user how to use the new network monitoring feature. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1702) Add document for network monitoring.
[ https://issues.apache.org/jira/browse/MESOS-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097888#comment-14097888 ] Jie Yu commented on MESOS-1702: --- https://reviews.apache.org/r/24719 > Add document for network monitoring. > > > Key: MESOS-1702 > URL: https://issues.apache.org/jira/browse/MESOS-1702 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Jie Yu > > The doc should tell the user how to use the new network monitoring feature. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1580) Accept --isolation=external through a deprecation cycle.
[ https://issues.apache.org/jira/browse/MESOS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-1580: -- Target Version/s: 0.20.0 > Accept --isolation=external through a deprecation cycle. > > > Key: MESOS-1580 > URL: https://issues.apache.org/jira/browse/MESOS-1580 > Project: Mesos > Issue Type: Task > Components: containerization, slave >Reporter: Benjamin Hindman >Assignee: Timothy Chen > > The feature branch at github.com/mesos/mesos/tree/docker removes the > --isolation=external option and forces people instead to do > --containerizers=external to get the same thing. We should actually put > --isolation=external through a deprecation cycle. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1454) Command executor should have nonzero resources
[ https://issues.apache.org/jira/browse/MESOS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-1454: --- Fix Version/s: 0.20.0 > Command executor should have nonzero resources > -- > > Key: MESOS-1454 > URL: https://issues.apache.org/jira/browse/MESOS-1454 > Project: Mesos > Issue Type: Bug >Reporter: Ian Downes >Assignee: Ian Downes > Fix For: 0.20.0 > > > The command executor is used when TaskInfo does not provide an ExecutorInfo. > It is not given any dedicated resources but the executor will be launched > with the first task's resources. However, assuming a single task (or a final > task), when that task terminates the container will be updated to zero > resources - see containerizer->update in Slave::statusUpdate(). > Possible solutions: > - Require a task to specify an executor and resources for it. > - Add sufficient allowance for the command executor beyond the task's > resources. This leads to an overcommit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-1454) Command executor should have nonzero resources
[ https://issues.apache.org/jira/browse/MESOS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Downes resolved MESOS-1454. --- Resolution: Fixed https://reviews.apache.org/r/22251 commit 75798d437f5f1f7d08b61388c9f1018a54553908 Author: Ian Downes Date: Wed Jun 4 16:19:54 2014 -0700 > Command executor should have nonzero resources > -- > > Key: MESOS-1454 > URL: https://issues.apache.org/jira/browse/MESOS-1454 > Project: Mesos > Issue Type: Bug >Reporter: Ian Downes >Assignee: Ian Downes > > The command executor is used when TaskInfo does not provide an ExecutorInfo. > It is not given any dedicated resources but the executor will be launched > with the first task's resources. However, assuming a single task (or a final > task), when that task terminates the container will be updated to zero > resources - see containerizer->update in Slave::statusUpdate(). > Possible solutions: > - Require a task to specify an executor and resources for it. > - Add sufficient allowance for the command executor beyond the task's > resources. This leads to an overcommit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (MESOS-1454) Command executor should have nonzero resources
[ https://issues.apache.org/jira/browse/MESOS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Downes reassigned MESOS-1454: - Assignee: Ian Downes > Command executor should have nonzero resources > -- > > Key: MESOS-1454 > URL: https://issues.apache.org/jira/browse/MESOS-1454 > Project: Mesos > Issue Type: Bug >Reporter: Ian Downes >Assignee: Ian Downes > > The command executor is used when TaskInfo does not provide an ExecutorInfo. > It is not given any dedicated resources but the executor will be launched > with the first task's resources. However, assuming a single task (or a final > task), when that task terminates the container will be updated to zero > resources - see containerizer->update in Slave::statusUpdate(). > Possible solutions: > - Require a task to specify an executor and resources for it. > - Add sufficient allowance for the command executor beyond the task's > resources. This leads to an overcommit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-1652) Stream Docker logs into sandbox logs
[ https://issues.apache.org/jira/browse/MESOS-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Hindman resolved MESOS-1652. - Resolution: Fixed Fix Version/s: 0.20.0 commit e43b0c70037940fa1c42f044d5b6ddde943b3736 Author: Timothy Chen Date: Wed Aug 13 10:30:03 2014 -0700 Redirect Docker logs. > Stream Docker logs into sandbox logs > > > Key: MESOS-1652 > URL: https://issues.apache.org/jira/browse/MESOS-1652 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen >Assignee: Timothy Chen > Fix For: 0.20.0 > > > We should write logs either during or after the task launched the logs from > the docker container into the sandbox so it can be viewed without actually > going to the host and calling "docker logs". -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1652) Stream Docker logs into sandbox logs
[ https://issues.apache.org/jira/browse/MESOS-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097866#comment-14097866 ] Benjamin Hindman commented on MESOS-1652: - Actually, this ended up being: https://reviews.apache.org/r/24709 > Stream Docker logs into sandbox logs > > > Key: MESOS-1652 > URL: https://issues.apache.org/jira/browse/MESOS-1652 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen >Assignee: Timothy Chen > > We should write logs either during or after the task launched the logs from > the docker container into the sandbox so it can be viewed without actually > going to the host and calling "docker logs". -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1580) Accept --isolation=external through a deprecation cycle.
[ https://issues.apache.org/jira/browse/MESOS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Hindman updated MESOS-1580: Shepherd: Benjamin Hindman Assignee: Timothy Chen > Accept --isolation=external through a deprecation cycle. > > > Key: MESOS-1580 > URL: https://issues.apache.org/jira/browse/MESOS-1580 > Project: Mesos > Issue Type: Task > Components: containerization, slave >Reporter: Benjamin Hindman >Assignee: Timothy Chen > > The feature branch at github.com/mesos/mesos/tree/docker removes the > --isolation=external option and forces people instead to do > --containerizers=external to get the same thing. We should actually put > --isolation=external through a deprecation cycle. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-1006) Invalid free when in ProcessIsolator Usage when executing a short task
[ https://issues.apache.org/jira/browse/MESOS-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler resolved MESOS-1006. Resolution: Fixed Fix Version/s: 0.18.0 Assignee: Benjamin Hindman This was fixed as part of MESOS-963. > Invalid free when in ProcessIsolator Usage when executing a short task > -- > > Key: MESOS-1006 > URL: https://issues.apache.org/jira/browse/MESOS-1006 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.17.0 > Environment: MacOS 10.9.1 >Reporter: Florian Douetteau >Assignee: Benjamin Hindman > Fix For: 0.18.0 > > > Executing: > mesos execute --command=/bin/ls --master=127.0.0.1:5050 --name=test > Slave Log: > I0214 11:46:34.732306 294408192 status_update_manager.cpp:367] Forwarding > status update TASK_RUNNING (UUID: 956f2268-f677-4ff0-86d2-95e338b11447) for > task test of framework 201402141053-16777343-5050-50707-0010 to > master@127.0.0.1:5050 > I0214 11:46:34.732408 296017920 slave.cpp:1882] Sending acknowledgement for > status update TASK_RUNNING (UUID: 956f2268-f677-4ff0-86d2-95e338b11447) for > task test of framework 201402141053-16777343-5050-50707-0010 to > executor(1)@127.0.0.1:57686 > I0214 11:46:34.772078 294408192 status_update_manager.cpp:392] Received > status update acknowledgement (UUID: 956f2268-f677-4ff0-86d2-95e338b11447) > for task test of framework 201402141053-16777343-5050-50707-0010 > mesos-slave(52021,0x1119cb000) malloc: *** error for object 0x79702e72657672: > pointer being freed was not allocated > *** set a breakpoint in malloc_error_break to debug > *** Aborted at 1392407195 (unix time) try "date -d @1392407195" if you are > using GNU date *** > PC: @ 0x7fff8f602866 __pthread_kill > *** SIGABRT (@0x7fff8f602866) received by PID 52021 (TID 0x1119cb000) stack > trace: *** > @ 0x7fff907a35aa _sigtramp > @0x0 (unknown) > @ 0x7fff8d43ebba abort > @ 0x7fff8d3ba093 free > @0x1101a11c2 std::__1::vector<>::erase() > @0x110197dcb os::process() > @0x11019eaad os::processes() > @0x110198957 os::children() > @0x1101939f3 mesos::internal::slave::ProcessIsolator::usage() > @0x1101115d3 > _ZZN7process8dispatchIN5mesos18ResourceStatisticsENS1_8internal5slave8IsolatorERKNS1_11FrameworkIDERKNS1_10ExecutorIDES6_S9_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSG_FSE_T1_T2_ET3_T4_ENKS0_IS2_S5_S8_SB_S6_S9_EUlPNS_11ProcessBaseEE_clESS_ > @0x11036cd13 process::ProcessBase::visit() > @0x1103640d2 process::ProcessManager::resume() > @0x110363c2f process::schedule() > @ 0x7fff8b269899 _pthread_body > @ 0x7fff8b26972a _pthread_start > @ 0x7fff8b26dfc9 thread_start > Abort trap: 6 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1580) Accept --isolation=external through a deprecation cycle.
[ https://issues.apache.org/jira/browse/MESOS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097853#comment-14097853 ] Jay Buffington commented on MESOS-1580: --- Commit 29910a6e removed --isolation=external, which breaks backwards compat. If this is not fixed before 0.20 is released users running 0.19 with an external containerize (e.g. deimos) will have to change their start args to the mesos-slave process.. > Accept --isolation=external through a deprecation cycle. > > > Key: MESOS-1580 > URL: https://issues.apache.org/jira/browse/MESOS-1580 > Project: Mesos > Issue Type: Task > Components: containerization, slave >Reporter: Benjamin Hindman > > The feature branch at github.com/mesos/mesos/tree/docker removes the > --isolation=external option and forces people instead to do > --containerizers=external to get the same thing. We should actually put > --isolation=external through a deprecation cycle. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-780) Adding support for 3rd party performance and health monitoring.
[ https://issues.apache.org/jira/browse/MESOS-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097763#comment-14097763 ] Steven Schlansker commented on MESOS-780: - I've started a (very basic) Nagios check: https://github.com/opentable/nagios-mesos Hopefully someone finds it useful / contributes improvements :) > Adding support for 3rd party performance and health monitoring. > --- > > Key: MESOS-780 > URL: https://issues.apache.org/jira/browse/MESOS-780 > Project: Mesos > Issue Type: Improvement > Components: framework >Reporter: Bernardo Gomez Palacio > > User Story: > As a SysAdmin I should be able to monitor Mesos (Masters and Slaves) with > 3rd party tools such as: > * [Ganglia|http://ganglia.sourceforge.net/] > * [Graphite|http://graphite.wikidot.com/] > * [Nagios|http://www.nagios.org/] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1652) Stream Docker logs into sandbox logs
[ https://issues.apache.org/jira/browse/MESOS-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097534#comment-14097534 ] Jay Buffington commented on MESOS-1652: --- https://reviews.apache.org/r/24464 > Stream Docker logs into sandbox logs > > > Key: MESOS-1652 > URL: https://issues.apache.org/jira/browse/MESOS-1652 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen >Assignee: Timothy Chen > > We should write logs either during or after the task launched the logs from > the docker container into the sandbox so it can be viewed without actually > going to the host and calling "docker logs". -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-899) make install does not install python libraries
[ https://issues.apache.org/jira/browse/MESOS-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097351#comment-14097351 ] Benjamin Hindman commented on MESOS-899: Awesome, thanks [~tstclair]! > make install does not install python libraries > -- > > Key: MESOS-899 > URL: https://issues.apache.org/jira/browse/MESOS-899 > Project: Mesos > Issue Type: Bug >Reporter: Benjamin Mahler >Assignee: Thomas Rampelberg > > 'make install' does not currently install the python libraries. > Would love to hear how to do this idiomatically, we could add an install hook > to run easy_install or python setup.py install, with the correct installation > prefix. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-899) make install does not install python libraries
[ https://issues.apache.org/jira/browse/MESOS-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097343#comment-14097343 ] Timothy St. Clair commented on MESOS-899: - [~benjaminhindman] It looks like this isn't landing for 0.20 according to [~thomasr], so I will work with him to ensure the checks are in place prior to submission. > make install does not install python libraries > -- > > Key: MESOS-899 > URL: https://issues.apache.org/jira/browse/MESOS-899 > Project: Mesos > Issue Type: Bug >Reporter: Benjamin Mahler >Assignee: Thomas Rampelberg > > 'make install' does not currently install the python libraries. > Would love to hear how to do this idiomatically, we could add an install hook > to run easy_install or python setup.py install, with the correct installation > prefix. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1645) 0.20.0 Release
[ https://issues.apache.org/jira/browse/MESOS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-1645: -- Description: I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228) - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) - Enable building against installed third-party dependencies (MESOS-1071) I would like to track blockers for the release on this ticket. was: I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228). - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) I would like to track blockers for the release on this ticket. > 0.20.0 Release > -- > > Key: MESOS-1645 > URL: https://issues.apache.org/jira/browse/MESOS-1645 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Jie Yu > > I would like to volunteer to be the release manager for 0.20.0, which will be > releasing the following major features: > - Docker support in Mesos (MESOS-1524) > - Container level network monitoring for mesos containerizer (MESOS-1228) > - Authorization (MESOS-1342) > - Framework rate limiting (MESOS-1306) > - Enable building against installed third-party dependencies (MESOS-1071) > I would like to track blockers for the release on this ticket. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-1228) Container level network monitoring
[ https://issues.apache.org/jira/browse/MESOS-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu resolved MESOS-1228. --- Resolution: Fixed > Container level network monitoring > -- > > Key: MESOS-1228 > URL: https://issues.apache.org/jira/browse/MESOS-1228 > Project: Mesos > Issue Type: Epic > Components: containerization, isolation, statistics >Reporter: Jie Yu >Assignee: Jie Yu > Fix For: 0.20.0 > > > Our goal is to get per-container network statistics. For instance, number of > packets received/sent (RX_PACKETS, TX_PACKETS), how many bytes received/sent > (RX_BYTES, TX_BYTES), etc. > We have a couple of options here for implementing it. > 1) If we have enough IPs (we are assuming IPv4 here as most people are still > using IPv4) such that each container can has an individual IP, we can > leverage the Linux bridge. > 2) If we don't have enough IPs, we can use port forwarding based on port > ranges. In other words, each container will be assigned a range of ports from > the host. The isolator will setup filters to properly redirect packets to the > corresponding containers based on dst ip/ports. > 3) We can use NAT if the processes running inside a container does not need > public IPs. > Our first step is to go with option (2). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1228) Container level network monitoring
[ https://issues.apache.org/jira/browse/MESOS-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-1228: -- Fix Version/s: 0.20.0 > Container level network monitoring > -- > > Key: MESOS-1228 > URL: https://issues.apache.org/jira/browse/MESOS-1228 > Project: Mesos > Issue Type: Epic > Components: containerization, isolation, statistics >Reporter: Jie Yu >Assignee: Jie Yu > Fix For: 0.20.0 > > > Our goal is to get per-container network statistics. For instance, number of > packets received/sent (RX_PACKETS, TX_PACKETS), how many bytes received/sent > (RX_BYTES, TX_BYTES), etc. > We have a couple of options here for implementing it. > 1) If we have enough IPs (we are assuming IPv4 here as most people are still > using IPv4) such that each container can has an individual IP, we can > leverage the Linux bridge. > 2) If we don't have enough IPs, we can use port forwarding based on port > ranges. In other words, each container will be assigned a range of ports from > the host. The isolator will setup filters to properly redirect packets to the > corresponding containers based on dst ip/ports. > 3) We can use NAT if the processes running inside a container does not need > public IPs. > Our first step is to go with option (2). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1071) Enable building against installed third-party dependencies.
[ https://issues.apache.org/jira/browse/MESOS-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097198#comment-14097198 ] Benjamin Hindman commented on MESOS-1071: - [~tstclair]: yes. > Enable building against installed third-party dependencies. > --- > > Key: MESOS-1071 > URL: https://issues.apache.org/jira/browse/MESOS-1071 > Project: Mesos > Issue Type: Epic > Components: build >Reporter: Benjamin Hindman >Assignee: Timothy St. Clair > Fix For: 0.20.0 > > Attachments: modified_tillt.patch > > > Most of our third-party dependencies are included in the project and > statically linked into our resulting binaries and libraries. We would like to > enable building Mesos but using system installed dependencies instead. > In certain circumstances this is more difficult because we've actually needed > to "patch" these libraries (either for C++11 or to alter semantics). > Rather than eliminating our internal copies of these third-party dependencies > the first step should be to just enable using external (i.e., system > installed) dependencies. We already do this for ZooKeeper by allowing people > to use the --without-included-zookeeper flag during compilation. We should do > this for other libraries as well. In fact, for the libraries that we have not > patched (and even for some that we have patched) we should check to see if an > appropriate system installed dependency exists and preferentially use that > unless --with-included-dependency is explicitly used. > Note that this issue represents a stepping stone to removing our third-party > dependencies from our repository. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1071) Enable building against installed third-party dependencies.
[ https://issues.apache.org/jira/browse/MESOS-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097182#comment-14097182 ] Timothy St. Clair commented on MESOS-1071: -- [~benjaminhindman] Do his patches include a .tar.gz for pip & wheel? > Enable building against installed third-party dependencies. > --- > > Key: MESOS-1071 > URL: https://issues.apache.org/jira/browse/MESOS-1071 > Project: Mesos > Issue Type: Epic > Components: build >Reporter: Benjamin Hindman >Assignee: Timothy St. Clair > Fix For: 0.20.0 > > Attachments: modified_tillt.patch > > > Most of our third-party dependencies are included in the project and > statically linked into our resulting binaries and libraries. We would like to > enable building Mesos but using system installed dependencies instead. > In certain circumstances this is more difficult because we've actually needed > to "patch" these libraries (either for C++11 or to alter semantics). > Rather than eliminating our internal copies of these third-party dependencies > the first step should be to just enable using external (i.e., system > installed) dependencies. We already do this for ZooKeeper by allowing people > to use the --without-included-zookeeper flag during compilation. We should do > this for other libraries as well. In fact, for the libraries that we have not > patched (and even for some that we have patched) we should check to see if an > appropriate system installed dependency exists and preferentially use that > unless --with-included-dependency is explicitly used. > Note that this issue represents a stepping stone to removing our third-party > dependencies from our repository. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1071) Enable building against installed third-party dependencies.
[ https://issues.apache.org/jira/browse/MESOS-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097170#comment-14097170 ] Benjamin Hindman commented on MESOS-1071: - What's the plan for pip and wheel once we commit [~thomasr]'s patch for being able to uninstall Mesos Python packages? Are we not going to unbundle them because they never actually get statically linked or installed themselves? > Enable building against installed third-party dependencies. > --- > > Key: MESOS-1071 > URL: https://issues.apache.org/jira/browse/MESOS-1071 > Project: Mesos > Issue Type: Epic > Components: build >Reporter: Benjamin Hindman >Assignee: Timothy St. Clair > Fix For: 0.20.0 > > Attachments: modified_tillt.patch > > > Most of our third-party dependencies are included in the project and > statically linked into our resulting binaries and libraries. We would like to > enable building Mesos but using system installed dependencies instead. > In certain circumstances this is more difficult because we've actually needed > to "patch" these libraries (either for C++11 or to alter semantics). > Rather than eliminating our internal copies of these third-party dependencies > the first step should be to just enable using external (i.e., system > installed) dependencies. We already do this for ZooKeeper by allowing people > to use the --without-included-zookeeper flag during compilation. We should do > this for other libraries as well. In fact, for the libraries that we have not > patched (and even for some that we have patched) we should check to see if an > appropriate system installed dependency exists and preferentially use that > unless --with-included-dependency is explicitly used. > Note that this issue represents a stepping stone to removing our third-party > dependencies from our repository. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-1071) Enable building against installed third-party dependencies.
[ https://issues.apache.org/jira/browse/MESOS-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy St. Clair resolved MESOS-1071. -- Resolution: Fixed Fix Version/s: 0.20.0 All children have been committed. > Enable building against installed third-party dependencies. > --- > > Key: MESOS-1071 > URL: https://issues.apache.org/jira/browse/MESOS-1071 > Project: Mesos > Issue Type: Epic > Components: build >Reporter: Benjamin Hindman >Assignee: Timothy St. Clair > Fix For: 0.20.0 > > Attachments: modified_tillt.patch > > > Most of our third-party dependencies are included in the project and > statically linked into our resulting binaries and libraries. We would like to > enable building Mesos but using system installed dependencies instead. > In certain circumstances this is more difficult because we've actually needed > to "patch" these libraries (either for C++11 or to alter semantics). > Rather than eliminating our internal copies of these third-party dependencies > the first step should be to just enable using external (i.e., system > installed) dependencies. We already do this for ZooKeeper by allowing people > to use the --without-included-zookeeper flag during compilation. We should do > this for other libraries as well. In fact, for the libraries that we have not > patched (and even for some that we have patched) we should check to see if an > appropriate system installed dependency exists and preferentially use that > unless --with-included-dependency is explicitly used. > Note that this issue represents a stepping stone to removing our third-party > dependencies from our repository. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1701) Build Error with gcc 4.7.3
Thomas Hoppe created MESOS-1701: --- Summary: Build Error with gcc 4.7.3 Key: MESOS-1701 URL: https://issues.apache.org/jira/browse/MESOS-1701 Project: Mesos Issue Type: Bug Components: build Affects Versions: 0.19.1 Environment: Gentoo Linux Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.3/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/python --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.7.3-r1 p1.4, pie-0.5.5' --enable-libstdcxx-time --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64 --disable-altivec --disable-fixed-point --enable-targets=all --disable-libgcj --enable-libgomp --disable-libmudflap --disable-libssp --enable-lto --without-cloog --without-ppl Thread model: posix gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) Reporter: Thomas Hoppe Priority: Minor *** Warning: Linking the shared library libmesos.la against the *** static library ../3rdparty/leveldb/libleveldb.a is not portable! libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../lib64/crti.o /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/crtbeginS.o -Wl,--whole-archive ./.libs/libmesos_no_3rdparty.a ../3rdparty/libprocess/.libs/libprocess.a ./.libs/libjava.a -Wl,--no-whole-archive ../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src/.libs/libprotobuf.a ../3rdparty/libprocess/3rdparty/glog-0.3.3/.libs/libglog.a ../3rdparty/leveldb/libleveldb.a ../3rdparty/zookeeper-3.4.5/src/c/.libs/libzookeeper_mt.a /temp1/mesos-0.19.1/build/3rdparty/libprocess/3rdparty/glog-0.3.3/.libs/libglog.a -lpthread /temp1/mesos-0.19.1/build/3rdparty/libprocess/3rdparty/libev-4.15/.libs/libev.a /usr/lib64/libsasl2.so -ldl -lresolv -lcurl -lz -lrt -lunwind -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/lib -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/crtendS.o /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../lib64/crtn.o-pthread -Wl,-soname -Wl,libmesos-0.19.1.so -o .libs/libmesos-0.19.1.so libtool: link: (cd ".libs" && rm -f "libmesos.so" && ln -s "libmesos-0.19.1.so" "libmesos.so") libtool: link: ( cd ".libs" && rm -f "libmesos.la" && ln -s "../libmesos.la" "libmesos.la" ) g++ -DPACKAGE_NAME=\"mesos\" -DPACKAGE_TARNAME=\"mesos\" -DPACKAGE_VERSION=\"0.19.1\" -DPACKAGE_STRING=\"mesos\ 0.19.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mesos\" -DVERSION=\"0.19.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_PTHREAD=1 -DMESOS_HAS_JAVA=1 -DHAVE_PYTHON=\"2.7\" -DMESOS_HAS_PYTHON=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror -DLIBDIR=\"/usr/local/lib\" -DPKGLIBEXECDIR=\"/usr/local/libexec/mesos\" -DPKGDATADIR=\"/usr/local/share/mesos\" -I../../include -I../../3rdparty/libprocess/include -I../../3rdparty/libprocess/3rdparty/stout/include -I../include -I../3rdparty/libprocess/3rdparty/boost-1.53.0 -I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src -I../3rdparty/libprocess/3rdparty/picojson-4f93734 -I../3rdparty/libprocess/3rdparty/glog-0.3.3/src -I../3rdparty/leveldb/include -I../3rdparty/zookeeper-3.4.5/src/c/include -I../3rdparty/zookeeper-3.4.5/src/c/generated -pthread -g -g2 -O2 -MT local/mesos_local-main.o -MD -MP -MF local/.deps/mesos_local-main.Tpo -c -o local/mesos_local-main.o `test -f 'local/main.cpp' || echo '../../src/'`local/main.cpp mv -f local/.deps/mesos_local-main.Tpo local/.deps/mesos_local-main.Po /bin/sh ../libtool --tag=CXX --mode=link g++ -pthread -g -g2 -O2 -o mesos-local local/mesos_local-main.o libmesos.la -
