Update URLs in documentation

Update URLs according to OpenStack document migration
BTW: Do some optimization as well (http -> https)

Change-Id: Ie9cc2c831186cd4dbbde08973032aece20540fc2
This commit is contained in:
Hangdong Zhang 2017-07-20 14:47:23 +08:00
parent d256ab054a
commit fde7ba8bfb
6 changed files with 15 additions and 15 deletions

View File

@ -27,14 +27,14 @@ Contributing to Openstack
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.
@ -86,7 +86,7 @@ The patches should include the following:
- Release note
- A reno entry needs to be included for every change:
http://docs.openstack.org/developer/reno/usage.html#creating-new-release-notes
https://docs.openstack.org/reno/latest/user/usage.html#creating-new-release-notes
Bug Fixes

View File

@ -24,4 +24,4 @@
collectd-ceilometer-plugin Style Commandments
=============================================
Read the OpenStack Style Commandments http://docs.openstack.org/developer/hacking/
Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/

View File

@ -32,12 +32,12 @@ This allows a more comprehensive set of platform telemetry to be made available
to OpenStack which enables service assurance, fault management and monitoring.
* Free software: Apache license
* Source: http://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin
* Source: https://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin
* Installation:
http://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin/tree/doc/source/installation.rst
* Bugs: http://bugs.launchpad.net/collectd-ceilometer-plugin
https://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin/tree/doc/source/installation.rst
* Bugs: https://bugs.launchpad.net/collectd-ceilometer-plugin
* Usage:
http://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin/tree/doc/source/usage.rst
https://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin/tree/doc/source/usage.rst
* Contact: E-mail the dev mailing list with the [collectd-ceilometer-plugin] tag
mailto:openstack-dev@lists.openstack.org?subject=[collectd-ceilometer-plugin]

View File

@ -39,7 +39,7 @@ Installation of DevStack
Follow the instructions provided in the following documentation to set up your
own DevStack.
http://docs.openstack.org/developer/devstack/guides/single-machine.html
https://docs.openstack.org/devstack/latest/guides/single-machine.html
Once DevStack is ready to be deployed, follow the configuration steps in the
next section to allow the installation of the plugin during deployment.

View File

@ -49,13 +49,13 @@ Please follow the steps below to create a heat template that enables auto-scalin
1. The instructions outlined in the link below will enable you to create a
simple template that will define your resource, i.e. the cloud application,
that you want to scale, e.g. OS::Nova::Server.
https://docs.openstack.org/developer/heat/template_guide/hot_guide.html
https://docs.openstack.org/heat/latest/template_guide/hot_guide.html
2. Define the scaling group for the above resource that you want to scale. At a
minimum the "desired_capacity", the "min_size" and the "max_size" and the
resource itself has to be specified.
For more information on this resource:
https://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::AutoScalingGroup
https://docs.openstack.org/heat/latest/template_guide/openstack.html#OS::Heat::AutoScalingGroup
::
@ -68,7 +68,7 @@ Please follow the steps below to create a heat template that enables auto-scalin
a separate policy can be defined for each alarm state; "alarm", "ok" and
"insufficient data".
For more information on this resource:
https://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ScalingPolicy
https://docs.openstack.org/heat/latest/template_guide/openstack.html#OS::Heat::ScalingPolicy
::
@ -134,7 +134,7 @@ an OS::Aodh::Alarm resource.
Define this resource with the ceilometer meter that you want to monitor and
the threshold you want the alarm to be triggered at.
For more information on this resource:
https://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Aodh::Alarm
https://docs.openstack.org/heat/latest/template_guide/openstack.html#OS::Aodh::Alarm
::
@ -151,7 +151,7 @@ OS::Aodh::GnocchiAggregationByMetricsAlarm resource.
Define this resource with the metric/s from the gnocchi plugin and the
threshold you want the alarm to be triggered on.
For more information on this resource:
https://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Aodh::GnocchiAggregationByMetricsAlarm
https://docs.openstack.org/heat/latest/template_guide/openstack.html#OS::Aodh::GnocchiAggregationByMetricsAlarm
::

View File

@ -39,7 +39,7 @@ Installation of Kolla
Please refer to this doc for instructions about how to install kolla.
http://docs.openstack.org/developer/kolla/quickstart.html
https://docs.openstack.org/kolla-ansible/latest/quickstart.html
For the simplest installation follow the instructions for evaluation and
development purposes.