Style FAQ questions with emphasis
This commit is contained in:
1 parent
82c9a88aa2
commit
3a2452baf6
1 file changed
+11
-11
+11
-11
@@ -5,19 +5,19 @@ menu_order: 100
|
||||
|
||||
|
||||
|
||||
###Q:How do I obtain the IP of a specific container when I'm using Weave?
|
||||
**Q:How do I obtain the IP of a specific container when I'm using Weave?**
|
||||
|
||||
You can use `weave ps <container>` to see the allocated address of a container on a Weave network.
|
||||
|
||||
See [Troubleshooting Weave - List attached containers](/site/troubleshooting.md#list-attached-containers).
|
||||
|
||||
|
||||
###Q: How do I expose one of my containers to the outside world?
|
||||
**Q: How do I expose one of my containers to the outside world?**
|
||||
|
||||
Exposing a container to the outside world is described in [Exposing Services to the Outside](/site/using-weave/service-export.md).
|
||||
|
||||
|
||||
###Q: My dockerized app needs to check the request of a an application that uses a static IP. Is it possible to manually change the IP of a container?
|
||||
**Q: My dockerized app needs to check the request of a an application that uses a static IP. Is it possible to manually change the IP of a container?**
|
||||
|
||||
|
||||
You can manually change the IP of a container using [Classless Inter-Domain Routing or CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
|
||||
@@ -25,7 +25,7 @@ You can manually change the IP of a container using [Classless Inter-Domain Rout
|
||||
For more information, refer to [Manually Specifying the IP Address of a Container](/site/using-weave/manual-ip-address.md).
|
||||
|
||||
|
||||
###Q:Can I connect my existing 'legacy' network with a Weave container network?
|
||||
**Q:Can I connect my existing 'legacy' network with a Weave container network?**
|
||||
|
||||
Yes you can.
|
||||
|
||||
@@ -36,7 +36,7 @@ The simplest way to accomplish this would be to run Weave on the host and then r
|
||||
You can read about exposing ports in [Service Exporting](/site/using-weave/service-export.md)
|
||||
|
||||
|
||||
###Q: Why am I seeing the same IP address assigned to two different containers on different hosts?
|
||||
**Q: Why am I seeing the same IP address assigned to two different containers on different hosts?**
|
||||
|
||||
Under normal circumstances, this should never happen, but it can occur if `weave forget` and `weave rmpeer` was run on more than one host.
|
||||
|
||||
@@ -49,14 +49,14 @@ Some peers may be able to communicate their claim to the others before they run
|
||||
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?
|
||||
**Q: What is the best practice for resetting a node that goes out of service?**
|
||||
|
||||
When a node goes out of service, the best option is to call `weave rmpeer` on one host and then `weave forget` on all the other hosts.
|
||||
|
||||
See [Starting, Stopping and Removing Peers](/site/ipam/stop-remove-peers-ipam.md) for an indepth discussion.
|
||||
See [Starting, Stopping and Removing Peers](/site/ipam/stop-remove-peers-ipam.md) for an in-depth discussion.
|
||||
|
||||
|
||||
###Q: What about Weave's performance? Are software defined network overlays just as fast as native networking?
|
||||
**Q: What about Weave's performance? Are software defined network overlays just as fast as native networking?**
|
||||
|
||||
All virtualization techniques have some overhead, and Weave's overhead is typically around 2-3%. Unless your system is completely bottlenecked on the network, you won't notice this during normal operation.
|
||||
|
||||
@@ -65,14 +65,14 @@ Weave Net also automatically uses the fastest datapath between two hosts. When W
|
||||
For more information about fast datapath see [How Fast Datapath Works](/site/fastdp/fastdp-how-it-works.md)
|
||||
|
||||
|
||||
###Q:How can I tell if Weave is using fast datapath (fastdp) or not?
|
||||
**Q:How can I tell if Weave is using fast datapath (fastdp) or not?**
|
||||
|
||||
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.md)
|
||||
|
||||
|
||||
###Q: Does encryption work with fastdp?
|
||||
**Q: Does encryption work with fastdp?**
|
||||
|
||||
Encryption does not work with fast datapath. If you enable encryption using the `--password` option to launch Weave (or you use the `WEAVE_PASSWORD` environment variable), fast datapath will by default be disabled.
|
||||
|
||||
@@ -80,7 +80,7 @@ You can however have a mixture of fast datapath connections over trusted links,
|
||||
|
||||
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?
|
||||
**Q: Can I create multiple networks where containers can communicate on one network, but are isolated from containers on other networks?**
|
||||
|
||||
Yes, of course! Weave allows you to run isolated networks and still allow open communications between individual containers from those isolated networks. You can find information on how to do this in [Application Isolation](/site/using-weave/application-isolation.md)
|
||||
|
||||
|
||||
Reference in new issue
Block a user