openstack
/
charm-specs
Code Issues Proposed changes

Replacing the HTTP protocal with HTTPS in internal-dns.rst. 

Change-Id: I22810cfff9136df83a880994e3810e08d3539e2e
This commit is contained in:
zhouxinyong 2018-11-13 23:39:32 +08:00
parent 275721c90c
commit 9fd3f8bb4c
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/newton/implemented/external-networking-redux.rst
View File

@ -145,4 +145,4 @@ References
---------- ----------
- https://bugs.launchpad.net/neutron/+bug/1491668 - https://bugs.launchpad.net/neutron/+bug/1491668
- http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html - https://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html

4
specs/queens/implemented/routed-provider-networks-neutron-charms.rst
View File

@ -52,10 +52,10 @@ Considerations for routed provider networks include:
* live migration and evacutation of instances (constrain to the same L2); * live migration and evacutation of instances (constrain to the same L2);
* DHCP and meta-data agent scheduling. * DHCP and meta-data agent scheduling.
A `nova spec <http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/neutron-routed-networks.html A `nova spec <https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/neutron-routed-networks.html
>`__ for routed provider networks contains a detailed overview of the >`__ for routed provider networks contains a detailed overview of the
implemenation details to address the above points, including usage of implemenation details to address the above points, including usage of
`generic resource pools. <http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/generic-resource-pools.html>`__ `generic resource pools. <https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/generic-resource-pools.html>`__
In order to account for IPv4 address ranges associated with segments Neutron In order to account for IPv4 address ranges associated with segments Neutron
uses Nova placement API to create IPv4 inventories and update them if needed. uses Nova placement API to create IPv4 inventories and update them if needed.

2
specs/rocky/backlog/charm-panko.rst
View File

@ -44,7 +44,7 @@ used to send data specified by publishers. So were
* Panko dispatcher `deprecation <https://docs.openstack.org/releasenotes/panko/unreleased.html#deprecation-notes>`__. * Panko dispatcher `deprecation <https://docs.openstack.org/releasenotes/panko/unreleased.html#deprecation-notes>`__.
* `Notes <https://docs.openstack.org/releasenotes/ceilometer/ocata.html#deprecation-notes>`__ on unneeded duplication of publishers and dispatchers. * `Notes <https://docs.openstack.org/releasenotes/ceilometer/ocata.html#deprecation-notes>`__ on unneeded duplication of publishers and dispatchers.
* A `discussion <http://lists.openstack.org/pipermail/openstack-dev/2017-April/115576.html>`__ on dispatchers vs publishers. * A `discussion <https://lists.openstack.org/pipermail/openstack-dev/2017-April/115576.html>`__ on dispatchers vs publishers.
This is instead done directly by publishers in Pike and Panko publisher is This is instead done directly by publishers in Pike and Panko publisher is
present in Panko's repository itself, not ceilometer repository. present in Panko's repository itself, not ceilometer repository.

2
specs/stein/backlog/charm-panko.rst
View File

@ -44,7 +44,7 @@ used to send data specified by publishers. So were
* Panko dispatcher `deprecation <https://docs.openstack.org/releasenotes/panko/unreleased.html#deprecation-notes>`__. * Panko dispatcher `deprecation <https://docs.openstack.org/releasenotes/panko/unreleased.html#deprecation-notes>`__.
* `Notes <https://docs.openstack.org/releasenotes/ceilometer/ocata.html#deprecation-notes>`__ on unneeded duplication of publishers and dispatchers. * `Notes <https://docs.openstack.org/releasenotes/ceilometer/ocata.html#deprecation-notes>`__ on unneeded duplication of publishers and dispatchers.
* A `discussion <http://lists.openstack.org/pipermail/openstack-dev/2017-April/115576.html>`__ on dispatchers vs publishers. * A `discussion <https://lists.openstack.org/pipermail/openstack-dev/2017-April/115576.html>`__ on dispatchers vs publishers.
This is instead done directly by publishers in Pike and Panko publisher is This is instead done directly by publishers in Pike and Panko publisher is
present in Panko's repository itself, not ceilometer repository. present in Panko's repository itself, not ceilometer repository.