Merge "Replace http with https for doc links in kuryr-libnetwork"

CONTRIBUTING.rst

@@ -1,14 +1,14 @@
 If you would like to contribute to the development of OpenStack, you must
 follow the steps in this page:
 
-   http://docs.openstack.org/infra/manual/developers.html
+   https://docs.openstack.org/infra/manual/developers.html
 
 If you already have a good understanding of how the system works and your
 OpenStack accounts are set up, you can skip to the development workflow
 section of this documentation to learn how changes to OpenStack should be
 submitted for review via the Gerrit tool:
 
-   http://docs.openstack.org/infra/manual/developers.html#development-workflow
+   https://docs.openstack.org/infra/manual/developers.html#development-workflow
 
 Pull requests submitted through GitHub will be ignored.
 

HACKING.rst

@@ -1,4 +1,4 @@
 kuryr Style Commandments
 ===============================================
 
-Read the OpenStack Style Commandments http://docs.openstack.org/developer/hacking/
+Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/

README.rst

@@ -2,8 +2,8 @@
 Team and repository tags
 ========================
 
-.. image:: http://governance.openstack.org/badges/kuryr-libnetwork.svg
-    :target: http://governance.openstack.org/reference/tags/index.html
+.. image:: https://governance.openstack.org/tc/badges/kuryr-libnetwork.svg
+    :target: https://governance.openstack.org/tc/reference/tags/index.html
 
 .. Change things from this point on
 
@@ -29,7 +29,7 @@ K8s's CNI and so on, is maintained in separate Kuryr repo as a common library.
 
 
 * Free software: Apache license
-* Documentation: http://docs.openstack.org/developer/kuryr-libnetwork
+* Documentation: https://docs.openstack.org/kuryr-libnetwork/latest/
 * Source: http://git.openstack.org/cgit/openstack/kuryr-libnetwork
 * Bugs: http://bugs.launchpad.net/kuryr-libnetwork
 

contrib/docker/v2plugin/config.json

@@ -1,6 +1,6 @@
 {
     "Description": "kuryr-libnetwork plugin for Docker",
-    "Documentation": "http://docs.openstack.org/developer/kuryr-libnetwork",
+    "Documentation": "https://docs.openstack.org/kuryr-libnetwork/latest/",
     "Entrypoint": ["/opt/kuryr-libnetwork/contrib/docker/run_kuryr.sh"],
     "Interface" : {
         "Types": ["docker.networkdriver/1.0", "docker.ipamdriver/1.0"],

doc/source/devref/libnetwork_remote_driver_design.rst

@@ -51,7 +51,7 @@ Neutron resource Id's and Docker Id's (UUID's)
 
 4. libnetwork makes API calls against Kuryr
 
-5. Kuryr receives the requests and calls Neutron APIs with `Neutron client <http://docs.openstack.org/developer/python-neutronclient/>`_
+5. Kuryr receives the requests and calls Neutron APIs with `Neutron client <https://docs.openstack.org/python-neutronclient/latest/>`_
 
 6. Kuryr receives the responses from Neutron and compose the responses for
    libnetwork
@@ -366,7 +366,7 @@ Libnetwork User Workflow (with Kuryr as remote network driver) - Host Networking
 Mapping between the CNM and the Neutron's Networking Model
 ----------------------------------------------------------
 
-Kuryr communicates with Neutron via `Neutron client <http://docs.openstack.org/developer/python-neutronclient/>`_
+Kuryr communicates with Neutron via `Neutron client <https://docs.openstack.org/python-neutronclient/latest/>`_
 and bridges between libnetwork and Neutron by translating their networking models.
 The following table depicts the current mapping between libnetwork and Neutron models:
 

setup.cfg

@@ -5,7 +5,7 @@ description-file =
     README.rst
 author = OpenStack
 author-email = openstack-dev@lists.openstack.org
-home-page = http://docs.openstack.org/developer/kuryr-libnetwork
+home-page = https://docs.openstack.org/kuryr-libnetwork/latest/
 classifier =
     Environment :: OpenStack
     Intended Audience :: Information Technology