@ -25,7 +25,7 @@ for deploying and managing containers as first class resources in OpenStack.
* * *Source:* * http://git.openstack.org/cgit/openstack/magnum
* * *Blueprints:* * https://blueprints.launchpad.net/magnum
* * *Bugs:* * http://bugs.launchpad.net/magnum
* * *Re ST Client:* * http://git.openstack.org/cgit/openstack/python-magnumclient
* * *RE ST Client:* * http://git.openstack.org/cgit/openstack/python-magnumclient
Architecture
============
@ -45,20 +45,20 @@ There are several different types of objects in the magnum system:
* * *Container:* * A Docker container
Two binaries work together to compose the magnum system. The first binary
(accessed by the python-magnumclient code) is the magnum-api Re ST server. The
ReST server may run as one process or multiple processes. When a Re ST request
(accessed by the python-magnumclient code) is the magnum-api RE ST server. The
REST server may run as one process or multiple processes. When a RE ST request
is sent to the client API, the request is sent via AMQP to the
magnum-conductor process. The Re ST server is horizontally scalable. At this
magnum-conductor process. The RE ST server is horizontally scalable. At this
time, the conductor is limited to one process, but we intend to add horizontal
scalability to the conductor as well.
The magnum-conductor process runs on a controller machine and connects to a
Kubernetes or Docker ReST API endpoint. The Kubernetes and Docker Re ST API
Kubernetes or Docker REST API endpoint. The Kubernetes and Docker RE ST API
endpoints are managed by the bay object.
When service or pod objects are created, Kubernetes may be directly contacted
via the Kubernetes Re ST API. When container objects are acted upon, the
Docker Re ST API may be directly contacted.
via the Kubernetes RE ST API. When container objects are acted upon, the
Docker RE ST API may be directly contacted.
Features
========