openstack
/
magnum
Code Issues Proposed changes
Container Infrastructure Management Service for OpenStack
613 Commits 6 Branches 52 Tags 94 MiB
Python 73%
Shell 26.7%
Dockerfile 0.3%
Go to file
Steven Dake e6e86f7163 Merge heat-kubernetes pull request 14 
Pull request 14 changes the start order of Kubernetes.  The master
now starts first, and the minion starts after the master completes.

This prevents flanneld in the minions from timing out and failing to
start the kubernetes services on the minions.

See:
https://github.com/larsks/heat-kubernetes/pull/14/

Change-Id: Ia823fd3593dc7c5d9d9c6327e009b833ad586a5c
Closes-bug: #1434468
 		2015-03-22 16:47:28 -07:00
contrib/devstack Removing duplicate service definition 2015-03-21 00:39:06 +00:00
doc/source Update quickstart doc 2015-03-19 15:50:14 +00:00
etc/magnum Allow specification of ssh authorized key and token url for coreos. 2015-03-16 09:31:38 +05:30
magnum Merge heat-kubernetes pull request 14 2015-03-22 16:47:28 -07:00
specs Fix typos in magnum/specs/containers-service.rst 2015-03-18 11:34:42 +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 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
README.rst Fix a small architectural error 2015-03-21 00:16:55 -07:00
babel.cfg Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
openstack-common.conf Sync with latest oslo-incubator 2015-03-21 00:05:52 +00: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