Container Infrastructure Management Service for OpenStack
You cannot 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
Hongbin Lu e54428845b Add tests for Pod and Service on dbapi
Did the following fix/modification to make the tests pass:
* Raise an exception on deleting non-existent pod or service.
* Rename the following methods:
  get_service_by_bay_uuid -> get_services_by_bay_uuid (db)
  get_by_bay_uuid -> list_by_bay_uuid (objects)

Change-Id: I7cbeb119550acecdbf0697df19172a8285eabca8
9 years ago
doc/source fix the wrong order of steps and missing password in db connection 9 years ago
etc/magnum Added Magnum Configuration file 9 years ago
magnum Add tests for Pod and Service on dbapi 9 years ago
specs Added multi-region/multi-cloud use case to specs 9 years ago
.coveragerc Initial commit from github (squashed) 9 years ago
.gitignore Modify gitignore to ignore cover 9 years ago
.gitreview Added .gitreview 9 years ago
.mailmap Initial commit from github (squashed) 9 years ago
.testr.conf Look for tests only under magnum/tests directory 9 years ago
CONTRIBUTING.rst Workflow documentation is now in infra-manual 9 years ago
Dockerfile Fix dockerfile comment containing unrecognized argument 'host' 9 years ago
HACKING.rst Initial commit from github (squashed) 9 years ago
LICENSE Initial commit from github (squashed) 9 years ago Copy Ironic's database model codebase 9 years ago
README.rst Add BayModel to magnum README 9 years ago
babel.cfg Initial commit from github (squashed) 9 years ago
openstack-common.conf Migrate to oslo.context 9 years ago
requirements.txt Migrate to oslo.context 9 years ago
setup.cfg Rename backend to conductor 9 years ago Initial commit from github (squashed) 9 years ago
test-requirements.txt Initial commit from github (squashed) 9 years ago
tox.ini Enable automatic sample config generation 9 years ago



new Openstack project for containers.


There are six 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
  • 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-backend process. The ReST server is horizontally scalable. AT this time, the backend is limited to one process, but we intend to add horizontal scalability to the backend 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.


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

Installation and Usage

  • Getting Started Guides: [doc/source/dev/dev-quickstart.rst](doc/source/dev/dev-quickstart.rst)