openstack/openstack-manuals
Code Issues Proposed changes

Merge "[networking] use https instead of http for docs.o.o"

Browse Source
This commit is contained in:
Jenkins 2017-01-27 15:32:01 +00:00 committed by Gerrit Code Review
commit d412ae92fe
17 changed files with 43 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/networking-guide/setup.cfg
View File

@ -3,7 +3,7 @@ name = openstacknetworkingguide
summary = OpenStack Networking Guide
author = OpenStack
author-email = openstack-docs@lists.openstack.org
home-page = http://docs.openstack.org/
home-page = https://docs.openstack.org/
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology

2
doc/networking-guide/source/config-auto-allocation.rst
View File

@ -31,7 +31,7 @@ topology creation. To perform this task, proceed with the following steps:
Setting up an external network is described in
`OpenStack Administrator Guide
<http://docs.openstack.org/admin-guide/networking-adv-features.html>`_.
<https://docs.openstack.org/admin-guide/networking-adv-features.html>`_.
Assuming the external network to be used for the auto-allocation feature
is named ``public``, make it the default external network
with the following command:

8
doc/networking-guide/source/config-lbaas.rst
View File

@ -15,7 +15,7 @@ There are two reference implementations of LBaaS v2.
The one is an agent based implementation with HAProxy.
The agents handle the HAProxy configuration and manage the HAProxy daemon.
Another LBaaS v2 implementation, `Octavia
<http://docs.openstack.org/developer/octavia/>`_, has a separate API and
<https://docs.openstack.org/developer/octavia/>`_, has a separate API and
separate worker processes that build load balancers within virtual machines on
hypervisors that are managed by the Compute service. You do not need an agent
for Octavia.
@ -25,8 +25,8 @@ for Octavia.
LBaaS v1 was removed in the Newton release. These links provide more
details about how LBaaS v1 works and how to configure it:
* `Load-Balancer-as-a-Service (LBaaS) overview <http://docs.openstack.org/admin-guide/networking-introduction.html#load-balancer-as-a-service-lbaas-overview>`__
* `Basic Load-Balancer-as-a-Service operations <http://docs.openstack.org/admin-guide/networking-adv-features.html#basic-load-balancer-as-a-service-operations>`__
* `Load-Balancer-as-a-Service (LBaaS) overview <https://docs.openstack.org/admin-guide/networking-introduction.html#load-balancer-as-a-service-lbaas-overview>`__
* `Basic Load-Balancer-as-a-Service operations <https://docs.openstack.org/admin-guide/networking-adv-features.html#basic-load-balancer-as-a-service-operations>`__
.. warning::
@ -138,7 +138,7 @@ The `Hands on Lab - Install and Configure OpenStack Octavia
session at the OpenStack Summit in Tokyo provides an overview of Octavia.
The DevStack documentation offers a `simple method to deploy Octavia
<http://docs.openstack.org/developer/devstack/guides/devstack-with-lbaas-v2.html>`_
<https://docs.openstack.org/developer/devstack/guides/devstack-with-lbaas-v2.html>`_
and test the service with redundant load balancer instances. If you already
have Octavia installed and configured within your environment, you can
configure the Network service to use Octavia:

40
doc/networking-guide/source/config-ml2.rst
View File

@ -104,7 +104,7 @@ To enable type drivers in the ML2 plug-in. Edit the
Update Link. See bug https://bugs.launchpad.net/openstack-manuals/+bug/1567792
For more details, see the
`Networking configuration options <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-plug-in-configuration-options>`__
`Networking configuration options <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-plug-in-configuration-options>`__
of Configuration Reference.
The following type drivers are available
@ -125,21 +125,21 @@ But only administrative (privileged) users can manage those
networks because they interface with the physical network infrastructure.
More information about provider networks see
:doc:`intro-os-networking` or the `OpenStack Administrator Guide
<http://docs.openstack.org/admin-guide/networking-adv-features.html#provider-networks>`__.
<https://docs.openstack.org/admin-guide/networking-adv-features.html#provider-networks>`__.
* Flat
The administrator needs to configure a list of physical network names that
can be used for provider networks.
For more details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-flat-type-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-flat-type-configuration-options>`__.
* VLAN
The administrator needs to configure a list of physical network names that
can be used for provider networks.
For more details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-vlan-type-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-vlan-type-configuration-options>`__.
* GRE
@ -168,7 +168,7 @@ within the allocation that an administrator or operator defines for
them. More information about project and provider networks see
:doc:`intro-os-networking`
or the `OpenStack Administrator Guide
<http://docs.openstack.org/admin-guide/networking-adv-features.html#provider-networks>`__.
<https://docs.openstack.org/admin-guide/networking-adv-features.html#provider-networks>`__.
Project network configurations are made in the
``/etc/neutron/plugins/ml2/ml2_conf.ini`` configuration file on the neutron
@ -179,21 +179,21 @@ server:
The administrator needs to configure the range of VLAN IDs that can be
used for project network allocation.
For more details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-vlan-type-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-vlan-type-configuration-options>`__.
* GRE
The administrator needs to configure the range of tunnel IDs that can be
used for project network allocation.
For more details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-gre-type-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-gre-type-configuration-options>`__.
* VXLAN
The administrator needs to configure the range of VXLAN IDs that can be
used for project network allocation.
For more details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-vxlan-type-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-vxlan-type-configuration-options>`__.
.. note::
Flat networks for project allocation are not supported. They only
@ -214,7 +214,7 @@ To enable mechanism drivers in the ML2 plug-in, edit the
Update Link. See bug https://bugs.launchpad.net/openstack-manuals/+bug/1567792
For more details, see the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-plug-in-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-plug-in-configuration-options>`__.
* Linux bridge
@ -232,7 +232,7 @@ For more details, see the
The administrator needs to define a list PCI hardware that shall be used
by OpenStack. For more details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-sr-iov-mechanism-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-sr-iov-mechanism-configuration-options>`__.
* MacVTap
@ -243,7 +243,7 @@ For more details, see the
The administrator can configure some optional configuration options. For more
details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-l2-population-mechanism-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-l2-population-mechanism-configuration-options>`__.
* Specialized
@ -283,7 +283,7 @@ resources. It typically runs on each Network Node and on each Compute Node.
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#open-vswitch-agent-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#open-vswitch-agent-configuration-options>`__.
* Linux bridge agent
@ -295,7 +295,7 @@ resources. It typically runs on each Network Node and on each Compute Node.
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#linux-bridge-agent-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#linux-bridge-agent-configuration-options>`__.
* SRIOV Nic Switch agent
@ -308,7 +308,7 @@ resources. It typically runs on each Network Node and on each Compute Node.
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#sr-iov-agent-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#sr-iov-agent-configuration-options>`__.
* MacVTap agent
@ -321,7 +321,7 @@ resources. It typically runs on each Network Node and on each Compute Node.
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-macvtap-mechanism-configuration-options>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-macvtap-mechanism-configuration-options>`__.
L3 agent
^^^^^^^^
@ -334,7 +334,7 @@ Configuration for the L3 agent is typically done in the
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#l3-agent>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#l3-agent>`__.
DHCP agent
^^^^^^^^^^
@ -348,7 +348,7 @@ Configuration for the DHCP agent is typically done in the
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#dhcp-agent>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#dhcp-agent>`__.
Metadata agent
^^^^^^^^^^^^^^
@ -361,7 +361,7 @@ Configuration for the Metadata agent is typically done in the
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#metadata-agent>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#metadata-agent>`__.
L3 metering agent
^^^^^^^^^^^^^^^^^
@ -374,7 +374,7 @@ Configuration for the L3 metering agent is typically done in the
you pass this configuration file as argument.
For a detailed list of configuration options, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#metering-agent>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#metering-agent>`__.
Security
--------
@ -384,7 +384,7 @@ L2 agents support some important security configurations.
* Security Groups
For more details, see the related section in the
`Configuration Reference <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#security-groups>`__.
`Configuration Reference <https://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#security-groups>`__.
* Arp Spoofing Prevention

2
doc/networking-guide/source/config-ovs-dpdk.rst
View File

@ -54,7 +54,7 @@ pages. This can be done through flavors. For example:
$ openstack flavor set m1.large --property hw:mem_page_size=large
For more information about the syntax for ``hw:mem_page_size``, refer to the
`Flavors <http://docs.openstack.org/admin-guide/compute-flavors.html>`__ guide.
`Flavors <https://docs.openstack.org/admin-guide/compute-flavors.html>`__ guide.
.. note::

2
doc/networking-guide/source/config-ovsfwdriver.rst
View File

@ -42,5 +42,5 @@ Enable the native OVS firewall driver
firewall_driver = openvswitch
For more information, see the `developer documentation
<http://docs.openstack.org/developer/neutron/devref/openvswitch_firewall.html>`_
<https://docs.openstack.org/developer/neutron/devref/openvswitch_firewall.html>`_
and the `video <https://www.youtube.com/watch?v=SOHeZ3g9yxM>`_.

4
doc/networking-guide/source/config-sfc.rst
View File

@ -65,7 +65,7 @@ path rendering.
:alt: Port chain model
See the `developer documentation
<http://docs.openstack.org/developer/networking-sfc/>`_ for more information.
<https://docs.openstack.org/developer/networking-sfc/>`_ for more information.
Resources
~~~~~~~~~
@ -220,7 +220,7 @@ HTTP (TCP) traffic flows from 192.168.1.11:1000 to 192.168.2.11:80.
This command requires additional options to successfully launch an
instance. See the
`CLI reference <http://docs.openstack.org/cli-reference/openstack.html>`_
`CLI reference <https://docs.openstack.org/cli-reference/openstack.html>`_
for more information.
Alternatively, you can launch each instance with one network interface and

2
doc/networking-guide/source/config-sriov.rst
View File

@ -379,7 +379,7 @@ Once configuration is complete, you can launch instances with SR-IOV ports.
There are two ways to attach VFs to an instance. You can create an SR-IOV
port or use the ``pci_alias`` in the Compute service. For more
information about using ``pci_alias``, refer to `nova-api configuration
<http://docs.openstack.org/admin-guide/compute-pci-passthrough.html#configure-nova-api-controller>`__.
<https://docs.openstack.org/admin-guide/compute-pci-passthrough.html#configure-nova-api-controller>`__.
SR-IOV with InfiniBand
~~~~~~~~~~~~~~~~~~~~~~

2
doc/networking-guide/source/config.rst
View File

@ -35,4 +35,4 @@ Configuration
.. note::
For general configuration, see the `Configuration Reference
<http://docs.openstack.org/newton/config-reference/>`_.
<https://docs.openstack.org/newton/config-reference/>`_.

2
doc/networking-guide/source/deploy-lb-provider.rst
View File

@ -83,7 +83,7 @@ Controller node
* Disable service plug-ins because provider networks do not require
any. However, this breaks portions of the dashboard that manage
the Networking service. See the
`Newton Install Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`__
`Newton Install Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`__
for more information.
.. code-block:: ini

2
doc/networking-guide/source/deploy-ovs-provider.rst
View File

@ -95,7 +95,7 @@ Controller node
any. However, this breaks portions of the dashboard that manage
the Networking service. See the
`Newton Install Tutorials and Guides
<http://docs.openstack.org/project-install-guide/newton>`__ for more
<https://docs.openstack.org/project-install-guide/newton>`__ for more
information.
.. code-block:: ini

2
doc/networking-guide/source/deploy.rst
View File

@ -38,7 +38,7 @@ total of five nodes. Each building block could also require additional
infrastructure or changes to existing infrastructure such as networks.
For basic configuration of prerequisites, see the
`Newton Install Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`__.
`Newton Install Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`__.
.. note::

2
doc/networking-guide/source/fwaas-v1-scenario.rst
View File

@ -115,7 +115,7 @@ Then, create a firewall that applies the policy.
* To add a single rule, use the insert-rule operation.
For more details, see `Networking command-line client
<http://docs.openstack.org/cli-reference/neutron.html>`_
<https://docs.openstack.org/cli-reference/neutron.html>`_
in the OpenStack Command-Line Interface Reference.
.. note::

2
doc/networking-guide/source/fwaas-v2-scenario.rst
View File

@ -113,7 +113,7 @@ Then, create a firewall that applies the policy.
* To add a single rule, use the insert-rule operation.
For more details, see `Networking command-line client
<http://docs.openstack.org/cli-reference/neutron.html>`_
<https://docs.openstack.org/cli-reference/neutron.html>`_
in the OpenStack Command-Line Interface Reference.
.. note::

4
doc/networking-guide/source/fwaas.rst
View File

@ -66,6 +66,6 @@ effect this.
\*\* This feature is planned for Ocata.
For further information, see `v1 configuration guide
<http://docs.openstack.org/newton/networking-guide/fwaas-v1-scenario.html>`_ or
<https://docs.openstack.org/newton/networking-guide/fwaas-v1-scenario.html>`_ or
`v2 configuration guide
<http://docs.openstack.org/newton/networking-guide/fwaas-v2-scenario.html>`_.
<https://docs.openstack.org/newton/networking-guide/fwaas-v2-scenario.html>`_.

4
doc/networking-guide/source/intro-basic-networking.rst
View File

@ -412,8 +412,8 @@ for many TCP-based services, as well as services that use other layer 4
protocols that employ ports. Registering a TCP port number is not required, but
registering a port number is helpful to avoid collisions with other
services. See `Appendix B. Firewalls and default ports
<http://docs.openstack.org/newton/config-reference/firewalls-default-ports.html>`_
of the `OpenStack Configuration Reference <http://docs.openstack.org/newton/config-reference/>`_
<https://docs.openstack.org/newton/config-reference/firewalls-default-ports.html>`_
of the `OpenStack Configuration Reference <https://docs.openstack.org/newton/config-reference/>`_
for the default TCP ports used by various services involved in an OpenStack
deployment.

4
doc/networking-guide/source/shared/deploy-config-neutron-common.txt
View File

@ -16,8 +16,8 @@
[agent]
# ...
See the `Installation Tutorials and Guides <http://docs.openstack.org>`_ and
`Configuration Reference <http://docs.openstack.org>`_ for your OpenStack
See the `Installation Tutorials and Guides <https://docs.openstack.org>`_ and
`Configuration Reference <https://docs.openstack.org>`_ for your OpenStack
release to obtain the appropriate additional configuration for the
``[DEFAULT]``, ``[database]``, ``[keystone_authtoken]``, ``[nova]``, and
``[agent]`` sections.