You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by vi...@apache.org on 2016/08/10 19:31:43 UTC
mesos git commit: Fixed typo for REX-Ray in 1.0 blog post.
Repository: mesos
Updated Branches:
refs/heads/master 044450208 -> f7bc7e470
Fixed typo for REX-Ray in 1.0 blog post.
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/f7bc7e47
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/f7bc7e47
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/f7bc7e47
Branch: refs/heads/master
Commit: f7bc7e470a64fde5b539adac810ccd1f77ebf119
Parents: 0444502
Author: Vinod Kone <vi...@gmail.com>
Authored: Wed Aug 10 12:31:13 2016 -0700
Committer: Vinod Kone <vi...@gmail.com>
Committed: Wed Aug 10 12:31:13 2016 -0700
----------------------------------------------------------------------
site/source/blog/2016-07-27-mesos-1-0-0-released.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/f7bc7e47/site/source/blog/2016-07-27-mesos-1-0-0-released.md
----------------------------------------------------------------------
diff --git a/site/source/blog/2016-07-27-mesos-1-0-0-released.md b/site/source/blog/2016-07-27-mesos-1-0-0-released.md
index 6252c4d..62a1dd3 100644
--- a/site/source/blog/2016-07-27-mesos-1-0-0-released.md
+++ b/site/source/blog/2016-07-27-mesos-1-0-0-released.md
@@ -36,7 +36,7 @@ With the addition of support for the Container Networking Interface ([CNI](https
One of the highlights of the new CNI support is the ability to now provide a single IP per container in Mesos. This is one of the most requested features that Mesos has ever had!! Since the CNI interface is widely supported by networking vendors, this gives Mesos tremendous flexibility in orchestrating containers on a wide variety of networking technologies (e.g, VxLAN, [DC/OS overlay](https://dcos.io/docs/1.8/administration/overlay-networks/), [Calico](https://www.projectcalico.org/), [Weave](https://github.com/weaveworks/weave-cni), [Flannel](https://github.com/containernetworking/cni/blob/master/Documentation/flannel.md)).
### Storage
-Starting from Mesos 1.0, we added **experimnental support** for external storage to Mesos. Before this feature, while users could use persistent volumes for running stateful services, there were some limitations. First, the users were not able to easily use non-local storage volumes. Second, data migrations for local persistent volumes had to be manually handled by operators. The newly added `docker/volume` isolator addresses these limitations. Currently, the isolator interacts with the Docker volume plugins (e.g., [Rexray](https://github.com/emccode/rexray), [Flocker](https://github.com/ClusterHQ/flocker), [Convoy](https://github.com/rancher/convoy)) using a tool called `dvdcli`. By speaking the Docker volume plugin API, Mesos containers can connect with external volumes from numerous storage providers (e.g., Amazon EBS, Ceph, EMC ScaleIO).
+Starting from Mesos 1.0, we added **experimnental support** for external storage to Mesos. Before this feature, while users could use persistent volumes for running stateful services, there were some limitations. First, the users were not able to easily use non-local storage volumes. Second, data migrations for local persistent volumes had to be manually handled by operators. The newly added `docker/volume` isolator addresses these limitations. Currently, the isolator interacts with the Docker volume plugins (e.g., [REX-Ray](https://github.com/emccode/rexray), [Flocker](https://github.com/ClusterHQ/flocker), [Convoy](https://github.com/rancher/convoy)) using a tool called `dvdcli`. By speaking the Docker volume plugin API, Mesos containers can connect with external volumes from numerous storage providers (e.g., Amazon EBS, Ceph, EMC ScaleIO).
### Security