Container Infrastructure Management Service for OpenStack
Go to file
OpenStack Proposal Bot eb7abda967 Updated from global requirements
Change-Id: Ife58c75075f659a658c53dbf08398294afa611f8
2015-07-01 14:13:23 +00:00
contrib/templates/example Add Template Definitions 2015-04-09 08:47:15 -07:00
devstack Devstack: Add admin creds in magnum.conf 2015-06-29 08:50:29 +08:00
doc/source Merge "Not need to use bay uuid" 2015-06-25 13:09:53 +00:00
etc/magnum Merge "policy check for node" 2015-07-01 01:09:02 +00:00
magnum Merge "Backport "configure docker storage correctly"" 2015-07-01 01:13:40 +00:00
specs Web Interface for Magnum in Horizon 2015-06-18 10:13:01 +01:00
tools Convert to new DevStack plugin model for functional testing 2015-04-02 21:14:20 -04:00
.coveragerc Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
.gitignore Add coe attribute to BayModel 2015-04-27 21:10:57 -05:00
.gitreview Update .gitreview for project rename 2015-03-28 00:20:40 +00:00
.mailmap Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
.testr.conf Make room for functional tests 2015-04-02 12:25:43 -04:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:45 +00:00
Dockerfile Fix the docker build image issue 2015-05-18 11:11:25 +08:00
HACKING.rst Correct Hacking rule code 2015-06-17 14:14:25 +08:00
LICENSE Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
MANIFEST.in Copy Ironic's database model codebase 2014-12-02 15:04:31 -07:00
README.rst Update magnum document to use openstack as namespace 2015-03-28 20:14:42 +08:00
babel.cfg Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
bandit.yaml Add Bandit security lint checking via tox 2015-04-08 10:41:42 -07:00
functional_creds.conf.sample Make functional test work with new tox env 2015-05-19 11:07:34 +08:00
openstack-common.conf port to oslo.service 2015-06-28 14:29:00 +08:00
requirements.txt Updated from global requirements 2015-07-01 14:13:23 +00:00
setup.cfg Add Swarm TemplateDefinition 2015-04-17 12:19:27 -07:00
setup.py Updated from global requirements 2015-06-22 08:21:50 +00:00
test-requirements-bandit.txt Update bandit for new usage requirement 2015-04-10 11:19:17 +08:00
test-requirements.txt Updated from global requirements 2015-07-01 14:13:23 +00:00
tox.ini port to oslo.service 2015-06-28 14:29:00 +08:00

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

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