The updated API include the following: 1) get_bay_by_id 2) get_baymodel_by_id 3) get_node_by_id 4) get_container_by_id Implements part of bp multi-tenant Change-Id: I7d2f8b7ea361b38d6f0110772c10f93037c7aefb
|8 years ago|
|doc/source||8 years ago|
|etc/magnum||8 years ago|
|magnum||8 years ago|
|specs||8 years ago|
|.coveragerc||9 years ago|
|.gitignore||9 years ago|
|.gitreview||9 years ago|
|.mailmap||9 years ago|
|.testr.conf||9 years ago|
|CONTRIBUTING.rst||9 years ago|
|Dockerfile||9 years ago|
|HACKING.rst||9 years ago|
|LICENSE||9 years ago|
|MANIFEST.in||9 years ago|
|README.rst||8 years ago|
|babel.cfg||9 years ago|
|openstack-common.conf||9 years ago|
|requirements.txt||8 years ago|
|setup.cfg||9 years ago|
|setup.py||8 years ago|
|test-requirements.txt||8 years ago|
|tox.ini||9 years ago|
new Openstack project for containers.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/magnum
- Source: http://git.openstack.org/cgit/stackforge/magnum
- Bugs: http://bugs.launchpad.net/magnum
- ReST Client: http://git.openstack.org/cgit/stackforge/python-magnumclient
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.
- 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
- Getting Started Guides: https://github.com/stackforge/magnum/blob/master/doc/source/dev/dev-quickstart.rst