[ovs-dev] [PATCH 1/2] docs: Resolve broken URLs
Stephen Finucane
stephen at that.guru
Fri Dec 23 23:04:11 UTC 2016
These were found using the 'linkcheck' builder.
Signed-off-by: Stephen Finucane <stephen at that.guru>
Cc: Ben Pfaff <blp at ovn.org>
---
Documentation/faq/openflow.rst | 2 +-
Documentation/faq/vlan.rst | 4 ++--
Documentation/faq/vxlan.rst | 2 +-
Documentation/howto/dpdk.rst | 2 +-
Documentation/internals/contributing/coding-style.rst | 2 +-
.../internals/contributing/documentation-style.rst | 2 +-
.../internals/contributing/submitting-patches.rst | 6 +++---
Documentation/internals/security.rst | 17 +++++++++--------
Documentation/intro/install/general.rst | 4 ++--
Documentation/intro/install/windows.rst | 2 +-
Documentation/topics/testing.rst | 2 +-
Documentation/topics/windows.rst | 16 ++++++++--------
Documentation/tutorials/ovn-basics.rst | 4 ++--
13 files changed, 33 insertions(+), 32 deletions(-)
diff --git a/Documentation/faq/openflow.rst b/Documentation/faq/openflow.rst
index e9a3a74..abe89c6 100644
--- a/Documentation/faq/openflow.rst
+++ b/Documentation/faq/openflow.rst
@@ -523,7 +523,7 @@ Q: The "learn" action can't learn the action I want, can you improve it?
example:
- Resubmit to a table selected based on learned information, e.g. see:
- http://openvswitch.org/pipermail/discuss/2016-June/021694.html
+ https://mail.openvswitch.org/pipermail/ovs-discuss/2016-June/021694.html
- MAC learning in the middle of a pipeline, as described in
:doc:`/tutorials/ovs-advanced`
diff --git a/Documentation/faq/vlan.rst b/Documentation/faq/vlan.rst
index 0024ce8..3b09d89 100644
--- a/Documentation/faq/vlan.rst
+++ b/Documentation/faq/vlan.rst
@@ -206,8 +206,8 @@ but other hosts that are only on VLAN 0 can reach the IP address configured on
VLAN 9. What's going on?
A: `RFC 1122 section 3.3.4.2 "Multihoming Requirements"
- <https://tools.ietf.org/html/rfc1122#section-3.3.4.2>`__ describes two
- approaches to IP address handling in Internet hosts:
+ <https://tools.ietf.org/html/rfc1122>`__ describes two approaches to IP
+ address handling in Internet hosts:
- In the "Strong ES Model", where an ES is a host ("End System"), an IP
address is primarily associated with a particular interface. The host
diff --git a/Documentation/faq/vxlan.rst b/Documentation/faq/vxlan.rst
index 966f79e..c036ffd 100644
--- a/Documentation/faq/vxlan.rst
+++ b/Documentation/faq/vxlan.rst
@@ -31,7 +31,7 @@ Q: What's a VXLAN?
to solve the scaling challenges of VLAN networks in a multi-tenant
environment. VXLAN is an overlay network which transports an L2 network
over an existing L3 network. For more information on VXLAN, please see `RFC
- 7348 <http://tools.ietf.org/html/rfc7348>`__.
+ 7348 <https://tools.ietf.org/html/rfc7348>`__.
Q: How much of the VXLAN protocol does Open vSwitch currently support?
diff --git a/Documentation/howto/dpdk.rst b/Documentation/howto/dpdk.rst
index f55ae3b..e96ce56 100644
--- a/Documentation/howto/dpdk.rst
+++ b/Documentation/howto/dpdk.rst
@@ -224,7 +224,7 @@ tcpdump. Issue the following command to view the contents of ``pkts.pcap``::
$ tcpdump -r pkts.pcap
More information on the pdump app and its usage can be found in the `DPDK docs
-<http://dpdk.org/doc/guides/sample_app_ug/pdump.html>`__.
+<http://dpdk.org/doc/guides/tools/pdump.html>`__.
Jumbo Frames
------------
diff --git a/Documentation/internals/contributing/coding-style.rst b/Documentation/internals/contributing/coding-style.rst
index 8410064..e62f5e3 100644
--- a/Documentation/internals/contributing/coding-style.rst
+++ b/Documentation/internals/contributing/coding-style.rst
@@ -638,5 +638,5 @@ Python
------
When introducing new Python code, try to follow Python's `PEP 8
-<http://www.python.org/dev/peps/pep-0008/>`__ style. Consider running the
+<https://www.python.org/dev/peps/pep-0008/>`__ style. Consider running the
``pep8`` or ``flake8`` tool against your code to find issues.
diff --git a/Documentation/internals/contributing/documentation-style.rst b/Documentation/internals/contributing/documentation-style.rst
index ef0e0e7..ea41a07 100644
--- a/Documentation/internals/contributing/documentation-style.rst
+++ b/Documentation/internals/contributing/documentation-style.rst
@@ -365,4 +365,4 @@ Useful Links
- `Quick reStructuredText
<http://docutils.sourceforge.net/docs/user/rst/quickref.html>`__
-- `Sphinx Documentation <http://sphinx.readthedocs.org/en/latest/rest.html>`__
+- `Sphinx Documentation <http://sphinx.readthedocs.io/en/latest/rest.html>`__
diff --git a/Documentation/internals/contributing/submitting-patches.rst b/Documentation/internals/contributing/submitting-patches.rst
index 9fb7785..36e3b17 100644
--- a/Documentation/internals/contributing/submitting-patches.rst
+++ b/Documentation/internals/contributing/submitting-patches.rst
@@ -402,9 +402,9 @@ not want to use Git.
Patches should be inline in the email message. Some email clients corrupt
white space or wrap lines in patches. There are hints on how to configure many
email clients to avoid this problem on `kernel.org
-<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/email-clients.txt>`__.
-If you cannot convince your email client not to mangle patches, then sending
-the patch as an attachment is a second choice.
+<https://static.lwn.net/kerneldoc/process/email-clients.html>`__. If you
+cannot convince your email client not to mangle patches, then sending the patch
+as an attachment is a second choice.
Follow the style used in the code that you are modifying. :doc:`coding-style`
file describes the coding style used in most of Open vSwitch. Use Linux kernel
diff --git a/Documentation/internals/security.rst b/Documentation/internals/security.rst
index 8062211..da7b9b0 100644
--- a/Documentation/internals/security.rst
+++ b/Documentation/internals/security.rst
@@ -89,12 +89,12 @@ Consider reporting the information mentioned in :doc:`bugs`, where relevant.
Reporters may ask for a GPG key while initiating contact with the security team
to deliver more sensitive reports.
-The Linux kernel has its own vulnerability management process:
-https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SecurityBugs
-Handling of vulnerabilities that affect both the Open vSwitch tree and the
-upstream Linux kernel should be reported through both processes. Send your
-report as a single email to both the kernel and OVS security teams to allow
-those teams to most easily coordinate among themselves.
+The Linux kernel has `its own vulnerability management process
+<https://static.lwn.net/kerneldoc/admin-guide/security-bugs.html>`__. Handling
+of vulnerabilities that affect both the Open vSwitch tree and the upstream
+Linux kernel should be reported through both processes. Send your report as a
+single email to both the kernel and OVS security teams to allow those teams to
+most easily coordinate among themselves.
Step 2: Assessment
------------------
@@ -220,8 +220,9 @@ sections for the document include:
Certificate of Origin. It should also include other appropriate
tags, such as Acked-by tags obtained during review.
-CVE-2016-2074 is an example advisory document, available at:
-http://openvswitch.org/pipermail/announce/2016-March/000082.html
+`CVE-2016-2074
+<https://mail.openvswitch.org/pipermail/ovs-announce/2016-March/000082.html>`__
+is an example advisory document.
Step 3b: Fix
------------
diff --git a/Documentation/intro/install/general.rst b/Documentation/intro/install/general.rst
index 52327a0..f40ba91 100644
--- a/Documentation/intro/install/general.rst
+++ b/Documentation/intro/install/general.rst
@@ -137,7 +137,7 @@ If you are going to extensively modify Open vSwitch, consider installing the
following to obtain better warnings:
- "sparse" version 0.4.4 or later
- (http://www.kernel.org/pub/software/devel/sparse/dist/).
+ (https://www.kernel.org/pub/software/devel/sparse/dist/).
- GNU make.
@@ -171,7 +171,7 @@ simply install and run Open vSwitch you require the following software:
- For optional support of ingress policing on Linux, the "tc" program
from iproute2 (part of all major distributions and available at
- http://www.linux-foundation.org/en/Net:Iproute2).
+ https://wiki.linuxfoundation.org/networking/iproute2).
- Python 2.7. You must also have the Python six library.
diff --git a/Documentation/intro/install/windows.rst b/Documentation/intro/install/windows.rst
index 23a5a9b..9bd1813 100644
--- a/Documentation/intro/install/windows.rst
+++ b/Documentation/intro/install/windows.rst
@@ -97,7 +97,7 @@ The following explains the steps in some detail.
- OpenSSL
To get SSL support for Open vSwitch on Windows, you will need to install
- `OpenSSL for Windows <http://www.openssl.org/related/binaries.html>`__
+ `OpenSSL for Windows <https://wiki.openssl.org/index.php/Binaries>`__
Note down the directory where OpenSSL is installed (e.g.:
``C:/OpenSSL-Win32``) for later use.
diff --git a/Documentation/topics/testing.rst b/Documentation/topics/testing.rst
index 599e570..4b31966 100644
--- a/Documentation/topics/testing.rst
+++ b/Documentation/topics/testing.rst
@@ -355,7 +355,7 @@ travis-ci.
Instructions to setup travis-ci for your GitHub repository:
-1. Go to http://travis-ci.org/ and sign in using your GitHub ID.
+1. Go to https://travis-ci.org/ and sign in using your GitHub ID.
2. Go to the "Repositories" tab and enable the ovs repository. You may disable
builds for pushes or pull requests.
3. In order to avoid forks sending build failures to the upstream mailing list,
diff --git a/Documentation/topics/windows.rst b/Documentation/topics/windows.rst
index 81c1da5..6d7158e 100644
--- a/Documentation/topics/windows.rst
+++ b/Documentation/topics/windows.rst
@@ -499,12 +499,12 @@ driver.
References
----------
-.. [1] Hyper-V Extensible Switch http://msdn.microsoft.com/en-us/library/windows/hardware/hh598161(v=vs.85).aspx
-.. [2] Hyper-V Extensible Switch Extensions http://msdn.microsoft.com/en-us/library/windows/hardware/hh598169(v=vs.85).aspx
+.. [1] Hyper-V Extensible Switch https://msdn.microsoft.com/windows/hardware/drivers/network/hyper-v-extensible-switch
+.. [2] Hyper-V Extensible Switch Extensions https://msdn.microsoft.com/windows/hardware/drivers/network/hyper-v-extensible-switch-extensions
.. [3] DPIF Provider http://openvswitch.sourcearchive.com/documentation/1.1.0-1/dpif-provider_8h_source.html
-.. [4] Hyper-V Extensible Switch Components http://msdn.microsoft.com/en-us/library/windows/hardware/hh598163(v=vs.85).aspx
-.. [5] Windows Filtering Platform http://msdn.microsoft.com/en-us/library/windows/desktop/aa366510(v=vs.85).aspx
-.. [6] IP Helper http://msdn.microsoft.com/en-us/library/windows/hardware/ff557015(v=vs.85).aspx
-.. [7] How to Port Open vSwitch to New Software or Hardware http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob;f=PORTING
-.. [8] Netlink http://en.wikipedia.org/wiki/Netlink
-.. [9] epoll http://en.wikipedia.org/wiki/Epoll
+.. [4] Hyper-V Extensible Switch Components https://msdn.microsoft.com/windows/hardware/drivers/network/hyper-v-extensible-switch-components
+.. [5] Windows Filtering Platform https://msdn.microsoft.com/en-us/library/windows/desktop/aa366510(v=vs.85).aspx
+.. [6] IP Helper https://msdn.microsoft.com/windows/hardware/drivers/network/ip-helper
+.. [7] How to Port Open vSwitch to New Software or Hardware :doc:`porting`
+.. [8] Netlink https://en.wikipedia.org/wiki/Netlink
+.. [9] epoll https://en.wikipedia.org/wiki/Epoll
diff --git a/Documentation/tutorials/ovn-basics.rst b/Documentation/tutorials/ovn-basics.rst
index 8115edd..f7783cf 100644
--- a/Documentation/tutorials/ovn-basics.rst
+++ b/Documentation/tutorials/ovn-basics.rst
@@ -866,7 +866,7 @@ logical flows described above give a very good idea of what the flows look
like, though.
`This blog post
-<http://blog.russellbryant.net/2015/10/22/openstack-security-groups-using-ovn-acls/>`__
+<https://blog.russellbryant.net/2015/10/22/openstack-security-groups-using-ovn-acls/>`__
discusses OVN ACLs from an OpenStack perspective and also provides an example
of what the resulting OpenFlow flows look like.
@@ -962,7 +962,7 @@ should see it output to the local ports ``lport1`` and ``lport2``::
$ ovn/env8/packet2.sh
.. _ovn-architecture: http://openvswitch.org/support/dist-docs/ovn-architecture.7.html
-.. _Tutorial: https://github.com/openvswitch/ovs/blob/master/tutorial/tutorial.rst
+.. _Tutorial: :ref:`ovs-advanced`
.. _ovn-nb(5): http://openvswitch.org/support/dist-docs/ovn-nb.5.html
.. _ovn-sb(5): http://openvswitch.org/support/dist-docs/ovn-sb.5.html
.. _vtep(5): http://openvswitch.org/support/dist-docs/vtep.5.html
--
2.9.3
More information about the dev
mailing list