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.
Jenkins 255428cc8e Merge "Make rc_create return 400 with invalid json manifest" 4 years ago
doc/source Merge "Fix doc typo and make style consistent" 4 years ago
etc/magnum Move folder heat-kubernetes to magnum/templates 4 years ago
magnum Merge "Make rc_create return 400 with invalid json manifest" 4 years ago
specs Fix the typo in specs 4 years ago
.coveragerc Initial commit from github (squashed) 4 years ago
.gitignore Modify gitignore to ignore cover 4 years ago
.gitreview Added .gitreview 4 years ago
.mailmap Initial commit from github (squashed) 4 years ago
.testr.conf Look for tests only under magnum/tests directory 4 years ago
CONTRIBUTING.rst Workflow documentation is now in infra-manual 4 years ago
Dockerfile Fix dockerfile comment containing unrecognized argument 'host' 4 years ago
HACKING.rst Correct doc format 4 years ago
LICENSE Initial commit from github (squashed) 4 years ago
MANIFEST.in Copy Ironic's database model codebase 4 years ago
README.rst Change link of quick start to git.openstack.org 4 years ago
babel.cfg Initial commit from github (squashed) 4 years ago
openstack-common.conf Fix typo in openstack-common 4 years ago
requirements.txt Add Heat tasks 4 years ago
setup.cfg Rename backend to conductor 4 years ago
setup.py Sync from oslo requirements 4 years ago
test-requirements.txt Requirements List Updates 4 years ago
tox.ini Cleanup code and remove newly ignored hack rules 4 years ago

README.rst

Magnum

new Openstack project for containers.

Architecture

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-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.

Features

  • 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