openstack
/
oslo-specs
Code Issues Proposed changes

Fix misspell word 

Change-Id: I86a99f7e1cdc792ae30f92a614dad8b255a1f86a
This commit is contained in:
Q.hongtao 2019-09-06 16:15:51 +08:00
parent c1da62c5f5
commit d0364e048b
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/juno/amqp10-driver-implementation.rst
View File

@ -165,7 +165,7 @@ users. It does however restrict choice.
Another alternative would be to choose a different protocol as the
basis of the new driver. MQTT is focused on a pub-sub pattern and
doesn't incorporate competing consumers as is required for the current
olso.messaging semantics. STOMP doesn't define interoperable
oslo.messaging semantics. STOMP doesn't define interoperable
mechanisms for request-response. Since two of the existing drivers use
earlier versions of AMQP, AMQP supports all the patterns needed and
AMQP is an open standard (now standardised under ISO) it seems a

2
specs/newton/policy-in-code.rst
View File

@ -125,7 +125,7 @@ will initially hold rulenames, rules, and descriptions.
Files to change:
* olso_policy/policy.py
* oslo_policy/policy.py
Alternatives
------------

2
specs/newton/policy-sample-generation.rst
View File

@ -52,7 +52,7 @@ deployers maintain and trim their policy files.
Files to change:
* olso_policy/generator.py (new file)
* oslo_policy/generator.py (new file)
* setup.cfg (register an entry point)
Alternatives