From 88c6c17767fca8f97093ed639ba374252fbe059d Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Mon, 18 Apr 2016 12:20:47 +0100 Subject: [PATCH] Minor improvements to docs --- site/features.md | 13 +++++-------- site/introducing-weave.md | 6 +++--- 2 files changed, 8 insertions(+), 11 deletions(-) diff --git a/site/features.md b/site/features.md index c7efb19b..24225c2e 100644 --- a/site/features.md +++ b/site/features.md @@ -3,9 +3,6 @@ title: Feature Overview menu_order: 20 --- -The following is a comprehensive list and overview of all the features available in Weave -Net: - * [Virtual Ethernet Switch](#virtual-ethernet-switch) * [Fast Data Path](#fast-data-path) * [Seamless Docker Integration](#docker) @@ -42,7 +39,7 @@ tools and applications, developed over decades, can still be used to configure, secure, monitor, and troubleshoot a container network. -Broadcast and Multicast protocols can also be implemented +Broadcast and Multicast protocols can also be used over Weave Net. To start using Weave Net, see [Installing Weave Net](/site/installing-weave.md) @@ -66,7 +63,7 @@ See [Using Fast Datapath](/using-weave/fastdp.md) and Weave Net includes a [Docker API Proxy](/site/weave-docker-api.md), which can be used to start containers using the Docker [command-line interface](https://docs.docker.com/reference/commandline/cli/) or the [remote API](https://docs.docker.com/reference/api/docker_remote_api/), and attach them to the Weave network before they begin execution. -To use the proxy run: +To use the proxy, run: host1$ eval $(weave env) @@ -138,8 +135,8 @@ to communicate with each other but not with the containers of other applications. To isolate applications, Weave Net can make use of the -`isolation-through-subnets` technique. This common strategy - is an example of how with Weave many of your `on metal` +_isolation-through-subnets_ technique. This common strategy + is an example of how with Weave many "on metal" techniques can be used to deploy your applications to containers. @@ -179,7 +176,7 @@ mechanism which you can use in conjunction with or as an alternative to any other security technologies you have running alongside Weave. -Weave Net implements encryption and security using [Daniel J. Bernstein's NaCl library](http://nacl.cr.yp.to/index.html). +Weave Net implements encryption and security using the Go version of [Daniel J. Bernstein's NaCl library](http://nacl.cr.yp.to/index.html). For information on how to secure your Docker network connections, see [Securing Connections Across Untrusted Networks](/site/using-weave/security-untrusted-networks.md) and for a more technical discussion on how Weave implements encryption see, [Weave Encryption](/how-it-works/encryption.md) and [How Weave Implements Encryption](/site/how-it-works/encryption-implementation.md). diff --git a/site/introducing-weave.md b/site/introducing-weave.md index 5be2968d..67e12946 100644 --- a/site/introducing-weave.md +++ b/site/introducing-weave.md @@ -4,7 +4,7 @@ menu_order: 10 --- -Weave Net creates a virtual network that connects Docker containers deployed across multiple hosts and enables their automatic discovery. With Weave Net, portable microservices-based applications consisting of multiple containers can run anywhere: on one host, multiple hosts or even across cloud providers and data centers. Applications use the network just as if the containers were all plugged into the same network switch, without having to configure port mappings, or ambassador links. +Weave Net creates a virtual network that connects Docker containers across multiple hosts and enables their automatic discovery. With Weave Net, portable microservices-based applications consisting of multiple containers can run anywhere: on one host, multiple hosts or even across cloud providers and data centers. Applications use the network just as if the containers were all plugged into the same network switch, without having to configure port mappings, ambassadors or links. Services provided by application containers on the weave network can be exposed to the outside world, regardless of where they are running. Similarly, existing internal systems can be opened to accept connections from application containers irrespective of their location. @@ -52,9 +52,9 @@ Multicast addressing and routing is fully supported in Weave Net. Data can be se ###NAT Traversal -With Weave Net, deploy your peer-to-peer file sharing applications and voice over IP and take advantage of built-in NAT traversal. With Weave your app is portable, containerized and with its standardized approach to networking it gives you one less thing to worry about. +With Weave Net, deploy your applications - whether peer-to-peer file sharing, voice over IP or anything else - and take advantage of built-in NAT traversal. With Weave your app is portable, containerized and with its standardized approach to networking it gives you one less thing to worry about. -###Run with Anything: Kubernetes, Mesos, Amazon ECS +###Run with Anything: Kubernetes, Mesos, Amazon ECS, ... Weave Net is a good choice if you want one tool for everything. For example: In addition to Docker plugins, you can also use Weave as a Kubernetes plugin. You can also use Weave with Amazon ECS or with Mesos and Marathon. Refer to our Getting Started and Integration Guides for more information.