openstack
/
tacker
Code Issues Proposed changes

Update and replace http with https for doc links in tacker 

1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links

Change-Id: Ia5d317646a97a5be09aa9131d0900261bee78824
This commit is contained in:
shangxiaobj 2017-08-11 00:39:56 -07:00 committed by ShangXiao
parent e31015cd75
commit a35d8a879d
5 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/contributor/development.environment.rst
View File

@ -27,7 +27,7 @@ to using Git and `this guide`_ for a tutorial on using Gerrit and Git for
code contribution to Openstack projects. code contribution to Openstack projects.
.. _this Git tutorial: http://git-scm.com/book/en/Getting-Started .. _this Git tutorial: http://git-scm.com/book/en/Getting-Started
.. _this guide: http://docs.openstack.org/infra/manual/developers.html#development-workflow .. _this guide: https://docs.openstack.org/infra/manual/developers.html#development-workflow
If you want to be able to run Tacker in a full OpenStack environment, If you want to be able to run Tacker in a full OpenStack environment,
you can use the excellent `DevStack`_ project to do so. There is a wiki page you can use the excellent `DevStack`_ project to do so. There is a wiki page

2
doc/source/contributor/tacker_functional_test.rst
View File

@ -118,7 +118,7 @@ Committing testcase and opening a review:
* Once testcase is added in local setup, commit the testcase and open for * Once testcase is added in local setup, commit the testcase and open for
review using below guidelines: review using below guidelines:
http://docs.openstack.org/infra/manual/developers.html https://docs.openstack.org/infra/manual/developers.html
Sample testcase: Sample testcase:
================ ================

4
doc/source/install/manual_installation.rst
View File

@ -26,14 +26,14 @@ Pre-requisites
============== ==============
1). Ensure that OpenStack components Keystone, Glance, Nova, Neutron, Heat and 1). Ensure that OpenStack components Keystone, Glance, Nova, Neutron, Heat and
Horizon are installed. Refer http://docs.openstack.org/ for installation of Horizon are installed. Refer https://docs.openstack.org/ for installation of
OpenStack on different Operating Systems. OpenStack on different Operating Systems.
2). Create client environment scripts "admin-openrc.sh" and "demo-openrc.sh" 2). Create client environment scripts "admin-openrc.sh" and "demo-openrc.sh"
for the admin and demo projects. Sample instructions for Ubuntu can be found for the admin and demo projects. Sample instructions for Ubuntu can be found
at link below: at link below:
http://docs.openstack.org/newton/install-guide-ubuntu/keystone-openrc.html#creating-the-scripts https://docs.openstack.org/newton/install-guide-ubuntu/keystone-openrc.html#creating-the-scripts
3). Ensure that the below required packages are installed on the system. 3). Ensure that the below required packages are installed on the system.

2
doc/source/user/enhanced_placement_awareness_usage_guide.rst
View File

@ -85,7 +85,7 @@ nova.conf file.
The SR-IOV feature enablement requires configuration on both the controller The SR-IOV feature enablement requires configuration on both the controller
and compute nodes. Please refer link similar to below for the appropriate and compute nodes. Please refer link similar to below for the appropriate
OpenStack release to setup SR-IOV: OpenStack release to setup SR-IOV:
http://docs.openstack.org/networking-guide/config-sriov.html https://docs.openstack.org/networking-guide/config-sriov.html
The CPU Pinning feature enablement requires configuring the nova.conf on The CPU Pinning feature enablement requires configuring the nova.conf on
compute nodes. It requires an entry similar to below: compute nodes. It requires an entry similar to below:

4
doc/source/user/vnf_component_usage_guide.rst
View File

@ -43,8 +43,8 @@ can be referred `here <https://github.com/openstack/heat-templates/blob/master/
hot/software-config/elements/README.rst>`_. The tool hot/software-config/elements/README.rst>`_. The tool
'tools/vnfc/build_image.sh' can be used to generate such a kind of image. 'tools/vnfc/build_image.sh' can be used to generate such a kind of image.
Currently VNFC feature works by using `heat software config <http://docs.openstack.org/ Currently VNFC feature works by using `heat software config <https://docs.openstack.org/heat/latest/
developer/heat/template_guide/openstack.html#OS::Heat::SoftwareConfig>`_ which template_guide/software_deployment.html#software-config-resources>`_ which
makes use of heat API. makes use of heat API.
So the glance images which has heat-config agents installed are only to be So the glance images which has heat-config agents installed are only to be