openstack
/
magnum
Code Issues Proposed changes

Fix a small architectural error 

Originally magnum-conductor was called magnum-backend, but was renamed.
Apparently the documentation didn't get completely modified.

Change-Id: I369a21b4b05192ea16171f53089c5220bd5c8ef5
This commit is contained in:
Steven Dake 2015-03-21 00:15:44 -07:00
parent 7d02f45c90
commit ed10176aa4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -31,7 +31,7 @@ process. The ReST server is horizontally scalable. At this time, the
conductor is limited to one process, but we intend to add horizontal conductor is limited to one process, but we intend to add horizontal
scalability to the conductor as well. scalability to the conductor as well.
The magnum-backend process runs on a controller machine and connects to a The magnum-conductor process runs on a controller machine and connects to a
kubernetes or docker ReST API endpoint. The kubernetes and docker ReST API kubernetes or docker ReST API endpoint. The kubernetes and docker ReST API
endpoints are managed by the bay object. endpoints are managed by the bay object.