openstack
/
kuryr-libnetwork
Code Issues Proposed changes

Merge "Fix typos in Kuryr files"

This commit is contained in:
Jenkins 2016-04-05 06:10:28 +00:00 committed by Gerrit Code Review
parent e53e6e5d59 7dba65042f
commit 5d687a4d66
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/devref/libnetwork_remote_driver_design.rst
View File

@ -296,7 +296,7 @@ Libnetwork User Workflow (with Kuryr as remote network driver) - Host Networking
::
$ CID=d7fcc280916a8b771d2375688b700b036519d92ba2989622627e641bdde6e646
$ sudo docker network disconnet foo $CID
$ sudo docker network disconnect foo $CID
This makes a HTTP POST call on ``/NetworkDriver.Leave`` with the following
JSON data.
@ -397,11 +397,11 @@ Notes on implementing the libnetwork remote driver API in Kuryr
---------------------------------------------------------------
1. DiscoverNew Notification:
Neutron does not use the informaton related to discovery of new resources such
Neutron does not use the information related to discovery of new resources such
as new nodes and therefore the implementation of this API method does nothing.
2. DiscoverDelete Notification:
Neutron does not use the informaton related to discovery of resources such as
Neutron does not use the information related to discovery of resources such as
nodes being deleted and therefore the implementation of this API method does
nothing.

2
doc/source/specs/mitaka/index.rst
View File

@ -20,7 +20,7 @@
(Avoid deeper levels because they do not render well.)
Mitaka Sepcifications
Mitaka Specifications
=====================
This section contains detailed specification documents for

4
doc/source/specs/mitaka/kuryr_k8s_integration.rst
View File

@ -207,7 +207,7 @@ Service Discovery
Service discovery should be supported via environment variables.
Kubernetes also offers a DNS cluster add-on to support application services name
resolution. It uses SkyDNS with helper container, kube2sky to bridge between
kubernetes to SkyDNS and etcd to maintain services registry.
kubernetes to SkyDNS and etcd to maintain services registry.
Kubernetes Service DNS names can be resolved using standard methods inside the
pods (i.e. gethostbyname). DNS server runs as kubernetes service with assigned
static IP from the service cluster ip range. Both DNS server IP and domain are
@ -250,7 +250,7 @@ of the Pod, more accurately of the infrastructure container. Kuryr will provide
CNI Driver that implements [3]. In order to be able to configure and report an
IP configuration, the Kuryr CNI driver must be able to access IPAM to get IP
details for the Pod. The IP, port UUID, GW and port type details should be
available to the driver via **CNI_ARGS** in additon to the standard content::
available to the driver via **CNI_ARGS** in addition to the standard content::
CNI_ARGS=K8S_POD_NAMESPACE=default;\
K8S_POD_NAME=nginx-app-722l8;\

2
doc/source/specs/mitaka/nested_containers.rst
View File

@ -386,7 +386,7 @@ Kuryr Agent running inside Nova instances will communicate with OpenStack APIs.
happen, credentials will have to be stored inside Nova instances hosting Bays.
This arrangement poses a security threat that credentials might be compromised and there
could be ways malacious containers could get access to credentials or Kuryr Agent.
could be ways malicious containers could get access to credentials or Kuryr Agent.
To mitigate the impact, there are multiple options:
1. Run Kuryr Agent in two modes: primary and secondary. Only primary mode has access to the