openstack/zun
Code Issues Proposed changes

Replace curly quotes with straight quotes

Browse Source 
Change-Id: I3896bb9c44abc0c0c5585726cd1c21d97dbec8a7
This commit is contained in:
gaofei 2018-01-24 11:00:55 +08:00
parent 84dd0dc361
commit d52b59aff0
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-ref/source/parameters.yaml
View File

@ -173,7 +173,7 @@ addresses:
auto_remove:
description: |
enable auto-removal of the container on daemon side
when the container’s process exits.
when the container's process exits.
in: body
type: boolean
binary:

2
doc/source/contributor/mod-wsgi.rst
View File

@ -86,7 +86,7 @@ Create zun-uwsgi.ini file::
enable-threads = true
# Set the number of threads usually with the returns of command nproc
threads = 8
# Make sure the client doesn’t try to re-use the connection.
# Make sure the client doesn't try to re-use the connection.
add-header = Connection: close
# Set uid and gip to a appropriate user on your server. In many
# installations ``zun`` will be correct.

4
specs/container-SRIOV-networking.rst
View File

@ -33,8 +33,8 @@ These two dependencies are addressed under separated blueprint[1][2].
Kuryr driver is used for Zun container networking. Kuryr implements a
libnetwork remote network driver and maps its calls to OpenStack Neutron.
It works as a translator between libnetwork’s Container Network Model (CNM)
and Neutron’s networking model. Kuryr also acts as a libnetwork IPAM driver.
It works as a translator between libnetwork's Container Network Model (CNM)
and Neutron's networking model. Kuryr also acts as a libnetwork IPAM driver.
This design will try to use the existing functions provided by Kuryr and
identify the new requirements for Kuryr and Zun for the SR-IOV support.