Container Infrastructure Management Service for OpenStack
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Kai Qiang Wu(Kennan) c99dd870df
Fix unit test failure
8 years ago
contrib/templates/example Add Template Definitions 8 years ago
devstack Merge "Swith auth_uri to use v2.0" 8 years ago
doc/source 'nose' is no longer required for testing Magnum 8 years ago
etc/magnum Add periodic task framework 8 years ago
magnum Fix unit test failure 8 years ago
specs Web Interface for Magnum in Horizon 8 years ago
tools Convert to new DevStack plugin model for functional testing 8 years ago
.coveragerc Initial commit from github (squashed) 8 years ago
.gitignore add .idea to .gitignore 8 years ago
.gitreview Update .gitreview for project rename 8 years ago
.mailmap Initial commit from github (squashed) 8 years ago
.testr.conf Make room for functional tests 8 years ago
CONTRIBUTING.rst Workflow documentation is now in infra-manual 8 years ago
Dockerfile Fix the docker build image issue 8 years ago
HACKING.rst Correct Hacking rule code 8 years ago
LICENSE Initial commit from github (squashed) 8 years ago Copy Ironic's database model codebase 8 years ago
README.rst Update magnum document to use openstack as namespace 8 years ago
babel.cfg Initial commit from github (squashed) 8 years ago
bandit.yaml Add Bandit security lint checking via tox 8 years ago
functional_creds.conf.sample Make functional test work with new tox env 8 years ago
openstack-common.conf port to oslo.service 8 years ago
requirements.txt Updated from global requirements 8 years ago
setup.cfg Add Swarm TemplateDefinition 8 years ago Updated from global requirements 8 years ago
test-requirements-bandit.txt Update bandit for new usage requirement 8 years ago
test-requirements.txt 'nose' is no longer required for testing Magnum 8 years ago
tox.ini port to oslo.service 8 years ago



new Openstack project for containers.


There are seven different types of objects in the Magnum system:

  • Bay: A collection of node objects where work is scheduled
  • BayModel: An object stores template information about the bay which is used to create new bays consistently
  • Node: A baremetal or virtual machine where work executes
  • Pod: A collection of containers running on one physical or virtual machine
  • Service: An abstraction which defines a logical set of pods and a policy by which to access them
  • ReplicationController: An abstraction for managing a group of PODs to ensure a specified number of PODs are running
  • 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 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-conductor 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.


  • Abstractions for bays, containers, nodes, pods, and services
  • Integration with Kubernetes and Docker for backend container technology.
  • Integration with Keystone for multi-tenant security.
  • Integration with Neutron for k8s multi-tenancy network security.

Installation and Usage