openstack
/
magnum
Code Issues Proposed changes
Container Infrastructure Management Service for OpenStack
196 Commits 6 Branches 52 Tags 94 MiB
Python 73%
Shell 26.7%
Dockerfile 0.3%
Go to file
Jenkins 66047a39d6 Merge "Add hooks to obtain conductor api" 2014-12-30 16:28:55 +00:00
doc/source fix the wrong order of steps and missing password in db connection 2014-12-23 14:39:02 +08:00
etc/magnum Added Magnum Configuration file 2014-11-24 22:47:32 +05:30
magnum Merge "Add hooks to obtain conductor api" 2014-12-30 16:28:55 +00:00
specs Containers Service Spec 2014-11-20 19:28:10 +00:00
.coveragerc Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
.gitignore Modify gitignore to ignore cover 2014-11-20 23:27:20 +09:00
.gitreview Added .gitreview 2014-11-07 10:08:48 +00:00
.mailmap Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
.testr.conf Look for tests only under magnum/tests directory 2014-12-04 00:16:09 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:45 +00:00
Dockerfile Fix dockerfile comment containing unrecognized argument 'host' 2014-12-01 15:41:29 +01:00
HACKING.rst Initial commit from github (squashed) 2014-11-18 09:23:37 -05: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 Add a hyper-link for quick start 2014-12-22 04:36:15 -05:00
babel.cfg Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
openstack-common.conf Migrate to oslo.context 2014-12-14 16:38:34 +05:30
requirements.txt Migrate to oslo.context 2014-12-14 16:38:34 +05:30
setup.cfg Rename backend to conductor 2014-12-11 16:51:08 -07:00
setup.py Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
test-requirements.txt Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
tox.ini Enable automatic sample config generation 2014-11-24 12:34:07 -08:00

README.rst

Magnum

new Openstack project for containers.

Architecture

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

  • Bay: A collection of node objects where work is scheduled
  • Node: A baremetal or virtual machine where work executes
  • Pod: A collection of containers running on one physical or virtual machine
  • Service: A port to Pod mapping
  • 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.

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