Update http link to https

update http link to https

Change-Id: I0d0d60f610f341d62a2c7186ee33ce783584a1b5
This commit is contained in:
taoguo 2018-11-12 20:02:25 +08:00
parent 064b35fa4e
commit 3a4d763131
11 changed files with 13 additions and 13 deletions

View File

@ -44,7 +44,7 @@ http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2
Nova supports to create a server with a block device mapping:
http://docs.openstack.org/api/openstack-compute/2/content/ext-os-block-device-mapping-v2-boot.html
https://docs.openstack.org/api/openstack-compute/2/content/ext-os-block-device-mapping-v2-boot.html
So, we should support the 'BlockDeviceMappings' for AWS::EC2::Instance
resource.

View File

@ -28,7 +28,7 @@ only through an AWS IAM resource type.
This was discussed on the mailing list in the thread beginning here:
http://lists.openstack.org/pipermail/openstack-dev/2015-January/055554.html
https://lists.openstack.org/pipermail/openstack-dev/2015-January/055554.html
Proposed change
===============

View File

@ -17,7 +17,7 @@ Problem description
Cinder provide encrypted volume creation by using encrypted volume type
as described in below wiki page:
http://docs.openstack.org/juno/config-reference/content/section_volume-encryption.html
https://docs.openstack.org/juno/config-reference/content/section_volume-encryption.html
Proposed change
===============

View File

@ -79,7 +79,7 @@ Work Items
Dependencies
============
[1] oslo-incubator module: http://git.openstack.org/cgit/openstack/oslo-incubator/tree/openstack/common/report
[1] oslo-incubator module: https://git.openstack.org/cgit/openstack/oslo-incubator/tree/openstack/common/report
[2] nova guru meditation reports: https://blueprints.launchpad.net/nova/+spec/guru-meditation-report
[3] blog about nova guru reports: https://www.berrange.com/posts/2015/02/19/nova-and-its-use-of-olso-incubator-guru-meditation-reports/
[4] oslo.reports repo: https://github.com/directxman12/oslo.reports

View File

@ -50,7 +50,7 @@ services in a given heat deployment:
- Default sorting direction is desc for created_at and updated_at and
for other allowed attributes, it will be asc.
- sort key value format to be aligned with API-WG
http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst
https://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst
* Filtering :

View File

@ -47,7 +47,7 @@ in a given stack:
- Default sorting direction is desc for created_at,
updated_at and asc for status, name.
- sort key value format to be aligned with API-WG
http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst
https://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/pagination_filter_sort.rst
* Filtering :

View File

@ -22,7 +22,7 @@ template based on the specified resource type, this is the functionality
exposed via the 'heat resource-type-template' command. And the link of the
API:
http://developer.openstack.org/api-ref-orchestration-v1.html
https://developer.openstack.org/api-ref-orchestration-v1.html
See resource_types/{type_name}/template API.

View File

@ -409,8 +409,8 @@ References
https://github.com/openstack/neutron-lbaas
https://github.com/openstack/heat
http://docs.openstack.org/developer/heat/template_guide/openstack.html
http://developer.openstack.org/api-ref-networking-v2-ext.html#lbaas-v2.0
https://docs.openstack.org/developer/heat/template_guide/openstack.html
https://developer.openstack.org/api-ref-networking-v2-ext.html#lbaas-v2.0
Alternatives
------------

View File

@ -17,7 +17,7 @@ Problem description
===================
Devstack support external plugins as documented here:
http://docs.openstack.org/developer/devstack/plugins.html
https://docs.openstack.org/developer/devstack/plugins.html
By enabling this plugin, we just need to properly set up devstack
local[rc] file to be able to setup heat.
A good example is ironic one:
@ -47,7 +47,7 @@ Proposed change
enable_plugin heat https://git.openstack.org/openstack/heat
The detailed introduction is here:
http://docs.openstack.org/developer/devstack/plugins.html
https://docs.openstack.org/developer/devstack/plugins.html
2. Steps to support devstack plugin in heat.

View File

@ -102,5 +102,5 @@ Implemention will follow in the style of
<https://blueprints.launchpad.net/heat/+spec/heat-glance-image-tag-support>_`.
For more information on Glance's image metadata capabilities, please see
`Image metadata <http://docs.openstack.org/image-guide/image-metadata.html>_`.
`Image metadata <https://docs.openstack.org/image-guide/image-metadata.html>_`.

View File

@ -26,7 +26,7 @@ Problem description
OpenStack neutron suppports Service Function Chaining (sfc) as an official
sub-project and more details are available at
http://docs.openstack.org/developer/networking-sfc/ . Heat does not provide
https://docs.openstack.org/developer/networking-sfc/ . Heat does not provide
resource plugins for Networking Service Function Chaining and this blueprint
is created to provide required plug-ins.