openstack/cinder
Code Issues Proposed changes

Fix wrong links in Cinder

Browse Source 
Some docs links have changed.
We should update the wrong links in our codes.

Change-Id: I5046be23703192ed6fad805355c8c50b9b4a71c8
This commit is contained in:
yanghuichan
2017-09-06 15:14:27 +08:00
parent 2f5d69bf15
commit 8a490fb6df
7 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
HACKING.rst
View File

@@ -2,7 +2,7 @@ Cinder Style Commandments
========================= =========================
- Step 1: Read the OpenStack Style Commandments - Step 1: Read the OpenStack Style Commandments
https://docs.openstack.org/developer/hacking/ https://docs.openstack.org/hacking/latest/
- Step 2: Read on - Step 2: Read on
Cinder Specific Commandments Cinder Specific Commandments

2
cinder/tests/tempest/README.rst
View File

@@ -5,7 +5,7 @@ Tempest Integration for Cinder
This directory contains additional Cinder tempest tests. This directory contains additional Cinder tempest tests.
See the tempest plugin docs for information on using it: See the tempest plugin docs for information on using it:
http://docs.openstack.org/developer/tempest/plugin.html#using-plugins https://docs.openstack.org/tempest/latest/plugin.html#using-plugins
To run all tests from this plugin, install cinder into your environment. Then To run all tests from this plugin, install cinder into your environment. Then
from the tempest directory run:: from the tempest directory run::

2
doc/source/configuration/block-storage/drivers/coho-data-driver.rst
View File

@@ -40,7 +40,7 @@ following capabilities in the OpenStack Block Storage API
The QoS keys above must be created and associated with a volume type. The QoS keys above must be created and associated with a volume type.
For information about how to set the key-value pairs and associate For information about how to set the key-value pairs and associate
them with a volume type, see the `volume qos them with a volume type, see the `volume qos
<https://docs.openstack.org/developer/python-openstackclient/command-objects/volume-qos.html>`_ <https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/volume-qos.html>`_
section in the OpenStackClient command list. section in the OpenStackClient command list.
.. note:: .. note::

4
doc/source/configuration/block-storage/drivers/kaminario-driver.rst
View File

@@ -100,8 +100,8 @@ Cinder Driver for single FC or iSCSI backend.
scheduler_default_filters = DriverFilter,CapabilitiesFilter scheduler_default_filters = DriverFilter,CapabilitiesFilter
See following links for more information: See following links for more information:
`<https://docs.openstack.org/developer/cinder/scheduler-filters.html>`_ `<https://docs.openstack.org/cinder/latest/scheduler-filters.html>`_
`<https://docs.openstack.org/admin-guide/blockstorage-driver-filter-weighing.html>`_ `<https://docs.openstack.org/cinder/latest/admin/blockstorage-driver-filter-weighing.html>`_
#. Under the ``[DEFAULT]`` section, set the enabled_backends parameter #. Under the ``[DEFAULT]`` section, set the enabled_backends parameter
with the iSCSI or FC back-end group with the iSCSI or FC back-end group

2
doc/source/configuration/block-storage/drivers/solidfire-volume-driver.rst
View File

@@ -94,7 +94,7 @@ following capabilities in the OpenStack Block Storage API
The QoS keys above no longer require to be scoped but must be created and The QoS keys above no longer require to be scoped but must be created and
associated to a volume type. For information about how to set the key-value associated to a volume type. For information about how to set the key-value
pairs and associate them with a volume type, see the `volume qos pairs and associate them with a volume type, see the `volume qos
<https://docs.openstack.org/developer/python-openstackclient/command-objects/volume-qos.html>`_ <https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/volume-qos.html>`_
section in the OpenStackClient command list. section in the OpenStackClient command list.
.. note:: .. note::

4
doc/source/configuration/block-storage/schedulers.rst
View File

@@ -6,6 +6,6 @@ Block Storage service uses the ``cinder-scheduler`` service
to determine how to dispatch block storage requests. to determine how to dispatch block storage requests.
For more information, see `Cinder Scheduler Filters For more information, see `Cinder Scheduler Filters
<https://docs.openstack.org/developer/cinder/scheduler-filters.html>`_ <https://docs.openstack.org/cinder/latest/scheduler-filters.html>`_
and `Cinder Scheduler Weights and `Cinder Scheduler Weights
<https://docs.openstack.org/developer/cinder/scheduler-weights.html>`_. <https://docs.openstack.org/cinder/latest/scheduler-weights.html>`_.

8
doc/source/configuration/block-storage/volume-encryption.rst
View File

@@ -53,18 +53,18 @@ Key management access control
Special privileges can be assigned on behalf of an end user to allow Special privileges can be assigned on behalf of an end user to allow
them to manage their own encryption keys, which are required when them to manage their own encryption keys, which are required when
creating the encrypted volumes. The Barbican `Default Policy creating the encrypted volumes. The Barbican `Default Policy
<https://docs.openstack.org/developer/barbican/admin-guide-cloud/access_control.html#default-policy>`_ <https://docs.openstack.org/barbican/latest/admin/access_control.html#default-policy>`_
for access control specifies that only users with an ``admin`` or for access control specifies that only users with an ``admin`` or
``creator`` role can create keys. The policy is very flexible and ``creator`` role can create keys. The policy is very flexible and
can be modified. can be modified.
To assign the ``creator`` role, the admin must know the user ID, To assign the ``creator`` role, the admin must know the user ID,
project ID, and creator role ID. See `Assign a role project ID, and creator role ID. See `Assign a role
<https://docs.openstack.org/admin-guide/cli-manage-projects-users-and-roles.html#assign-a-role>`_ <https://docs.openstack.org/keystone/latest/admin/cli-manage-projects-users-and-roles.html#assign-a-role>`_
for more information. An admin can list existing roles and associated for more information. An admin can list existing roles and associated
IDs using the ``openstack role list`` command. If the creator IDs using the ``openstack role list`` command. If the creator
role does not exist, the admin can `create the role role does not exist, the admin can `create the role
<https://docs.openstack.org/admin-guide/cli-manage-projects-users-and-roles.html#create-a-role>`_. <https://docs.openstack.org/keystone/latest/admin/cli-manage-projects-users-and-roles.html#create-a-role>`_.
Create an encrypted volume type Create an encrypted volume type
@@ -153,7 +153,7 @@ the creator role in the following way:
For details, see the For details, see the
`Barbican Access Control page `Barbican Access Control page
<https://docs.openstack.org/developer/barbican/admin-guide-cloud/access_control.html>`_. <https://docs.openstack.org/barbican/latest/admin/access_control.html>`_.
.. note:: .. note::