Repository: mesos Updated Branches: refs/heads/master 2f864bbda -> ae965b40a
Fixed style issues in CHANGELOG. Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/ae965b40 Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/ae965b40 Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/ae965b40 Branch: refs/heads/master Commit: ae965b40a407a64e97691655b481d083b2ec92a0 Parents: 2f864bb Author: Jie Yu <[email protected]> Authored: Sat Aug 16 22:58:13 2014 -0700 Committer: Jie Yu <[email protected]> Committed: Sat Aug 16 22:58:13 2014 -0700 ---------------------------------------------------------------------- CHANGELOG | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/ae965b40/CHANGELOG ---------------------------------------------------------------------- diff --git a/CHANGELOG b/CHANGELOG index 6612262..1a3a7d5 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -5,26 +5,26 @@ This release includes a lot of new cool features. The major new features are listed below: * Docker support in Mesos. - * Users now can launch executors/tasks within Docker containers. - * Mesos now supports running multiple containerizers simultaneously. The slave - can dynamically choose a containerizer to launch containers based on the - configuration of executors/tasks. + * Users now can launch executors/tasks within Docker containers. + * Mesos now supports running multiple containerizers simultaneously. The slave + can dynamically choose a containerizer to launch containers based on the + configuration of executors/tasks. * Container level network monitoring for mesos containerizer. - * Network statistics for each active container can be retrieved through the - /monitor/statistics.json endpoint on the slave. - * Completely transparent to the tasks running on the slave. No need to change - the service discovery mechanism for tasks. + * Network statistics for each active container can be retrieved through the + /monitor/statistics.json endpoint on the slave. + * Completely transparent to the tasks running on the slave. No need to change + the service discovery mechanism for tasks. * Framework authorization. - * Allows frameworks to (re-)register with authorized roles. - * Allows frameworks to launch tasks/executors as authorized users. - * Allows authorized principals to shutdown framework(s) through HTTP endpoint. + * Allows frameworks to (re-)register with authorized roles. + * Allows frameworks to launch tasks/executors as authorized users. + * Allows authorized principals to shutdown framework(s) through HTTP endpoint. * Framework rate limiting. - * In a multi-framework environment, this feature aims to protect the - throughput of high-SLA (e.g., production, service) frameworks by having the - master throttle messages from other (e.g., development, batch) frameworks. + * In a multi-framework environment, this feature aims to protect the + throughput of high-SLA (e.g., production, service) frameworks by having the + master throttle messages from other (e.g., development, batch) frameworks. * Enable building against installed third-party dependencies.
