openstack/magnum
Code Issues Proposed changes
Container Infrastructure Management Service for OpenStack
659 Commits 7 Branches 57 Tags 94 MiB
Python 72.9%
Shell 26.8%
Dockerfile 0.3%
4c2b973859
Go to file
Davanum Srinivas 4c2b973859 Convert to new DevStack plugin model for functional testing 
Switch over to the new plugin style as documented here:
http://docs.openstack.org/developer/devstack/plugins.html

Makes it very easy to setup a CI job. Added a new
directory for functional job and the tests are run
from the post_test_hook.sh. There's even a "magnum bay-list"
in the shell script to show that we are actually making
calls to the magnum API endpoint and things are working
fine. Note that this is just the minimal plumbing needed
and there's a lot more effort needed to come up with
proper test cases for testing magnum functionality.

Closes-Bug: #1439621
Change-Id: I88d45015338ef55713b32de196f9071c8fc2031b
2015-04-02 21:14:20 -04:00
contrib/devstack Convert to new DevStack plugin model for functional testing 2015-04-02 21:14:20 -04:00
devstack Convert to new DevStack plugin model for functional testing 2015-04-02 21:14:20 -04:00
doc/source Fix some typos in magnum document 2015-03-31 21:23:14 +08:00
etc/magnum Support keystone regions 2015-03-26 22:28:46 +01:00
magnum Convert to new DevStack plugin model for functional testing 2015-04-02 21:14:20 -04:00
specs Add a spce between the words of feature and set in the spec file 2015-03-25 15:10:43 +00: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 Modify gitignore to ignore cover 2014-11-20 23:27:20 +09: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
babel.cfg Initial commit from github (squashed) 2014-11-18 09:23:37 -05: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 Correct doc format 2015-02-28 07:06:18 +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
openstack-common.conf Sync with latest oslo-incubator 2015-03-21 00:05:52 +00:00
README.rst Update magnum document to use openstack as namespace 2015-03-28 20:14:42 +08:00
requirements.txt Add Heat tasks 2015-03-09 08:14:17 +09:00
setup.cfg Rename backend to conductor 2014-12-11 16:51:08 -07:00
setup.py Sync from oslo requirements 2015-01-14 08:29:17 +08:00
test-requirements.txt Requirements List Updates 2015-03-04 07:00:17 +00:00
tox.ini Cleanup code and remove newly ignored hack rules 2015-02-06 22:40:23 -05: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