Merge pull request #2115 from weaveworks/issues/2114-docs-in-wordpress
Restructure `/site` to conform to Wordepress requirements
This commit is contained in:
commit
a897a7711c
66 files changed
+106
-6337
No files matched your search
-13
@@ -1,13 +0,0 @@
|
||||
language: python
|
||||
sudo: false
|
||||
|
||||
env:
|
||||
- PATH="${PATH}:${HOME}/gsutil"
|
||||
|
||||
install:
|
||||
- pip install pyopenssl
|
||||
- curl --silent --location https://storage.googleapis.com/pub/gsutil.tar.gz | tar xz -C $HOME
|
||||
- bin/setup-ci-secrets $encrypted_5ba036e89377_key $encrypted_5ba036e89377_iv
|
||||
|
||||
script:
|
||||
- 'test "${TRAVIS_PULL_REQUEST}" = "true" || site/build-and-publish.sh'
|
||||
@@ -1,3 +0,0 @@
|
||||
source 'https://rubygems.org'
|
||||
|
||||
gem 'jekyll'
|
||||
@@ -1,70 +0,0 @@
|
||||
GEM
|
||||
remote: https://rubygems.org/
|
||||
specs:
|
||||
blankslate (2.1.2.4)
|
||||
celluloid (0.16.0)
|
||||
timers (~> 4.0.0)
|
||||
classifier-reborn (2.0.3)
|
||||
fast-stemmer (~> 1.0)
|
||||
coffee-script (2.3.0)
|
||||
coffee-script-source
|
||||
execjs
|
||||
coffee-script-source (1.9.1)
|
||||
colorator (0.1)
|
||||
execjs (2.3.0)
|
||||
fast-stemmer (1.0.2)
|
||||
ffi (1.9.6)
|
||||
hitimes (1.2.2)
|
||||
jekyll (2.5.3)
|
||||
classifier-reborn (~> 2.0)
|
||||
colorator (~> 0.1)
|
||||
jekyll-coffeescript (~> 1.0)
|
||||
jekyll-gist (~> 1.0)
|
||||
jekyll-paginate (~> 1.0)
|
||||
jekyll-sass-converter (~> 1.0)
|
||||
jekyll-watch (~> 1.1)
|
||||
kramdown (~> 1.3)
|
||||
liquid (~> 2.6.1)
|
||||
mercenary (~> 0.3.3)
|
||||
pygments.rb (~> 0.6.0)
|
||||
redcarpet (~> 3.1)
|
||||
safe_yaml (~> 1.0)
|
||||
toml (~> 0.1.0)
|
||||
jekyll-coffeescript (1.0.1)
|
||||
coffee-script (~> 2.2)
|
||||
jekyll-gist (1.1.0)
|
||||
jekyll-paginate (1.1.0)
|
||||
jekyll-sass-converter (1.3.0)
|
||||
sass (~> 3.2)
|
||||
jekyll-watch (1.2.1)
|
||||
listen (~> 2.7)
|
||||
kramdown (1.5.0)
|
||||
liquid (2.6.2)
|
||||
listen (2.8.5)
|
||||
celluloid (>= 0.15.2)
|
||||
rb-fsevent (>= 0.9.3)
|
||||
rb-inotify (>= 0.9)
|
||||
mercenary (0.3.5)
|
||||
parslet (1.5.0)
|
||||
blankslate (~> 2.0)
|
||||
posix-spawn (0.3.10)
|
||||
pygments.rb (0.6.2)
|
||||
posix-spawn (~> 0.3.6)
|
||||
yajl-ruby (~> 1.2.0)
|
||||
rb-fsevent (0.9.4)
|
||||
rb-inotify (0.9.5)
|
||||
ffi (>= 0.5.0)
|
||||
redcarpet (3.2.2)
|
||||
safe_yaml (1.0.4)
|
||||
sass (3.4.13)
|
||||
timers (4.0.1)
|
||||
hitimes
|
||||
toml (0.1.2)
|
||||
parslet (~> 1.5.0)
|
||||
yajl-ruby (1.2.1)
|
||||
|
||||
PLATFORMS
|
||||
ruby
|
||||
|
||||
DEPENDENCIES
|
||||
jekyll
|
||||
@@ -1,13 +0,0 @@
|
||||
markdown: redcarpet
|
||||
|
||||
redcarpet:
|
||||
extensions: ['fenced_code_blocks', 'smart']
|
||||
|
||||
exclude:
|
||||
- 'Gemfile'
|
||||
- 'Gemfile.lock'
|
||||
- 'params.json'
|
||||
- 'build-and-publish.sh'
|
||||
|
||||
google:
|
||||
analytics: "UA-57286487-1"
|
||||
@@ -1,85 +0,0 @@
|
||||
<!-- FOOTER -->
|
||||
<div class="section footer">
|
||||
<div class="container">
|
||||
<div class="row clearfix">
|
||||
<div class="col-sm-3 col-md-2">
|
||||
<b>Company</b><br>
|
||||
<a href="http://weave.works/about.html">About Weave</a><br>
|
||||
<a href="http://weave.works/team.html">Meet the Team</a><br>
|
||||
<!-- <a href="#">Careers</a><br> -->
|
||||
<a href="http://blog.weave.works">Blog</a><br>
|
||||
<a href="http://weave.works/articles/">Learn More</a><br>
|
||||
</div>
|
||||
<div class="col-sm-3 col-md-2">
|
||||
<b>Community</b><br>
|
||||
<a href="http://weave.works/help/index.html#partners">Partners</a><br>
|
||||
<a href="http://github.com/weaveworks">Code</a><br>
|
||||
</div>
|
||||
<div class="col-sm-3 col-md-2">
|
||||
<b>Documentation</b><br>
|
||||
<a href="http://docs.weave.works">Docs</a><br>
|
||||
<a href="http://weave.works/guides/">Getting Started Guides</a><br>
|
||||
<a href="http://weave.works/help/index.html">Help and Support</a><br>
|
||||
<a href="http://blog.weave.works">Blog</a><br>
|
||||
</div>
|
||||
<div class="col-sm-3 col-md-2">
|
||||
<b>Get in Touch</b><br>
|
||||
<div class="hidden-md hidden-lg">
|
||||
<a href="mailto:help@weave.works">help@weave.works</a><br>
|
||||
</div>
|
||||
<a href="http://twitter.com/weaveworks">Twitter</a><br>
|
||||
<a href="http://github.com/weaveworks">Github</a><br>
|
||||
<a href="http://slideshare.net/weaveworks">Slideshare</a><br>
|
||||
<a href="https://www.linkedin.com/company/weaveworks">Linkedin</a><br>
|
||||
<a href="https://plus.google.com/+WeaveWorksInc/">GooglePlus</a><br>
|
||||
</div>
|
||||
<div class="col-md-3 hidden-xs hidden-sm">
|
||||
<b>Talk to a human</b>
|
||||
<div align="center">
|
||||
<br>
|
||||
<a href="mailto:help@weave.works" class="btn btn-lg">Drop us a line</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<br>
|
||||
<br>
|
||||
<div class="col-sm-4">
|
||||
<p class="copyright">© Weaveworks 2014 ‐ 2015</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
|
||||
<!--[if lt IE 9]>
|
||||
<script src="http://weave.works/js/html5shiv.js"></script>
|
||||
<![endif]-->
|
||||
|
||||
<script type="text/javascript">
|
||||
WebFontConfig = { fontdeck: { id: '56326' } };
|
||||
|
||||
(function() {
|
||||
var wf = document.createElement('script');
|
||||
wf.src = ('https:' == document.location.protocol ? 'https' : 'http') +
|
||||
'://ajax.googleapis.com/ajax/libs/webfont/1/webfont.js';
|
||||
wf.type = 'text/javascript';
|
||||
wf.async = 'true';
|
||||
var s = document.getElementsByTagName('script')[0];
|
||||
s.parentNode.insertBefore(wf, s);
|
||||
})();
|
||||
</script>
|
||||
<script type="text/javascript">
|
||||
piAId = '124932';
|
||||
piCId = '85570';
|
||||
|
||||
(function() {
|
||||
function async_load(){
|
||||
var s = document.createElement('script'); s.type = 'text/javascript';
|
||||
s.src = ('https:' == document.location.protocol ? 'https://pi' : 'http://cdn') + '.pardot.com/pd.js';
|
||||
var c = document.getElementsByTagName('script')[0]; c.parentNode.insertBefore(s, c);
|
||||
}
|
||||
if(window.attachEvent) { window.attachEvent('onload', async_load); }
|
||||
else { window.addEventListener('load', async_load, false); }
|
||||
})();
|
||||
</script>
|
||||
@@ -1,25 +0,0 @@
|
||||
<div class="section section-header navbaronly">
|
||||
<div class="navbar navbar-inverse">
|
||||
<div class="container">
|
||||
<div class="navbar-header">
|
||||
<a class="navbar-brand" href="http://weave.works/"><img src="http://www.weave.works/wp-content/uploads/2015/11/weave-logo-nav.png" class=" img-responsive" align="left"></a>
|
||||
</div>
|
||||
<div class="nav-wrapper">
|
||||
<ul class="nav navbar-nav navbar-right">
|
||||
<li>
|
||||
<a href="http://docs.weave.works">Docs</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://github.com/weaveworks">Code</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://blog.weave.works">Blog</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://weave.works/help/index.html">Help & Support</a>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,12 +0,0 @@
|
||||
{% if site.google.analytics %}
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
|
||||
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
|
||||
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
|
||||
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
|
||||
|
||||
ga('create', '{{ site.google.analytics }}', 'auto');
|
||||
ga('send', 'pageview');
|
||||
|
||||
</script>
|
||||
{% endif %}
|
||||
@@ -1,46 +0,0 @@
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<meta charset='utf-8' />
|
||||
<meta http-equiv="X-UA-Compatible" content="chrome=1" />
|
||||
|
||||
<title>weave {% if page.title %} | {{ page.title }} {% endif %}</title>
|
||||
|
||||
<meta name="description" content="Weave creates a virtual network that connects Docker containers deployed across multiple hosts and enables their automatic discovery.">
|
||||
<meta name="keywords" content="docker, networking, microservices, dns, software defined networking, linux, ubuntu, kubernetes, docker deployment, docker management, docker integration, docker mesos">
|
||||
<link rel="author" href="https://plus.google.com/+WeaveWorksInc"/>
|
||||
<link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.url }}">
|
||||
|
||||
<link href="{{ site.url }}/atom.xml" type="application/atom+xml" rel="alternate" title="{{ site.title }} Atom Feed">
|
||||
|
||||
<!-- Mobile Specific Metas
|
||||
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
|
||||
<!-- CSS
|
||||
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
|
||||
<link rel="stylesheet" type="text/css" href="assets/custom.css?v=1">
|
||||
|
||||
<!-- Favicon
|
||||
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
|
||||
<link rel="shortcut icon" type="image/png" href="http://weave.works/img/favicon.png">
|
||||
|
||||
{% include tracking.html %}
|
||||
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div class="content">
|
||||
{% include header-navbaronly.html %}
|
||||
<div class="container markdown-page">
|
||||
<div class="col-md-8 col-md-offset-2">
|
||||
{{ content }}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
{% include footer.html %}
|
||||
|
||||
</body>
|
||||
</html>
|
||||
File diff suppressed because it is too large.
Load diff
@@ -1,36 +0,0 @@
|
||||
#!/bin/sh -ex
|
||||
|
||||
cd $(dirname $0)/
|
||||
|
||||
## Use GCS until we set up Route53/CloudFront/S3
|
||||
|
||||
BRANCH=${TRAVIS_BRANCH:-`git rev-parse --abbrev-ref @`}
|
||||
COMMIT=${TRAVIS_COMMIT:-`git rev-parse @`}
|
||||
OUTPUT="weave/${BRANCH}/${COMMIT}"
|
||||
|
||||
if [ -n "${TRAVIS_TAG}" ]; then
|
||||
## Travis will run separate build for commit and tag pushes,
|
||||
OUTPUT="weave/${TRAVIS_TAG}"
|
||||
fi
|
||||
|
||||
if [ "${BRANCH}" = "latest_release_doc_updates" ]; then
|
||||
OUTPUT="weave/latest_release"
|
||||
fi
|
||||
|
||||
export BRANCH COMMIT OUTPUT
|
||||
|
||||
bundle install --path=.bundle
|
||||
bundle exec jekyll build --verbose
|
||||
|
||||
gsutil -m rsync -r -d _site "gs://docs.weave.works/${OUTPUT}"
|
||||
|
||||
echo "Published at http://docs.weave.works/${OUTPUT}"
|
||||
|
||||
if [ -z "${TRAVIS_TAG}" -a ! "${BRANCH}" = "latest_release_doc_updates" ]; then
|
||||
echo "<meta http-equiv=\"refresh\" content=\"0; url=http://docs.weave.works/${OUTPUT}\" />" \
|
||||
| gsutil \
|
||||
-h "Content-Type:text/html" \
|
||||
-h "Cache-Control:private, max-age=0, no-transform" \
|
||||
cp -a "public-read" - "gs://docs.weave.works/weave/${BRANCH}/index.html"
|
||||
gsutil -m rsync -r -d -p gs://docs.weave.works/${OUTPUT} gs://docs.weave.works/weave/${BRANCH}/head
|
||||
fi
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Building Weave Net
|
||||
layout: default
|
||||
menu_order: 160
|
||||
---
|
||||
|
||||
# Building Weave Net
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Encryption and Weave Net
|
||||
layout: default
|
||||
menu_order: 90
|
||||
---
|
||||
|
||||
|
||||
Weave Net peers
|
||||
[communicate with each other over both TCP and UDP](/site/router-topology/overview.md). This
|
||||
[communicate with each other over both TCP and UDP](/site/router-topology.md). This
|
||||
communication
|
||||
[can be encrypted](/site/using-weave/security-untrusted-networks.md).
|
||||
|
||||
@@ -4,7 +4,7 @@ layout: default
|
||||
---
|
||||
|
||||
This section describes some details of Weave Net's built-in
|
||||
[encryption](/site/encryption/crypto-overview.md):
|
||||
[encryption](/site/encryption.md):
|
||||
|
||||
* [Establishing the Ephemeral Session Key](#ephemeral-key)
|
||||
* [Key Generation](#csprng)
|
||||
|
||||
+5
-5
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Weave Net FAQ
|
||||
layout: default
|
||||
menu_order: 140
|
||||
---
|
||||
|
||||
|
||||
@@ -46,7 +46,7 @@ Once the peers detect the inconsistency, they log the error and drop the connect
|
||||
|
||||
Some peers may be able to communicate their claim to the others before they run `rmpeer` (i.e. it's a race), so what you can expect is a few cliques of peers that are still talking to each other, but repeatedly dropping attempted connections with peers in other cliques.
|
||||
|
||||
For more information on see [Address Allocation with IP Address Management (IPAM)](/site/ipam/overview-init-ipam.md) and also, [Starting, Stopping and Removing Peers](/site/ipam/stop-remove-peers-ipam.md)
|
||||
For more information on see [Address Allocation with IP Address Management (IPAM)](/site/ipam.md) and also, [Starting, Stopping and Removing Peers](/site/ipam/stop-remove-peers-ipam.md)
|
||||
|
||||
|
||||
###Q: What is the best practise for resetting a node that goes out of service?
|
||||
@@ -69,7 +69,7 @@ For more information about fast datapath see [How Fast Datapath Works](/site/fas
|
||||
|
||||
To view whether Weave is using fastdp or not, you can run, `weave status connections`
|
||||
|
||||
For more information on this command, see [Using Fast Datapath](/site/fastdp/using-fastdp.md)
|
||||
For more information on this command, see [Using Fast Datapath](/site/fastdp.md)
|
||||
|
||||
|
||||
###Q: Does encryption work with fastdp?
|
||||
@@ -78,7 +78,7 @@ Encryption does not work with fast datapath. If you enable encryption using the
|
||||
|
||||
You can however have a mixture of fast datapath connections over trusted links, as well as, encrypted connections over untrusted links.
|
||||
|
||||
See [Using Fast Datapath](/site/fastdp/using-fastdp.md) for more information
|
||||
See [Using Fast Datapath](/site/fastdp.md) for more information
|
||||
|
||||
###Q: Can I create multiple networks where containers can communicate on one network, but are isolated from containers on other networks?
|
||||
|
||||
@@ -88,6 +88,6 @@ Yes, of course! Weave allows you to run isolated networks and still allow open
|
||||
**See Also**
|
||||
|
||||
* [Troubleshooting Weave](/site/troublehooting.md)
|
||||
* [Troubleshooting IPAM](/site/ipam/troubleshooting.md)
|
||||
* [Troubleshooting IPAM](/site/ipam.md)
|
||||
* [Troubleshooting the Proxy](/site/weave-docker-api/using-proxy.md)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using Fast Datapath
|
||||
layout: default
|
||||
menu_order: 70
|
||||
---
|
||||
|
||||
|
||||
@@ -1,21 +1,21 @@
|
||||
---
|
||||
title: How Fast Datapath Works
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
|
||||
Weave Net implements an overlay network between Docker hosts. Without fast datapath enabled, each packet is encapsulated in a tunnel protocol header and sent to the destination host, where the header is removed. The Weave router is a user space process, which means that the packet follows a winding path in and out of the Linux kernel:
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
The fast datapath in Weave Net uses the Linux kernel's [Open vSwitch datapath module](https://www.kernel.org/doc/Documentation/networking/openvswitch.txt). This module enables the Weave Net router to tell the kernel how to process packets:
|
||||
|
||||

|
||||

|
||||
|
||||
Because Weave Net issues instructions directly to the kernel, context switches are decreased, and so by using `fast datapath` CPU overhead and latency is reduced. The packet goes straight from your application to the kernel, where the Virtual Extensible Lan (VXLAN) header is added (the NIC does this if it offers VXLAN acceleration). VXLAN is an IETF standard UDP-based tunneling protocol that enable you to use common networking tools like [Wireshark](https://www.wireshark.org/) to inspect the tunneled packets.
|
||||
|
||||

|
||||

|
||||
|
||||
Prior to version 1.2, Weave Net used a custom encapsulation format. Fast datapath uses VXLAN, and like Weave Net's custom encapsulation format, VXLAN is UDP-based, and therefore needs no special configuration with network infrastructure.
|
||||
|
||||
@@ -25,6 +25,6 @@ Prior to version 1.2, Weave Net used a custom encapsulation format. Fast datapat
|
||||
**See Also**
|
||||
|
||||
* [Deploying Applications to Weave](/site/using-weave/deploying-applications.md)
|
||||
* [Using Fast Datapath](/site/fastdp/using-fastdp.md)
|
||||
* [Using Fast Datapath](/site/fastdp.md)
|
||||
|
||||
|
||||
File renamed without changes.
File renamed without changes.
File renamed without changes.
+9
-9
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Weave Features
|
||||
layout: default
|
||||
menu_order: 20
|
||||
---
|
||||
|
||||
The following is a comprehensive list and overview of all the features available in Weave
|
||||
@@ -28,7 +28,7 @@ Net:
|
||||
* [Fault Tolerance](#fault-tolerance)
|
||||
|
||||
For step-by-step instructions on how to use Weave Net,
|
||||
see [Using Weave Net](/site/using-weave/intro-example.md)
|
||||
see [Using Weave Net](/site/using-weave.md)
|
||||
|
||||
###<a name="virtual-ethernet-switch"></a>Virtual Ethernet Switch
|
||||
|
||||
@@ -59,12 +59,12 @@ Fast datapath does not support encryption. For full details on configuring
|
||||
Weave when you have connections that traverse untrusted networks,
|
||||
see [Securing Connections Across Untrusted Networks](/site/using-weave/security-untrusted-networks.md) for more details.
|
||||
|
||||
See [Using Fast Datapath](/site/fastdp/using-fastdp.md) and
|
||||
See [Using Fast Datapath](/site/fastdp.md) and
|
||||
[How Fast Datapath Works](/site/fastdp/fastdp-how-it-works.md).
|
||||
|
||||
###<a name="docker"></a>Seamless Docker Integration (Weave Docker API Proxy)
|
||||
|
||||
Weave Net includes a [Docker API Proxy](/site/weave-docker-api/set-up-proxy.md), which can be
|
||||
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
|
||||
@@ -97,7 +97,7 @@ when there are network connectivity problems.
|
||||
>*Note:* The plugin is an *alternative* to the proxy, and therefore you do
|
||||
*not* need to run `eval $(weave env)` beforehand.
|
||||
|
||||
See [Using the Weave Docker Network Plugin](/site/plugin/weave-plugin-how-to.md) for more details.
|
||||
See [Using the Weave Docker Network Plugin](/site/plugin.md) for more details.
|
||||
|
||||
|
||||
###<a name="cniplugin"></a>Weave Network CNI Plugin
|
||||
@@ -114,13 +114,13 @@ Containers are automatically allocated a unique IP address. To view the addresse
|
||||
Instead of allowing Weave to automatically allocate addresses, an IP address and a network can be explicitly
|
||||
specified. See [How to Manually Specify IP Addresses and Subnets](/site/using-weave/manual-ip-address.md) for instructions.
|
||||
|
||||
For a discussion on how Weave Net uses IPAM, see [Automatic IP Address Management](/site/ipam/overview-init-ipam.md). And also review the
|
||||
[the basics of IP addressing](/site/ip-addresses/ip-addresses.md) for an explanation of addressing and private networks.
|
||||
For a discussion on how Weave Net uses IPAM, see [Automatic IP Address Management](/site/ipam.md). And also review the
|
||||
[the basics of IP addressing](/site/ip-addresses.md) for an explanation of addressing and private networks.
|
||||
|
||||
|
||||
###<a name="naming-and-discovery"></a>Naming and Discovery
|
||||
|
||||
Named containers are automatically registered in [weaveDNS](/site/weavedns/overview-using-weavedns.md),
|
||||
Named containers are automatically registered in [weaveDNS](/site/weavedns.md),
|
||||
and are discoverable by using standard, simple name lookups:
|
||||
|
||||
host1$ docker run -dti --name=service ubuntu
|
||||
@@ -184,7 +184,7 @@ Weave Net implements encryption and security using [Daniel J. Bernstein's NaCl l
|
||||
|
||||
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, [Using Encryption with Weave](/site/encryption/crypto-overview.md) and [How Weave Implements Encryption](/site/encryption/implementation.md)
|
||||
and for a more technical discussion on how Weave implements encryption see, [Using Encryption with Weave](/site/encryption.md) and [How Weave Implements Encryption](/site/encryption/implementation.md)
|
||||
|
||||
|
||||
###<a name="host-network-integration"></a>Host Network Integration
|
||||
|
||||
@@ -1,14 +0,0 @@
|
||||
---
|
||||
title: weave, the Docker network
|
||||
layout: default
|
||||
---
|
||||
|
||||
# Weave Documentation
|
||||
|
||||
* [Introduction, Installation and Example](https://github.com/weaveworks/weave#readme)
|
||||
* [Getting Started Guides](http://weave.works/guides/)
|
||||
* [Features](features.html)
|
||||
* [Troubleshooting](troubleshooting.html)
|
||||
* [Building](building.html)
|
||||
* [How it works](how-it-works.html)
|
||||
* [Latest release](https://github.com/weaveworks/weave/releases/tag/latest_release)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Installing Weave Net
|
||||
layout: default
|
||||
menu_order: 30
|
||||
---
|
||||
|
||||
|
||||
@@ -38,10 +38,10 @@ for the latest Weave AMIs and
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using Weave Net](/site/using-weave/intro-example.md)
|
||||
* [Using Weave Net](/site/using-weave.md)
|
||||
* [Getting Started Guides](http://www.weave.works/guides/)
|
||||
* [Features](/site/features.md)
|
||||
* [Troubleshooting](/site/troubleshooting.md)
|
||||
* [Building](/site/building.md)
|
||||
* [Using Weave with Systemd](/site/systemd.md)
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Introducing Weave Net
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Services provided by application containers on the weave network can be exposed
|
||||
|
||||
Weave Net simplifies setting up a container network. Because containers on a Weave network use standard port numbers, (for example MySQL’s default is port 3306), managing microservices is straightforward. Every container can find the IP of any other container using a simple DNS query on the container's name, and it can also communicate directly without NAT, without using port mappings or complicated ambassador linking. And best of all deploying a Weave container network requires zero changes to your application’s code.
|
||||
|
||||

|
||||

|
||||
|
||||
###Service Discovery
|
||||
|
||||
@@ -36,7 +36,7 @@ Weave Net can forward traffic between nodes, and it works even if the mesh netwo
|
||||
|
||||
Weave Net automatically chooses the fastest path between two hosts, offering near native throughput and latency, all without your intervention.
|
||||
|
||||
See [How Fast Datapath Works](/site/fastdp/using-fastdp.md) for more information.
|
||||
See [How Fast Datapath Works](/site/fastdp.md) for more information.
|
||||
|
||||
###Network Operations Friendly
|
||||
|
||||
@@ -59,7 +59,7 @@ With Weave Net, deploy your peer-to-peer file sharing applications and voice ove
|
||||
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.
|
||||
|
||||
For a complete list and description of Weave Net’s current feature set see, [Weave Net Features](/site/features/features.md)
|
||||
For a complete list and description of Weave Net’s current feature set see, [Weave Net Features](/site/features.md)
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: IP Addresses, Routes and Networks
|
||||
layout: default
|
||||
menu_order: 50
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configuring Weave to Explicitly Use an IP Range
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
The default configurations for both Weave Net and Docker use [Private
|
||||
@@ -39,4 +39,4 @@ Networks](https://en.wikipedia.org/wiki/Private_network). For example
|
||||
|
||||
**See Also**
|
||||
|
||||
* [IP Addresses, Routes and Networks](/site/ip-addresses/ip-addresses.md)
|
||||
* [IP Addresses, Routes and Networks](/site/ip-addresses.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Address Allocation with IP Address Management (IPAM)
|
||||
layout: default
|
||||
menu_order: 110
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Automatic Allocation Across Multiple Subnets
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
|
||||
@@ -62,6 +62,6 @@ for manual allocation.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam/overview-init-ipam.md)
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam.md)
|
||||
* [Isolating Applications on a Weave Network](/site/using-weave/application-isolation.md)
|
||||
* [Starting, Stopping and Removing Peers](/site/ipam/stop-remove-peers-ipam.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Starting, Stopping and Removing Peers
|
||||
layout: default
|
||||
menu_order: 20
|
||||
---
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ later rejoin the Weave network, the same IP address may be allocated
|
||||
twice.
|
||||
|
||||
Assume you had started the three peers in the
|
||||
[overview example](/site/ipam/overview-init-ipam.md), and then host3
|
||||
[overview example](/site/ipam.md), and then host3
|
||||
caught fire, you can go to one of the other hosts and run:
|
||||
|
||||
host1$ weave rmpeer host3
|
||||
@@ -37,6 +37,6 @@ status`.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam/overview-init-ipam.md)
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam.md)
|
||||
* [Automatic Allocation Across Multiple Subnets](/site/ipam/allocation-multi-ipam.md)
|
||||
* [Isolating Applications on a Weave Network](/site/using-weave/application-isolation.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting the IP Allocator
|
||||
layout: default
|
||||
menu_order: 30
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
{"name":"Weave","tagline":"The Docker Network","body":"","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."}
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using the Weave Net Docker Network Plugin
|
||||
layout: default
|
||||
menu_order: 80
|
||||
---
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ on any of the hosts, and they can all communicate with each other.
|
||||
|
||||
>**Warning!** It is inadvisable to attach containers to the Weave network using the Weave Docker Networking Plugin and Weave Docker API Proxy simultaneously. Such containers will end up with two Weave network interfaces and two IP addresses, which is rarely desirable. To ensure that the proxy is not being used, do not run eval $(weave env), or docker $(weave config).
|
||||
|
||||
In order to use Weave Net's [Service Discovery](/site/weavedns/overview-using-weavedns.md) you
|
||||
In order to use Weave Net's [Service Discovery](/site/weavedns.md) you
|
||||
must pass the additional arguments `--dns` and `-dns-search`, for
|
||||
which a helper is provided in the Weave script:
|
||||
|
||||
@@ -29,5 +29,5 @@ route, add the `--no-multicast-route` flag to `weave launch-plugin`.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using the Weave Net Docker Network Plugin](/site/plugin/weave-plugin-how-to.md)
|
||||
* [Using the Weave Net Docker Network Plugin](/site/plugin.md)
|
||||
* [How the Weave Network Plugin Works](/site/plugin/plugin-how-it-works.md)
|
||||
@@ -29,6 +29,6 @@ store, but the first part of
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using the Weave Net Docker Network Plugin](/site/plugin/weave-plugin-how-to.md)
|
||||
* [Using the Weave Net Docker Network Plugin](/site/plugin.md)
|
||||
* [Plugin Command-line Arguments](/site/plugin/plug-in-command-line.md)
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: How Weave Net Works
|
||||
layout: default
|
||||
menu_order: 100
|
||||
---
|
||||
|
||||
|
||||
@@ -43,7 +44,7 @@ changing topology. For example, in this network, peer 1 is connected
|
||||
directly to 2 and 3, but if 1 needs to send a packet to 4 or 5 it must
|
||||
first send it to peer 3:
|
||||
|
||||

|
||||

|
||||
|
||||
**See Also**
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Weave Net Interprets Network Topology
|
||||
layout: default
|
||||
menu_order: 20
|
||||
---
|
||||
|
||||
This section contains the following topics:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Weave Net Router Encapsulation
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
|
||||
@@ -61,4 +61,4 @@ MAC discovery.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [How Weave Net Inteprets Network Topology](/site/router-topology/network-topology.md)
|
||||
* [How Weave Net Inteprets Network Topology](/site/router-topology/network-topology.md)
|
||||
+2
-2
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using Weave with Systemd
|
||||
layout: default
|
||||
menu_order: 130
|
||||
---
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ context with the commands shown below. You will need to have the
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using Weave Net](/site/using-weave/intro-example.md)
|
||||
* [Using Weave Net](/site/using-weave.md)
|
||||
* [Getting Started Guides](http://www.weave.works/guides/)
|
||||
* [Features](/site/features.md)
|
||||
* [Troubleshooting](/site/troubleshooting.md)
|
||||
File renamed without changes.
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting Weave Net
|
||||
layout: default
|
||||
menu_order: 150
|
||||
---
|
||||
|
||||
|
||||
@@ -78,7 +78,7 @@ $ weave status
|
||||
````
|
||||
|
||||
The terms used here are explained further at
|
||||
[How Weave Net Works](/site/router-topology/overview.md).
|
||||
[How Weave Net Works](/site/router-topology.md).
|
||||
|
||||
* **Version** - shows the Weave Net version.
|
||||
|
||||
@@ -92,7 +92,7 @@ can be overridden by using the `--nickname` argument at `weave
|
||||
launch`.
|
||||
|
||||
* **Encryption** - indicates whether
|
||||
[encryption](/site/encryption/crypto-overview.md) is in use for communication
|
||||
[encryption](/site/encryption.md) is in use for communication
|
||||
between peers.
|
||||
|
||||
* **PeerDiscovery** - indicates whether
|
||||
@@ -305,5 +305,5 @@ and the container image versions as git hashes.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Troubleshooting IPAM](/site/ipam/troubleshooting.md)
|
||||
* [Troubleshooting IPAM](/site/ipam/troubleshooting-ipam.md)
|
||||
* [Troubleshooting the Proxy](/site/weave-docker-api/using-proxy.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using Weave Net - Example
|
||||
layout: default
|
||||
menu_order: 40
|
||||
---
|
||||
|
||||
Weave Net provides a simple to deploy networking solution for containerized apps. The example described and built upon throughout this `Using Weave Net` section describes how to manage a Weave container network using a sample application which consists of two simple `netcat` services deployed to containers on two separate hosts, and sometimes extended across three hosts.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Isolating Applications on a Weave Network
|
||||
layout: default
|
||||
menu_order: 30
|
||||
---
|
||||
|
||||
A single Weave network can host multiple, isolated applications where each application's containers are able
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploying Applications To Weave Net
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
This section contains the following topics:
|
||||
@@ -32,7 +32,7 @@ Where,
|
||||
/var/run/Docker.sock: permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?` then you likely need to be 'root' in order to connect to the Docker daemon. If so, run the above and all subsequent commands in a *single* root shell (e.g. one created with `sudo -s`). Do *not* prefix individual commands with `sudo`, since some commands modify environment entries and hence they all need to be executed from the same shell.
|
||||
|
||||
|
||||
>**Important!** if you are running the Weave Docker Network Plugin do not run `eval $(weave env)`. See [Using the Weave Net Docker Network Plugin](/site/pluing/weave-plugin-how-to.md) for more information.
|
||||
>**Important!** if you are running the Weave Docker Network Plugin do not run `eval $(weave env)`. See [Using the Weave Net Docker Network Plugin](/site/plugin.md) for more information.
|
||||
|
||||
Weave Net must be launched once per host. The relevant container images will be pulled down from Docker Hub on demand during `weave launch`.
|
||||
|
||||
@@ -108,5 +108,5 @@ Weave Net supports *any* protocol, and it doesn't have to be over TCP/IP. For ex
|
||||
**See Also**
|
||||
|
||||
* [Installing Weave Net](/site/installing-weave.md)
|
||||
* [Using Fastdp With Weave Net](/site/fastdp/using-fastdp.md)
|
||||
* [Using the Weave Net Docker Network Plugin](/site/plugin/weave-plugin-how-to.md)
|
||||
* [Using Fastdp With Weave Net](/site/fastdp.md)
|
||||
* [Using the Weave Net Docker Network Plugin](/site/plugin.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Dynamically Attaching and Detaching Applications
|
||||
layout: default
|
||||
menu_order: 40
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Adding and Removing Hosts Dynamically
|
||||
layout: default
|
||||
menu_order: 50
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Integrating a Host Network with Weave Net
|
||||
layout: default
|
||||
menu_order: 60
|
||||
---
|
||||
|
||||
Weave application networks can be integrated with an external host network, establishing connectivity between the host and with application containers running anywhere.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Manually Specifying the IP Address of a Container
|
||||
layout: default
|
||||
menu_order: 20
|
||||
---
|
||||
|
||||
Containers are automatically allocated an IP address that is unique across the Weave network. You can see which address was allocated by running, [`weave ps`](/site/troubleshooting.md#weave-status):
|
||||
@@ -10,7 +10,7 @@ Containers are automatically allocated an IP address that is unique across the W
|
||||
|
||||
Weave Net detects when a container has exited and releases its allocated addresses so they can be re-used by the network.
|
||||
|
||||
See the [Automatic IP Address Management](/site/ipam/overview-init-ipam.md) and also an explanation of [the basics of IP addressing](/site/ip-addresses/ip-addresses.md) for further details.
|
||||
See the [Automatic IP Address Management](/site/ipam.md) and also an explanation of [the basics of IP addressing](/site/ip-addresses.md) for further details.
|
||||
|
||||
Instead of allowing Weave Net to allocate IP addresses automatically (using IPAM), there may be instances where you need to control a particular container or a cluster by setting an IP address for it.
|
||||
|
||||
@@ -53,5 +53,5 @@ Individual IP addresses given to containers must, of course, be unique. If you p
|
||||
|
||||
* [Managing Services: Exporting, Importing, Binding and Routing](/site/using-weave/service-management.md)
|
||||
* [Configuring Weave to Explicitly Use an IP Range](/site/ip-addresses/configuring-weave.md)
|
||||
* [Automatic IP Address Management](/site/ipam/overview-init-ipam.md)
|
||||
* [Automatic IP Address Management](/site/ipam.md)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling Multi-Cloud, Multi-Hop Networking and Routing
|
||||
layout: default
|
||||
menu_order: 100
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Securing Connections Across Untrusted Networks
|
||||
layout: default
|
||||
menu_order: 80
|
||||
---
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ password at `weave launch` the router falls back to a slower
|
||||
|
||||
If some of your peers are co-located in a trusted network (for example within the boundary of your own data center) you can use the `--trusted-subnets` argument to `weave launch` to selectively disable data plane encryption as an optimization.
|
||||
|
||||
>**Note:** Both peers must consider the other to be in a trusted subnet for this to take place - if they do not agree, Weave Net [falls back to a slower method](/site/fastdp/using-fastdp.md) for transporting data between peers, since fast datapath does not support encryption.
|
||||
>**Note:** Both peers must consider the other to be in a trusted subnet for this to take place - if they do not agree, Weave Net [falls back to a slower method](/site/fastdp.md) for transporting data between peers, since fast datapath does not support encryption.
|
||||
|
||||
Be aware that:
|
||||
|
||||
@@ -45,5 +45,5 @@ Be aware that:
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using Encryption With Weave Net](/site/encryption/crypto-overview.md)
|
||||
* [Using Fast Datapath](/site/using-weave/using-fastdap.md)
|
||||
* [Using Encryption With Weave Net](/site/encryption.md)
|
||||
* [Using Fast Datapath](/site/using-weave.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Exposing Services to the Outside World
|
||||
layout: default
|
||||
menu_order: 70
|
||||
---
|
||||
|
||||
Services running in containers on a Weave network can be made
|
||||
@@ -35,5 +35,5 @@ Similar NAT rules to the above can be used to expose services not just to the ou
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using Weave Net](/site/using-weave/intro-example.md)
|
||||
* [Using Weave Net](/site/using-weave.md)
|
||||
* [Managing Services in Weave Net: Exporting, Importing, Binding and Routing](/site/using-weave/service-management.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Managing Services in Weave Net - Exporting, Importing, Binding and Routing
|
||||
layout: default
|
||||
menu_order: 90
|
||||
---
|
||||
|
||||
This section contains the following topics:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Setting Up The Weave Net Docker API Proxy
|
||||
layout: default
|
||||
menu_order: 60
|
||||
---
|
||||
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Using Automatic Discovery With the Weave Net Proxy
|
||||
layout: default
|
||||
menu_order: 30
|
||||
---
|
||||
|
||||
Containers launched via the proxy use [weaveDNS](/site/weavedns/overview-using-weavedns.md)
|
||||
Containers launched via the proxy use [weaveDNS](/site/weavedns.md)
|
||||
automatically if it is running when they are started -
|
||||
see the [weaveDNS usage](/site/weavedns/overview-using-weavedns.md#usage) section for an in depth
|
||||
see the [weaveDNS usage](/site/weavedns.md#usage) section for an in depth
|
||||
explanation of the behaviour and how to control it.
|
||||
|
||||
Typically, the proxy passes on container names as-is to weaveDNS
|
||||
|
||||
@@ -4,7 +4,7 @@ layout: default
|
||||
---
|
||||
|
||||
|
||||
If [automatic IP address allocation](/site/ipam/overview-init-ipam.md) is enabled in Weave Net (by default IPAM is enabled),
|
||||
If [automatic IP address allocation](/site/ipam.md) is enabled in Weave Net (by default IPAM is enabled),
|
||||
then containers started via the proxy are automatically assigned an IP address, *without having to specify any
|
||||
special environment variables or any other options*.
|
||||
|
||||
@@ -37,5 +37,5 @@ container with a blank `WEAVE_CIDR`, for example:
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam/overview-init-ipam.md)
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam.md)
|
||||
* [How to Manually Specify IP Addresses and Subnets](/site/using-weave/manual-ip-address.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Launching Containers With Weave Run (without the Proxy)
|
||||
layout: default
|
||||
menu_order: 50
|
||||
---
|
||||
|
||||
|
||||
@@ -41,6 +41,6 @@ containers using `docker start` and attaches them to the Weave network.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api/set-up-proxy.md)
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api.md)
|
||||
* [Securing Docker Communications With TLS](/site/weave-docker-api/securing-proxy.md)
|
||||
* [Name Resolution via `/etc/hosts`](/site/weave-docker-api/name-resolution-proxy.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Name resolution via `/etc/hosts`
|
||||
layout: default
|
||||
menu_order: 40
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Securing the Docker Communications With TLS
|
||||
layout: default
|
||||
menu_order: 20
|
||||
---
|
||||
|
||||
If you are [connecting to the docker daemon with
|
||||
@@ -55,4 +55,4 @@ proxy port.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api/set-up-proxy.md)
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting
|
||||
layout: default
|
||||
menu_order: 60
|
||||
---
|
||||
|
||||
The command
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using The Weave Docker API Proxy
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ modified to wait for the Weave network interface to become
|
||||
available.
|
||||
|
||||
When they are started via the Weave Net proxy, containers are
|
||||
[automatically assigned IP addresses](/site/ipam/overview-init-ipam.md) and connected to the
|
||||
[automatically assigned IP addresses](/site/ipam.md) and connected to the
|
||||
Weave network.
|
||||
|
||||
###Creating and Starting Containers with the Weave Net Proxy
|
||||
@@ -56,6 +56,6 @@ route, add the `--no-multicast-route` flag to `weave launch-proxy`.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api/set-up-proxy.md)
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api.md)
|
||||
* [Securing Docker Communications With TLS](securing-proxy.md)
|
||||
* [Launching Containers With Weave Run (without the Proxy)](/site/weave-docker-api/launching-without-proxy.md)
|
||||
File renamed without changes.
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using WeaveDNS
|
||||
layout: default
|
||||
menu_order: 120
|
||||
---
|
||||
|
||||
|
||||
@@ -44,5 +44,5 @@ disable weaveDNS itself, launch weave with the `--no-dns` option.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [How Weave Finds Containers](/site/weave-docker-api/how-works-weavedns.md)
|
||||
* [Load Balancing and Fault Resilience with WeaveDNS](/site/weave-docker-api/load-balance-fault-weavedns.md)
|
||||
* [How Weave Finds Containers](/site/weave-docker-api.md)
|
||||
* [Load Balancing and Fault Resilience with WeaveDNS](/site/weavedns/load-balance-fault-weavedns.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Weave Finds Containers
|
||||
layout: default
|
||||
menu_order: 10
|
||||
---
|
||||
|
||||
|
||||
@@ -54,6 +54,6 @@ $ sudo DOCKER_BRIDGE=someother weave run ...
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using WeaveDNS](/site/weavedns/overview-using-weavedns.md)
|
||||
* [Using WeaveDNS](/site/weavedns.md)
|
||||
* [Load Balancing with weaveDNS](/site/weavedns/load-balance-fault-weavedns.md)
|
||||
* [Managing Domain Entries](/site/weavedns/managing-domains-weavedns.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Load Balancing and Fault Resilience with weaveDNS
|
||||
layout: default
|
||||
menu_order: 20
|
||||
---
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ weaveDNS returns all addresses, in a random order, for each request.
|
||||
This provides a basic load balancing capability.
|
||||
|
||||
Expanding the
|
||||
[overview example](/site/weavedns/overview-using-weavedns.md), let us
|
||||
[overview example](/site/weavedns.md), let us
|
||||
start an additional `pingme` container on a 2nd host, and then run
|
||||
some ping tests...
|
||||
|
||||
@@ -47,6 +47,6 @@ container that is still alive.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [How Weave Finds Containers](/site/weave-docker-api/how-works-weavedns.md)
|
||||
* [How Weave Finds Containers](/site/weave-docker-api.md)
|
||||
* [Managing Domains](/site/weavedns/managing-domains-weavedns.md)
|
||||
* [Managing Domain Entries](/site/weavedns/managing-entries-weavedns.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Managing Domains
|
||||
layout: default
|
||||
menu_order: 30
|
||||
---
|
||||
|
||||
The following topics are discussed:
|
||||
@@ -46,6 +46,6 @@ link-local as per [RFC6762](https://tools.ietf.org/html/rfc6762),
|
||||
(though this is not strictly necessary).
|
||||
|
||||
|
||||
* [How Weave Finds Containers](/site/weave-docker-api/how-works-weavedns.md)
|
||||
* [Load Balancing and Fault Resilience with WeaveDNS](/site/weave-docker-api/load-balance-fault-weavedns.md)
|
||||
* [How Weave Finds Containers](/site/weave-docker-api.md)
|
||||
* [Load Balancing and Fault Resilience with WeaveDNS](/site/weavedns/load-balance-fault-weavedns.md)
|
||||
* [Managing Domain Entries](/site/weavedns/managing-entries-weavedns.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Managing Domain Entries
|
||||
layout: default
|
||||
menu_order: 40
|
||||
---
|
||||
|
||||
|
||||
@@ -82,6 +82,6 @@ weaveDNS instance will receive.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [How Weave Finds Containers](/site/weave-docker-api/how-works-weavedns.md)
|
||||
* [Load Balancing and Fault Resilience with WeaveDNS](/site/weave-docker-api/load-balance-fault-weavedns.md)
|
||||
* [How Weave Finds Containers](/site/weave-docker-api.md)
|
||||
* [Load Balancing and Fault Resilience with WeaveDNS](/site/weavedns/load-balance-fault-weavedns.md)
|
||||
* [Managing Domains](/site/weavedns/managing-domains-weavedns.md)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting and Present Limitations
|
||||
layout: default
|
||||
menu_order: 50
|
||||
---
|
||||
|
||||
|
||||
|
||||
File renamed without changes.
Reference in new issue
Block a user