openstack
/
neutron
Code Issues Proposed changes

Fixed docs job failure 

Removed one orphan reference of unclear value (pudb), and moved another
one into the text itself. This allows to pass gate with new sphinx.

Change-Id: I943d9b0904731ebcc4d3fd3a9b686fd08b03c48b
Closes-Bug: #1694614
This commit is contained in:
Ihar Hrachyshka 2017-05-31 07:39:11 -07:00
parent c430e9b8d4
commit 6cfe39708f
2 changed files with 4 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
TESTING.rst
View File

@ -626,6 +626,4 @@ TBD: how to do this with tox.
References
~~~~~~~~~~
.. [#pudb] PUDB debugger:
https://pypi.python.org/pypi/pudb
.. _file-based-sqlite: http://lists.openstack.org/pipermail/openstack-dev/2016-July/099861.html

12
doc/source/devref/provisioning_blocks.rst
View File

@ -32,8 +32,10 @@ When that entity has finishing provisioning, we just update the STATUS
directly to active. However, there are resources in Neutron that require
provisioning by multiple asynchronous entities before they are ready to
be used so managing the transition to the ACTIVE status becomes more
complex. To handle these cases, Neutron has the provisioning_blocks
module to track the entities that are still provisioning a resource.
complex. To handle these cases, Neutron has `the provisioning_blocks
module
<http://git.openstack.org/cgit/openstack/neutron/tree/neutron/db/provisioning_blocks.py>`_
to track the entities that are still provisioning a resource.
The main example of this is with ML2, the L2 agents and the DHCP agents.
When a port is created and bound to a host, it's placed in the DOWN
@ -151,9 +153,3 @@ the port is deleted or it is successful.
If an ML2 driver immediately places a bound port in the ACTIVE state
(e.g. after calling a backend in update_port_postcommit), this patch
will not have any impact on that process.
References
----------
.. [#] Provisioning Blocks Module: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/db/provisioning_blocks.py