a62d6bac63
Magnum documentation updated to reflect current usage. Cleanups for syntax and readability applied as needed. DocImpact Closes-Bug: #1472029 Change-Id: If3d8660e6763083544529f469be02eec73e9fd0c
3.2 KiB
Welcome to Magnum's Developer Documentation!
Magnum is an OpenStack project which offers container orchestration engines for deploying and managing containers as first class resources in OpenStack.
- Free software: under the Apache license
- Source: http://git.openstack.org/cgit/openstack/magnum
- Blueprints: https://blueprints.launchpad.net/magnum
- Bugs: http://bugs.launchpad.net/magnum
- ReST Client: http://git.openstack.org/cgit/openstack/python-magnumclient
Architecture
There are several 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 resources 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 may be directly contacted via the Kubernetes ReST API. When container objects are acted upon, the Docker ReST API may be directly contacted.
Features
- Abstractions for bays, containers, nodes, pods, replication controllers, and services
- Integration with Kubernetes and Docker for backend container technology
- Integration with Keystone for multi-tenant security
- Integration with Neutron for Kubernetes multi-tenancy network security
Developer Info
dev/dev-quickstart dev/dev-manual-devstack contributing