|Jenkins 2c36791bbf Merge "Devstack is broken with heat/juno branch"||4 years ago|
|doc/source||4 years ago|
|etc/magnum||4 years ago|
|magnum||4 years ago|
|specs||4 years ago|
|.coveragerc||4 years ago|
|.gitignore||4 years ago|
|.gitreview||4 years ago|
|.mailmap||4 years ago|
|.testr.conf||4 years ago|
|CONTRIBUTING.rst||4 years ago|
|Dockerfile||4 years ago|
|HACKING.rst||4 years ago|
|LICENSE||4 years ago|
|MANIFEST.in||4 years ago|
|README.rst||4 years ago|
|babel.cfg||4 years ago|
|openstack-common.conf||4 years ago|
|requirements.txt||4 years ago|
|setup.cfg||4 years ago|
|setup.py||4 years ago|
|test-requirements.txt||4 years ago|
|tox.ini||4 years ago|
new Openstack project for containers.
There are seven different types of objects in the Magnum system:
Two binaries work together to compose the Magnum system. The first binary accessed by the python-magnumclient code is the magnum-api ReST server. The ReST server may run as one process or multiple processes. When a ReST request is sent to the client API, the request is sent via AMQP to the magnum-conductor process. The ReST 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-backend process runs on a controller machine and connects to a kubernetes or docker ReST API endpoint. The kubernetes and docker ReST API endpoints are managed by the bay object.
When service or pod objects are created, Kubernetes is directly contacted via the k8s ReST API. When container objects are acted upon, the docker ReST API is directly contacted.