[jira] [Updated] (MESOS-3684) Port slave/containerizer/external_containerizer.cpp to Windowh

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3684:

Summary: Port slave/containerizer/external_containerizer.cpp to Windowh  
(was: Port slave/containerizer/external_containerizer.cpp to Windows)

> Port slave/containerizer/external_containerizer.cpp to Windowh
> --
>
> Key: MESOS-3684
> URL: https://issues.apache.org/jira/browse/MESOS-3684
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>
> Important subset of the dependency tree follows:
> slave/containerizer/containerizer.cpp: containerizer.hpp, dispatch, fs, os, 
> uuid, flags, slave
> containerizer: future, process, fetcher, flags
> dispatch.hpp: process.hpp
> flags.hpp: os.hpp, path.hpp, fetch.hpp
> future.hpp: pid.hpp
> fetcher: type_utils, future, process, subprocess
> flags.hpp: os.hpp, path.hpp, fetch.hpp
> fetch.hpp: path.hpp
> type_utils.hpp: uuid.hpp
> subprocess: os, future



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3683) Port slave/containerizer/isolator.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3683:

Summary: Port slave/containerizer/isolator.hpp to Windows  (was: Port 
slave/containerizer/isolator.cpp to Windows)

> Port slave/containerizer/isolator.hpp to Windows
> 
>
> Key: MESOS-3683
> URL: https://issues.apache.org/jira/browse/MESOS-3683
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3684) Port slave/containerizer/external_containerizer.cpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3684:
---

 Summary: Port slave/containerizer/external_containerizer.cpp to 
Windows
 Key: MESOS-3684
 URL: https://issues.apache.org/jira/browse/MESOS-3684
 Project: Mesos
  Issue Type: Task
  Components: containerization
Reporter: Alex Clemmer
Assignee: Alex Clemmer


Important subset of the dependency tree follows:

slave/containerizer/containerizer.cpp: containerizer.hpp, dispatch, fs, os, 
uuid, flags, slave
containerizer: future, process, fetcher, flags
dispatch.hpp: process.hpp
flags.hpp: os.hpp, path.hpp, fetch.hpp
future.hpp: pid.hpp
fetcher: type_utils, future, process, subprocess
flags.hpp: os.hpp, path.hpp, fetch.hpp
fetch.hpp: path.hpp
type_utils.hpp: uuid.hpp
subprocess: os, future



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3683) Port slave/containerizer/isolator.cpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3683:
---

 Summary: Port slave/containerizer/isolator.cpp to Windows
 Key: MESOS-3683
 URL: https://issues.apache.org/jira/browse/MESOS-3683
 Project: Mesos
  Issue Type: Task
  Components: containerization
Reporter: Alex Clemmer
Assignee: Alex Clemmer







--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3685) Port process/io.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3685:
---

 Summary: Port process/io.hpp to Windows
 Key: MESOS-3685
 URL: https://issues.apache.org/jira/browse/MESOS-3685
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3682) Port slave/containerizer/launcher.cpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3682:

Description: 



  was:
Important subset of the dependency tree follows:

slave/containerizer/containerizer.cpp: containerizer.hpp, dispatch, fs, os, 
uuid, flags, slave
containerizer: future, process, fetcher, flags
dispatch.hpp: process.hpp
flags.hpp: os.hpp, path.hpp, fetch.hpp
future.hpp: pid.hpp
fetcher: type_utils, future, process, subprocess
flags.hpp: os.hpp, path.hpp, fetch.hpp
fetch.hpp: path.hpp
type_utils.hpp: uuid.hpp
subprocess: os, future


> Port slave/containerizer/launcher.cpp to Windows
> 
>
> Key: MESOS-3682
> URL: https://issues.apache.org/jira/browse/MESOS-3682
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3620) Create slave/containerizer/isolators/filesystem/windows.cpp

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3620:

Summary: Create slave/containerizer/isolators/filesystem/windows.cpp  (was: 
Create slave/containerizer/isolators/filesyste/windows.cpp)

> Create slave/containerizer/isolators/filesystem/windows.cpp
> ---
>
> Key: MESOS-3620
> URL: https://issues.apache.org/jira/browse/MESOS-3620
> Project: Mesos
>  Issue Type: Task
>  Components: isolation
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesospehre, windows
>
> Should look a lot like the posix.cpp flavor. Important subset of the 
> dependency tree follows for the posix flavor:
> slave/containerizer/isolators/filesystem/posix.cpp: filesystem/posix, fs, os, 
> path
> filesystem/posix: flags, isolator



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3681) Port slave/containerizer/fetcher.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3681:
---

 Summary: Port slave/containerizer/fetcher.hpp to Windows
 Key: MESOS-3681
 URL: https://issues.apache.org/jira/browse/MESOS-3681
 Project: Mesos
  Issue Type: Task
  Components: containerization
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3682) Port slave/containerizer/launcher.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3682:

Summary: Port slave/containerizer/launcher.hpp to Windows  (was: Port 
slave/containerizer/launcher.cpp to Windows)

> Port slave/containerizer/launcher.hpp to Windows
> 
>
> Key: MESOS-3682
> URL: https://issues.apache.org/jira/browse/MESOS-3682
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3684) Port slave/containerizer/external_containerizer.hpp to Windowh

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3684:

Summary: Port slave/containerizer/external_containerizer.hpp to Windowh  
(was: Port slave/containerizer/external_containerizer.cpp to Windowh)

> Port slave/containerizer/external_containerizer.hpp to Windowh
> --
>
> Key: MESOS-3684
> URL: https://issues.apache.org/jira/browse/MESOS-3684
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3030) Build failure on OS 10.11 using Xcode 7.

[Till Toenshoff (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950168#comment-14950168
 ] 

Till Toenshoff commented on MESOS-3030:
---

The issues persists all the way to OS X 10.11 release, will propose a fix.

> Build failure on OS 10.11 using Xcode 7.
> 
>
> Key: MESOS-3030
> URL: https://issues.apache.org/jira/browse/MESOS-3030
> Project: Mesos
>  Issue Type: Bug
> Environment: OS 10.11 Beta (15A215h), Apple LLVM version 7.0.0 
> (clang-700.0.57.2)
>Reporter: Till Toenshoff
>
> When trying to build Mesos (recent master) on OS X El Capitan (public beta 1) 
> with apple's clang distribution via Xcode 7 (beta 3) the following warnings 
> trigger build failures;
> h6.Boost: unused-local-typedef 
> {noformat}
> ../3rdparty/libprocess/3rdparty/boost-1.53.0/boost/tuple/detail/tuple_basic.hpp:228:31:
>  error: unused typedef 'cons_element' [-Werror,-Wunused-local-typedef]
>   typedef typename impl::type cons_element;
> {noformat}
> h6.CyrusSASL2: deprecated-declarations
> {noformat}
> distcc[57619] ERROR: compile 
> /Users/till/.ccache/tmp/authentica.stdout.lobomacpro2.fritz.box.48363.0QJikQ.ii
>  on localhost failed
> ../../src/authentication/cram_md5/authenticatee.cpp:75:7: error: 
> 'sasl_dispose' is deprecated: first deprecated in OS X 10.11 
> [-Werror,-Wdeprecated-declarations]
>   sasl_dispose();
>   ^
> /usr/include/sasl/sasl.h:746:13: note: 'sasl_dispose' has been explicitly 
> marked deprecated here
> extern void sasl_dispose(sasl_conn_t **pconn) 
> __attribute__((availability(macosx,introduced=10.0,deprecated=10.11)));
> ^
> {noformat}
> 
> A simple workaround is disabling those warnings for now;
> {noformat}
> export CXXFLAGS="-Wno-unused-local-typedef -Wno-deprecated-declarations"
> export CCFLAGS="-Wno-unused-local-typedef -Wno-deprecated-declarations"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3686) General cleanup of documentation

[Chris Elsmore (JIRA)]

Chris Elsmore created MESOS-3686:


 Summary: General cleanup of documentation
 Key: MESOS-3686
 URL: https://issues.apache.org/jira/browse/MESOS-3686
 Project: Mesos
  Issue Type: Documentation
  Components: documentation, general
Reporter: Chris Elsmore


Current documentation is inconsistent, and could do with a clean up:-

* File names use a mix of hyphens and underscores,  some start with 'mesos' 
some not.

* A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3684) Port slave/containerizer/external_containerizer.cpp to Windowh

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3684:

Description: (was: Important subset of the dependency tree follows:

slave/containerizer/containerizer.cpp: containerizer.hpp, dispatch, fs, os, 
uuid, flags, slave
containerizer: future, process, fetcher, flags
dispatch.hpp: process.hpp
flags.hpp: os.hpp, path.hpp, fetch.hpp
future.hpp: pid.hpp
fetcher: type_utils, future, process, subprocess
flags.hpp: os.hpp, path.hpp, fetch.hpp
fetch.hpp: path.hpp
type_utils.hpp: uuid.hpp
subprocess: os, future)

> Port slave/containerizer/external_containerizer.cpp to Windowh
> --
>
> Key: MESOS-3684
> URL: https://issues.apache.org/jira/browse/MESOS-3684
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-2021) Mesos will not execute on ARM CPU based System

[Kevin Lyda (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950110#comment-14950110
 ] 

Kevin Lyda commented on MESOS-2021:
---

We're trying to get this working as part of the Dublin Mesoscon hackathon.

It's in the https://github.com/lyda/mesos-on-arm repo and we'll see about 
getting the fixes committed.

> Mesos will not execute on ARM CPU based System
> --
>
> Key: MESOS-2021
> URL: https://issues.apache.org/jira/browse/MESOS-2021
> Project: Mesos
>  Issue Type: Bug
>  Components: cli, general
>Affects Versions: 0.20.1
> Environment: Linux c1-10-1-2-103.cloud.online.net 3.17.0-85 #2 SMP 
> Wed Oct 15 15:31:27 CEST 2014 armv7l Marvell Armada 370/XP (Device Tree) 
> GNU/Linux
>Reporter: Axel Etcheverry
>
> Configuration : ../configure --disable-java
> {noformat}
> c1-10-1-2-103 build # ./bin/mesos-master.sh --ip=127.0.0.1 
> --work_dir=/var/lib/mesos
> I1031 12:11:04.993352 21161 main.cpp:155] Build: 2014-10-31 01:04:48 by root
> I1031 12:11:04.995046 21161 main.cpp:157] Version: 0.20.1
> F1031 12:11:04.997396 21161 leveldb.cpp:160] Check failed: 
> leveldb::BytewiseComparator()->Compare(one, two) < 0 
> *** Check failure stack trace: ***
> @ 0xb63db678  google::LogMessage::Fail()
> @ 0xb63dd428  google::LogMessage::SendToLog()
> @ 0xb63db294  google::LogMessage::Flush()
> @ 0xb63ddbc4  google::LogMessageFatal::~LogMessageFatal()
> @ 0xb62c8fb0  mesos::internal::log::LevelDBStorage::restore()
> @ 0xb6337198  mesos::internal::log::ReplicaProcess::restore()
> @ 0xb6337920  mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0xb6337ad4  mesos::internal::log::Replica::Replica()
> @ 0xb62ca948  mesos::internal::log::LogProcess::LogProcess()
> @ 0xb62cabc8  mesos::internal::log::Log::Log()
> @0x41818  main
> @ 0xb51965f8  (unknown)
> Aborted
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3686) General cleanup of documentation

[Chris Elsmore (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Elsmore updated MESOS-3686:
-
Description: 
Park of the MesosCon Europe 2015 Hackathon!

Current documentation is inconsistent, and could do with a clean up:-

* File names use a mix of hyphens and underscores,  some start with 'mesos' 
some not.

* A general clean up of broken links, and markdown tables etc.

  was:
Current documentation is inconsistent, and could do with a clean up:-

* File names use a mix of hyphens and underscores,  some start with 'mesos' 
some not.

* A general clean up of broken links, and markdown tables etc.


> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Park of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-1661) socket errors should show IP address

[Adam B (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951447#comment-14951447
 ] 

Adam B commented on MESOS-1661:
---

Assigned to Brice. Dominic's not an active shepherd anymore, so I removed him. 
Maybe [~jvanremoortere] can take a look?

> socket errors should show IP address
> 
>
> Key: MESOS-1661
> URL: https://issues.apache.org/jira/browse/MESOS-1661
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: David Robinson
>Assignee: Brice Arnould
>Priority: Minor
>  Labels: newbie
>
> [Log messages that show socket 
> errors|https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/process.cpp#L1035]
>  (Connection refused, Broken pipe etc) should also show the remote IP 
> address. It's difficult to troubleshoot why a connection is being refused 
> when you don't know where it's trying to connect.
> {noformat:title=sample log snippet}
> I0801 23:15:57.315096 20305 log.cpp:656] Attempting to start the writer
> I0801 23:15:57.315913 20313 replica.cpp:474] Replica received implicit 
> promise request with proposal 865
> I0801 23:15:57.316473 20326 process.cpp:1096] Socket error while receiving: 
> Connection refused
> I0801 23:15:57.316499 20326 process.cpp:1140] Socket error while sending: 
> Broken pipe
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1661) socket errors should show IP address

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-1661:
--
Shepherd:   (was: Dominic Hamon)

> socket errors should show IP address
> 
>
> Key: MESOS-1661
> URL: https://issues.apache.org/jira/browse/MESOS-1661
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: David Robinson
>Assignee: Brice Arnould
>Priority: Minor
>  Labels: newbie
>
> [Log messages that show socket 
> errors|https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/process.cpp#L1035]
>  (Connection refused, Broken pipe etc) should also show the remote IP 
> address. It's difficult to troubleshoot why a connection is being refused 
> when you don't know where it's trying to connect.
> {noformat:title=sample log snippet}
> I0801 23:15:57.315096 20305 log.cpp:656] Attempting to start the writer
> I0801 23:15:57.315913 20313 replica.cpp:474] Replica received implicit 
> promise request with proposal 865
> I0801 23:15:57.316473 20326 process.cpp:1096] Socket error while receiving: 
> Connection refused
> I0801 23:15:57.316499 20326 process.cpp:1140] Socket error while sending: 
> Broken pipe
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1661) socket errors should show IP address

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-1661:
--
Assignee: Brice Arnould  (was: Ken Sipe)

> socket errors should show IP address
> 
>
> Key: MESOS-1661
> URL: https://issues.apache.org/jira/browse/MESOS-1661
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: David Robinson
>Assignee: Brice Arnould
>Priority: Minor
>  Labels: newbie
>
> [Log messages that show socket 
> errors|https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/process.cpp#L1035]
>  (Connection refused, Broken pipe etc) should also show the remote IP 
> address. It's difficult to troubleshoot why a connection is being refused 
> when you don't know where it's trying to connect.
> {noformat:title=sample log snippet}
> I0801 23:15:57.315096 20305 log.cpp:656] Attempting to start the writer
> I0801 23:15:57.315913 20313 replica.cpp:474] Replica received implicit 
> promise request with proposal 865
> I0801 23:15:57.316473 20326 process.cpp:1096] Socket error while receiving: 
> Connection refused
> I0801 23:15:57.316499 20326 process.cpp:1140] Socket error while sending: 
> Broken pipe
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-3493) benchmark for declining offers

[James Peach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Peach reassigned MESOS-3493:
--

Assignee: James Peach

> benchmark for declining offers
> --
>
> Key: MESOS-3493
> URL: https://issues.apache.org/jira/browse/MESOS-3493
> Project: Mesos
>  Issue Type: Improvement
>  Components: test
>Reporter: James Peach
>Assignee: James Peach
>Priority: Minor
>
> I wrote a benchmark that can be used to demonstrate the performance issues 
> addressed in MESOS-3052, MESOS-3051, MESOS-3157 and MESOS-3075. The benchmark 
> simulates a number of frameworks that start declining all offers once they 
> reach the limit of work they need to do.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3664) Port process/metrics/metric.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3664:
---

 Summary: Port process/metrics/metric.hpp to Windows
 Key: MESOS-3664
 URL: https://issues.apache.org/jira/browse/MESOS-3664
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3666) Port process/metrics/metrics.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3666:
---

 Summary: Port process/metrics/metrics.hpp to Windows
 Key: MESOS-3666
 URL: https://issues.apache.org/jira/browse/MESOS-3666
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3678) Port slave/containerizer/composing.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3678:

Description: (was: Important subset of the dependency tree follows:

slave/containerizer/containerizer.cpp: containerizer.hpp, dispatch, fs, os, 
uuid, flags, slave
containerizer: future, process, fetcher, flags
dispatch.hpp: process.hpp
flags.hpp: os.hpp, path.hpp, fetch.hpp
future.hpp: pid.hpp
fetcher: type_utils, future, process, subprocess
flags.hpp: os.hpp, path.hpp, fetch.hpp
fetch.hpp: path.hpp
type_utils.hpp: uuid.hpp
subprocess: os, future)

> Port slave/containerizer/composing.hpp to Windows
> -
>
> Key: MESOS-3678
> URL: https://issues.apache.org/jira/browse/MESOS-3678
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3680) Port slave/containerizer/fetcher.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3680:
---

 Summary: Port slave/containerizer/fetcher.hpp to Windows
 Key: MESOS-3680
 URL: https://issues.apache.org/jira/browse/MESOS-3680
 Project: Mesos
  Issue Type: Task
  Components: containerization
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3672) Port process/timer.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3672:

Summary: Port process/timer.hpp to Windows  (was: Port process/dispatch.hpp 
to Windows)

> Port process/timer.hpp to Windows
> -
>
> Key: MESOS-3672
> URL: https://issues.apache.org/jira/browse/MESOS-3672
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3673) Port process/timerout.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3673:
---

 Summary: Port process/timerout.hpp to Windows
 Key: MESOS-3673
 URL: https://issues.apache.org/jira/browse/MESOS-3673
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3675) Port process/check.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3675:
---

 Summary: Port process/check.hpp to Windows
 Key: MESOS-3675
 URL: https://issues.apache.org/jira/browse/MESOS-3675
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3676) Port process/collect.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3676:
---

 Summary: Port process/collect.hpp to Windows
 Key: MESOS-3676
 URL: https://issues.apache.org/jira/browse/MESOS-3676
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3677) Port slave/status_update_manager.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3677:
---

 Summary: Port slave/status_update_manager.hpp to Windows
 Key: MESOS-3677
 URL: https://issues.apache.org/jira/browse/MESOS-3677
 Project: Mesos
  Issue Type: Task
  Components: slave
Reporter: Alex Clemmer
Assignee: Alex Clemmer


Required to send updates to the master.

Important subset of dependencies this requires:

slave/status_update_manager.cpp: pid, future, uuid, flags
pid.hpp: address.hpp, ip.hpp
address.hpp: *, ip.hpp, net.hpp
net.hpp: ip, networking stuff
future.hpp: pid.hpp
flags.hpp: os.hpp, path.hpp, fetch.hpp
fetch.hpp: path.hpp



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3649) Port process/future.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3649:

Summary: Port process/future.hpp to Windows  (was: Port 
process/metrics/metrics.hpp to Windows)

> Port process/future.hpp to Windows
> --
>
> Key: MESOS-3649
> URL: https://issues.apache.org/jira/browse/MESOS-3649
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3668) Port process/delay.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3668:
---

 Summary: Port process/delay.hpp to Windows
 Key: MESOS-3668
 URL: https://issues.apache.org/jira/browse/MESOS-3668
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3674) Port process/async.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3674:
---

 Summary: Port process/async.hpp to Windows
 Key: MESOS-3674
 URL: https://issues.apache.org/jira/browse/MESOS-3674
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3678) Port slave/containerizer/composing.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3678:
---

 Summary: Port slave/containerizer/composing.hpp to Windows
 Key: MESOS-3678
 URL: https://issues.apache.org/jira/browse/MESOS-3678
 Project: Mesos
  Issue Type: Task
  Components: containerization
Reporter: Alex Clemmer
Assignee: Alex Clemmer


Important subset of the dependency tree follows:

slave/containerizer/containerizer.cpp: containerizer.hpp, dispatch, fs, os, 
uuid, flags, slave
containerizer: future, process, fetcher, flags
dispatch.hpp: process.hpp
flags.hpp: os.hpp, path.hpp, fetch.hpp
future.hpp: pid.hpp
fetcher: type_utils, future, process, subprocess
flags.hpp: os.hpp, path.hpp, fetch.hpp
fetch.hpp: path.hpp
type_utils.hpp: uuid.hpp
subprocess: os, future



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3680) Port slave/containerizer/subprocess.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3680:

Summary: Port slave/containerizer/subprocess.hpp to Windows  (was: Port 
slave/containerizer/fetcher.hpp to Windows)

> Port slave/containerizer/subprocess.hpp to Windows
> --
>
> Key: MESOS-3680
> URL: https://issues.apache.org/jira/browse/MESOS-3680
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3680) Port process/subprocess.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3680:

Component/s: (was: containerization)

> Port process/subprocess.hpp to Windows
> --
>
> Key: MESOS-3680
> URL: https://issues.apache.org/jira/browse/MESOS-3680
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3680) Port process/subprocess.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3680:

Component/s: libprocess

> Port process/subprocess.hpp to Windows
> --
>
> Key: MESOS-3680
> URL: https://issues.apache.org/jira/browse/MESOS-3680
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3680) Port process/subprocess.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3680:

Summary: Port process/subprocess.hpp to Windows  (was: Port 
slave/containerizer/subprocess.hpp to Windows)

> Port process/subprocess.hpp to Windows
> --
>
> Key: MESOS-3680
> URL: https://issues.apache.org/jira/browse/MESOS-3680
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3661) Port slave/metrics.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3661:

Component/s: (was: libprocess)
 slave

> Port slave/metrics.hpp to Windows
> -
>
> Key: MESOS-3661
> URL: https://issues.apache.org/jira/browse/MESOS-3661
> Project: Mesos
>  Issue Type: Task
>  Components: slave
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3649) Port process/metrics/metrics.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3649:

Summary: Port process/metrics/metrics.hpp to Windows  (was: Port 
process/future.hpp to Windows)

> Port process/metrics/metrics.hpp to Windows
> ---
>
> Key: MESOS-3649
> URL: https://issues.apache.org/jira/browse/MESOS-3649
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3661) Port slave/metrics.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3661:

Summary: Port slave/metrics.hpp to Windows  (was: Port 
process/metrics/metrics.hpp to Windows)

> Port slave/metrics.hpp to Windows
> -
>
> Key: MESOS-3661
> URL: https://issues.apache.org/jira/browse/MESOS-3661
> Project: Mesos
>  Issue Type: Task
>  Components: slave
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3667) Port process/limiter.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3667:
---

 Summary: Port process/limiter.hpp to Windows
 Key: MESOS-3667
 URL: https://issues.apache.org/jira/browse/MESOS-3667
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3669) Port process/clock.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3669:
---

 Summary: Port process/clock.hpp to Windows
 Key: MESOS-3669
 URL: https://issues.apache.org/jira/browse/MESOS-3669
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3670) Port process/time.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3670:
---

 Summary: Port process/time.hpp to Windows
 Key: MESOS-3670
 URL: https://issues.apache.org/jira/browse/MESOS-3670
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3671) Port process/duration.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3671:
---

 Summary: Port process/duration.hpp to Windows
 Key: MESOS-3671
 URL: https://issues.apache.org/jira/browse/MESOS-3671
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3663) Port process/metrics/gauge.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3663:
---

 Summary: Port process/metrics/gauge.hpp to Windows
 Key: MESOS-3663
 URL: https://issues.apache.org/jira/browse/MESOS-3663
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3665) Port process/metrics/timeseries.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3665:
---

 Summary: Port process/metrics/timeseries.hpp to Windows
 Key: MESOS-3665
 URL: https://issues.apache.org/jira/browse/MESOS-3665
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3671) Port stout/duration.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3671:

Summary: Port stout/duration.hpp to Windows  (was: Port 
process/duration.hpp to Windows)

> Port stout/duration.hpp to Windows
> --
>
> Key: MESOS-3671
> URL: https://issues.apache.org/jira/browse/MESOS-3671
> Project: Mesos
>  Issue Type: Task
>  Components: stout
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3670) Port process/time.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3670:

Component/s: (was: libprocess)
 stout

> Port process/time.hpp to Windows
> 
>
> Key: MESOS-3670
> URL: https://issues.apache.org/jira/browse/MESOS-3670
> Project: Mesos
>  Issue Type: Task
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3671) Port process/duration.hpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3671:

Component/s: (was: libprocess)
 stout

> Port process/duration.hpp to Windows
> 
>
> Key: MESOS-3671
> URL: https://issues.apache.org/jira/browse/MESOS-3671
> Project: Mesos
>  Issue Type: Task
>  Components: stout
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3694) Enable building mesos.apache.org locally in a Docker container.

[Artem Harutyunyan (JIRA)]

Artem Harutyunyan created MESOS-3694:


 Summary: Enable building mesos.apache.org locally in a Docker 
container.
 Key: MESOS-3694
 URL: https://issues.apache.org/jira/browse/MESOS-3694
 Project: Mesos
  Issue Type: Bug
Reporter: Artem Harutyunyan
Assignee: Artem Harutyunyan


We should make it easy for everyone to modify the website and be able to 
generate it locally before pushing to upstream. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3493) benchmark for declining offers

[James Peach (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951307#comment-14951307
 ] 

James Peach commented on MESOS-3493:


[~jvanremoortere] can you take a look at the updated 
https://reviews.apache.org/r/38649/ ?

> benchmark for declining offers
> --
>
> Key: MESOS-3493
> URL: https://issues.apache.org/jira/browse/MESOS-3493
> Project: Mesos
>  Issue Type: Improvement
>  Components: test
>Reporter: James Peach
>Assignee: James Peach
>Priority: Minor
>
> I wrote a benchmark that can be used to demonstrate the performance issues 
> addressed in MESOS-3052, MESOS-3051, MESOS-3157 and MESOS-3075. The benchmark 
> simulates a number of frameworks that start declining all offers once they 
> reach the limit of work they need to do.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3519) Fix file descriptor leakage / double close in the code base

[Chi Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951294#comment-14951294
 ] 

Chi Zhang commented on MESOS-3519:
--

https://reviews.apache.org/r/39192/
https://reviews.apache.org/r/39193/

Should we abstract the Netlink in routing out for these?

> Fix file descriptor leakage / double close in the code base
> ---
>
> Key: MESOS-3519
> URL: https://issues.apache.org/jira/browse/MESOS-3519
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chi Zhang
>Assignee: Chi Zhang
> Fix For: 0.25.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3690) Changes to Apache Mesos' website

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950603#comment-14950603
 ] 

ASF GitHub Bot commented on MESOS-3690:
---

GitHub user fayusohenson opened a pull request:

https://github.com/apache/mesos/pull/75

Changes in support of MESOS-3690

https://issues.apache.org/jira/browse/MESOS-3690

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fayusohenson/mesos mesos-3690

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/75.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #75


commit ea1d56e3aefdafed6743ffe83f40f0eef4f7ca11
Author: Freddy Ayuso-Henson 
Date:   2015-10-09T15:12:18Z

Changes in support of MESOS-3690




> Changes to Apache Mesos' website
> 
>
> Key: MESOS-3690
> URL: https://issues.apache.org/jira/browse/MESOS-3690
> Project: Mesos
>  Issue Type: Improvement
>  Components: project website
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> Changes to the project website:
> - Support smaller screens/devices (mobile)
> - Limit images' max width when displayed
> - Update Bootstrap version
> - Other smaller changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3686) General cleanup of documentation

[Dave Lester (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Lester updated MESOS-3686:
---
Assignee: (was: Dave Lester)

> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-3686) General cleanup of documentation

[Dave Lester (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Lester reassigned MESOS-3686:
--

Assignee: Dave Lester

> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>Assignee: Dave Lester
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3689) Have a choice whether to delete the archive after extraction bypassing the cache.

[Joerg Schad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joerg Schad updated MESOS-3689:
---
Description: 
In certain cases when fetching archive files we would not like to keep the 
archive file around.



  was:
having the option of deteting or keeping the file in cache after by-passing the 
cache for that file.  3 files have been changed: 
1) fetcher.proto
  BYPASS_CACHE = 0;
  -->
  BYPASS_KEEP_CACHE = 0;
  BYPASS_REMOVE_CACHE = 3;

2)fetcher.cpp
fetch function and fetchBypassingCache function


> Have a choice whether to delete the archive after extraction bypassing the 
> cache.
> -
>
> Key: MESOS-3689
> URL: https://issues.apache.org/jira/browse/MESOS-3689
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Soheila Dehghanzadeh
>Assignee: Soheila Dehghanzadeh
>
> In certain cases when fetching archive files we would not like to keep the 
> archive file around.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3554) Allocator changes trigger large re-compiles

[Qian Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950612#comment-14950612
 ] 

Qian Zhang commented on MESOS-3554:
---

Just curious the large recompiles is because the templatized nature of the 
allocator? Or the header file "hierarchical.hpp" is included in a couple of 
source files (so once it is changed those files need to be recompiled)?

> Allocator changes trigger large re-compiles
> ---
>
> Key: MESOS-3554
> URL: https://issues.apache.org/jira/browse/MESOS-3554
> Project: Mesos
>  Issue Type: Improvement
>  Components: allocation
>Reporter: Joris Van Remoortere
>Assignee: Joris Van Remoortere
>  Labels: mesosphere
>
> Due to the templatized nature of the allocator, even small changes trigger 
> large recompiles of the code-base. This make iterating on changes expensive 
> for developers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3689) Have a choice whether to delete the archive after extraction bypassing the cache.

[Soheila Dehghanzadeh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Soheila Dehghanzadeh updated MESOS-3689:

Description: 
having the option of deteting or keeping the file in cache after by-passing the 
cache for that file.  3 files have been changed: 
1) fetcher.proto
  BYPASS_CACHE = 0;
  -->
  BYPASS_KEEP_CACHE = 0;
  BYPASS_REMOVE_CACHE = 3;

2)fetcher.cpp
fetch function and fetchBypassingCache function

> Have a choice whether to delete the archive after extraction bypassing the 
> cache.
> -
>
> Key: MESOS-3689
> URL: https://issues.apache.org/jira/browse/MESOS-3689
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Soheila Dehghanzadeh
>Assignee: Soheila Dehghanzadeh
>
> having the option of deteting or keeping the file in cache after by-passing 
> the cache for that file.  3 files have been changed: 
> 1) fetcher.proto
>   BYPASS_CACHE = 0;
>   -->
>   BYPASS_KEEP_CACHE = 0;
>   BYPASS_REMOVE_CACHE = 3;
> 2)fetcher.cpp
> fetch function and fetchBypassingCache function



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3687) Streamline site-building process

[Freddy Ayuso-Henson (JIRA)]

Freddy Ayuso-Henson created MESOS-3687:
--

 Summary: Streamline site-building process
 Key: MESOS-3687
 URL: https://issues.apache.org/jira/browse/MESOS-3687
 Project: Mesos
  Issue Type: Improvement
Reporter: Freddy Ayuso-Henson
Priority: Minor


The current site building and publishing process is somewhat cumbersome and 
complicated. As part of MesosCon Hackathon, aim to streamline/simplify this 
process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[Raffaele Di Fazio (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950206#comment-14950206
 ] 

Raffaele Di Fazio commented on MESOS-3688:
--

I'm not sure, how can this information be available? It doesn't seem to be 
exposed via the protobuf. 

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[Raffaele Di Fazio (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950229#comment-14950229
 ] 

Raffaele Di Fazio commented on MESOS-3688:
--

So what you are saying is that we can set MESOS_CONTAINER_NAME from the 
framework as an environment variable, but the framework, as far as I 
understand, doesn't know the current docker name as this is not exposed. So, 
the framework could provide another information but not the real docker name 
(which is generated by mesos). Am I right? 

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3579) FetcherCacheTest.LocalUncachedExtract is flaky

[Bernd Mathiske (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950288#comment-14950288
 ] 

Bernd Mathiske commented on MESOS-3579:
---

@greggomann Thank you! I will debug this.

> FetcherCacheTest.LocalUncachedExtract is flaky
> --
>
> Key: MESOS-3579
> URL: https://issues.apache.org/jira/browse/MESOS-3579
> Project: Mesos
>  Issue Type: Bug
>  Components: fetcher, test
>Reporter: Anand Mazumdar
>Assignee: Bernd Mathiske
>  Labels: flaky-test, mesosphere
>
> From ASF CI:
> https://builds.apache.org/job/Mesos/866/COMPILER=clang,CONFIGURATION=--verbose,OS=ubuntu:14.04,label_exp=docker%7C%7CHadoop/console
> {code}
> [ RUN  ] FetcherCacheTest.LocalUncachedExtract
> Using temporary directory '/tmp/FetcherCacheTest_LocalUncachedExtract_jHBfeA'
> I0925 19:15:39.541198 27410 leveldb.cpp:176] Opened db in 3.43934ms
> I0925 19:15:39.542362 27410 leveldb.cpp:183] Compacted db in 1.136184ms
> I0925 19:15:39.542428 27410 leveldb.cpp:198] Created db iterator in 35866ns
> I0925 19:15:39.542448 27410 leveldb.cpp:204] Seeked to beginning of db in 
> 8807ns
> I0925 19:15:39.542459 27410 leveldb.cpp:273] Iterated through 0 keys in the 
> db in 6325ns
> I0925 19:15:39.542505 27410 replica.cpp:744] Replica recovered with log 
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0925 19:15:39.543143 27438 recover.cpp:449] Starting replica recovery
> I0925 19:15:39.543393 27438 recover.cpp:475] Replica is in EMPTY status
> I0925 19:15:39.544373 27436 replica.cpp:641] Replica in EMPTY status received 
> a broadcasted recover request
> I0925 19:15:39.544791 27433 recover.cpp:195] Received a recover response from 
> a replica in EMPTY status
> I0925 19:15:39.545284 27433 recover.cpp:566] Updating replica status to 
> STARTING
> I0925 19:15:39.546155 27436 master.cpp:376] Master 
> c8bf1c95-50f4-4832-a570-c560f0b466ae (f57fd4291168) started on 
> 172.17.1.195:41781
> I0925 19:15:39.546257 27433 leveldb.cpp:306] Persisting metadata (8 bytes) to 
> leveldb took 747249ns
> I0925 19:15:39.546288 27433 replica.cpp:323] Persisted replica status to 
> STARTING
> I0925 19:15:39.546483 27434 recover.cpp:475] Replica is in STARTING status
> I0925 19:15:39.546187 27436 master.cpp:378] Flags at startup: --acls="" 
> --allocation_interval="1secs" --allocator="HierarchicalDRF" 
> --authenticate="true" --authenticate_slaves="true" --authenticators="crammd5" 
> --authorizers="local" 
> --credentials="/tmp/FetcherCacheTest_LocalUncachedExtract_jHBfeA/credentials" 
> --framework_sorter="drf" --help="false" --hostname_lookup="true" 
> --initialize_driver_logging="true" --log_auto_initialize="true" 
> --logbufsecs="0" --logging_level="INFO" --max_slave_ping_timeouts="5" 
> --quiet="false" --recovery_slave_removal_limit="100%" 
> --registry="replicated_log" --registry_fetch_timeout="1mins" 
> --registry_store_timeout="25secs" --registry_strict="true" 
> --root_submissions="true" --slave_ping_timeout="15secs" 
> --slave_reregister_timeout="10mins" --user_sorter="drf" --version="false" 
> --webui_dir="/mesos/mesos-0.26.0/_inst/share/mesos/webui" 
> --work_dir="/tmp/FetcherCacheTest_LocalUncachedExtract_jHBfeA/master" 
> --zk_session_timeout="10secs"
> I0925 19:15:39.546567 27436 master.cpp:423] Master only allowing 
> authenticated frameworks to register
> I0925 19:15:39.546617 27436 master.cpp:428] Master only allowing 
> authenticated slaves to register
> I0925 19:15:39.546632 27436 credentials.hpp:37] Loading credentials for 
> authentication from 
> '/tmp/FetcherCacheTest_LocalUncachedExtract_jHBfeA/credentials'
> I0925 19:15:39.546931 27436 master.cpp:467] Using default 'crammd5' 
> authenticator
> I0925 19:15:39.547044 27436 master.cpp:504] Authorization enabled
> I0925 19:15:39.547276 27441 whitelist_watcher.cpp:79] No whitelist given
> I0925 19:15:39.547320 27434 hierarchical.hpp:468] Initialized hierarchical 
> allocator process
> I0925 19:15:39.547471 27438 replica.cpp:641] Replica in STARTING status 
> received a broadcasted recover request
> I0925 19:15:39.548318 27443 recover.cpp:195] Received a recover response from 
> a replica in STARTING status
> I0925 19:15:39.549067 27435 recover.cpp:566] Updating replica status to VOTING
> I0925 19:15:39.549115 27440 master.cpp:1603] The newly elected leader is 
> master@172.17.1.195:41781 with id c8bf1c95-50f4-4832-a570-c560f0b466ae
> I0925 19:15:39.549162 27440 master.cpp:1616] Elected as the leading master!
> I0925 19:15:39.549190 27440 master.cpp:1376] Recovering from registrar
> I0925 19:15:39.549342 27434 registrar.cpp:309] Recovering registrar
> I0925 19:15:39.549666 27430 leveldb.cpp:306] Persisting metadata (8 bytes) to 
> leveldb took 418187ns
> I0925 19:15:39.549753 27430 replica.cpp:323] Persisted replica status to 
> VOTING
> I0925 19:15:39.550089 

[jira] [Commented] (MESOS-3687) Streamline site-building process

[haosdent (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950175#comment-14950175
 ] 

haosdent commented on MESOS-3687:
-

+1 for this

> Streamline site-building process
> 
>
> Key: MESOS-3687
> URL: https://issues.apache.org/jira/browse/MESOS-3687
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> The current site building and publishing process is somewhat cumbersome and 
> complicated. As part of MesosCon Hackathon, aim to streamline/simplify this 
> process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[haosdent (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950211#comment-14950211
 ] 

haosdent commented on MESOS-3688:
-

It is not from protobuf. From environment variables. You could see more details 
from https://issues.apache.org/jira/browse/MESOS-3377

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3689) Have a choice whether to delete the archive after extraction bypassing the cache.

[Soheila Dehghanzadeh (JIRA)]

Soheila Dehghanzadeh created MESOS-3689:
---

 Summary: Have a choice whether to delete the archive after 
extraction bypassing the cache.
 Key: MESOS-3689
 URL: https://issues.apache.org/jira/browse/MESOS-3689
 Project: Mesos
  Issue Type: Improvement
Reporter: Soheila Dehghanzadeh
Assignee: Soheila Dehghanzadeh






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[haosdent (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950298#comment-14950298
 ] 

haosdent commented on MESOS-3688:
-

Sorry to could not understand "is this information also available to 
frameworks?" here. Could you explain more?

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[Raffaele Di Fazio (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950321#comment-14950321
 ] 

Raffaele Di Fazio commented on MESOS-3688:
--

Yes, I was just wondering how could a framework (Marathon, in my case) read 
this information so that I could make it available through Marathon's REST API. 

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3686) General cleanup of documentation

[Chris Elsmore (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Elsmore updated MESOS-3686:
-
Description: 
Part of the MesosCon Europe 2015 Hackathon!

Current documentation is inconsistent, and could do with a clean up:-

* File names use a mix of hyphens and underscores,  some start with 'mesos' 
some not.

* A general clean up of broken links, and markdown tables etc.

  was:
Park of the MesosCon Europe 2015 Hackathon!

Current documentation is inconsistent, and could do with a clean up:-

* File names use a mix of hyphens and underscores,  some start with 'mesos' 
some not.

* A general clean up of broken links, and markdown tables etc.


> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3686) General cleanup of documentation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950339#comment-14950339
 ] 

ASF GitHub Bot commented on MESOS-3686:
---

GitHub user elsmorian opened a pull request:

https://github.com/apache/mesos/pull/70

Documentation file naming cleanup

Part of https://issues.apache.org/jira/browse/MESOS-3686

Clean up of filenames in documentation, prefer hyphens and drop 'mesos' 
from filenames

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fayusohenson/mesos docs

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/70.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #70


commit aba24e7c2ee93ef85a7043f34580d834324fd926
Author: Chris Elsmore 
Date:   2015-10-09T10:44:36Z

underscores to hyphens

commit 75d0a5613382214c4cf003733f771b0ff8ba0c55
Author: Chris Elsmore 
Date:   2015-10-09T11:05:01Z

drop mesos from architecture filename

commit 8c1f40faa9aa390dae95a3ebf20147b116c5d851
Author: Chris Elsmore 
Date:   2015-10-09T11:10:19Z

drop mesos from c++-style-guide filename

commit b35c0ffda619b47c7f72eeb520bef2fbcbb418e3
Author: Chris Elsmore 
Date:   2015-10-09T11:13:04Z

drop mesos from containerizer filename

commit da6d4c9440efb14d7c2dc499f9906f52bd1ba014
Author: Chris Elsmore 
Date:   2015-10-09T11:27:06Z

Added info for docs submissions through GH and reviewboard

commit 98ed7e8646e738fde51fbd7cee4a65cd3d4e9ecb
Author: Chris Elsmore 
Date:   2015-10-09T11:29:04Z

drop mesos from documentation-guide filename

commit 610c2fd8f086b961bb0ccc596349e3bd00f74ad8
Author: Chris Elsmore 
Date:   2015-10-09T12:07:24Z

drop mesos from doxygen-style-guide filename

commit 1c92b88a2c1357a421836264a584a048a662dbac
Author: Chris Elsmore 
Date:   2015-10-09T12:18:19Z

drop mesos from mesos-frameworks filename

commit bbe3b5d0c95cac5a17c17316efb14bdd4c81ef38
Author: Chris Elsmore 
Date:   2015-10-09T12:20:51Z

drop mesos from mesos-markdown-style-guide filename

commit 0e4eaf8c454356700f72b7da92bec2dabd16b425
Author: Chris Elsmore 
Date:   2015-10-09T12:23:50Z

drop mesos from mesos-presentations filename

commit 7427565941e23a3b06bf7950045515d31724df20
Author: Chris Elsmore 
Date:   2015-10-09T12:25:25Z

drop mesos from mesos-roadmap filename

commit 5bcf67b5cd329dd47addf0440bbfb35e9c8ce96f
Author: Chris Elsmore 
Date:   2015-10-09T12:30:46Z

drop mesos from mesos-ssl filename

commit 0c1c52eb40af69097cab6aaa65d0604ad88a5af9
Author: Chris Elsmore 
Date:   2015-10-09T12:33:05Z

drop mesos from mesos-testing-patterns filename




> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3690) Changes to Apache Mesos' website

[Freddy Ayuso-Henson (JIRA)]

Freddy Ayuso-Henson created MESOS-3690:
--

 Summary: Changes to Apache Mesos' website
 Key: MESOS-3690
 URL: https://issues.apache.org/jira/browse/MESOS-3690
 Project: Mesos
  Issue Type: Improvement
  Components: project website
Reporter: Freddy Ayuso-Henson
Priority: Minor


Changes to the project website:

- Support smaller screens/smaller devices
- Limit images' max width when displayed
- Update Bootstrap version
- Other smaller changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3690) Changes to Apache Mesos' website

[Freddy Ayuso-Henson (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freddy Ayuso-Henson updated MESOS-3690:
---
Description: 
Changes to the project website:

- Support smaller screens/devices (mobile)
- Limit images' max width when displayed
- Update Bootstrap version
- Other smaller changes

  was:
Changes to the project website:

- Support smaller screens/smaller devices
- Limit images' max width when displayed
- Update Bootstrap version
- Other smaller changes


> Changes to Apache Mesos' website
> 
>
> Key: MESOS-3690
> URL: https://issues.apache.org/jira/browse/MESOS-3690
> Project: Mesos
>  Issue Type: Improvement
>  Components: project website
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> Changes to the project website:
> - Support smaller screens/devices (mobile)
> - Limit images' max width when displayed
> - Update Bootstrap version
> - Other smaller changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-2237) Missing end of sentence in 2nd paragraph of architecture overview

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950464#comment-14950464
 ] 

ASF GitHub Bot commented on MESOS-2237:
---

GitHub user elsmorian opened a pull request:

https://github.com/apache/mesos/pull/71

Use character entity references instead of angle brackets

Fixes https://issues.apache.org/jira/browse/MESOS-2237

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fayusohenson/mesos mesos-2237

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/71.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #71


commit 0d97ce12c8134e3753ca166ad1f5ab00a761c415
Author: Chris Elsmore 
Date:   2015-10-09T14:22:54Z

Use character entity references instead of angle brackets




> Missing end of sentence in 2nd paragraph of architecture overview
> -
>
> Key: MESOS-2237
> URL: https://issues.apache.org/jira/browse/MESOS-2237
> Project: Mesos
>  Issue Type: Bug
>  Components: documentation
> Environment: N/A. I'm looking at the documentation on the Mesos 
> website.
>Reporter: Richard Barrell
>
> I'm reading: http://mesos.apache.org/documentation/latest/mesos-architecture/
> The 2nd paragraph reads "The master enables fine-grained sharing of resources 
> (cpu, ram, ...) across applications by making them resource offers. Each 
> resource offer contains a list of . The master decides how many resources to 
> offer to..."
> Presumably its author intended it to have something after "of" in the phrase 
> "a list of ."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-2237) Missing end of sentence in 2nd paragraph of architecture overview

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950476#comment-14950476
 ] 

ASF GitHub Bot commented on MESOS-2237:
---

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/71


> Missing end of sentence in 2nd paragraph of architecture overview
> -
>
> Key: MESOS-2237
> URL: https://issues.apache.org/jira/browse/MESOS-2237
> Project: Mesos
>  Issue Type: Bug
>  Components: documentation
> Environment: N/A. I'm looking at the documentation on the Mesos 
> website.
>Reporter: Richard Barrell
>
> I'm reading: http://mesos.apache.org/documentation/latest/mesos-architecture/
> The 2nd paragraph reads "The master enables fine-grained sharing of resources 
> (cpu, ram, ...) across applications by making them resource offers. Each 
> resource offer contains a list of . The master decides how many resources to 
> offer to..."
> Presumably its author intended it to have something after "of" in the phrase 
> "a list of ."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3688) Get Container Name information when launching a container task

[Raffaele Di Fazio (JIRA)]

Raffaele Di Fazio created MESOS-3688:


 Summary: Get Container Name information when launching a container 
task
 Key: MESOS-3688
 URL: https://issues.apache.org/jira/browse/MESOS-3688
 Project: Mesos
  Issue Type: Improvement
  Components: containerization
Affects Versions: 0.24.1
Reporter: Raffaele Di Fazio


We want to get the Docker Name (or Docker ID, or both) when launching a 
container task with mesos. The container name is generated by mesos itself 
(i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
and it would be nice to expose this information to frameworks so that this 
information can be used, for example by Marathon to give this information to 
users via a REST API. 
To go a bit in depth with our use case, we have files created by fluentd 
logdriver that are named with Docker Name or Docker ID (full or short) and we 
need a mapping for the users of the REST API and thus the first step is to make 
this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[haosdent (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950204#comment-14950204
 ] 

haosdent commented on MESOS-3688:
-

When start docker container, we would pass a MESOS_CONTAINER_NAME to docker 
container, is it satisfy your requirement?

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[haosdent (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950233#comment-14950233
 ] 

haosdent commented on MESOS-3688:
-

Not, I mean we could get docker container name in tasks through the environment 
variable MESOS_CONTAINER_NAME

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3687) Streamline site-building process

[Jonathon Rossi (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950439#comment-14950439
 ] 

Jonathon Rossi commented on MESOS-3687:
---

This will also fix broken images that reference images under "docs/images", 
e.g.:
http://mesos.apache.org/documentation/latest/networking-for-mesos-managed-containers/

> Streamline site-building process
> 
>
> Key: MESOS-3687
> URL: https://issues.apache.org/jira/browse/MESOS-3687
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> The current site building and publishing process is somewhat cumbersome and 
> complicated. As part of MesosCon Hackathon, aim to streamline/simplify this 
> process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3687) Streamline site-building process

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950478#comment-14950478
 ] 

ASF GitHub Bot commented on MESOS-3687:
---

GitHub user jonorossi opened a pull request:

https://github.com/apache/mesos/pull/72

Import site building from subversion for MESOS-3687

https://issues.apache.org/jira/browse/MESOS-3687

/cc @davelester

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fayusohenson/mesos site-import

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/72.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #72


commit 44aa47b948f944d4c46fe76d7c41808d4580b81f
Author: Jonathon Rossi 
Date:   2015-10-09T10:18:57Z

Import site building from subversion for MESOS-3687




> Streamline site-building process
> 
>
> Key: MESOS-3687
> URL: https://issues.apache.org/jira/browse/MESOS-3687
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> The current site building and publishing process is somewhat cumbersome and 
> complicated. As part of MesosCon Hackathon, aim to streamline/simplify this 
> process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3487) Running libprocess tests in a loop leads to unbounded memory growth.

[Diana Arroyo (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950480#comment-14950480
 ] 

Diana Arroyo commented on MESOS-3487:
-

When running the test above it failed with the following error.  Will 
investigate this error below to determine if it is a root cause of this JIRA 
item or if the error below is a separate problem.


../../../3rdparty/libprocess/src/tests/subprocess_tests.cpp:668: Failure
s: Failed to create pipe: Too many open files
*** Aborted at 1444396878 (unix time) try "date -d @1444396878" if you are 
using GNU date ***
PC: @   0x6636aa testing::UnitTest::AddTestPartResult()
*** SIGSEGV (@0x0) received by PID 9679 (TID 0x7ff297880780) from PID 0; stack 
trace: ***
@ 0x7ff297462340 (unknown)
@   0x6636aa testing::UnitTest::AddTestPartResult()
@   0x6583a9 testing::internal::AssertHelper::operator=()
@   0x61e3eb SubprocessTest_Environment_Test::TestBody()
@   0x681ae0 
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@   0x67c4dc 
testing::internal::HandleExceptionsInMethodIfSupported<>()
@   0x65d611 testing::Test::Run()
@   0x65dd94 testing::TestInfo::Run()
@   0x65e3da testing::TestCase::Run()
@   0x664b22 testing::internal::UnitTestImpl::RunAllTests()
@   0x68289f 
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@   0x67d1ac 
testing::internal::HandleExceptionsInMethodIfSupported<>()
@   0x6638be testing::UnitTest::Run()
@   0x4e1e8f RUN_ALL_TESTS()
@   0x4e1ca8 main
@ 0x7ff29646dec5 (unknown)
@   0x40be6b (unknown)

> Running libprocess tests in a loop leads to unbounded memory growth.
> 
>
> Key: MESOS-3487
> URL: https://issues.apache.org/jira/browse/MESOS-3487
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Reporter: Benjamin Mahler
>Assignee: Diana Arroyo
>  Labels: newbie
>
> Was doing some repeat testing on a patch to check for flakiness and noticed 
> that the libprocess tests appear to have a leak that leads to unbounded 
> memory growth.
> I checked the stout tests as well, they appear ok.
> Notice the large RSS for the libprocess tests:
> {noformat}
>   PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
> 55133 root  20   0  479m 9.9m 6860 S 56.8  0.0   0:02.36 tests
> 16410 root  20   0  575m 152m 6864 S 60.1  0.2   6:09.70 tests
> 61363 root  20   0  606m 304m 6948 R 74.7  0.4  15:50.11 tests
> 32836 root  20   0  116m 9032 5580 S 88.3  0.0   3:46.32 stout-tests
> {noformat}
> Commands to reproduce:
> {noformat}
> $ sudo ./3rdparty/libprocess/tests --gtest_repeat=-1 --gtest_break_on_failure
> $ sudo ./3rdparty/libprocess/3rdparty/stout-tests --gtest_repeat=-1 
> --gtest_break_on_failure
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3686) General cleanup of documentation

[Dave Lester (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Lester updated MESOS-3686:
---
Labels: documentation  (was: docuentation)

> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: documentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MESOS-3688) Get Container Name information when launching a container task

[Yan Xu (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950693#comment-14950693
 ] 

Yan Xu edited comment on MESOS-3688 at 10/9/15 4:55 PM:


He's saying that in your task if you read $MESOS_CONTAINER_NAME you'll get the 
container name. 

In fact, you can specify a custom environment variable when you launch the 
task/app and it'll get passed to the task itself (and you can have your task 
log it, have it be the first line in your log, etc.), then you'll be able to 
grep this in the log.

Will this help?


was (Author: xujyan):
He's saying that in your task if you read MESOS_CONTAINER_NAME you'll get the 
container name. 

In fact, you specify a custom environment variable when you launch the task/app 
and it'll get passed to the task itself (and you can have your task log it, 
have it be the first line in your log, etc.), then you'll be able to grep this 
in the log.

Will this help?

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MESOS-3556) mesos.cli broken in 0.24.x

[Marco Massenzio (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950492#comment-14950492
 ] 

Marco Massenzio edited comment on MESOS-3556 at 10/9/15 5:06 PM:
-

PR merged.
New version ({{0.1.5}}) uploaded to PyPi.


was (Author: marco-mesos):
PR merged.

> mesos.cli broken in 0.24.x
> --
>
> Key: MESOS-3556
> URL: https://issues.apache.org/jira/browse/MESOS-3556
> Project: Mesos
>  Issue Type: Bug
>  Components: cli
>Affects Versions: 0.24.0, 0.24.1
>Reporter: Radoslaw Gruchalski
>Assignee: Marco Massenzio
>  Labels: mesosphere
>
> The issue was initially reported on the mailing list: 
> http://www.mail-archive.com/user@mesos.apache.org/msg04670.html
> The format of the master data stored in zookeeper has changed but the 
> mesos.cli does not reflect these changes causing tools like {{mesos-tail}} 
> and {{mesos-ps}} to fail.
> Example error from {{mesos-tail}}:
> {noformat}
> mesos-master ~$ mesos tail -f -n 50 service
> Traceback (most recent call last):
>   File "/usr/local/bin/mesos-tail", line 11, in 
> sys.exit(main())
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/cli.py", line 61, in 
> wrapper
> return fn(*args, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/cmds/tail.py", line 
> 55, in main
> args.task, args.file, fail=(not args.follow)):
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/cluster.py", line 
> 27, 
> in files
> tlist = MASTER.tasks(fltr)
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/master.py", line 
> 174, 
> in tasks
> self._task_list(active_only
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/master.py", line 
> 153, 
> in _task_list
> *[util.merge(x, *keys) for x in self.frameworks(active_only)])
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/master.py", line 
> 185, 
> in frameworks
> return util.merge(self.state, *keys)
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/util.py", line 58, 
> in 
> __get__
> value = self.fget(inst)
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/master.py", line 
> 123, 
> in state
> return self.fetch("/master/state.json").json()
>   File "/usr/local/lib/python2.7/dist-packages/mesos/cli/master.py", line 64, 
> in fetch
> return requests.get(urlparse.urljoin(self.host, url), **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 69, in 
> get
> return request('get', url, params=params, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 50, in 
> request
> response = session.request(method=method, url=url, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
> 451, 
> in request
> prep = self.prepare_request(req)
>   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
> 382, 
> in prepare_request
> hooks=merge_hooks(request.hooks, self.hooks),
>   File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 304, 
> in prepare
> self.prepare_url(url, params)
>   File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 357, 
> in prepare_url
> raise InvalidURL(*e.args)
> requests.exceptions.InvalidURL: Failed to parse: 
> 10.100.1.100:5050","port":5050,"version":"0.24.1"}
> {noformat}
> The problem exists in 
> https://github.com/mesosphere/mesos-cli/blob/master/mesos/cli/master.py#L107. 
> The code should be along the lines of:
> {noformat}
> try:
> parsed =  json.loads(val)
> return parsed["address"]["ip"] + ":" + 
> str(parsed["address"]["port"])
> except Exception:
> return val.split("@")[-1]
> {noformat}
> This causes the master address to come back correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3183) Documentation images do not load

[Joseph Wu (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950686#comment-14950686
 ] 

Joseph Wu commented on MESOS-3183:
--

Update: [~davelester] has submitted the {{rake.patch}}, see [the svn 
commit|http://svn.apache.org/viewvc?view=revision=1707725].

Images still don't show up, since all links which are formatted like 
{{images/foo.png}} will point to 
{{/documentation/latest/some-document/images/foo.png}} instead of 
{{/documentation/latest/images/foo.png}}.

We're still discussing how to make the URL change compatible with versioned 
documentation.

> Documentation images do not load
> 
>
> Key: MESOS-3183
> URL: https://issues.apache.org/jira/browse/MESOS-3183
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Affects Versions: 0.24.0
>Reporter: James Mulcahy
>Assignee: Joseph Wu
>Priority: Minor
>  Labels: mesosphere
> Attachments: rake.patch
>
>
> Any images which are referenced from the generated docs ({{docs/*.md}}) do 
> not show up on the website.  For example:
> * [External 
> Containerizer|http://mesos.apache.org/documentation/latest/external-containerizer/]
> * [Fetcher Cache 
> Internals|http://mesos.apache.org/documentation/latest/fetcher-cache-internals/]
> * [Maintenance|http://mesos.apache.org/documentation/latest/maintenance/] 
> * 
> [Oversubscription|http://mesos.apache.org/documentation/latest/oversubscription/]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3589) Mesos tasks with many ports cause significant master performance problems

[James Mulcahy (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950859#comment-14950859
 ] 

James Mulcahy commented on MESOS-3589:
--

I ran some experiments this morning, switching the framework from randomized to 
non-randomized port selection, and the results are as follows:

With "natural" (i.e. largely consecutive) port ordering, 76 jobs, 500 ports 
each, a state.json fetch takes:

~3-8s  (results were:  3.4, 5.9, 5.9, 3.4)

With "arbitrary" (i.e. randomized) port ordering, and all other variables 
consistent:

~19-25s (results were: 24.2, 25.3, 19.1, 24.1)

This is still on mesos 0.23.  I'm in the process of re-testing with 
4f9dd54cad125f9059cb0646d29f3e8ea680128f merged to 0.23 and will post results 
when I get them.

> Mesos tasks with many ports cause significant master performance problems
> -
>
> Key: MESOS-3589
> URL: https://issues.apache.org/jira/browse/MESOS-3589
> Project: Mesos
>  Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: James Mulcahy
> Attachments: mesos-master-perf-top-call-expanded.txt, 
> mesos-master-perf.txt
>
>
> Today, I used a framework to fire off some tasks which each requested a lot 
> of ports.  When doing so, the meson-master performance drops heavily.
> With 70 tasks each requesting 100 ports, the master seems to spend the 
> majority (~90%) of its time dealing with merging and coalescing Value_Range 
> objects.  
> I'll attach some text views of the output of 'perf' record/report from the 
> meson-master during this.  The call-graph trace for the most frequently 
> sampled call is:
> {code}
> -   4.42%  mesos-master  mesos-master [.] 
> google::protobuf::internal::RepeatedPtrFieldBase::size() const
>   
>   
>- google::protobuf::internal::RepeatedPtrFieldBase::size() const   
>   
>   
>   
>   - 37.05% mesos::Value_Ranges::range_size() const
>   
>   
>   
>  - 91.07% mesos::coalesce(mesos::Value_Ranges*, mesos::Value_Range 
> const&)   
>   
>  
> - mesos::coalesce(mesos::Value_Ranges*, mesos::Value_Ranges 
> const&)   
>   
> 
>- 68.35% mesos::operator+=(mesos::Value_Ranges&, 
> mesos::Value_Ranges const&)   
>   
> 
>   - 99.46% Option 
> mesos::Resources::get(std::string const&) const  
>   
>  
>  - mesos::internal::model(mesos::Resources const&)
>   
>   
>   
> - 97.58% mesos::internal::model(mesos::internal::Task 
> const&)   
>   
>   
>  
> mesos::internal::master::model(mesos::internal::master::Framework const&) 
>   
>   
>  
>  
> mesos::internal::master::Master::Http::state(process::http::Request const&) 
> const 
> 

[jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task

[Yan Xu (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950693#comment-14950693
 ] 

Yan Xu commented on MESOS-3688:
---

He's saying that in your task if you read MESOS_CONTAINER_NAME you'll get the 
container name. 

In fact, you specify a custom environment variable when you launch the task/app 
and it'll get passed to the task itself (and you can have your task log it, 
have it be the first line in your log, etc.), then you'll be able to grep this 
in the log.

Will this help?

> Get Container Name information when launching a container task
> --
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Affects Versions: 0.24.1
>Reporter: Raffaele Di Fazio
>  Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a 
> container task with mesos. The container name is generated by mesos itself 
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") 
> and it would be nice to expose this information to frameworks so that this 
> information can be used, for example by Marathon to give this information to 
> users via a REST API. 
> To go a bit in depth with our use case, we have files created by fluentd 
> logdriver that are named with Docker Name or Docker ID (full or short) and we 
> need a mapping for the users of the REST API and thus the first step is to 
> make this information available from mesos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3686) General cleanup of documentation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950352#comment-14950352
 ] 

ASF GitHub Bot commented on MESOS-3686:
---

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/70


> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3370) Deprecate the external containerizer

[Tom Arnfeld (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950394#comment-14950394
 ] 

Tom Arnfeld commented on MESOS-3370:


Thanks for the heads up [~adam-mesos], much appreciated indeed!

We still have one or two things using it, though that's mostly on us to update 
and deal with. I've no major objection to it being removed really... given that 
modules etc. have been in mesos for so long already.

The only thing that's to note is that the Hadoop on Mesos project still uses 
the old external container info format 
(https://github.com/mesos/hadoop/issues/49) but we need to update it anyway so 
this'll give us a kick to work on it.

> Deprecate the external containerizer
> 
>
> Key: MESOS-3370
> URL: https://issues.apache.org/jira/browse/MESOS-3370
> Project: Mesos
>  Issue Type: Task
>Reporter: Niklas Quarfot Nielsen
>
> To our knowledge, no one is using the external containerizer and we could 
> clean up code paths in the slave and containerizer interface (the dual 
> launch() signatures)
> In a deprecation cycle, we can move this code into a module (dependent on 
> containerizer modules landing) and from there, move it into it's own repo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3693) Port stout/os/open.hpp to Windows

[Alex Clemmer (JIRA)]

Alex Clemmer created MESOS-3693:
---

 Summary: Port stout/os/open.hpp to Windows
 Key: MESOS-3693
 URL: https://issues.apache.org/jira/browse/MESOS-3693
 Project: Mesos
  Issue Type: Task
  Components: stout
Reporter: Alex Clemmer
Assignee: Alex Clemmer






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3487) Running libprocess tests in a loop leads to unbounded memory growth.

[Neil Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950937#comment-14950937
 ] 

Neil Conway commented on MESOS-3487:


There have been a bunch of fixes recently to address file descriptor leaks, so 
make sure you're testing using the current master code.

> Running libprocess tests in a loop leads to unbounded memory growth.
> 
>
> Key: MESOS-3487
> URL: https://issues.apache.org/jira/browse/MESOS-3487
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Reporter: Benjamin Mahler
>Assignee: Diana Arroyo
>  Labels: newbie
>
> Was doing some repeat testing on a patch to check for flakiness and noticed 
> that the libprocess tests appear to have a leak that leads to unbounded 
> memory growth.
> I checked the stout tests as well, they appear ok.
> Notice the large RSS for the libprocess tests:
> {noformat}
>   PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
> 55133 root  20   0  479m 9.9m 6860 S 56.8  0.0   0:02.36 tests
> 16410 root  20   0  575m 152m 6864 S 60.1  0.2   6:09.70 tests
> 61363 root  20   0  606m 304m 6948 R 74.7  0.4  15:50.11 tests
> 32836 root  20   0  116m 9032 5580 S 88.3  0.0   3:46.32 stout-tests
> {noformat}
> Commands to reproduce:
> {noformat}
> $ sudo ./3rdparty/libprocess/tests --gtest_repeat=-1 --gtest_break_on_failure
> $ sudo ./3rdparty/libprocess/3rdparty/stout-tests --gtest_repeat=-1 
> --gtest_break_on_failure
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3614) Port slave/slave.cpp to Windows

[Alex Clemmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Clemmer updated MESOS-3614:

Description: 
Depends on pretty much all "porting" tasks in the slave component. COmplete 
those first.

And impartial dependency graph looks like this:

# async: dispatch, future, process
# address.hpp: *, ip.hpp, net.hpp
# check: future
# containerizer: future, process, fetcher, flags
# collect: future, defer, process
# defer.hpp: deferred.hpp, dispatch.hpp
# deferred.hpp: dispatch.hpp, pid.hpp
# delay.hpp: dispatch.hpp
# disk: flags, state, isolator
# dispatch.hpp: process.hpp
# executor.hpp: defer.hpp, deferred.hpp, process.hpp
# fetch.hpp: path.hpp
# fetcher: type_utils, future, process, subprocess
# flags.hpp: os.hpp, path.hpp, fetch.hpp
# fs: *
# future.hpp: pid.hpp
# isolator: process
# ip.hpp: *
# launch: subcommand
# launcher: isolator, future, usbprocess, flags
# monitor.hpp: future.hpp
# net.hpp: ip, networking stuff
# noop: resource_estimator
# path.hpp: *
# pid.hpp: address.hpp, ip.hpp
# process.hpp: *
# protobuf.hpp: *
# protobuf_utils: isolator, ip, uuid
# filesystem/posix: flags, isolator
# os.hpp: *
# reap: future
# resource_estimator: future
# state: type_utils, pid, os, path, protobuf, uuid
# subcommand: flags
# subprocess: os, future
# type_utils.hpp: uuid.hpp
# uuid.hpp: *

  was:Depends on pretty much all "porting" tasks in the slave component. 
COmplete those first.


> Port slave/slave.cpp to Windows
> ---
>
> Key: MESOS-3614
> URL: https://issues.apache.org/jira/browse/MESOS-3614
> Project: Mesos
>  Issue Type: Task
>  Components: slave
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
>  Labels: mesosphere, windows
>
> Depends on pretty much all "porting" tasks in the slave component. COmplete 
> those first.
> And impartial dependency graph looks like this:
> # async: dispatch, future, process
> # address.hpp: *, ip.hpp, net.hpp
> # check: future
> # containerizer: future, process, fetcher, flags
> # collect: future, defer, process
> # defer.hpp: deferred.hpp, dispatch.hpp
> # deferred.hpp: dispatch.hpp, pid.hpp
> # delay.hpp: dispatch.hpp
> # disk: flags, state, isolator
> # dispatch.hpp: process.hpp
> # executor.hpp: defer.hpp, deferred.hpp, process.hpp
> # fetch.hpp: path.hpp
> # fetcher: type_utils, future, process, subprocess
> # flags.hpp: os.hpp, path.hpp, fetch.hpp
> # fs: *
> # future.hpp: pid.hpp
> # isolator: process
> # ip.hpp: *
> # launch: subcommand
> # launcher: isolator, future, usbprocess, flags
> # monitor.hpp: future.hpp
> # net.hpp: ip, networking stuff
> # noop: resource_estimator
> # path.hpp: *
> # pid.hpp: address.hpp, ip.hpp
> # process.hpp: *
> # protobuf.hpp: *
> # protobuf_utils: isolator, ip, uuid
> # filesystem/posix: flags, isolator
> # os.hpp: *
> # reap: future
> # resource_estimator: future
> # state: type_utils, pid, os, path, protobuf, uuid
> # subcommand: flags
> # subprocess: os, future
> # type_utils.hpp: uuid.hpp
> # uuid.hpp: *



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3589) Mesos tasks with many ports cause significant master performance problems

[James Mulcahy (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951100#comment-14951100
 ] 

James Mulcahy commented on MESOS-3589:
--

As above, I've back ported the patch and the results are as follows:

Random Ports

~5.8-10.4s (results were: 10.4, 5.8, 8.3, 8.0)

Sequential Ports

~3.5-8.3s (results were: 6, 7.7, 8.3, 3.5)

In summary, the patch makes a huge improvement to the Value_Range handling.
Schedulers which randomize ports still see worse state.json fetch times, but 
it's no longer ~4x slower, it's closer to ~1.5x slower.

I'll leave it to the mesos team to judge whether this should be marked as 
fixed, or whether they want to keep it open to track the potential for further 
improvements here?


> Mesos tasks with many ports cause significant master performance problems
> -
>
> Key: MESOS-3589
> URL: https://issues.apache.org/jira/browse/MESOS-3589
> Project: Mesos
>  Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: James Mulcahy
> Attachments: mesos-master-perf-top-call-expanded.txt, 
> mesos-master-perf.txt
>
>
> Today, I used a framework to fire off some tasks which each requested a lot 
> of ports.  When doing so, the meson-master performance drops heavily.
> With 70 tasks each requesting 100 ports, the master seems to spend the 
> majority (~90%) of its time dealing with merging and coalescing Value_Range 
> objects.  
> I'll attach some text views of the output of 'perf' record/report from the 
> meson-master during this.  The call-graph trace for the most frequently 
> sampled call is:
> {code}
> -   4.42%  mesos-master  mesos-master [.] 
> google::protobuf::internal::RepeatedPtrFieldBase::size() const
>   
>   
>- google::protobuf::internal::RepeatedPtrFieldBase::size() const   
>   
>   
>   
>   - 37.05% mesos::Value_Ranges::range_size() const
>   
>   
>   
>  - 91.07% mesos::coalesce(mesos::Value_Ranges*, mesos::Value_Range 
> const&)   
>   
>  
> - mesos::coalesce(mesos::Value_Ranges*, mesos::Value_Ranges 
> const&)   
>   
> 
>- 68.35% mesos::operator+=(mesos::Value_Ranges&, 
> mesos::Value_Ranges const&)   
>   
> 
>   - 99.46% Option 
> mesos::Resources::get(std::string const&) const  
>   
>  
>  - mesos::internal::model(mesos::Resources const&)
>   
>   
>   
> - 97.58% mesos::internal::model(mesos::internal::Task 
> const&)   
>   
>   
>  
> mesos::internal::master::model(mesos::internal::master::Framework const&) 
>   
>   
>  
>  
> mesos::internal::master::Master::Http::state(process::http::Request const&) 
> const 
>   
>

[jira] [Issue Comment Deleted] (MESOS-3686) General cleanup of documentation

[Chris Elsmore (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Elsmore updated MESOS-3686:
-
Comment: was deleted

(was: This was addressed in https://github.com/apache/mesos/pull/70 )

> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3686) General cleanup of documentation

[Chris Elsmore (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950497#comment-14950497
 ] 

Chris Elsmore commented on MESOS-3686:
--

This was addressed in https://github.com/apache/mesos/pull/70 

> General cleanup of documentation
> 
>
> Key: MESOS-3686
> URL: https://issues.apache.org/jira/browse/MESOS-3686
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, general
>Reporter: Chris Elsmore
>  Labels: docuentation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Part of the MesosCon Europe 2015 Hackathon!
> Current documentation is inconsistent, and could do with a clean up:-
> * File names use a mix of hyphens and underscores,  some start with 'mesos' 
> some not.
> * A general clean up of broken links, and markdown tables etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3687) Streamline site-building process

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950531#comment-14950531
 ] 

ASF GitHub Bot commented on MESOS-3687:
---

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/72


> Streamline site-building process
> 
>
> Key: MESOS-3687
> URL: https://issues.apache.org/jira/browse/MESOS-3687
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> The current site building and publishing process is somewhat cumbersome and 
> complicated. As part of MesosCon Hackathon, aim to streamline/simplify this 
> process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3687) Streamline site-building process

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950541#comment-14950541
 ] 

ASF GitHub Bot commented on MESOS-3687:
---

GitHub user jonorossi opened a pull request:

https://github.com/apache/mesos/pull/73

Streamline site-building process for MESOS-3687

https://issues.apache.org/jira/browse/MESOS-3687

/cc @davelester

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fayusohenson/mesos site

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/73.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #73


commit cf547afffe6056025259e0a7843912df153befd4
Author: Jonathon Rossi 
Date:   2015-10-09T10:28:00Z

Remove task that clones the git repo

The site now builds out of the source code git repo so we are running
in it.

commit d2946c8590983fffd93af107438ae7f136f7b0d8
Author: Jonathon Rossi 
Date:   2015-10-09T12:08:36Z

Fix building site inside source repository

commit e1b92dc760d9b201be0e8ff4dfc759863841093e
Author: Jonathon Rossi 
Date:   2015-10-09T12:22:40Z

Restore removal of .DS_Store files

commit 260acd03b45c9a203a53bc92171aedadbb970dad
Author: Jonathon Rossi 
Date:   2015-10-09T13:25:23Z

Fix handling of images in docs so they actually work

commit 3c264c0929d328b1f8bedac3ad2fddadf782ec71
Author: Jonathon Rossi 
Date:   2015-10-09T13:32:55Z

Fix hardcoded image in docs

commit 37dfd1cb5ba3486693870b608aedaef313c4ad21
Author: Jonathon Rossi 
Date:   2015-10-09T14:29:03Z

Fix generating javadoc and doxygen for the web site




> Streamline site-building process
> 
>
> Key: MESOS-3687
> URL: https://issues.apache.org/jira/browse/MESOS-3687
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> The current site building and publishing process is somewhat cumbersome and 
> complicated. As part of MesosCon Hackathon, aim to streamline/simplify this 
> process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-191) Add support for disk spindles in resources

[David Greenberg (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950569#comment-14950569
 ] 

David Greenberg commented on MESOS-191:
---

Design Doc: 
https://docs.google.com/document/d/1syPxygVNEHjG6FoyqslnpUGgNpYKU9QzKBuV2yKmjfQ/edit?usp=sharing

> Add support for disk spindles in resources
> --
>
> Key: MESOS-191
> URL: https://issues.apache.org/jira/browse/MESOS-191
> Project: Mesos
>  Issue Type: Story
>Reporter: Vinod Kone
>
> It would be nice to schedule mesos tasks with fine-grained disk scheduling. 
> The idea is, a slave with multiple spindles, would specify spindle specific 
> config. Mesos would then include this info in its resource offers to 
> frameworks. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3691) apply-review.sh breaks author name for GitHub pull requests

[Jonathon Rossi (JIRA)]

Jonathon Rossi created MESOS-3691:
-

 Summary: apply-review.sh breaks author name for GitHub pull 
requests
 Key: MESOS-3691
 URL: https://issues.apache.org/jira/browse/MESOS-3691
 Project: Mesos
  Issue Type: Bug
Reporter: Jonathon Rossi
Priority: Minor


The author name gets replaced with just the last name:

See the following commit for an example:
https://github.com/apache/mesos/commit/145dc90b127a76dbc0ced914e9c46a537aae903c.patch



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3691) apply-review.sh breaks author name for GitHub pull requests

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950559#comment-14950559
 ] 

ASF GitHub Bot commented on MESOS-3691:
---

GitHub user jonorossi opened a pull request:

https://github.com/apache/mesos/pull/74

Fix apply-review.sh breaking author names for pull requests

https://issues.apache.org/jira/browse/MESOS-3691

/cc @davelester

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fayusohenson/mesos fix-apply-review

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/74.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #74


commit 0bd1225dc8243f14e49177fe408be05f1aca2829
Author: Jonathon Rossi 
Date:   2015-10-09T15:27:00Z

Fix apply-review.sh breaking author names for pull requests

MESOS-3691




> apply-review.sh breaks author name for GitHub pull requests
> ---
>
> Key: MESOS-3691
> URL: https://issues.apache.org/jira/browse/MESOS-3691
> Project: Mesos
>  Issue Type: Bug
>Reporter: Jonathon Rossi
>Priority: Minor
>
> The author name gets replaced with just the last name:
> See the following commit for an example:
> https://github.com/apache/mesos/commit/145dc90b127a76dbc0ced914e9c46a537aae903c.patch



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3691) apply-review.sh breaks author name for GitHub pull requests

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950560#comment-14950560
 ] 

ASF GitHub Bot commented on MESOS-3691:
---

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/74


> apply-review.sh breaks author name for GitHub pull requests
> ---
>
> Key: MESOS-3691
> URL: https://issues.apache.org/jira/browse/MESOS-3691
> Project: Mesos
>  Issue Type: Bug
>Reporter: Jonathon Rossi
>Priority: Minor
>
> The author name gets replaced with just the last name:
> See the following commit for an example:
> https://github.com/apache/mesos/commit/145dc90b127a76dbc0ced914e9c46a537aae903c.patch



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-3692) Clarify error message 'could not chown work directory'

[Frank Scholten (JIRA)]

Frank Scholten created MESOS-3692:
-

 Summary: Clarify error message 'could not chown work directory'
 Key: MESOS-3692
 URL: https://issues.apache.org/jira/browse/MESOS-3692
 Project: Mesos
  Issue Type: Documentation
  Components: documentation
Affects Versions: 0.25.0
Reporter: Frank Scholten
Priority: Minor


When deploying a framework I encountered the error message 'could not chown 
work directory'.

It took me a while to figure out that this happened because my framework was 
registered as a user on my host machine which did not exist on the Docker 
container and the agent was running as root.

I suggest to clarify this message by pointing out to either set 
{{--switch-user}}  to {{false}} or to run the framework as the same user as the 
agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3687) Streamline site-building process

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950564#comment-14950564
 ] 

ASF GitHub Bot commented on MESOS-3687:
---

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/73


> Streamline site-building process
> 
>
> Key: MESOS-3687
> URL: https://issues.apache.org/jira/browse/MESOS-3687
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Freddy Ayuso-Henson
>Priority: Minor
>
> The current site building and publishing process is somewhat cumbersome and 
> complicated. As part of MesosCon Hackathon, aim to streamline/simplify this 
> process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)