Modified: mesos/site/publish/documentation/latest/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/index.html (original) +++ mesos/site/publish/documentation/latest/index.html Mon Feb 8 16:43:52 2016 @@ -86,115 +86,116 @@ <h2>Mesos Fundamentals</h2> <ul> -<li><a href="/documentation/latest/architecture/">Mesos Architecture</a> providing an overview of Mesos concepts.</li> -<li><a href="/documentation/latest/presentations/">Video and Slides of Mesos Presentations</a></li> +<li><a href="/documentation/latest/./architecture/">Mesos Architecture</a> providing an overview of Mesos concepts.</li> +<li><a href="/documentation/latest/./presentations/">Video and Slides of Mesos Presentations</a></li> </ul> <h2>Running Mesos</h2> <ul> -<li><a href="/documentation/latest/getting-started/">Getting Started</a> for basic instructions on compiling and installing Mesos.</li> -<li><a href="/documentation/latest/upgrades/">Upgrades</a> for upgrading a Mesos cluster.</li> -<li><a href="/documentation/latest/configuration/">Configuration</a> for command-line arguments.</li> -<li><a href="/documentation/latest/containerizer/">Containerizer</a> for containerizer overview and use cases. +<li><a href="/documentation/latest/./getting-started/">Getting Started</a> for basic instructions on compiling and installing Mesos.</li> +<li><a href="/documentation/latest/./upgrades/">Upgrades</a> for upgrading a Mesos cluster.</li> +<li><a href="/documentation/latest/./configuration/">Configuration</a> for command-line arguments.</li> +<li><a href="endpoints/">HTTP Endpoints</a> for available HTTP endpoints.</li> +<li><a href="/documentation/latest/./containerizer/">Containerizer</a> for containerizer overview and use cases. <ul> -<li><a href="/documentation/latest/containerizer-internals/">Containerizer Internals</a> for implementation details of containerizers.</li> -<li><a href="/documentation/latest/mesos-containerizer/">Mesos Containerizer</a> default containerizer, supports both Linux and POSIX systems.</li> -<li><a href="/documentation/latest/docker-containerizer/">Docker Containerizer</a> for launching a Docker image as a Task, or as an Executor.</li> -<li><a href="/documentation/latest/external-containerizer/">External Containerizer</a> for custom containerization implementations (deprecated).</li> +<li><a href="/documentation/latest/./containerizer-internals/">Containerizer Internals</a> for implementation details of containerizers.</li> +<li><a href="/documentation/latest/./mesos-containerizer/">Mesos Containerizer</a> default containerizer, supports both Linux and POSIX systems.</li> +<li><a href="/documentation/latest/./docker-containerizer/">Docker Containerizer</a> for launching a Docker image as a Task, or as an Executor.</li> +<li><a href="/documentation/latest/./external-containerizer/">External Containerizer</a> for custom containerization implementations (deprecated).</li> </ul> </li> -<li><a href="/documentation/latest/roles/">Roles</a></li> -<li><a href="/documentation/latest/authentication/">Framework Authentication</a></li> -<li><a href="/documentation/latest/authorization/">Framework Authorization</a></li> -<li><a href="/documentation/latest/framework-rate-limiting/">Framework Rate Limiting</a></li> -<li><a href="/documentation/latest/logging/">Logging</a></li> -<li><a href="/documentation/latest/high-availability/">High Availability</a> for running multiple masters simultaneously.</li> -<li><a href="/documentation/latest/operational-guide/">Operational Guide</a></li> -<li><a href="/documentation/latest/monitoring/">Monitoring</a></li> -<li><a href="/documentation/latest/network-monitoring/">Network Monitoring and Isolation</a></li> -<li><a href="/documentation/latest/slave-recovery/">Slave Recovery</a> for doing seamless upgrades.</li> -<li><a href="/documentation/latest/maintenance/">Maintenance</a> for performing maintenance on a Mesos cluster.</li> -<li><a href="/documentation/latest/tools/">Tools</a> for setting up and running a Mesos cluster.</li> -<li><a href="/documentation/latest/ssl/">SSL</a> for enabling and enforcing SSL communication.</li> -<li><a href="/documentation/latest/mesos-provisioner/">Mesos Image Provisioner</a> for provisioning container filesystems from different image formats.</li> +<li><a href="/documentation/latest/./roles/">Roles</a></li> +<li><a href="/documentation/latest/./authentication/">Framework Authentication</a></li> +<li><a href="/documentation/latest/./authorization/">Framework Authorization</a></li> +<li><a href="/documentation/latest/./framework-rate-limiting/">Framework Rate Limiting</a></li> +<li><a href="/documentation/latest/./logging/">Logging</a></li> +<li><a href="/documentation/latest/./high-availability/">High Availability</a> for running multiple masters simultaneously.</li> +<li><a href="/documentation/latest/./operational-guide/">Operational Guide</a></li> +<li><a href="/documentation/latest/./monitoring/">Monitoring</a></li> +<li><a href="/documentation/latest/./network-monitoring/">Network Monitoring and Isolation</a></li> +<li><a href="/documentation/latest/./slave-recovery/">Slave Recovery</a> for doing seamless upgrades.</li> +<li><a href="/documentation/latest/./maintenance/">Maintenance</a> for performing maintenance on a Mesos cluster.</li> +<li><a href="/documentation/latest/./tools/">Tools</a> for setting up and running a Mesos cluster.</li> +<li><a href="/documentation/latest/./ssl/">SSL</a> for enabling and enforcing SSL communication.</li> +<li><a href="/documentation/latest/./mesos-provisioner/">Mesos Image Provisioner</a> for provisioning container filesystems from different image formats.</li> </ul> <h2>Advanced Features</h2> <ul> -<li><a href="/documentation/latest/attributes-resources/">Attributes and Resources</a> for how to describe the slaves that comprise a cluster.</li> -<li><a href="/documentation/latest/fetcher/">Fetcher Cache</a> for how to configure the Mesos fetcher cache.</li> -<li><a href="/documentation/latest/networking-for-mesos-managed-containers/">Networking for Mesos-managed Containers</a></li> -<li><a href="/documentation/latest/oversubscription/">Oversubscription</a> for how to configure Mesos to take advantage of unused resources to launch “best-effort” tasks.</li> -<li><a href="/documentation/latest/persistent-volume/">Persistent Volume</a> for how to allow tasks to access persistent storage resources.</li> -<li><a href="/documentation/latest/quota/">Quota</a> for how to configure Mesos to provide guaranteed resource allocations for use by a role.</li> -<li><a href="/documentation/latest/reservation/">Reservation</a> for how operators and frameworks can reserve resources on individual agents for use by a role.</li> +<li><a href="/documentation/latest/./attributes-resources/">Attributes and Resources</a> for how to describe the slaves that comprise a cluster.</li> +<li><a href="/documentation/latest/./fetcher/">Fetcher Cache</a> for how to configure the Mesos fetcher cache.</li> +<li><a href="/documentation/latest/./networking-for-mesos-managed-containers/">Networking for Mesos-managed Containers</a></li> +<li><a href="/documentation/latest/./oversubscription/">Oversubscription</a> for how to configure Mesos to take advantage of unused resources to launch “best-effort” tasks.</li> +<li><a href="/documentation/latest/./persistent-volume/">Persistent Volume</a> for how to allow tasks to access persistent storage resources.</li> +<li><a href="/documentation/latest/./quota/">Quota</a> for how to configure Mesos to provide guaranteed resource allocations for use by a role.</li> +<li><a href="/documentation/latest/./reservation/">Reservation</a> for how operators and frameworks can reserve resources on individual agents for use by a role.</li> </ul> <h2>Running Mesos Frameworks</h2> <ul> -<li><a href="/documentation/latest/frameworks/">Mesos frameworks</a> for a list of apps built on top of Mesos and instructions on how to run them.</li> -<li><a href="/documentation/latest/sandbox/">Sandbox</a> describes a useful debugging arena for most users.</li> +<li><a href="/documentation/latest/./frameworks/">Mesos frameworks</a> for a list of apps built on top of Mesos and instructions on how to run them.</li> +<li><a href="/documentation/latest/./sandbox/">Sandbox</a> describes a useful debugging arena for most users.</li> </ul> <h2>Developing Mesos Frameworks</h2> <ul> -<li><a href="/documentation/latest/app-framework-development-guide/">Framework Development Guide</a> describes how to build applications on top of Mesos.</li> -<li><a href="/documentation/latest/high-availability-framework-guide/">Designing Highly Available Mesos Frameworks</a></li> -<li><a href="/documentation/latest/reconciliation/">Reconciliation</a> for ensuring a framework’s state remains eventually consistent in the face of failures.</li> -<li><a href="/documentation/latest/scheduler-http-api/">Scheduler HTTP API</a> describes the new HTTP API for communication between schedulers and the Mesos master.</li> -<li><a href="/documentation/latest/executor-http-api/">Executor HTTP API</a> describes the new HTTP API for communication between executors and the Mesos agent.</li> +<li><a href="/documentation/latest/./app-framework-development-guide/">Framework Development Guide</a> describes how to build applications on top of Mesos.</li> +<li><a href="/documentation/latest/./high-availability-framework-guide/">Designing Highly Available Mesos Frameworks</a></li> +<li><a href="/documentation/latest/./reconciliation/">Reconciliation</a> for ensuring a framework’s state remains eventually consistent in the face of failures.</li> +<li><a href="/documentation/latest/./scheduler-http-api/">Scheduler HTTP API</a> describes the new HTTP API for communication between schedulers and the Mesos master.</li> +<li><a href="/documentation/latest/./executor-http-api/">Executor HTTP API</a> describes the new HTTP API for communication between executors and the Mesos agent.</li> <li><a href="/api/latest/java/">Javadoc</a> documents the Mesos Java API.</li> <li><a href="/api/latest/c++/namespacemesos.html">Doxygen</a> documents the Mesos C++ API.</li> -<li><a href="/documentation/latest/tools/">Developer Tools</a> for hacking on Mesos or writing frameworks.</li> -<li><a href="/documentation/latest/versioning/">Versioning</a> describes how Mesos does API and release versioning.</li> +<li><a href="/documentation/latest/./tools/">Developer Tools</a> for hacking on Mesos or writing frameworks.</li> +<li><a href="/documentation/latest/./versioning/">Versioning</a> describes how Mesos does API and release versioning.</li> </ul> <h2>Extending Mesos</h2> <ul> -<li><a href="/documentation/latest/modules/">Mesos Modules</a> for specifying Mesos modules for master, slave and tests.</li> -<li><a href="/documentation/latest/allocation-module/">Allocation Modules</a> for how to write custom resource allocators.</li> +<li><a href="/documentation/latest/./modules/">Mesos Modules</a> for specifying Mesos modules for master, slave and tests.</li> +<li><a href="/documentation/latest/./allocation-module/">Allocation Modules</a> for how to write custom resource allocators.</li> </ul> <h2>Contributing to Mesos</h2> <ul> -<li><a href="/documentation/latest/reporting-a-bug/">Reporting an Issue, Improvement, or Feature</a> for getting started with JIRA.</li> -<li><a href="/documentation/latest/submitting-a-patch/">Submitting a Patch</a> for getting started with ReviewBoard and our tooling around it.</li> -<li><a href="/documentation/latest/testing-patterns/">Testing Patterns</a> for tips and tricks used in Mesos tests.</li> -<li><a href="/documentation/latest/effective-code-reviewing/">Effective Code Reviewing</a> guidelines, tips, and learnings for how to do effective code reviews.</li> -<li><a href="/documentation/latest/engineering-principles-and-practices/">Engineering Principles and Practices</a> to serve as a shared set of project-level values for the community.</li> -<li><a href="/documentation/latest/committing/">Committing</a> guidelines for committing changes.</li> -<li><a href="/documentation/latest/committers/">Committers and Maintainers</a> a listing of project committers and component maintainers; useful when seeking feedback.</li> +<li><a href="/documentation/latest/./reporting-a-bug/">Reporting an Issue, Improvement, or Feature</a> for getting started with JIRA.</li> +<li><a href="/documentation/latest/./submitting-a-patch/">Submitting a Patch</a> for getting started with ReviewBoard and our tooling around it.</li> +<li><a href="/documentation/latest/./testing-patterns/">Testing Patterns</a> for tips and tricks used in Mesos tests.</li> +<li><a href="/documentation/latest/./effective-code-reviewing/">Effective Code Reviewing</a> guidelines, tips, and learnings for how to do effective code reviews.</li> +<li><a href="/documentation/latest/./engineering-principles-and-practices/">Engineering Principles and Practices</a> to serve as a shared set of project-level values for the community.</li> +<li><a href="/documentation/latest/./committing/">Committing</a> guidelines for committing changes.</li> +<li><a href="/documentation/latest/./committers/">Committers and Maintainers</a> a listing of project committers and component maintainers; useful when seeking feedback.</li> <li><a href="/api/latest/c++/">Doxygen</a> documents the internal Mesos APIs.</li> -<li><a href="/documentation/latest/documentation-guide/">Documentation Guide</a> +<li><a href="/documentation/latest/./documentation-guide/">Documentation Guide</a> <ul> -<li><a href="/documentation/latest/c++-style-guide/">C++ Style Guide</a></li> -<li><a href="/documentation/latest/doxygen-style-guide/">Doxygen Style Guide</a></li> -<li><a href="/documentation/latest/markdown-style-guide/">Markdown Style Guide</a></li> +<li><a href="/documentation/latest/./c++-style-guide/">C++ Style Guide</a></li> +<li><a href="/documentation/latest/./doxygen-style-guide/">Doxygen Style Guide</a></li> +<li><a href="/documentation/latest/./markdown-style-guide/">Markdown Style Guide</a></li> </ul> </li> -<li><a href="/documentation/latest/roadmap/">Development Roadmap</a></li> -<li><a href="/documentation/latest/release-guide/">Release Guide</a></li> +<li><a href="/documentation/latest/./roadmap/">Development Roadmap</a></li> +<li><a href="/documentation/latest/./release-guide/">Release Guide</a></li> </ul> <h2>More Info about Mesos</h2> <ul> -<li><a href="/documentation/latest/powered-by-mesos/">Powered by Mesos</a> lists organizations and software that are powered by Apache Mesos.</li> +<li><a href="/documentation/latest/./powered-by-mesos/">Powered by Mesos</a> lists organizations and software that are powered by Apache Mesos.</li> <li>Academic Papers and Project History</li> </ul>
Modified: mesos/site/publish/documentation/latest/logging/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/logging/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/logging/index.html (original) +++ mesos/site/publish/documentation/latest/logging/index.html Mon Feb 8 16:43:52 2016 @@ -92,7 +92,7 @@ degree of control Mesos has over the sou <li><a href="#Internal">Internal</a> - Master and Agent.</li> <li><a href="#Containers">Containers</a> - Executors and Tasks.</li> <li>External - Components launched outside of Mesos, like -Frameworks and <a href="/documentation/latest/high-availability/">ZooKeeper</a>. These are expected to +Frameworks and <a href="/documentation/latest/./high-availability/">ZooKeeper</a>. These are expected to implement their own logging solution.</li> </ul> @@ -102,7 +102,7 @@ implement their own logging solution.</l <p>The Mesos Master and Agent use the <a href="https://github.com/google/glog";>Google’s logging library</a>. For information regarding the command-line options used to configure this -library, see the <a href="/documentation/latest/configuration/">configuration documentation</a>. +library, see the <a href="/documentation/latest/./configuration/">configuration documentation</a>. Google logging options that are not explicitly mentioned there can be configured via environment variables.</p> @@ -118,12 +118,12 @@ original level after the given duration. <h2><a name="Containers"></a>Containers</h2> -<p>For background, see <a href="/documentation/latest/containerizer/">the containerizer documentation</a>.</p> +<p>For background, see <a href="/documentation/latest/./containerizer/">the containerizer documentation</a>.</p> <p>Mesos does not assume any structured logging for entities running inside containers. Instead, Mesos will store the stdout and stderr of containers into plain files (“stdout” and “stderr”) located inside -<a href="/documentation/latest/sandbox/#where-is-it">the sandbox</a>.</p> +<a href="/documentation/latest/./sandbox/#where-is-it">the sandbox</a>.</p> <p>In some cases, the default Container logger behavior of Mesos is not ideal:</p> @@ -166,7 +166,7 @@ specified maximum number of files is rea <p>The <code>LogrotateContainerLogger</code> can be loaded by specifying the library <code>liblogrotate_container_logger.so</code> in the -<a href="/documentation/latest/modules/#Invoking"><code>--modules</code> flag</a> when starting the Agent and by +<a href="/documentation/latest/./modules/#Invoking"><code>--modules</code> flag</a> when starting the Agent and by setting the <code>--container_logger</code> Agent flag to <code>org_apache_mesos_LogrotateContainerLogger</code>.</p> @@ -263,7 +263,7 @@ will continue to run.</p> <h3>Writing a Custom <code>ContainerLogger</code></h3> -<p>For basics on module writing, see <a href="/documentation/latest/modules/">the modules documentation</a>.</p> +<p>For basics on module writing, see <a href="/documentation/latest/./modules/">the modules documentation</a>.</p> <p>There are several caveats to consider when designing a new <code>ContainerLogger</code>:</p> @@ -278,7 +278,7 @@ that the container has exited. This pro <li>The <code>ContainerLogger</code> should not assume that containers have been launched with any specific <code>ContainerLogger</code>. The Agent may be restarted with a different <code>ContainerLogger</code>.</li> -<li>Each <a href="/documentation/latest/containerizer/">containerizer</a> running on an Agent uses its own +<li>Each <a href="/documentation/latest/./containerizer/">containerizer</a> running on an Agent uses its own instance of the <code>ContainerLogger</code>. This means more than one <code>ContainerLogger</code> may be running in a single Agent. However, each Agent will only run a single type of <code>ContainerLogger</code>.</li> Modified: mesos/site/publish/documentation/latest/mesos-provisioner/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/mesos-provisioner/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/mesos-provisioner/index.html (original) +++ mesos/site/publish/documentation/latest/mesos-provisioner/index.html Mon Feb 8 16:43:52 2016 @@ -197,8 +197,8 @@ backend tracked by MESOS-2971). For smal <h2>Related Docs</h2> -<p>For more information on the Mesos containerizer filesystem, namespace, and isolator features, visit <a href="/documentation/latest/mesos-containerizer/">Mesos Containerizer</a>. -For more information on launching Docker containers through the Docker containerizer, visit <a href="/documentation/latest/docker-containerizer/">Docker Containerizer</a>.</p> +<p>For more information on the Mesos containerizer filesystem, namespace, and isolator features, visit <a href="/documentation/latest/./mesos-containerizer/">Mesos Containerizer</a>. +For more information on launching Docker containers through the Docker containerizer, visit <a href="/documentation/latest/./docker-containerizer/">Docker Containerizer</a>.</p> </div> </div> Modified: mesos/site/publish/documentation/latest/networking-for-mesos-managed-containers/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/networking-for-mesos-managed-containers/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/networking-for-mesos-managed-containers/index.html (original) +++ mesos/site/publish/documentation/latest/networking-for-mesos-managed-containers/index.html Mon Feb 8 16:43:52 2016 @@ -231,7 +231,7 @@ before the address(es) are recycled.</p> there is an example implementation at https://github.com/mesosphere/net-modules.</p> <p>Once the network isolation module has been built into a shared dynamic library, -we can load it into Mesos Agent (see <a href="/documentation/latest/modules/">modules documentation</a> on +we can load it into Mesos Agent (see <a href="/documentation/latest/./modules/">modules documentation</a> on instructions for building and loading a module).</p> <h2>Enabling frameworks for IP-per-container capability</h2> Modified: mesos/site/publish/documentation/latest/newbie-guide/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/newbie-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/newbie-guide/index.html (original) +++ mesos/site/publish/documentation/latest/newbie-guide/index.html Mon Feb 8 16:43:52 2016 @@ -93,7 +93,7 @@ <h1>Contribution Process Overview</h1> -<p>The figure below shows a high-level process flow of the contribution delivery process for the Mesos open source distribution. Details of the process can be obtained from the [submitting-a-patch] (/documentation/latest/submitting-a-patch/) document of the Mesos distribution along with the Getting Started Guidance section of this document.</p> +<p>The figure below shows a high-level process flow of the contribution delivery process for the Mesos open source distribution. Details of the process can be obtained from the [submitting-a-patch] (/documentation/latest/./submitting-a-patch/) document of the Mesos distribution along with the Getting Started Guidance section of this document.</p> <p><img src="NewbieContributionOverview.jpg" alt="Newbie Document" /></p> @@ -135,7 +135,7 @@ <h1>Getting Started Guidance</h1> -<p>The following information will help provide additional guidance to execute the steps summarized in Contribution Process Overview described above as well as provide helpful hints when following the <a href="/documentation/latest/submitting-a-patch/">submitting-a-patch</a> document of the Mesos distribution.</p> +<p>The following information will help provide additional guidance to execute the steps summarized in Contribution Process Overview described above as well as provide helpful hints when following the <a href="/documentation/latest/./submitting-a-patch/">submitting-a-patch</a> document of the Mesos distribution.</p> <h2>Apache JIRA Account Pre-Requisite</h2> @@ -159,7 +159,7 @@ <h2>Download and Build Mesos</h2> -<p>Detailed steps are provided in the <a href="/documentation/latest/getting-started/">Mesos documentation</a> to download and build Mesos. When downloading the Mesos distribution there are 2 options to obtain the Mesos source code. For contributing, ensure that the Git option is used.</p> +<p>Detailed steps are provided in the <a href="/documentation/latest/./getting-started/">Mesos documentation</a> to download and build Mesos. When downloading the Mesos distribution there are 2 options to obtain the Mesos source code. For contributing, ensure that the Git option is used.</p> <h2>JIRA</h2> @@ -183,7 +183,7 @@ <p>There are a couple options to assign a work item: 1) create a new JIRA issue to work on or 2) identify an existing JIRA issue item to work on as described above. Whichever option is chosen there are several steps that should be followed when assigning yourself a JIRA ticket.</p> -<p>It is important to identify a shepherd before you assign a ticket to yourself. Working with a shepherd will reveal its priority at the current time. To identify a shepherd look at the <a href="/documentation/latest/committers/">maintainers</a> file to get an idea who to ask to shepherd your JIRA issue.\</p> +<p>It is important to identify a shepherd before you assign a ticket to yourself. Working with a shepherd will reveal its priority at the current time. To identify a shepherd look at the <a href="/documentation/latest/./committers/">maintainers</a> file to get an idea who to ask to shepherd your JIRA issue.\</p> <h2>JIRA Issue Solution Proposals</h2> @@ -196,11 +196,11 @@ </ol> -<p>Guidelines to consider when designing a solution can be found in the <a href="/documentation/latest/effective-code-reviewing/">effective-code-reviewing</a> document.</p> +<p>Guidelines to consider when designing a solution can be found in the <a href="/documentation/latest/./effective-code-reviewing/">effective-code-reviewing</a> document.</p> <h2>Making Changes</h2> -<p>After completing the solution review make the source code changes, build and successfully run relevant test cases. Guidelines for these processes can be found in the <a href="/documentation/latest/submitting-a-patch/">submitting-a-patch</a> and [mesos-c++style-guide] (/documentation/latest/c++-style-guide/).</p> +<p>After completing the solution review make the source code changes, build and successfully run relevant test cases. Guidelines for these processes can be found in the <a href="/documentation/latest/./submitting-a-patch/">submitting-a-patch</a> and [mesos-c++style-guide] (/documentation/latest/./c++-style-guide/).</p> <p>When creating and running test cases pay particular attention to race conditions. One recommendation is to run system tests multiple times. Below is a sample command to repeat the test 100 times.</p> @@ -210,7 +210,7 @@ <p>Submit your patch for review after you have come to an agreement with your shepherd on the proposed solution, made the modifications and successfully ran the test cases. Make sure your shepherd is added as a “reviewer” (among others) in the review. This will ensure that your reviews get processed.</p> -<p>When submitting a patch for review, include all testing done in the submission documentation. Follow the detailed steps found in the <a href="/documentation/latest/submitting-a-patch/">submitting-a-patch</a> document to submit a patch for review.</p> +<p>When submitting a patch for review, include all testing done in the submission documentation. Follow the detailed steps found in the <a href="/documentation/latest/./submitting-a-patch/">submitting-a-patch</a> document to submit a patch for review.</p> <h1>Advanced Level JIRA Items</h1> Modified: mesos/site/publish/documentation/latest/operational-guide/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/operational-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/operational-guide/index.html (original) +++ mesos/site/publish/documentation/latest/operational-guide/index.html Mon Feb 8 16:43:52 2016 @@ -85,7 +85,7 @@ <h2>Using a process supervisor</h2> -<p>Mesos uses a “<a href="https://en.wikipedia.org/wiki/Fail-fast";>fail-fast</a>” approach to error handling: if a serious error occurs, Mesos will typically exit rather than trying to continue running in a possibly erroneous state. For example, when Mesos is configured for <a href="/documentation/latest/high-availability/">high availability</a>, the leading master will abort itself when it discovers it has been partitioned away from the Zookeeper quorum. This is a safety precaution to ensure the previous leader doesn’t continue communicating in an unsafe state.</p> +<p>Mesos uses a “<a href="https://en.wikipedia.org/wiki/Fail-fast";>fail-fast</a>” approach to error handling: if a serious error occurs, Mesos will typically exit rather than trying to continue running in a possibly erroneous state. For example, when Mesos is configured for <a href="/documentation/latest/./high-availability/">high availability</a>, the leading master will abort itself when it discovers it has been partitioned away from the Zookeeper quorum. This is a safety precaution to ensure the previous leader doesn’t continue communicating in an unsafe state.</p> <p>To ensure that such failures are handled appropriately, production deployments of Mesos typically use a <em>process supervisor</em> (such as systemd or supervisord) to detect when Mesos processes exit. The supervisor can be configured to restart the failed process automatically and/or to notify the cluster operator to investigate the situation.</p> Modified: mesos/site/publish/documentation/latest/oversubscription/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/oversubscription/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/oversubscription/index.html (original) +++ mesos/site/publish/documentation/latest/oversubscription/index.html Mon Feb 8 16:43:52 2016 @@ -422,7 +422,7 @@ be above 6, or for 15 minutes will be ab seconds.</p> <p>To install a custom resource estimator and QoS controller, please refer to the -<a href="/documentation/latest/modules/">modules documentation</a>.</p> +<a href="/documentation/latest/./modules/">modules documentation</a>.</p> </div> </div> Modified: mesos/site/publish/documentation/latest/persistent-volume/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/persistent-volume/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/persistent-volume/index.html (original) +++ mesos/site/publish/documentation/latest/persistent-volume/index.html Mon Feb 8 16:43:52 2016 @@ -101,7 +101,7 @@ the volume. These rules exist to limit a volume containing sensitive data being offered to other frameworks in the cluster.</p> -<p>Please refer to the <a href="/documentation/latest/reservation/">Reservation</a> documentation for details +<p>Please refer to the <a href="/documentation/latest/./reservation/">Reservation</a> documentation for details regarding reservation mechanisms available in Mesos.</p> <p>Persistent volumes can be created by <strong>operators</strong> and authorized @@ -110,7 +110,7 @@ to authenticate/authorize the operations existing ACL mechanism. To use authorization with reserve, unreserve, create, and destroy operations, the Mesos master must be configured with the desired ACLs. For more information, see the -<a href="/documentation/latest/authorization/">authorization documentation</a>.</p> +<a href="/documentation/latest/./authorization/">authorization documentation</a>.</p> <ul> <li><code>Offer::Operation::Create</code> and <code>Offer::Operation::Destroy</code> messages are @@ -497,7 +497,7 @@ for the same role concurrently. In gener allowed to register in the same role, the operator should ensure that those frameworks are configured to collaborate with one another when using role-specific resources. For more information, see the discussion of -<a href="/documentation/latest/roles/#roles-multiple-frameworks">multiple frameworks in the same role</a>.</p></li> +<a href="/documentation/latest/./roles/#roles-multiple-frameworks">multiple frameworks in the same role</a>.</p></li> </ul> Modified: mesos/site/publish/documentation/latest/powered-by-mesos/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/powered-by-mesos/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/powered-by-mesos/index.html (original) +++ mesos/site/publish/documentation/latest/powered-by-mesos/index.html Mon Feb 8 16:43:52 2016 @@ -182,7 +182,7 @@ <h2>Software projects built on Mesos</h2> -<p>See the <a href="/documentation/latest/frameworks/">Mesos frameworks page</a> for a list of apps built on top of Mesos, and instructions on how to use them.</p> +<p>See the <a href="/documentation/latest/./frameworks/">Mesos frameworks page</a> for a list of apps built on top of Mesos, and instructions on how to use them.</p> <p>If you’re using Mesos, please add yourself to the list above, or email [email protected] and we’ll add you!</p> Modified: mesos/site/publish/documentation/latest/quota/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/quota/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/quota/index.html (original) +++ mesos/site/publish/documentation/latest/quota/index.html Mon Feb 8 16:43:52 2016 @@ -88,13 +88,13 @@ resources to frameworks even though they are beyond their fair share (e.g., when no other framework currently accepts these resources). There is no mechanism to lay away resources for future consumption in an entire cluster. Even though -<a href="/documentation/latest/reservation/">dynamic reservations</a> allow both operators and frameworks +<a href="/documentation/latest/./reservation/">dynamic reservations</a> allow both operators and frameworks to dynamically reserve resources on particular Mesos agents, it does not solve the above problem because any individual agents might fail.</p> <p>Since version 0.27.0 Mesos provides a mechanism to reserve a certain amount of resources in an entire cluster, i.e. not tied to a particular agent. <em>Quota</em> -allows operators to lay away resources for a given <a href="/documentation/latest/roles/">role</a>. These +allows operators to lay away resources for a given <a href="/documentation/latest/./roles/">role</a>. These resources cannot be hijacked by other roles and are guaranteed to be available for the role if there are enough resources in the cluster. Quota can be viewed as a cluster-wide dynamic reservation available for operators only.</p> @@ -157,7 +157,7 @@ in order to update a quota for a given r existing quota and then set a new one.</p> <p>The endpoint can optionally use authentication and authorization. See the -<a href="/documentation/latest/authentication/">authentication guide</a> for details.</p> +<a href="/documentation/latest/./authentication/">authentication guide</a> for details.</p> <p><a name="setRequest"></a></p> @@ -194,7 +194,7 @@ can use the following <code>jsonMessageB <p>A set request is only valid for roles for which no quota is currently set. However if the master is configured without an explicit -<a href="/documentation/latest/roles/">role whitelist</a> a set request can introduce new roles.</p> +<a href="/documentation/latest/./roles/">role whitelist</a> a set request can introduce new roles.</p> <p>In order to bypass the <a href="#capacityHeuristic">capacity heuristic</a> check the operator should set an optional <code>force</code> field:</p> @@ -311,10 +311,10 @@ possible to set quota for port resources endpoint, the following steps are triggered:</p> <ol> -<li><a href="/documentation/latest/authentication/">Authenticate</a> the HTTP request.</li> +<li><a href="/documentation/latest/./authentication/">Authenticate</a> the HTTP request.</li> <li>Parse and validate the request. See <a href="#setRequest">description of possible error codes</a>.</li> -<li><a href="/documentation/latest/authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> +<li><a href="/documentation/latest/./authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> <li>Run the <a href="#capacityHeuristic">capacity heuristic</a> if not disabled by <a href="#setRequest">the <code>force</code> flag</a>.</li> <li>Reliably store quota. See <a href="#failover">details on failover recovery</a>.</li> @@ -326,10 +326,10 @@ See <a href="#setRequest">description of The quota remove request processing is simpler and triggers the following steps:</p> <ol> -<li><a href="/documentation/latest/authentication/">Authenticate</a> the HTTP request.</li> +<li><a href="/documentation/latest/./authentication/">Authenticate</a> the HTTP request.</li> <li>Validate the request. See <a href="#removeRequest">description of potential error codes</a>.</li> -<li><a href="/documentation/latest/authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> +<li><a href="/documentation/latest/./authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> <li>Reliably remove quota.</li> </ol> Modified: mesos/site/publish/documentation/latest/release-guide/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/release-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/release-guide/index.html (original) +++ mesos/site/publish/documentation/latest/release-guide/index.html Mon Feb 8 16:43:52 2016 @@ -184,7 +184,7 @@ added for any new features.</p></li> <blockquote><p>NOTE: <code>X.Y.Z</code> is based on <a href="http://semver.org/";>semantic versioning</a> scheme. <code>R</code> is release candidate version that starts with 1.</p></blockquote></li> -<li><p>Tag the release externally and deploy the corresponding JAR to the Apache maven repository. +<li><p>Tag the release externally and deploy the corresponding JAR to the <a href="https://repository.apache.org";>Apache maven repository</a>. It is recommended to use the <code>support/tag.sh</code> script to accomplish this.</p> <pre><code> $ ./support/tag.sh X.Y.Z R Modified: mesos/site/publish/documentation/latest/reporting-a-bug/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/reporting-a-bug/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/reporting-a-bug/index.html (original) +++ mesos/site/publish/documentation/latest/reporting-a-bug/index.html Mon Feb 8 16:43:52 2016 @@ -88,7 +88,7 @@ <ul> <li>We track all issues via Apache’s hosted <a href="https://issues.apache.org/jira/browse/MESOS";>JIRA issue tracker</a>, so if you don’t already have an account you’ll need to register for one. It’s quick and easy.</li> <li>A JIRA should be created for every task, feature, bug-fix, etc. This makes it easy to track progress.</li> -<li>If you are planning to work on the ticket, please assign the JIRA issue to yourself before you start working on it. This helps to avoid duplication of work and alerts anyone who is following that issue. It is highly encouraged to start a discussion with others in the community about how to solve the issue. The <a href="/documentation/latest/submitting-a-patch/">contribution guidelines</a> discuss how to contribute to Mesos development in more detail.</li> +<li>If you are planning to work on the ticket, please assign the JIRA issue to yourself before you start working on it. This helps to avoid duplication of work and alerts anyone who is following that issue. It is highly encouraged to start a discussion with others in the community about how to solve the issue. The <a href="/documentation/latest/./submitting-a-patch/">contribution guidelines</a> discuss how to contribute to Mesos development in more detail.</li> </ul> Modified: mesos/site/publish/documentation/latest/reservation/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/reservation/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/reservation/index.html (original) +++ mesos/site/publish/documentation/latest/reservation/index.html Mon Feb 8 16:43:52 2016 @@ -89,7 +89,7 @@ which enabled operators to specify the r This was extended with <strong>dynamic reservation</strong> in 0.23.0 which enabled operators and authorized <strong>frameworks</strong> to dynamically reserve resources in the cluster.</p> -<p>In both types of reservations, resources are reserved for a <a href="/documentation/latest/roles/"><strong>role</strong></a>.</p> +<p>In both types of reservations, resources are reserved for a <a href="/documentation/latest/./roles/"><strong>role</strong></a>.</p> <h2>Static Reservation (since 0.14.0)</h2> @@ -127,7 +127,7 @@ to reserve and unreserve resources post authenticate/authorize the operations. Permissions are specified via the existing ACL mechanism. To use authorization with reserve/unreserve operations, the Mesos master must be configured with the desired ACLs. For more information, -see the <a href="/documentation/latest/authorization/">authorization documentation</a>.</p> +see the <a href="/documentation/latest/./authorization/">authorization documentation</a>.</p> <ul> <li><code>Offer::Operation::Reserve</code> and <code>Offer::Operation::Unreserve</code> messages are Modified: mesos/site/publish/documentation/latest/roles/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/roles/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/roles/index.html (original) +++ mesos/site/publish/documentation/latest/roles/index.html Mon Feb 8 16:43:52 2016 @@ -84,7 +84,7 @@ <h1>Roles</h1> <p>In Mesos, <strong>roles</strong> can be used to specify that certain -<a href="/documentation/latest/attributes-resources/">resources</a> are reserved for the use of one or more +<a href="/documentation/latest/./attributes-resources/">resources</a> are reserved for the use of one or more frameworks. Roles can be used to enable a variety of restrictions on how resources are offered to frameworks. Some use-cases for roles include:</p> @@ -94,7 +94,7 @@ particular framework.</li> <li>dividing a cluster between two organizations: resources assigned for use by organization <em>A</em> will only be offered to frameworks that have registered using organization <em>A</em>’s role.</li> -<li>ensuring that <a href="/documentation/latest/persistent-volume/">persistent volumes</a> created by one +<li>ensuring that <a href="/documentation/latest/./persistent-volume/">persistent volumes</a> created by one framework are not offered to frameworks registered with a different role.</li> <li>expressing that one group of frameworks should be considered “higher priority” (and offered more resources) than another group of frameworks.</li> @@ -105,7 +105,7 @@ framework are not offered to frameworks <p>There are two ways to control which roles a framework is allowed to register as. First, ACLs can be used to specify which framework principals can register -as which roles. For more information, see the <a href="/documentation/latest/authorization/">authorization</a> +as which roles. For more information, see the <a href="/documentation/latest/./authorization/">authorization</a> documentation.</p> <p>Second, a <em>role whitelist</em> can be configured by passing the <code>--roles</code> flag to @@ -164,7 +164,7 @@ role-specific resources are used appropr reserved <em>statically</em> (when the agent that hosts the resource is started) or <em>dynamically</em>: frameworks and operators can specify that a certain resource should subsequently be reserved for use by a given role. For more information, -see the <a href="/documentation/latest/reservation/">reservation</a> documentation.</p> +see the <a href="/documentation/latest/./reservation/">reservation</a> documentation.</p> <h2>The default role</h2> Modified: mesos/site/publish/documentation/latest/sandbox/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/sandbox/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/sandbox/index.html (original) +++ mesos/site/publish/documentation/latest/sandbox/index.html Mon Feb 8 16:43:52 2016 @@ -92,7 +92,7 @@ own sandbox and the executor’s wor <p>The sandbox holds:</p> <ul> -<li>Files <a href="/documentation/latest/fetcher/">fetched by Mesos</a>, prior to starting +<li>Files <a href="/documentation/latest/./fetcher/">fetched by Mesos</a>, prior to starting the executor’s tasks.</li> <li>The output of the executor and tasks (as files “stdout” and “stderr”).</li> <li>Files created by the executor and tasks, with some exceptions.</li> @@ -100,7 +100,7 @@ the executor’s tasks.</li> <blockquote><p><strong>NOTE:</strong> With the introduction of -<a href="/documentation/latest/persistent-volume/">persistent volumes</a>, executors +<a href="/documentation/latest/./persistent-volume/">persistent volumes</a>, executors and tasks should never create files outside of the sandbox. However, some containerizers do not enforce this sandboxing.</p></blockquote> @@ -232,7 +232,7 @@ will be killed if the sandbox size excee <li>Docker containerizer - As of Docker <code>1.9.1</code>, the Docker containerizer does not enforce nor support a disk quota. See the <a href="https://github.com/docker/docker/issues/3804";>Docker issue</a>.</li> -<li><a href="/documentation/latest/external-containerizer/">External containerizer</a>.</li> +<li><a href="/documentation/latest/./external-containerizer/">External containerizer</a>.</li> </ul> @@ -257,7 +257,7 @@ After the delay, the files are deleted.< <p>Additionally, according to the <code>--disk_watch_interval</code> agent flag, files scheduled for garbage collection are pruned based on the available disk and the <code>--gc_disk_headroom</code> agent flag. -See <a href="/documentation/latest/configuration/#gc_disk_headroom">the formula here</a>.</p> +See <a href="/documentation/latest/./configuration/#gc_disk_headroom">the formula here</a>.</p> </div> </div> Modified: mesos/site/publish/documentation/latest/scheduler-http-api/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/scheduler-http-api/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/scheduler-http-api/index.html (original) +++ mesos/site/publish/documentation/latest/scheduler-http-api/index.html Mon Feb 8 16:43:52 2016 @@ -94,7 +94,7 @@ <p>Note that we refer to this endpoint with its suffix “/scheduler” in the rest of this document. This endpoint accepts HTTP POST requests with data encoded as JSON (Content-Type: application/json) or binary Protobuf (Content-Type: application/x-protobuf). The first request that a scheduler sends to “/scheduler” endpoint is called SUBSCRIBE and results in a streaming response (“200 OK” status code with Transfer-Encoding: chunked). <strong>Schedulers are expected to keep the subscription connection open as long as possible (barring errors in network, software, hardware etc.) and incrementally process the response</strong> (NOTE: HTTP client libraries that can only parse the response after the connection is closed cannot be used). For the encoding used, please refer to <strong>Events</strong> section below.</p> -<p>All the subsequent (non subscribe) requests to “/scheduler” endpoint (see details below in <strong>Calls</strong> section) must be sent using a different connection(s) than the one being used for subscription. Master responds to these HTTP POST requests with “202 Accepted” status codes (or, for unsuccessful requests, with 4xx or 5xx status codes; details in later sections). The “202 Accepted” response means that a request has been accepted for processing, not that the processing of the request has been completed. The request might or might not be acted upon by Mesos (e.g., master fails during the processing of the request). Any asynchronous responses from these requests will be streamed on long-lived subscription connection.</p> +<p>All the subsequent (non subscribe) requests to “/scheduler” endpoint (see details below in <strong>Calls</strong> section) must be sent using a different connection(s) than the one being used for subscription. Master responds to these HTTP POST requests with “202 Accepted” status codes (or, for unsuccessful requests, with 4xx or 5xx status codes; details in later sections). The “202 Accepted” response means that a request has been accepted for processing, not that the processing of the request has been completed. The request might or might not be acted upon by Mesos (e.g., master fails during the processing of the request). Any asynchronous responses from these requests will be streamed on the long-lived subscription connection.</p> <h2>Calls</h2> @@ -104,7 +104,7 @@ <h3>RecordIO response format</h3> -<p>The response returned from the <code>SUBSCRIBE</code> call (see <a href="#subscribe">below</a> is encoded in RecordIO format, which essentially prepends to a single record (either JSON or serialized Protobuf) its length in bytes, followed by a newline and then the data:</p> +<p>The response returned from the <code>SUBSCRIBE</code> call (see <a href="#subscribe">below</a>) is encoded in RecordIO format, which essentially prepends to a single record (either JSON or serialized Protobuf) its length in bytes, followed by a newline and then the data:</p> <p>The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.1";>BNF grammar</a> for a RecordIO-encoded streaming response is:</p> @@ -580,7 +580,7 @@ HTTP/1.1 202 Accepted <h2>Master detection</h2> -<p>Mesos has a high-availability mode that uses multiple Mesos masters; one active master (called the leader or leading master) and several standbys in case it fails. The masters elect the leader, with ZooKeeper coordinating the election. For more details please refer to the <a href="/documentation/latest/high-availability/">documentation</a>.</p> +<p>Mesos has a high-availability mode that uses multiple Mesos masters; one active master (called the leader or leading master) and several standbys in case it fails. The masters elect the leader, with ZooKeeper coordinating the election. For more details please refer to the <a href="/documentation/latest/./high-availability/">documentation</a>.</p> <p>Schedulers are expected to make HTTP requests to the leading master. If requests are made to a non-leading master a “HTTP 307 Temporary Redirect” will be received with the “Location” header pointing to the leading master.</p> Modified: mesos/site/publish/documentation/latest/slave-recovery/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/slave-recovery/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/slave-recovery/index.html (original) +++ mesos/site/publish/documentation/latest/slave-recovery/index.html Mon Feb 8 16:43:52 2016 @@ -176,7 +176,7 @@ KillMode=process <h2>Upgrading to 0.14.0</h2> -<p>If you want to upgrade a running Mesos cluster to 0.14.0 to take advantage of slave recovery please follow the <a href="/documentation/latest/upgrades/">upgrade instructions</a>.</p> +<p>If you want to upgrade a running Mesos cluster to 0.14.0 to take advantage of slave recovery please follow the <a href="/documentation/latest/./upgrades/">upgrade instructions</a>.</p> </div> </div> Modified: mesos/site/publish/documentation/latest/submitting-a-patch/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/submitting-a-patch/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/submitting-a-patch/index.html (original) +++ mesos/site/publish/documentation/latest/submitting-a-patch/index.html Mon Feb 8 16:43:52 2016 @@ -115,7 +115,7 @@ <ol> <li>To find a shepherd, email the dev mailing list (include a link to your JIRA issue). You can also try asking by adding a comment to your JIRA issue.</li> -<li>You can also find a shepherd by asking the developers on IRC (in the <a href="irc://irc.freenode.net/mesos">mesos channel</a> on <a href="https://freenode.net";>Freenode</a>). You can find the current list of committers <a href="/documentation/latest/committers/">here</a>: a developer that has previously worked on the component you are modifying might be a good candidate shepherd.</li> +<li>You can also find a shepherd by asking the developers on IRC (in the <a href="irc://irc.freenode.net/mesos">mesos channel</a> on <a href="https://freenode.net";>Freenode</a>). You can find the current list of committers <a href="/documentation/latest/./committers/">here</a>: a developer that has previously worked on the component you are modifying might be a good candidate shepherd.</li> </ol> </li> </ol> @@ -127,13 +127,13 @@ <li><p>Create one or more test cases to exercise the bug or the feature (the Mesos team uses <a href="http://en.wikipedia.org/wiki/Test-driven_development";>test-driven development</a>). Before you start coding, make sure these test cases all fail.</p> <ol> -<li>The <a href="/documentation/latest/testing-patterns/">testing patterns</a> page has some suggestions for writing test cases.</li> +<li>The <a href="/documentation/latest/./testing-patterns/">testing patterns</a> page has some suggestions for writing test cases.</li> </ol> </li> <li><p>Make your changes to the code (using whatever IDE/editor you choose) to actually fix the bug or implement the feature.</p> <ol> -<li>Before beginning, please read the <a href="/documentation/latest/c++-style-guide/">Mesos C++ Style Guide</a>. It is recommended to use the git pre-commit hook (<code>support/hooks/pre-commit</code>) to automatically check for style errors. See the hook script for instructions to enable it.</li> +<li>Before beginning, please read the <a href="/documentation/latest/./c++-style-guide/">Mesos C++ Style Guide</a>. It is recommended to use the git pre-commit hook (<code>support/hooks/pre-commit</code>) to automatically check for style errors. See the hook script for instructions to enable it.</li> <li>Most of your changes will probably be to files inside of <code>BASE_MESOS_DIR</code></li> <li>From inside of the root Mesos directory: <code>./bootstrap</code> (Only required if building from git repository).</li> <li>To build, we recommend that you don’t build inside of the src directory. We recommend you do the following: @@ -154,7 +154,7 @@ <li>To execute a single unit test (helpful when trying to debug a test case failure), use something like: <code>make check GTEST_FILTER="HTTPTest.Delete"</code>.</li> </ol> </li> -<li><p>Divide your change into one or more Git commits. Each commit should represent a single logical (atomic) change to the Mesos source code: this makes your changes easier to review. For more information, see the <a href="/documentation/latest/effective-code-reviewing/">reviewer guidelines</a>.</p> +<li><p>Divide your change into one or more Git commits. Each commit should represent a single logical (atomic) change to the Mesos source code: this makes your changes easier to review. For more information, see the <a href="/documentation/latest/./effective-code-reviewing/">reviewer guidelines</a>.</p> <ol> <li>Try to avoid including other, unrelated cleanups (e.g., typo fixes or style nits) in the same commit that makes functional changes. While typo fixes are great, including them in the same commit as functional changes makes the commit history harder to read.</li> @@ -211,7 +211,7 @@ <h2>Style Guides</h2> <ul> -<li>For patches to the core, we ask that you follow the <a href="/documentation/latest/c++-style-guide/">Mesos C++ Style Guide</a>.</li> +<li>For patches to the core, we ask that you follow the <a href="/documentation/latest/./c++-style-guide/">Mesos C++ Style Guide</a>.</li> </ul> Modified: mesos/site/publish/documentation/latest/tools/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/tools/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/tools/index.html (original) +++ mesos/site/publish/documentation/latest/tools/index.html Mon Feb 8 16:43:52 2016 @@ -89,7 +89,7 @@ <ul> <li><a href="https://github.com/rayrod2030/collectd-mesos";>collectd plugin</a> to collect Mesos cluster metrics.</li> -<li><a href="/documentation/latest/deploy-scripts/">Deploy scripts</a> for launching a Mesos cluster on a set of machines.</li> +<li><a href="/documentation/latest/./deploy-scripts/">Deploy scripts</a> for launching a Mesos cluster on a set of machines.</li> <li><a href="https://github.com/everpeace/cookbook-mesos";>Chef cookbook by Everpeace</a> Install Mesos and configure master and slave. This cookbook supports installation from source or the Mesosphere packages.</li> <li><a href="https://github.com/mdsol/mesos_cookbook";>Chef cookbook by Mdsol</a> Application cookbook for installing the Apache Mesos cluster manager. This cookbook installs Mesos via packages provided by Mesosphere.</li> <li><a href="https://github.com/deric/puppet-mesos";>Puppet Module by Deric</a> This is a Puppet module for managing Mesos nodes in a cluster.</li> @@ -103,7 +103,7 @@ <p>If you want to hack on Mesos or write a new framework, these tools will help.</p> <ul> -<li><a href="/documentation/latest/clang-format/">clang-format</a> to automatically apply some of the style rules dictated by the <a href="/documentation/latest/c++-style-guide/">Mesos C++ Style Guide</a>.</li> +<li><a href="/documentation/latest/./clang-format/">clang-format</a> to automatically apply some of the style rules dictated by the <a href="/documentation/latest/./c++-style-guide/">Mesos C++ Style Guide</a>.</li> <li><a href="https://github.com/mesosphere/mesos-go";>Go Bindings and Examples</a> Write a Mesos framework in Go! Comes with an example scheduler and executor.</li> <li><a href="https://github.com/mesosphere/scala-sbt-mesos-framework.g8";>Mesos Framework giter8 Template</a> This is a giter8 template. The result of applying this template is a bare-bones Apache Mesos framework in Scala using SBT for builds and Vagrant for testing on a singleton cluster.</li> <li><a href="https://gist.github.com/guenter/7471695";>Scala Hello World</a> A simple Mesos “Hello World”: downloads and starts a web server on every node in the cluster.</li> Modified: mesos/site/publish/documentation/latest/upgrades/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/upgrades/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/upgrades/index.html (original) +++ mesos/site/publish/documentation/latest/upgrades/index.html Mon Feb 8 16:43:52 2016 @@ -88,7 +88,7 @@ <h2>Upgrading from 0.26.x to 0.27.x</h2> <ul> -<li><p>Mesos 0.27 introduces the concept of <em>implicit roles</em>. In previous releases, configuring roles required specifying a static whitelist of valid role names on master startup (via the <code>--roles</code> flag). In Mesos 0.27, if <code>--roles</code> is omitted, <em>any</em> role name can be used; controlling which principals are allowed to register as which roles should be done using <a href="/documentation/latest/authorization/">ACLs</a>. The role whitelist functionality is still supported but is deprecated.</p></li> +<li><p>Mesos 0.27 introduces the concept of <em>implicit roles</em>. In previous releases, configuring roles required specifying a static whitelist of valid role names on master startup (via the <code>--roles</code> flag). In Mesos 0.27, if <code>--roles</code> is omitted, <em>any</em> role name can be used; controlling which principals are allowed to register as which roles should be done using <a href="/documentation/latest/./authorization/">ACLs</a>. The role whitelist functionality is still supported but is deprecated.</p></li> <li><p>The Allocator API has changed due to the introduction of implicit roles. Custom allocator implementations will need to be updated. See <a href="https://issues.apache.org/jira/browse/MESOS-4000";>MESOS-4000</a> for more information.</p></li> <li><p>The <code>executorLost</code> callback in the Scheduler interface will now be called whenever the slave detects termination of a custom executor. This callback was never called in previous versions, so please make sure any framework schedulers can now safely handle this callback. Note that this callback may not be reliably delivered.</p></li> <li><p>The isolator <code>prepare</code> interface has been changed slightly. Instead of keeping adding parameters to the <code>prepare</code> interface, we decide to use a protobuf (<code>ContainerConfig</code>). Also, we renamed <code>ContainerPrepareInfo</code> to <code>ContainerLaunchInfo</code> to better capture the purpose of this struct. See <a href="https://issues.apache.org/jira/browse/MESOS-4240";>MESOS-4240</a> and <a href="https://issues.apache.org/jira/browse/MESOS-4282";>MESOS-4282</a> for more information. If you are an isolator module writer, you will have to adjust your isolator module according to the new interface and re-compile with 0.27.</p></li> Modified: mesos/site/publish/documentation/latest/versioning/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/versioning/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/latest/versioning/index.html (original) +++ mesos/site/publish/documentation/latest/versioning/index.html Mon Feb 8 16:43:52 2016 @@ -171,7 +171,7 @@ </ul> -<p>The detailed information about upgrading to a particular Mesos version would be posted <a href="/documentation/latest/upgrades/">here</a>.</p> +<p>The detailed information about upgrading to a particular Mesos version would be posted <a href="/documentation/latest/./upgrades/">here</a>.</p> <h3>Implementation Details</h3> Modified: mesos/site/publish/documentation/logging/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/logging/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/logging/index.html (original) +++ mesos/site/publish/documentation/logging/index.html Mon Feb 8 16:43:52 2016 @@ -92,7 +92,7 @@ degree of control Mesos has over the sou <li><a href="#Internal">Internal</a> - Master and Agent.</li> <li><a href="#Containers">Containers</a> - Executors and Tasks.</li> <li>External - Components launched outside of Mesos, like -Frameworks and <a href="/documentation/latest/high-availability/">ZooKeeper</a>. These are expected to +Frameworks and <a href="/documentation/latest/./high-availability/">ZooKeeper</a>. These are expected to implement their own logging solution.</li> </ul> @@ -102,7 +102,7 @@ implement their own logging solution.</l <p>The Mesos Master and Agent use the <a href="https://github.com/google/glog";>Google’s logging library</a>. For information regarding the command-line options used to configure this -library, see the <a href="/documentation/latest/configuration/">configuration documentation</a>. +library, see the <a href="/documentation/latest/./configuration/">configuration documentation</a>. Google logging options that are not explicitly mentioned there can be configured via environment variables.</p> @@ -118,12 +118,12 @@ original level after the given duration. <h2><a name="Containers"></a>Containers</h2> -<p>For background, see <a href="/documentation/latest/containerizer/">the containerizer documentation</a>.</p> +<p>For background, see <a href="/documentation/latest/./containerizer/">the containerizer documentation</a>.</p> <p>Mesos does not assume any structured logging for entities running inside containers. Instead, Mesos will store the stdout and stderr of containers into plain files (“stdout” and “stderr”) located inside -<a href="/documentation/latest/sandbox/#where-is-it">the sandbox</a>.</p> +<a href="/documentation/latest/./sandbox/#where-is-it">the sandbox</a>.</p> <p>In some cases, the default Container logger behavior of Mesos is not ideal:</p> @@ -166,7 +166,7 @@ specified maximum number of files is rea <p>The <code>LogrotateContainerLogger</code> can be loaded by specifying the library <code>liblogrotate_container_logger.so</code> in the -<a href="/documentation/latest/modules/#Invoking"><code>--modules</code> flag</a> when starting the Agent and by +<a href="/documentation/latest/./modules/#Invoking"><code>--modules</code> flag</a> when starting the Agent and by setting the <code>--container_logger</code> Agent flag to <code>org_apache_mesos_LogrotateContainerLogger</code>.</p> @@ -263,7 +263,7 @@ will continue to run.</p> <h3>Writing a Custom <code>ContainerLogger</code></h3> -<p>For basics on module writing, see <a href="/documentation/latest/modules/">the modules documentation</a>.</p> +<p>For basics on module writing, see <a href="/documentation/latest/./modules/">the modules documentation</a>.</p> <p>There are several caveats to consider when designing a new <code>ContainerLogger</code>:</p> @@ -278,7 +278,7 @@ that the container has exited. This pro <li>The <code>ContainerLogger</code> should not assume that containers have been launched with any specific <code>ContainerLogger</code>. The Agent may be restarted with a different <code>ContainerLogger</code>.</li> -<li>Each <a href="/documentation/latest/containerizer/">containerizer</a> running on an Agent uses its own +<li>Each <a href="/documentation/latest/./containerizer/">containerizer</a> running on an Agent uses its own instance of the <code>ContainerLogger</code>. This means more than one <code>ContainerLogger</code> may be running in a single Agent. However, each Agent will only run a single type of <code>ContainerLogger</code>.</li> Modified: mesos/site/publish/documentation/mesos-provisioner/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/mesos-provisioner/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/mesos-provisioner/index.html (original) +++ mesos/site/publish/documentation/mesos-provisioner/index.html Mon Feb 8 16:43:52 2016 @@ -197,8 +197,8 @@ backend tracked by MESOS-2971). For smal <h2>Related Docs</h2> -<p>For more information on the Mesos containerizer filesystem, namespace, and isolator features, visit <a href="/documentation/latest/mesos-containerizer/">Mesos Containerizer</a>. -For more information on launching Docker containers through the Docker containerizer, visit <a href="/documentation/latest/docker-containerizer/">Docker Containerizer</a>.</p> +<p>For more information on the Mesos containerizer filesystem, namespace, and isolator features, visit <a href="/documentation/latest/./mesos-containerizer/">Mesos Containerizer</a>. +For more information on launching Docker containers through the Docker containerizer, visit <a href="/documentation/latest/./docker-containerizer/">Docker Containerizer</a>.</p> </div> </div> Modified: mesos/site/publish/documentation/networking-for-mesos-managed-containers/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/networking-for-mesos-managed-containers/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/networking-for-mesos-managed-containers/index.html (original) +++ mesos/site/publish/documentation/networking-for-mesos-managed-containers/index.html Mon Feb 8 16:43:52 2016 @@ -231,7 +231,7 @@ before the address(es) are recycled.</p> there is an example implementation at https://github.com/mesosphere/net-modules.</p> <p>Once the network isolation module has been built into a shared dynamic library, -we can load it into Mesos Agent (see <a href="/documentation/latest/modules/">modules documentation</a> on +we can load it into Mesos Agent (see <a href="/documentation/latest/./modules/">modules documentation</a> on instructions for building and loading a module).</p> <h2>Enabling frameworks for IP-per-container capability</h2> Modified: mesos/site/publish/documentation/newbie-guide/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/newbie-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/newbie-guide/index.html (original) +++ mesos/site/publish/documentation/newbie-guide/index.html Mon Feb 8 16:43:52 2016 @@ -93,7 +93,7 @@ <h1>Contribution Process Overview</h1> -<p>The figure below shows a high-level process flow of the contribution delivery process for the Mesos open source distribution. Details of the process can be obtained from the [submitting-a-patch] (/documentation/latest/submitting-a-patch/) document of the Mesos distribution along with the Getting Started Guidance section of this document.</p> +<p>The figure below shows a high-level process flow of the contribution delivery process for the Mesos open source distribution. Details of the process can be obtained from the [submitting-a-patch] (/documentation/latest/./submitting-a-patch/) document of the Mesos distribution along with the Getting Started Guidance section of this document.</p> <p><img src="NewbieContributionOverview.jpg" alt="Newbie Document" /></p> @@ -135,7 +135,7 @@ <h1>Getting Started Guidance</h1> -<p>The following information will help provide additional guidance to execute the steps summarized in Contribution Process Overview described above as well as provide helpful hints when following the <a href="/documentation/latest/submitting-a-patch/">submitting-a-patch</a> document of the Mesos distribution.</p> +<p>The following information will help provide additional guidance to execute the steps summarized in Contribution Process Overview described above as well as provide helpful hints when following the <a href="/documentation/latest/./submitting-a-patch/">submitting-a-patch</a> document of the Mesos distribution.</p> <h2>Apache JIRA Account Pre-Requisite</h2> @@ -159,7 +159,7 @@ <h2>Download and Build Mesos</h2> -<p>Detailed steps are provided in the <a href="/documentation/latest/getting-started/">Mesos documentation</a> to download and build Mesos. When downloading the Mesos distribution there are 2 options to obtain the Mesos source code. For contributing, ensure that the Git option is used.</p> +<p>Detailed steps are provided in the <a href="/documentation/latest/./getting-started/">Mesos documentation</a> to download and build Mesos. When downloading the Mesos distribution there are 2 options to obtain the Mesos source code. For contributing, ensure that the Git option is used.</p> <h2>JIRA</h2> @@ -183,7 +183,7 @@ <p>There are a couple options to assign a work item: 1) create a new JIRA issue to work on or 2) identify an existing JIRA issue item to work on as described above. Whichever option is chosen there are several steps that should be followed when assigning yourself a JIRA ticket.</p> -<p>It is important to identify a shepherd before you assign a ticket to yourself. Working with a shepherd will reveal its priority at the current time. To identify a shepherd look at the <a href="/documentation/latest/committers/">maintainers</a> file to get an idea who to ask to shepherd your JIRA issue.\</p> +<p>It is important to identify a shepherd before you assign a ticket to yourself. Working with a shepherd will reveal its priority at the current time. To identify a shepherd look at the <a href="/documentation/latest/./committers/">maintainers</a> file to get an idea who to ask to shepherd your JIRA issue.\</p> <h2>JIRA Issue Solution Proposals</h2> @@ -196,11 +196,11 @@ </ol> -<p>Guidelines to consider when designing a solution can be found in the <a href="/documentation/latest/effective-code-reviewing/">effective-code-reviewing</a> document.</p> +<p>Guidelines to consider when designing a solution can be found in the <a href="/documentation/latest/./effective-code-reviewing/">effective-code-reviewing</a> document.</p> <h2>Making Changes</h2> -<p>After completing the solution review make the source code changes, build and successfully run relevant test cases. Guidelines for these processes can be found in the <a href="/documentation/latest/submitting-a-patch/">submitting-a-patch</a> and [mesos-c++style-guide] (/documentation/latest/c++-style-guide/).</p> +<p>After completing the solution review make the source code changes, build and successfully run relevant test cases. Guidelines for these processes can be found in the <a href="/documentation/latest/./submitting-a-patch/">submitting-a-patch</a> and [mesos-c++style-guide] (/documentation/latest/./c++-style-guide/).</p> <p>When creating and running test cases pay particular attention to race conditions. One recommendation is to run system tests multiple times. Below is a sample command to repeat the test 100 times.</p> @@ -210,7 +210,7 @@ <p>Submit your patch for review after you have come to an agreement with your shepherd on the proposed solution, made the modifications and successfully ran the test cases. Make sure your shepherd is added as a “reviewer” (among others) in the review. This will ensure that your reviews get processed.</p> -<p>When submitting a patch for review, include all testing done in the submission documentation. Follow the detailed steps found in the <a href="/documentation/latest/submitting-a-patch/">submitting-a-patch</a> document to submit a patch for review.</p> +<p>When submitting a patch for review, include all testing done in the submission documentation. Follow the detailed steps found in the <a href="/documentation/latest/./submitting-a-patch/">submitting-a-patch</a> document to submit a patch for review.</p> <h1>Advanced Level JIRA Items</h1> Modified: mesos/site/publish/documentation/operational-guide/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/operational-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/operational-guide/index.html (original) +++ mesos/site/publish/documentation/operational-guide/index.html Mon Feb 8 16:43:52 2016 @@ -85,7 +85,7 @@ <h2>Using a process supervisor</h2> -<p>Mesos uses a “<a href="https://en.wikipedia.org/wiki/Fail-fast";>fail-fast</a>” approach to error handling: if a serious error occurs, Mesos will typically exit rather than trying to continue running in a possibly erroneous state. For example, when Mesos is configured for <a href="/documentation/latest/high-availability/">high availability</a>, the leading master will abort itself when it discovers it has been partitioned away from the Zookeeper quorum. This is a safety precaution to ensure the previous leader doesn’t continue communicating in an unsafe state.</p> +<p>Mesos uses a “<a href="https://en.wikipedia.org/wiki/Fail-fast";>fail-fast</a>” approach to error handling: if a serious error occurs, Mesos will typically exit rather than trying to continue running in a possibly erroneous state. For example, when Mesos is configured for <a href="/documentation/latest/./high-availability/">high availability</a>, the leading master will abort itself when it discovers it has been partitioned away from the Zookeeper quorum. This is a safety precaution to ensure the previous leader doesn’t continue communicating in an unsafe state.</p> <p>To ensure that such failures are handled appropriately, production deployments of Mesos typically use a <em>process supervisor</em> (such as systemd or supervisord) to detect when Mesos processes exit. The supervisor can be configured to restart the failed process automatically and/or to notify the cluster operator to investigate the situation.</p> Modified: mesos/site/publish/documentation/oversubscription/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/oversubscription/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/oversubscription/index.html (original) +++ mesos/site/publish/documentation/oversubscription/index.html Mon Feb 8 16:43:52 2016 @@ -422,7 +422,7 @@ be above 6, or for 15 minutes will be ab seconds.</p> <p>To install a custom resource estimator and QoS controller, please refer to the -<a href="/documentation/latest/modules/">modules documentation</a>.</p> +<a href="/documentation/latest/./modules/">modules documentation</a>.</p> </div> </div> Modified: mesos/site/publish/documentation/persistent-volume/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/persistent-volume/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/persistent-volume/index.html (original) +++ mesos/site/publish/documentation/persistent-volume/index.html Mon Feb 8 16:43:52 2016 @@ -101,7 +101,7 @@ the volume. These rules exist to limit a volume containing sensitive data being offered to other frameworks in the cluster.</p> -<p>Please refer to the <a href="/documentation/latest/reservation/">Reservation</a> documentation for details +<p>Please refer to the <a href="/documentation/latest/./reservation/">Reservation</a> documentation for details regarding reservation mechanisms available in Mesos.</p> <p>Persistent volumes can be created by <strong>operators</strong> and authorized @@ -110,7 +110,7 @@ to authenticate/authorize the operations existing ACL mechanism. To use authorization with reserve, unreserve, create, and destroy operations, the Mesos master must be configured with the desired ACLs. For more information, see the -<a href="/documentation/latest/authorization/">authorization documentation</a>.</p> +<a href="/documentation/latest/./authorization/">authorization documentation</a>.</p> <ul> <li><code>Offer::Operation::Create</code> and <code>Offer::Operation::Destroy</code> messages are @@ -497,7 +497,7 @@ for the same role concurrently. In gener allowed to register in the same role, the operator should ensure that those frameworks are configured to collaborate with one another when using role-specific resources. For more information, see the discussion of -<a href="/documentation/latest/roles/#roles-multiple-frameworks">multiple frameworks in the same role</a>.</p></li> +<a href="/documentation/latest/./roles/#roles-multiple-frameworks">multiple frameworks in the same role</a>.</p></li> </ul> Modified: mesos/site/publish/documentation/powered-by-mesos/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/powered-by-mesos/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/powered-by-mesos/index.html (original) +++ mesos/site/publish/documentation/powered-by-mesos/index.html Mon Feb 8 16:43:52 2016 @@ -182,7 +182,7 @@ <h2>Software projects built on Mesos</h2> -<p>See the <a href="/documentation/latest/frameworks/">Mesos frameworks page</a> for a list of apps built on top of Mesos, and instructions on how to use them.</p> +<p>See the <a href="/documentation/latest/./frameworks/">Mesos frameworks page</a> for a list of apps built on top of Mesos, and instructions on how to use them.</p> <p>If you’re using Mesos, please add yourself to the list above, or email [email protected] and we’ll add you!</p> Modified: mesos/site/publish/documentation/quota/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/quota/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/quota/index.html (original) +++ mesos/site/publish/documentation/quota/index.html Mon Feb 8 16:43:52 2016 @@ -88,13 +88,13 @@ resources to frameworks even though they are beyond their fair share (e.g., when no other framework currently accepts these resources). There is no mechanism to lay away resources for future consumption in an entire cluster. Even though -<a href="/documentation/latest/reservation/">dynamic reservations</a> allow both operators and frameworks +<a href="/documentation/latest/./reservation/">dynamic reservations</a> allow both operators and frameworks to dynamically reserve resources on particular Mesos agents, it does not solve the above problem because any individual agents might fail.</p> <p>Since version 0.27.0 Mesos provides a mechanism to reserve a certain amount of resources in an entire cluster, i.e. not tied to a particular agent. <em>Quota</em> -allows operators to lay away resources for a given <a href="/documentation/latest/roles/">role</a>. These +allows operators to lay away resources for a given <a href="/documentation/latest/./roles/">role</a>. These resources cannot be hijacked by other roles and are guaranteed to be available for the role if there are enough resources in the cluster. Quota can be viewed as a cluster-wide dynamic reservation available for operators only.</p> @@ -157,7 +157,7 @@ in order to update a quota for a given r existing quota and then set a new one.</p> <p>The endpoint can optionally use authentication and authorization. See the -<a href="/documentation/latest/authentication/">authentication guide</a> for details.</p> +<a href="/documentation/latest/./authentication/">authentication guide</a> for details.</p> <p><a name="setRequest"></a></p> @@ -194,7 +194,7 @@ can use the following <code>jsonMessageB <p>A set request is only valid for roles for which no quota is currently set. However if the master is configured without an explicit -<a href="/documentation/latest/roles/">role whitelist</a> a set request can introduce new roles.</p> +<a href="/documentation/latest/./roles/">role whitelist</a> a set request can introduce new roles.</p> <p>In order to bypass the <a href="#capacityHeuristic">capacity heuristic</a> check the operator should set an optional <code>force</code> field:</p> @@ -311,10 +311,10 @@ possible to set quota for port resources endpoint, the following steps are triggered:</p> <ol> -<li><a href="/documentation/latest/authentication/">Authenticate</a> the HTTP request.</li> +<li><a href="/documentation/latest/./authentication/">Authenticate</a> the HTTP request.</li> <li>Parse and validate the request. See <a href="#setRequest">description of possible error codes</a>.</li> -<li><a href="/documentation/latest/authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> +<li><a href="/documentation/latest/./authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> <li>Run the <a href="#capacityHeuristic">capacity heuristic</a> if not disabled by <a href="#setRequest">the <code>force</code> flag</a>.</li> <li>Reliably store quota. See <a href="#failover">details on failover recovery</a>.</li> @@ -326,10 +326,10 @@ See <a href="#setRequest">description of The quota remove request processing is simpler and triggers the following steps:</p> <ol> -<li><a href="/documentation/latest/authentication/">Authenticate</a> the HTTP request.</li> +<li><a href="/documentation/latest/./authentication/">Authenticate</a> the HTTP request.</li> <li>Validate the request. See <a href="#removeRequest">description of potential error codes</a>.</li> -<li><a href="/documentation/latest/authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> +<li><a href="/documentation/latest/./authentication/">Authorize</a> the HTTP request if authorization is enabled.</li> <li>Reliably remove quota.</li> </ol> Modified: mesos/site/publish/documentation/release-guide/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/release-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/release-guide/index.html (original) +++ mesos/site/publish/documentation/release-guide/index.html Mon Feb 8 16:43:52 2016 @@ -184,7 +184,7 @@ added for any new features.</p></li> <blockquote><p>NOTE: <code>X.Y.Z</code> is based on <a href="http://semver.org/";>semantic versioning</a> scheme. <code>R</code> is release candidate version that starts with 1.</p></blockquote></li> -<li><p>Tag the release externally and deploy the corresponding JAR to the Apache maven repository. +<li><p>Tag the release externally and deploy the corresponding JAR to the <a href="https://repository.apache.org";>Apache maven repository</a>. It is recommended to use the <code>support/tag.sh</code> script to accomplish this.</p> <pre><code> $ ./support/tag.sh X.Y.Z R Modified: mesos/site/publish/documentation/reporting-a-bug/index.html URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/reporting-a-bug/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff ============================================================================== --- mesos/site/publish/documentation/reporting-a-bug/index.html (original) +++ mesos/site/publish/documentation/reporting-a-bug/index.html Mon Feb 8 16:43:52 2016 @@ -88,7 +88,7 @@ <ul> <li>We track all issues via Apache’s hosted <a href="https://issues.apache.org/jira/browse/MESOS";>JIRA issue tracker</a>, so if you don’t already have an account you’ll need to register for one. It’s quick and easy.</li> <li>A JIRA should be created for every task, feature, bug-fix, etc. This makes it easy to track progress.</li> -<li>If you are planning to work on the ticket, please assign the JIRA issue to yourself before you start working on it. This helps to avoid duplication of work and alerts anyone who is following that issue. It is highly encouraged to start a discussion with others in the community about how to solve the issue. The <a href="/documentation/latest/submitting-a-patch/">contribution guidelines</a> discuss how to contribute to Mesos development in more detail.</li> +<li>If you are planning to work on the ticket, please assign the JIRA issue to yourself before you start working on it. This helps to avoid duplication of work and alerts anyone who is following that issue. It is highly encouraged to start a discussion with others in the community about how to solve the issue. The <a href="/documentation/latest/./submitting-a-patch/">contribution guidelines</a> discuss how to contribute to Mesos development in more detail.</li> </ul>
