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

[Till Toenshoff (JIRA)]

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

Till Toenshoff commented on MESOS-3686:
---

This commit 
https://github.com/apache/mesos/commit/b29ec4f110483555a5e1a65ef25a7ecc13e31b7f 
is the source, it seems.

This is the fix: https://reviews.apache.org/r/41463/ 

> 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] [Commented] (MESOS-3686) General cleanup of documentation

[Till Toenshoff (JIRA)]

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

Till Toenshoff commented on MESOS-3686:
---

Seems we got duplicate documentation now.

https://github.com/apache/mesos/blob/master/docs/mesos-documentation-guide.md
https://github.com/apache/mesos/blob/master/docs/documentation-guide.md


> 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] [Assigned] (MESOS-4143) Reserve/UnReserve Dynamic Reservation Endpoints allow reservations on non-existing roles

[Neil Conway (JIRA)]

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

Neil Conway reassigned MESOS-4143:
--

Assignee: Neil Conway

> Reserve/UnReserve Dynamic Reservation Endpoints allow reservations on 
> non-existing roles
> 
>
> Key: MESOS-4143
> URL: https://issues.apache.org/jira/browse/MESOS-4143
> Project: Mesos
>  Issue Type: Bug
>  Components: general
>Affects Versions: 0.25.0, 0.26.0
>Reporter: John Omernik
>Assignee: Neil Conway
>
> When working with Dynamic reservations via the /reserve and /unreserve 
> endpoints, it is possible to reserve resources for roles that have not been 
> specified via the --roles flag on the master.  However, these roles are not 
> usable because the roles have not been defined, nor are they added to the 
> list of roles available. 
> Per the mailing list, changing roles after the fact is not possible at this 
> time. (That may be another JIRA), more importantly, the /reserve and 
> /unreserve end points should not allow reservation of roles not specified by 
> --roles.  



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

[jira] [Commented] (MESOS-4138) Document proposal for exclusive resources in Mesos

[Timothy Chen (JIRA)]

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

Timothy Chen commented on MESOS-4138:
-

The idea of exclusive resources is definitely needed! One question after 
reading the proposal is, how do we offer exclusive resources like cpusets? 
Clearly frameworks need to know the difference between shares and sets, but 
it's not specified in the proposal.

> Document proposal for exclusive resources in Mesos
> --
>
> Key: MESOS-4138
> URL: https://issues.apache.org/jira/browse/MESOS-4138
> Project: Mesos
>  Issue Type: Improvement
>  Components: isolation
>Reporter: Ian Downes
>
> Propose the concept of exclusivity to resources. An exclusive resource is a) 
> not shared with any other task, b) employs stronger isolation for more 
> predictable performance, and c) is consequently not oversubscribed (if 
> enabled). In contrast to normal resources, exclusive resources have greater 
> resource priority while oversubscribed resources have lower priority. 
> Initial resources that could support the notion of exclusivity include cpu, 
> network egress bandwidth, and IP addresses.
> Please see this 
> [document|https://docs.google.com/document/d/1Aby-U3-MPKE51s4aYd41L4Co2S97eM6LPtyzjyR_ecI/edit?usp=sharing].
>  All comments welcome!



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

[jira] [Updated] (MESOS-2980) Allow runtime configuration to be returned from provisioner

[Jie Yu (JIRA)]

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

Jie Yu updated MESOS-2980:
--
Shepherd: Jie Yu

> Allow runtime configuration to be returned from provisioner
> ---
>
> Key: MESOS-2980
> URL: https://issues.apache.org/jira/browse/MESOS-2980
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Timothy Chen
>Assignee: Gilbert Song
>  Labels: mesosphere
>
> Image specs also includes execution configuration (e.g: Env, user, ports, 
> etc).
> We should support passing those information from the image provisioner back 
> to the containerizer.



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

[jira] [Updated] (MESOS-4177) Create a user doc for Executor HTTP API

[Anand Mazumdar (JIRA)]

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

Anand Mazumdar updated MESOS-4177:
--
Sprint: Mesosphere Sprint 24

> Create a user doc for Executor HTTP API
> ---
>
> Key: MESOS-4177
> URL: https://issues.apache.org/jira/browse/MESOS-4177
> Project: Mesos
>  Issue Type: Bug
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
>  Labels: mesosphere
>
> We need a user doc similar to the corresponding one for the Scheduler HTTP 
> API.



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

[jira] [Updated] (MESOS-4184) Jenkins builds for Centos fail with missing 'which' utility and incorrect 'java.home'

[Kevin Klues (JIRA)]

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

Kevin Klues updated MESOS-4184:
---
Description: 
Jenkins builds are now consistently failing for centos 7, withe the failure:

checking value of Java system property 'java.home'...
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
configure: error: could not guess JAVA_HOME

They also fail early on during 'bootstrap' with a missing 'which' command.

The solution is to update support/docker_build.sh to install 'which' as well as 
make sure the proper versions of java are installed during the installation 
process.

The problem here is that we install maven BEFORE installing 
java-1.7.0-openjdk-devel, causing maven to pull in a dependency on 
java-1.8.0-openjdk. This causes problems with finding the proper java.home in 
our mesos/configure script because of the mismatch between the most up to date 
jre (1.8.0) and the most up to date development tools (1.7.0).  We can either 
update the script to pull in the 1.8 devel tools or move our dependence on 
maven until AFTER our installation of java-1.7.0-openjdk-devel.  Unclear what 
the best solution is.

  was:
Jenkins builds are now consistently failing for centos 7, withe the failure:

checking value of Java system property 'java.home'...
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
configure: error: could not guess JAVA_HOME

They also fail early on during 'bootstrap' with a missing 'which' command.

The solution is to update support/docker_build.sh to install 'which' as well as 
make sure the proper versions of java are installed during the installation 
process.

The problem here is that This is that we install maven
BEFORE installing java-1.7.0-openjdk-devel, causing maven to pull in a 
dependency on java-1.8.0-openjdk. This causes problems with finding the proper 
java.home in our mesos/configure script because of the mismatch between the 
most up to date jre (1.8.0) and the most up to date development tools (1.7.0).  
We can either update the script to pull in the 1.8 devel tools or move our 
dependence on maven until AFTER our installation of java-1.7.0-openjdk-devel.  
Unclear what the best solution is.


> Jenkins builds for Centos fail with missing 'which' utility and incorrect 
> 'java.home'
> -
>
> Key: MESOS-4184
> URL: https://issues.apache.org/jira/browse/MESOS-4184
> Project: Mesos
>  Issue Type: Bug
>  Components: jenkins
> Environment: centos 7
>Reporter: Kevin Klues
>Assignee: Kevin Klues
>
> Jenkins builds are now consistently failing for centos 7, withe the failure:
> checking value of Java system property 'java.home'...
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
> configure: error: could not guess JAVA_HOME
> They also fail early on during 'bootstrap' with a missing 'which' command.
> The solution is to update support/docker_build.sh to install 'which' as well 
> as make sure the proper versions of java are installed during the 
> installation process.
> The problem here is that we install maven BEFORE installing 
> java-1.7.0-openjdk-devel, causing maven to pull in a dependency on 
> java-1.8.0-openjdk. This causes problems with finding the proper java.home in 
> our mesos/configure script because of the mismatch between the most up to 
> date jre (1.8.0) and the most up to date development tools (1.7.0).  We can 
> either update the script to pull in the 1.8 devel tools or move our 
> dependence on maven until AFTER our installation of java-1.7.0-openjdk-devel. 
>  Unclear what the best solution is.



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

[jira] [Assigned] (MESOS-3742) Site needs to get updated as it still lists MesosCon Europe as an upcoming event

[Till Toenshoff (JIRA)]

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

Till Toenshoff reassigned MESOS-3742:
-

Assignee: Till Toenshoff

> Site needs to get updated as it still lists MesosCon Europe as an upcoming 
> event
> 
>
> Key: MESOS-3742
> URL: https://issues.apache.org/jira/browse/MESOS-3742
> Project: Mesos
>  Issue Type: Bug
>  Components: project website
>Reporter: Till Toenshoff
>Assignee: Till Toenshoff
>
> The Apache website does need to get updated as it still lists MesosCon Europe 
> as an upcoming event
> Even the registration page 
> (http://events.linuxfoundation.org/events/mesoscon-europe/attend/register) 
> still seems to accept registrations - something we might want to get fixed 
> upstream.



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

[jira] [Updated] (MESOS-4143) Reserve/UnReserve Dynamic Reservation Endpoints allow reservations on non-existing roles

[Anand Mazumdar (JIRA)]

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

Anand Mazumdar updated MESOS-4143:
--
  Sprint: Mesosphere Sprint 24
Story Points: 2
Target Version/s: 0.27.0
  Labels: mesosphere reservations  (was: )

> Reserve/UnReserve Dynamic Reservation Endpoints allow reservations on 
> non-existing roles
> 
>
> Key: MESOS-4143
> URL: https://issues.apache.org/jira/browse/MESOS-4143
> Project: Mesos
>  Issue Type: Bug
>  Components: general
>Affects Versions: 0.25.0, 0.26.0
>Reporter: John Omernik
>Assignee: Neil Conway
>  Labels: mesosphere, reservations
>
> When working with Dynamic reservations via the /reserve and /unreserve 
> endpoints, it is possible to reserve resources for roles that have not been 
> specified via the --roles flag on the master.  However, these roles are not 
> usable because the roles have not been defined, nor are they added to the 
> list of roles available. 
> Per the mailing list, changing roles after the fact is not possible at this 
> time. (That may be another JIRA), more importantly, the /reserve and 
> /unreserve end points should not allow reservation of roles not specified by 
> --roles.  



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

[jira] [Created] (MESOS-4184) Jenkins builds for Centos fail with missing 'which' utility and incorrect 'java.home'

[Kevin Klues (JIRA)]

Kevin Klues created MESOS-4184:
--

 Summary: Jenkins builds for Centos fail with missing 'which' 
utility and incorrect 'java.home'
 Key: MESOS-4184
 URL: https://issues.apache.org/jira/browse/MESOS-4184
 Project: Mesos
  Issue Type: Bug
  Components: jenkins
 Environment: centos 7
Reporter: Kevin Klues
Assignee: Kevin Klues


Jenkins builds are now consistently failing for centos 7, withe the failure:

checking value of Java system property 'java.home'...
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
configure: error: could not guess JAVA_HOME

They also fail early on during 'bootstrap' with a missing 'which' command.

The solution is to update support/docker_build.sh to install 'which' as well as 
make sure the proper versions of java are installed during the installation 
process.

The problem here is that This is that we install maven
BEFORE installing java-1.7.0-openjdk-devel, causing maven to pull in a 
dependency on java-1.8.0-openjdk. This causes problems with finding the proper 
java.home in our mesos/configure script because of the mismatch between the 
most up to date jre (1.8.0) and the most up to date development tools (1.7.0).  
We can either update the script to pull in the 1.8 devel tools or move our 
dependence on maven until AFTER our installation of java-1.7.0-openjdk-devel.  
Unclear what the best solution is.



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

[jira] [Updated] (MESOS-3844) getting started documentation has flaws, corrections suggested (http://mesos.apache.org/gettingstarted/)

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-3844:
--
Shepherd: Till Toenshoff  (was: Benjamin Hindman)

> getting started documentation has flaws, corrections suggested 
> (http://mesos.apache.org/gettingstarted/)
> 
>
> Key: MESOS-3844
> URL: https://issues.apache.org/jira/browse/MESOS-3844
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, project website, test
>Affects Versions: 0.25.0
> Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 
> (x86_64) with Updates HVM (a t2.medium instance)
>Reporter: Manne Laukkanen
>Assignee: Kevin Klues
>Priority: Trivial
>  Labels: build, documentation, mesosphere
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Getting started documentation, while having great virtues, has room for 
> improvement:
> 1) Documentation is illogical and wrong for this part:
>  " $ wget http://www.apache.org/dist/mesos/0.25.0/mesos-0.25.0.tar.gz
>  $ tar -zxf mesos-0.25.0.tar.gz" ...then, later:
> "# Install a few utility tools
> $ sudo yum install -y tar wget
> ..obviously using tar and wget is not possible before installing them.
> 2) Although vi is fine for many, utility tools having:
> sudo yum install -y tar wget nano
> might make editing e.g. the WANDISCO -repo file way easier for newbies.
> 3) Advice to launch Mesos with localhost option ( " ./bin/mesos-master.sh 
> --ip=127.0.0.1 --work_dir=/var/lib/mesos " ) will lead into a state where 
> Mesos UI can not be reached in port :5050 in a production environment e.g. in 
> AWS EC2. Mentioning this would help, not hinder deployment.



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

[jira] [Updated] (MESOS-4118) Update Getting Started for Mac OS X El Capitan

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-4118:
--
Shepherd: Till Toenshoff

> Update Getting Started for Mac OS X El Capitan
> --
>
> Key: MESOS-4118
> URL: https://issues.apache.org/jira/browse/MESOS-4118
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
> Environment: Mac OS X
>Reporter: Kevin Klues
>Assignee: Kevin Klues
>Priority: Minor
>  Labels: documentation, mesosphere
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> This ticket pertains to the Getting Started guide on the apache mesos website
> The current instructions for installing on Mac OS X only include instructions 
> for Yosemite.  The instructions to build for El Capitan are identical except 
> in the case of upgrading from Yosemite to El Capitan.  To build after an 
> upgrade requires a trivial (but important) step which is non-obvious -- you 
> have to rerun 'xcode-select --install' after you complete the upgrade.
> Let's change the heading for installing on Mac OS X to say:
> Mac OS X Yosemite & El Capitan
> and then add a comment at the bottom of the section to point out that a rerun 
> of 'xcode-select --install' is necessary after an upgrade from Yosemite to El 
> Capitan.



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

[jira] [Updated] (MESOS-4134) Add note about tunneling in site-docker README

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-4134:
--
Shepherd: Till Toenshoff

> Add note about tunneling in site-docker README
> --
>
> Key: MESOS-4134
> URL: https://issues.apache.org/jira/browse/MESOS-4134
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Kevin Klues
>Assignee: Kevin Klues
>Priority: Minor
>  Labels: documentation
>
> If we are running the site-docker container on a remote machine, we should 
> set up a tunnel to localhost to view the site locally.  The README should 
> explain how to do so.



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

[jira] [Updated] (MESOS-3954) The documentation should recommend an updated systemd for centos 7.

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-3954:
--
Shepherd: Till Toenshoff  (was: Benjamin Hindman)

> The documentation should recommend an updated systemd for centos 7.
> ---
>
> Key: MESOS-3954
> URL: https://issues.apache.org/jira/browse/MESOS-3954
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Till Toenshoff
>Assignee: Kevin Klues
>Priority: Minor
>  Labels: documentation, mesosphere
>
> After installing a plain centos 7, some Mesos tests kept failing due to 
> MESOS-3352.
> We should try to minimize such experience for our users by e.g. adding the 
> need for an explicit systemd update on this distribution (and maybe others).



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

[jira] [Updated] (MESOS-3842) getting started documentation following Mesos 0.25 build fails for CentOS7 (http://mesos.apache.org/gettingstarted/)

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-3842:
--
Shepherd: Till Toenshoff  (was: Benjamin Hindman)

> getting started documentation following Mesos 0.25 build fails for CentOS7 
> (http://mesos.apache.org/gettingstarted/)
> 
>
> Key: MESOS-3842
> URL: https://issues.apache.org/jira/browse/MESOS-3842
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, project website
>Affects Versions: 0.25.0
> Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 
> (x86_64) with Updates HVM (a t2.medium instance)
>Reporter: Manne Laukkanen
>Assignee: Kevin Klues
>  Labels: build, documentation, mesosphere
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> WANdisco SVN repo file usage leads to failure of build process with error, so 
> usage of it should be 1) discouraged 2) replaced with a working solution
> Proceeding according to documentation at 
> http://mesos.apache.org/gettingstarted/:
> # 'Mesos > 0.21.0' requires 'subversion > 1.8' devel package, which is
> # not available in the default repositories.
> # Add the WANdisco SVN repo file: '/etc/yum.repos.d/wandisco-svn.repo' with 
> content:
>   [WANdiscoSVN]
>   name=WANdisco SVN Repo 1.9
>   enabled=1
>   baseurl=http://opensource.wandisco.com/centos/7/svn-1.9/RPMS/$basearch/
>   gpgcheck=1
>   gpgkey=http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco
> ...we do as is described, then proceed to next step, which is 
> "# Install essential development tools."
> sudo yum groupinstall -y "Development Tools"
> ...the added WANDISCO -repo causes failed building process with error:
> Error: Package: subversion-1.9.2-1.x86_64 (WANdiscoSVN)
>Requires: libserf-1.so.0()(64bit)
>  - we end up with e.g. no build tools to proceed with, so process fails, 
> Mesos can not be built according to instructions (e.g. no C-compiler in 
> path...)
> Interestingly, building with aforementioned instructions (with some 
> modifications mentioned in ticket MESOS-3844) was successful without errors 
> justa a few days ago on 30 Oct 2015. WANDISCO repo breakage? 
> No changes to building machine image (the CentOS7 image) nor machine itself 
> (t2.medium EC2 instance) were made in between attempts.



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

[jira] [Updated] (MESOS-4072) The lt-mesos-master will coredump in some situation.

[Neil Conway (JIRA)]

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

Neil Conway updated MESOS-4072:
---
Fix Version/s: 0.27.0

> The lt-mesos-master will coredump in some situation.
> 
>
> Key: MESOS-4072
> URL: https://issues.apache.org/jira/browse/MESOS-4072
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Affects Versions: 0.25.0
>Reporter: Nan Xiao
>Assignee: Neil Conway
>  Labels: mesosphere, newbie
> Fix For: 0.27.0
>
>
>  I find  lt-mesos-master  will coredump when following conditions are met:  
> (1) The user doesn't have write permission of /var/lib/mesos directory:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/
> total 176
> dr-xr-xr-x 2 rootroot4096 Dec  7 03:08 mesos
> ..
> (2) the /var/lib/mesos is an empty folder:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/mesos/
> total 0
> Executing following command will core dump:
> nan@ubuntu:~/mesos-0.25.0/build$ ./bin/mesos-master.sh --ip=16.187.250.141 
> --work_dir=/var/lib/mesos
> I1207 03:18:36.431015 22951 main.cpp:229] Build: 2015-12-07 00:11:18 by nan
> I1207 03:18:36.431154 22951 main.cpp:231] Version: 0.25.0
> I1207 03:18:36.431388 22951 main.cpp:252] Using 'HierarchicalDRF' allocator
> F1207 03:18:36.431807 22951 replica.cpp:724] CHECK_SOME(state): IO error: 
> /var/lib/mesos/replicated_log/LOCK: No such file or directory Failed to 
> recover the log
> *** Check failure stack trace: ***
> @ 0x7f076bc208ca  google::LogMessage::Fail()
> @ 0x7f076bc20816  google::LogMessage::SendToLog()
> @ 0x7f076bc20218  google::LogMessage::Flush()
> @ 0x7f076bc2312c  google::LogMessageFatal::~LogMessageFatal()
> @ 0x7f076adf8f30  _CheckFatal::~_CheckFatal()
> @ 0x7f076baa4939  mesos::internal::log::ReplicaProcess::restore()
> @ 0x7f076baa0f8c  
> mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0x7f076baa4c95  mesos::internal::log::Replica::Replica()
> @ 0x7f076b9cf819  mesos::internal::log::LogProcess::LogProcess()
> @ 0x7f076b9d576c  mesos::internal::log::Log::Log()
> @   0x46d21f  main
> @ 0x7f0766f69ec5  (unknown)
> @   0x46b979  (unknown)
> Aborted (core dumped)
> Use gdb to analyze it:
> nan@ubuntu:~/mesos-0.25.0/build$ gdb 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master core
> GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master...done.
> [New LWP 22065]
> [New LWP 22087]
> [New LWP 22085]
> [New LWP 22089]
> [New LWP 22084]
> [New LWP 22086]
> [New LWP 22091]
> [New LWP 22088]
> [New LWP 22092]
> [New LWP 22090]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master 
> --ip=127.0.0.1 --work_di'.
> Program terminated with signal SIGABRT, Aborted.
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> 56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> Traceback (most recent call last):
>   File 
> "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py",
>  line 63, in 
> from libstdcxx.v6.printers import register_libstdcxx_printers
> ImportError: No module named 'libstdcxx'
> (gdb) bt
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x7fe9178140d8 in __GI_abort () at abort.c:89
> #2  0x7fe91c4b8c1b in DumpStackTraceAndExit () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #3  0x7fe91c4b28ca in google::LogMessage::Fail () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #4  0x7fe91c4b2816 in google::LogMessage::SendToLog () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #5  0x7fe91c4b2218 in google::LogMessage::Flush () from 
> 

[jira] [Updated] (MESOS-3305) Getting Started docs for Ubuntu needs reference to libsasl2-modules

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-3305:
--
Shepherd: Till Toenshoff  (was: Bernd Mathiske)

> Getting Started docs for Ubuntu needs reference to libsasl2-modules
> ---
>
> Key: MESOS-3305
> URL: https://issues.apache.org/jira/browse/MESOS-3305
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Affects Versions: 0.23.0
> Environment: Ubuntu 14.04
>Reporter: Andrew A Smith
>Assignee: Kevin Klues
>Priority: Minor
>  Labels: documentation, mesosphere, newbie
>
> Following the Getting Started docs leads to an error during configure, due to 
> a missing dependency.
> Error during configure:
> checking SASL CRAM-MD5 support... configure: error: no
> ---
> We need CRAM-MD5 support for SASL authentication.
> ---



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

[jira] [Updated] (MESOS-2209) Mesos should not use negative exit codes

[Neil Conway (JIRA)]

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

Neil Conway updated MESOS-2209:
---
Fix Version/s: 0.27.0

> Mesos should not use negative exit codes
> 
>
> Key: MESOS-2209
> URL: https://issues.apache.org/jira/browse/MESOS-2209
> Project: Mesos
>  Issue Type: Bug
>  Components: slave
>Affects Versions: 0.21.0
>Reporter: Steven Schlansker
>Priority: Minor
> Fix For: 0.27.0
>
>
> POSIX restricts exit codes to an unsigned 8 bit integer.
> Mesos has a number of places where it exits with status -1. outside that 
> range.  With some shells (notably dash, which is /bin/sh on Debian based 
> systems) this causes an error:
> {code}
> /bin/sh: 1: exit: Illegal number: -1
> {code}
> An example of where this is done is in exec.cpp
> {code}
>   void kill()
>   {
> VLOG(1) << "Committing suicide by killing the process group";
> // TODO(vinod): Invoke killtree without killing ourselves.
> // Kill the process group (including ourself).
> killpg(0, SIGKILL);
> // The signal might not get delivered immediately, so sleep for a
> // few seconds. Worst case scenario, exit abnormally.
> os::sleep(Seconds(5));
> exit(-1);
>   }
> {code}
> The code needs to be audited to always return valid exit codes.



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

[jira] [Created] (MESOS-4187) Avoid using absolute URLs in documentation pages

[Neil Conway (JIRA)]

Neil Conway created MESOS-4187:
--

 Summary: Avoid using absolute URLs in documentation pages
 Key: MESOS-4187
 URL: https://issues.apache.org/jira/browse/MESOS-4187
 Project: Mesos
  Issue Type: Documentation
Reporter: Neil Conway
Assignee: Neil Conway
Priority: Minor


Links from one documentation page to another should not use absolute URLs 
(e.g., {{http://mesos.apache.org/documentation/latest/...}}) for several good 
reasons. For instance, absolute URLs break when the docs are 
generated/previewed locally.



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

[jira] [Commented] (MESOS-4184) Jenkins builds for Centos fail with missing 'which' utility and incorrect 'java.home'

[Kevin Klues (JIRA)]

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

Kevin Klues commented on MESOS-4184:


https://reviews.apache.org/r/41475/

> Jenkins builds for Centos fail with missing 'which' utility and incorrect 
> 'java.home'
> -
>
> Key: MESOS-4184
> URL: https://issues.apache.org/jira/browse/MESOS-4184
> Project: Mesos
>  Issue Type: Bug
>  Components: jenkins
> Environment: centos 7
>Reporter: Kevin Klues
>Assignee: Kevin Klues
>
> Jenkins builds are now consistently failing for centos 7, withe the failure:
> checking value of Java system property 'java.home'...
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
> configure: error: could not guess JAVA_HOME
> They also fail early on during 'bootstrap' with a missing 'which' command.
> The solution is to update support/docker_build.sh to install 'which' as well 
> as make sure the proper versions of java are installed during the 
> installation process.
> The problem here is that we install maven BEFORE installing 
> java-1.7.0-openjdk-devel, causing maven to pull in a dependency on 
> java-1.8.0-openjdk. This causes problems with finding the proper java.home in 
> our mesos/configure script because of the mismatch between the most up to 
> date jre (1.8.0) and the most up to date development tools (1.7.0).  We can 
> either update the script to pull in the 1.8 devel tools or move our 
> dependence on maven until AFTER our installation of java-1.7.0-openjdk-devel. 
>  Unclear what the best solution is.



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

[jira] [Created] (MESOS-4185) Revisit the "System Requirements" for all systems in the "Getting Started" guide

[Kevin Klues (JIRA)]

Kevin Klues created MESOS-4185:
--

 Summary: Revisit the "System Requirements" for all systems in the 
"Getting Started" guide
 Key: MESOS-4185
 URL: https://issues.apache.org/jira/browse/MESOS-4185
 Project: Mesos
  Issue Type: Documentation
Reporter: Kevin Klues
Assignee: Kevin Klues
Priority: Minor


The "System Requirements" section of our "Getting Started" guide needs an 
overhaul.  Much of the information is outdated, and could likely be distilled 
down to a simpler set of dependencies (especially for Centos 6.6 and Centos 
7.1).  We should take a good hard look at these and see if all of the 
dependencies listed are necessary anymore.



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

[jira] [Updated] (MESOS-4125) Use 'git rev-parse --git-dir' instead of assuming '.git' in top dir

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-4125:
--
Shepherd: Till Toenshoff

> Use 'git rev-parse --git-dir' instead of assuming '.git' in top dir
> ---
>
> Key: MESOS-4125
> URL: https://issues.apache.org/jira/browse/MESOS-4125
> Project: Mesos
>  Issue Type: Improvement
>  Components: build
> Environment: All systems
>Reporter: Kevin Klues
>Assignee: Kevin Klues
>Priority: Minor
>  Labels: bootstrap, build, mesosphere
>
> This issue relates to files where we assume that mesos's '.git' folder is 
> always located in the top level directory of the mesos tree.
> For example, bootstrap makes this assumption.  Specifically, it attempts to 
> install pre-commit and post-rewrite hooks into the hardcoded .git/hooks 
> directory. However, it is not always true that the .git folder is located 
> here.
> Most notably, it is not true if the mesos tree is included as a submodule 
> inside another project. When included as a submodule, .git is no longer a 
> directory, but rather a file whose text contains a pointer back to the actual 
> location of the .git folder inside the containing project.  To get at this 
> directory, we need to run 'git rev-parse --git-dir' instead of simply 
> assuming that the local .git is the proper directory.



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

[jira] [Updated] (MESOS-4187) Avoid using absolute URLs in documentation pages

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-4187:
--
Shepherd: Till Toenshoff

> Avoid using absolute URLs in documentation pages
> 
>
> Key: MESOS-4187
> URL: https://issues.apache.org/jira/browse/MESOS-4187
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Neil Conway
>Assignee: Neil Conway
>Priority: Minor
>  Labels: documentation, mesosphere
>
> Links from one documentation page to another should not use absolute URLs 
> (e.g., {{http://mesos.apache.org/documentation/latest/...}}) for several good 
> reasons. For instance, absolute URLs break when the docs are 
> generated/previewed locally.



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

[jira] [Updated] (MESOS-4180) Add flags to update summary and description in updated patches for review.

[Till Toenshoff (JIRA)]

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

Till Toenshoff updated MESOS-4180:
--
Shepherd: Till Toenshoff

> Add flags to update summary and description in updated patches for review.
> --
>
> Key: MESOS-4180
> URL: https://issues.apache.org/jira/browse/MESOS-4180
> Project: Mesos
>  Issue Type: Improvement
>  Components: general
>Reporter: Kevin Klues
>Assignee: Kevin Klues
>Priority: Minor
>  Labels: reviewboard
>
> If you amend a commit message and post it to reviewboard via the 
> support/post_reviews.py script, then the summary / description on reviewboard 
> does not get updated between subsequent revisions. The only way to update 
> these is to modify them directly on the webpage. However, with a simple 
> directive in the .reviewboardrc file we can force the review's summary / 
> description to be updated to the text in the commit message.



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

[jira] [Created] (MESOS-4186) Serialize docker v1 image spec as protobuf

[Gilbert Song (JIRA)]

Gilbert Song created MESOS-4186:
---

 Summary: Serialize docker v1 image spec as protobuf
 Key: MESOS-4186
 URL: https://issues.apache.org/jira/browse/MESOS-4186
 Project: Mesos
  Issue Type: Improvement
  Components: containerization
Reporter: Gilbert Song
Assignee: Gilbert Song






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

[jira] [Updated] (MESOS-3896) Add accounting for reservation slack in the allocator.

[Klaus Ma (JIRA)]

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

Klaus Ma updated MESOS-3896:

Description: 
MESOS-XXX: Optimsistic accounter

{code}
class HierarchicalAllocatorProcess 
{
  struct Slave
  {
...
struct Optimistic 
{
  Resources total; // The total allocation slack resources
  Resources allocated; // The allocated allocation slack resources
};

Optimistic optimistic;
  };
}
{code}

MESOS-4146: flatten & allocationSlack for Optimistic Offer

{code}
class Resources
{
// Returns a Resources object with the same amount of each resource
// type as these Resources, but with all Resource objects marked as
// the specified `RevocableInfo::Type`; the other attribute is not
// affected.
Resources flatten(Resource::RevocableInfo::Type type);

// Return a Resources object that:
//   - if role is given, the resources did not include role's reserved
// resources.
//   - the resources's revocable type is `ALLOCATION_SLACK`
//   - the role of resources is set to "*"
Resources allocationSlack(Option role = None());
}
{code}

MESOS-XXX: Allocate the allocation_slack resources to framework

{code}
void HierarchicalAllocatorProcess::allocate(
const hashset& slaveIds_)
{
  foreach slave; foreach role; foreach framework
  {
Resource optimistic;

if (framework.revocable) {
  Resources total = 
slaves[slaveId].optimistic.total.allocationSlack(role);
  optimistic = total - slaves[slaveId].optimistic.allocated;
}

...
offerable[frameworkId][slaveId] += resources + optimistic;

...
slaves[slaveId].optimistic.allocated += optimistic;
  }
}
{code}
  
Here's some consideration about `ALLOCATION_SLACK`:

1. 'Old' resources (available/total) did not include ALLOCATION_SLACK
2. After `Quota`, `remainingClusterResources.contains` should not check 
ALLOCATION_SLACK; if there no enough resources,  master can still offer 
ALLOCATION_SALCK resources.
3. In sorter, it'll not include ALLOCATION_SLACK; as those resources are 
borrowed from other role/framework
4. If either normal resources or ALLOCATION_SLACK resources are 
allocable/!filtered, it can be offered to framework
5. Currently, allocator will assign all ALLOCATION_SALCK resources in slave to 
one framework

MESOS-XXX: Update ALLOCATION_SLACK for dynamic reservation (updateAllocation)

{code}
void HierarchicalAllocatorProcess::updateAllocation(
const FrameworkID& frameworkId,
const SlaveID& slaveId,
const vector& operations)
{
...
Try updatedOptimistic =
slaves[slaveId].optimistic.total.apply(operations);
CHECK_SOME(updatedTotal);

slaves[slaveId].optimistic.total =

updatedOptimistic.get().stateless().reserved().flatten(ALLOCATION_SLACK);
...
}
{code}

MESOS-XXX: Add ALLOCATION_SLACK when slaver register/re-register (addSlave)

{code}
void HierarchicalAllocatorProcess::addSlave(
const SlaveID& slaveId,
const SlaveInfo& slaveInfo,
const Option& unavailability,
const Resources& total,
const hashmap& used)
{
  ...
  slaves[slaveId].optimistic.total =
  total.stateless().reserved().flatten(ALLOCATION_SLACK);
  ...
}
{code}
  
No need to handle `removeSlave`, it'll all related info from `slaves` including 
`optimistic`.

MESOS-XXX: return resources to allocator (recoverResources)

{code}
void HierarchicalAllocatorProcess::recoverResources(
const FrameworkID& frameworkId,
const SlaveID& slaveId,
const Resources& resources,
const Option& filters)
{
  if (slaves.contains(slaveId))
  {
...
slaves[slaveId].optimistic.allocated -= resources.allocationSlack();
...
  }
}
{code}

> Add accounting for reservation slack in the allocator.
> --
>
> Key: MESOS-3896
> URL: https://issues.apache.org/jira/browse/MESOS-3896
> Project: Mesos
>  Issue Type: Bug
>Reporter: Artem Harutyunyan
>Assignee: Klaus Ma
>  Labels: mesosphere
>
> MESOS-XXX: Optimsistic accounter
> {code}
> class HierarchicalAllocatorProcess 
> {
>   struct Slave
>   {
> ...
> struct Optimistic 
> {
>   Resources total; // The total allocation slack resources
>   Resources allocated; // The allocated allocation slack resources
> };
> 
> Optimistic optimistic;
>   };
> }
> {code}
> MESOS-4146: flatten & allocationSlack for Optimistic Offer
> {code}
>  

[jira] [Commented] (MESOS-3891) Add a helper function to the Agent to check available resources before launching a task.

[Guangya Liu (JIRA)]

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

Guangya Liu commented on MESOS-3891:



Adding a queue to slave to queue all of the tasks related to allocation slack. 
The reason that we need this queue is because the task launch related with the 
allocation slack may trigger executor eviction and the eviction may take some 
time. Adding a queue here can make sure other tasks without allocation slack 
will not be delayed when the previous tasks related with allocation slack are 
evicting tasks.

Adding a queue can also help resolve the race condition issue: All of the tasks 
in the queue will be handled with FCFS policy.

{code}
_runTask() {
  ...
  if (!Resources(task.resources()).allocSlackRevocable().empty()) {
 // Put task to pending queue.
  }
 
 if (!Resources(task.resources()).stateless().reserved.empty()) {
 // Put task to pending queue.
  }
  ...
  // Handle other tasks.
}
{code}

> Add a helper function to the Agent to check available resources before 
> launching a task. 
> -
>
> Key: MESOS-3891
> URL: https://issues.apache.org/jira/browse/MESOS-3891
> Project: Mesos
>  Issue Type: Bug
>Reporter: Artem Harutyunyan
>Assignee: Guangya Liu
>  Labels: mesosphere
>
> Launching a task using revocable resources should be funnelled through an 
> accounting system:
> * If a task is launched using revocable resources, the resources must not be 
> in use when launching the task.  If they are in use, then the task should 
> fail to start.
> * If a task is launched using reserved resources, the resources must be made 
> available.  This means potentially evicting tasks which are using revocable 
> resources.
> Both cases could be implemented by adding a check in Slave::runTask, like a 
> new helper method:
> {noformat}
> class Slave {
>   ...
>   // Checks if the given resources are available (i.e. not utilized)
>   // for starting a task.  If not, the task should either fail to
>   // start or result in the eviction of revocable resources.
>   virtual process::Future checkAvailableResources(
>   const Resources& resources);
>   ...
> }
> {noformat}



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

[jira] [Created] (MESOS-4183) Move operator<< definitions to .cpp files and include in .hpp where possible

[Alexander Rukletsov (JIRA)]

Alexander Rukletsov created MESOS-4183:
--

 Summary: Move operator<< definitions to .cpp files and include 
 in .hpp where possible
 Key: MESOS-4183
 URL: https://issues.apache.org/jira/browse/MESOS-4183
 Project: Mesos
  Issue Type: Improvement
  Components: build
Reporter: Alexander Rukletsov
Assignee: Alexander Rukletsov
Priority: Minor


We often include complex headers like {{}} in ".hpp" files to define 
{{operator<<()}} inline (e.g. "mesos/authorizer/authorizer.hpp"). Instead, we 
can move definitions to corresponding ".cpp" files and replace stream headers 
with {{iosfwd}}, for example, this is partially done for {{URI}} in 
"mesos/uri/uri.hpp".



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

[jira] [Updated] (MESOS-4183) Move operator<< definitions to .cpp files and include in .hpp where possible

[Alexander Rukletsov (JIRA)]

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

Alexander Rukletsov updated MESOS-4183:
---
Shepherd: Michael Park

> Move operator<< definitions to .cpp files and include  in .hpp where 
> possible
> -
>
> Key: MESOS-4183
> URL: https://issues.apache.org/jira/browse/MESOS-4183
> Project: Mesos
>  Issue Type: Improvement
>  Components: build
>Reporter: Alexander Rukletsov
>Assignee: Alexander Rukletsov
>Priority: Minor
>  Labels: mesosphere
>
> We often include complex headers like {{}} in ".hpp" files to define 
> {{operator<<()}} inline (e.g. "mesos/authorizer/authorizer.hpp"). Instead, we 
> can move definitions to corresponding ".cpp" files and replace stream headers 
> with {{iosfwd}}, for example, this is partially done for {{URI}} in 
> "mesos/uri/uri.hpp".



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

[jira] [Commented] (MESOS-3153) Add tests for HTTPS SSL socket communication

[Joseph Wu (JIRA)]

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

Joseph Wu commented on MESOS-3153:
--

We probably want some of these tests (in libprocess) at some point.  But this 
may be blocked by [MESOS-3820] (unless you want to re-write the client/server 
logic in the tests).

> Add tests for HTTPS SSL socket communication
> 
>
> Key: MESOS-3153
> URL: https://issues.apache.org/jira/browse/MESOS-3153
> Project: Mesos
>  Issue Type: Bug
>Reporter: Jojy Varghese
>Assignee: Jojy Varghese
>Priority: Minor
>  Labels: mesosphere
>
> Unit tests are lacking for the following cases:
> 1. HTTPS Post with "None" payload. 
> 2. Verification of HTTPS payload on the SSL socket(maybe decode to a Request 
> object)
> 3. http -> ssl socket
> 4. https -> raw socket.



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

[jira] [Commented] (MESOS-4130) Document how the fetcher can reach across a proxy connection.

[Shuai Lin (JIRA)]

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

Shuai Lin commented on MESOS-4130:
--

https://reviews.apache.org/r/41438

> Document how the fetcher can reach across a proxy connection.
> -
>
> Key: MESOS-4130
> URL: https://issues.apache.org/jira/browse/MESOS-4130
> Project: Mesos
>  Issue Type: Documentation
>  Components: fetcher
>Reporter: Bernd Mathiske
>Assignee: Shuai Lin
>  Labels: mesosphere, newbie
>
> The fetcher uses libcurl for downloading content from HTTP, HTTPS, etc. There 
> is no source code in the pertinent parts of "net.hpp" that deals with proxy 
> settings. However, libcurl automatically picks up certain environment 
> variables and adjusts its settings accordingly. See "man libcurl-tutorial" 
> for details. See section "Proxies", subsection "Environment Variables". If 
> you follow this recipe in your Mesos agent startup script, you can use a 
> proxy. 
> We should document this in the fetcher (cache) doc 
> (http://mesos.apache.org/documentation/latest/fetcher/).



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