openstack
/
magnum
Code Issues Proposed changes
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.
412 Commits
7 Branches
37 Tags
88 MiB
Python 79.3%
Shell 20.4%
Dockerfile 0.3%
 
 
 
stable/zed
master
stable/2023.1
stable/wallaby
stable/xena
stable/yoga
stable/victoria
xena-em
13.1.1
16.0.0
16.0.0.0rc1
15.0.1
14.1.0
13.1.0
ussuri-eol
train-eol
stein-eol
rocky-eol
queens-eol
wallaby-em
15.0.0
15.0.0.0rc2
15.0.0.0rc1
pike-eol
12.1.1
victoria-em
14.0.0
14.0.0.0rc2
14.0.0.0rc1
11.2.1
12.1.0
11.2.0
ussuri-em
13.0.0
13.0.0.0rc1
ocata-eol
train-em
11.1.1
10.1.0
12.0.0
11.1.0
12.0.0.0rc2
12.0.0.0rc1
9.4.1
stein-em
11.0.0
11.0.0.0rc1
8.2.1
9.4.0
10.0.0
10.0.0.0rc2
10.0.0.0rc1
9.3.0
rocky-em
9.2.0
7.2.0
8.2.0
9.1.0
queens-em
9.0.0
9.0.0.0rc2
8.1.0
9.0.0.0rc1
pike-em
5.0.2
ocata-em
8.0.0
8.0.0.0rc2
8.0.0.0rc1
7.1.0
6.3.0
7.0.2
6.2.0
7.0.1
7.0.0
6.1.1
6.1.0
6.0.1
6.0.0
newton-eol
4.1.4
5.0.1
5.0.0
3.3.1
4.1.3
3.3.0
mitaka-eol
4.1.2
2.1.0
3.2.0
4.1.1
4.1.0
4.0.0
liberty-eol
3.1.1
3.1.0
3.0.0
kilo-eol
2.0.0
1.1.0
1.0.0.0b1
2015.1.0
2015.1.0b2
m1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd321980cb4'
${ noResults }
Go to file
Jay Lau (Guangya Liu) d321980cb4 Enable bay delete support multi tenant 
Implementes part of bp multi-tenant

Change-Id: I4eb26adabc34f8f359539cbd41cc2cda070db878
 		8 years ago
doc/source Point to proper quickstart guide in index.rst 8 years ago
etc/magnum Update the conf sample file 8 years ago
magnum Enable bay delete support multi tenant 8 years ago
specs Fix the typo in specs 8 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
MANIFEST.in Copy Ironic's database model codebase 9 years ago
README.rst Add a link for "Getting Started Guides" 8 years ago
babel.cfg Initial commit from github (squashed) 9 years ago
openstack-common.conf Migrate to oslo.context 9 years ago
requirements.txt Sync from oslo requirements 9 years ago
setup.cfg Rename backend to conductor 9 years ago
setup.py Sync from oslo requirements 9 years ago
test-requirements.txt Sync from oslo requirements 9 years ago
tox.ini Add unit tests for dbapi of Node and Container 9 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