openstack
/
magnum
Code Issues Proposed changes

Merge "Add dns server access confirmation"

This commit is contained in:
Jenkins 2016-10-06 13:44:22 +00:00 committed by Gerrit Code Review
parent 3c10f07885 278f92e5f9
commit c0c1551d5c
2 changed files with 16 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/dev/quickstart.rst
View File

@ -228,6 +228,17 @@ Create a keypair for use with the ClusterTemplate::
test -f ~/.ssh/id_rsa.pub || ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa
nova keypair-add --pub-key ~/.ssh/id_rsa.pub testkey
Check a dns server can resolve a host name properly::
dig <server name> @<dns server> +short
For example::
$ dig www.openstack.org @8.8.8.8 +short
www.openstack.org.cdn.cloudflare.net.
104.20.64.68
104.20.65.68
Building a Kubernetes Cluster - Based on Fedora Atomic
======================================================

10
doc/source/troubleshooting-guide.rst
View File

@ -223,11 +223,11 @@ Check the following:
<https://github.com/openstack/magnum/blob/master/doc/source/magnum-proxy.rst>`_.
- Is the traffic blocked by the security group? Check the
`rules of security group
<http://docs.openstack.org/openstack-ops/content/security_groups.html>`_.
<http://docs.openstack.org/ops-guide/ops-user-facing-operations.html#security-groups>`_.
- Is your host NAT'ing your internal network correctly? Check your host
`iptables <http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#iptables>`_.
`iptables <http://docs.openstack.org/ops-guide/ops-network-troubleshooting.html#iptables>`_.
- Use *tcpdump* for `networking troubleshooting
<http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#tcpdump>`_.
<http://docs.openstack.org/ops-guide/ops-network-troubleshooting.html#tcpdump>`_.
You can run *tcpdump* on the interface *docker0, flannel0* and *eth0* on the
node and then run *ping* to see the path of the message from the container.
@ -245,7 +245,7 @@ If the name lookup fails, check the following:
specified by "dns-nameserver" in the ClusterTemplate.
- If you are using your own DNS server by specifying "dns-nameserver"
in the ClusterTemplate, is it reachable and working?
- More help on `DNS troubleshooting <http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#debugging_dns_issues>`_.
- More help on `DNS troubleshooting <http://docs.openstack.org/ops-guide/ops-network-troubleshooting.html#debugging-dns-issues>`_.
Kubernetes networking
@ -333,7 +333,7 @@ If the ping is not successful, check the following:
- Is Flannel running properly? check the `Running Flannel`_.
- Ping and try `tcpdump
<http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#tcpdump>`_
<http://docs.openstack.org/ops-guide/ops-network-troubleshooting.html#tcpdump>`_
on each network interface along the path between two nodes
to see how far the message is able to travel.
The message path should be as follows: