Merge "Update the documentation link for doc migration"

This commit is contained in:
Jenkins 2017-07-14 20:53:16 +00:00 committed by Gerrit Code Review
commit b6c0a8f80e
8 changed files with 19 additions and 19 deletions

View File

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

View File

@ -143,7 +143,7 @@ for identifying the error. Additionally, each exception in sahara contains a
unique identifier that allows the user to find extra information about that
error in the sahara logs. You can see an example of provisioning progress
information here:
http://developer.openstack.org/api-ref/data-processing/#event-log
https://developer.openstack.org/api-ref/data-processing/#event-log
This means that if you add some important phase for cluster provisioning to
the sahara code, it's recommended to add a new provisioning step for this
@ -178,7 +178,7 @@ keystone ``Session`` and auth plugin objects (for example, ``Token`` and
``Password``). Sahara is migrating all clients to use this authentication
methodology, where available. For more information on using sessions with
keystone, please see
http://docs.openstack.org/developer/keystoneauth/using-sessions.html
https://docs.openstack.org/keystoneauth/latest/using-sessions.html
Storing sensitive information
-----------------------------
@ -188,8 +188,8 @@ information (for example, login credentials) in the records for a cluster,
job, or some other record. Storing secret information this way is **not**
safe. To mitigate the risk of storing this information, sahara provides
access to the OpenStack Key Manager service (implemented by the
`barbican project <http://docs.openstack.org/developer/barbican/>`_) through
the `castellan library <http://docs.openstack.org/developer/castellan/>`_.
`barbican project <https://docs.openstack.org/barbican/latest/>`_) through
the `castellan library <https://docs.openstack.org/castellan/latest/>`_.
To utilize the external key manager, the functions in
``sahara.service.castellan.utils`` are provided as wrappers around the

View File

@ -15,7 +15,7 @@ submit requests to the sahara service must provide an authentication token in
the ``X-Auth-Token`` request header. A user can obtain the token by
authenticating to the Identity service endpoint. For more information about
the Identity service, please see the `keystone project developer documentation
<http://docs.openstack.org/developer/keystone/>`_
<https://docs.openstack.org/keystone/latest/>`_
With each request, a user must specify the keystone project
in the url path, for example: '/v1.1/{project_id}/clusters'. Sahara

View File

@ -95,9 +95,9 @@ change your ``/etc/resolv.conf`` file by adding appropriate ip addresses of
DNS servers (e.g. 1.1.1.1 and 2.2.2.2). Also the VMs with DNS servers should
be available from your local machine.
.. _Designate manual installation: http://docs.openstack.org/developer/designate/install/ubuntu-liberty.html
.. _Configuring OpenStack Networking with Designate: http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.html#configuring-openstack-networking-for-integration-with-an-external-dns-service
.. _Designate devstack: http://docs.openstack.org/developer/designate/devstack.html
.. _Designate manual installation: https://docs.openstack.org/project-install-guide/dns/ocata/
.. _Configuring OpenStack Networking with Designate: https://docs.openstack.org/neutron/latest/admin/config-dns-int.html#configuring-openstack-networking-for-integration-with-an-external-dns-service
.. _Designate devstack: https://docs.openstack.org/designate/latest/contributor/devstack.html
.. _data_locality_configuration:
@ -266,8 +266,7 @@ Distributed periodic tasks are based on Hash Ring implementation and the Tooz
library that provides group membership support for a set of backends. In order
to use periodic tasks distribution, the following steps are required:
* One of the `supported backends <http://docs.openstack.org/developer/tooz/
compatibility.html#driver-support>`_ should be configured and started.
* One of the `supported backends <https://docs.openstack.org/tooz/latest/user/compatibility.html#driver-support>`_ should be configured and started.
* Backend URL should be set in the sahara configuration file with the
``periodic_coordinator_backend_url`` parameter. For example, if the
ZooKeeper backend is being used:
@ -326,7 +325,7 @@ within the stack.
With a Key Manager service deployed on the stack, sahara must be configured
to enable the external storage of secrets. Sahara uses the
`castellan <http://docs.openstack.org/developer/castellan/>`_ library
`castellan <https://docs.openstack.org/castellan/latest/>`_ library
to interface with the OpenStack Key Manager service. This library provides
configurable access to a key manager. To configure sahara to use barbican as
the key manager, edit the sahara configuration file as follows:
@ -489,7 +488,7 @@ sufficient but if your keystone identity is backed by LDAP or similar
then domain specific configurations should be used to ensure sahara's
access. Please see the `Keystone documentation`_ for more information.
.. _Keystone documentation: http://docs.openstack.org/developer/keystone/configuration.html#domain-specific-drivers
.. _Keystone documentation: https://docs.openstack.org/keystone/latest/configuration.html#domain-specific-drivers
With the domain created, sahara's configuration file should be updated to
include the new domain name and any potential roles that will be needed. For
@ -641,7 +640,7 @@ access.
For more information on Cross Origin Resource Sharing, please review the `W3C
CORS specification`_.
.. _Administrator Guide: http://docs.openstack.org/admin-guide/cross_project_cors.html
.. _Administrator Guide: https://docs.openstack.org/oslo.middleware/latest/admin/cross-project-cors.html
.. _W3C CORS specification: http://www.w3.org/TR/cors/
Cleanup time for incomplete clusters

View File

@ -29,7 +29,7 @@ work.
This feature is supported by all plugins out of the box, and can be enabled
during the cluster template creation.
.. _Nova documentation: http://docs.openstack.org/developer/nova
.. _Nova documentation: https://docs.openstack.org/nova/latest/
Block Storage support
---------------------

View File

@ -9,10 +9,10 @@ from the bare metal performance with self-service resource provisioning.
1. Create a new OpenStack environment using Devstack as described
in the `Devstack Guide <http://docs.openstack.org/developer/devstack/>`_
in the `Devstack Guide <https://docs.openstack.org/devstack/latest/>`_
2. Install Ironic as described in the `Ironic Installation Guide
<http://docs.openstack.org/developer/ironic/deploy/install-guide.html>`_
<https://docs.openstack.org/ironic/latest/install/index.html>`_
3. Install Sahara as described in the `Sahara Installation Guide
<https://docs.openstack.org/sahara/latest/userdoc/installation.guide.html>`_

View File

@ -14,7 +14,8 @@
# limitations under the License.
# It's based on oslo.i18n usage in OpenStack Keystone project and
# recommendations from http://docs.openstack.org/developer/oslo.i18n/usage.html
# recommendations from https://docs.openstack.org/oslo.i18n/latest/
# user/usage.html
import oslo_i18n

View File

@ -88,7 +88,7 @@ commands = pip-missing-reqs -d --ignore-file=sahara/tests/* sahara
# It runs tests from the specified dir (default is sahara/tests)
# in interactive mode, so, you could use pbr for tests debug.
# Example usage: tox -e debug -- -t sahara/tests/unit some.test.path
# http://docs.openstack.org/developer/oslotest/features.html#debugging-with-oslo-debug-helper
# https://docs.openstack.org/oslotest/latest/features.html#debugging-with-oslo-debug-helper
commands = oslo_debug_helper -t sahara/tests/unit {posargs}
[testenv:bandit]